+ Post New Thread
Results 1 to 7 of 7
Thin Client and Virtual Machines Thread, Connecting Two VMware Workstation Hosts in Technical; I started out using VMware Workstation 7.x on one host and everything was working great - created a virtual Windows ...
  1. #1

    Join Date
    Jan 2011
    Posts
    2
    Thank Post
    4
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Connecting Two VMware Workstation Hosts

    I started out using VMware Workstation 7.x on one host and everything was working great - created a virtual Windows 2008 DC, Exchange 2007 server, and various other servers. However, this test environment maxed out the RAM of my single VMware Workstation. Now I need to split the VM's between two VMware Workstations. I built two Windows 7 hosts, loaded VMware Workstation on both, and can't figure out how to connect vmwarelab1 host's VM's (192.168.142.x) to vmwarelab2 host's VM's. I know I need to somehow route between the two host PC's networks, but I am not sure how to accomplish this. I've seen some "linux floppy based routers" out there, but I don't know how to use those.

    Any help would be appreciated. Thanks in advance.

  2. #2

    SpuffMonkey's Avatar
    Join Date
    Jul 2005
    Posts
    2,259
    Thank Post
    55
    Thanked 283 Times in 189 Posts
    Rep Power
    135
    Wouldn't it be easier to stuff a PC full of RAM and install ESXi on it, copy the vm's over - and run them all from that?

  3. Thanks to SpuffMonkey from:

    davidmcgill (6th January 2011)

  4. #3
    Duke's Avatar
    Join Date
    May 2009
    Posts
    1,017
    Thank Post
    300
    Thanked 174 Times in 160 Posts
    Rep Power
    58
    I'm not sure I've 100% understood your problem and it's been a while since I've used the 'hosted' VMware stuff rather than bare-metal ESX/ESXi, but I'll throw this in:

    Make sure both hosts are running on the same IP range and subnet. Connect both PCs together via a cheap switch and make sure they can talk to each other (ping, view file shares) at the Windows level first. In VMware Workstation, make sure the virtual NICs are correctly configured to use the right physical NICs on the hosts. Make sure your virtual machines are configured to use the right virtual NIC, and assign the VMs IP addresses on the same IP range and subnet as both hosts. In theory, that's it, the VMs should now be able to ping/connect to each other.

    Chris

  5. Thanks to Duke from:

    davidmcgill (6th January 2011)

  6. #4
    Butuz's Avatar
    Join Date
    Feb 2007
    Location
    Wales, UK
    Posts
    1,579
    Thank Post
    211
    Thanked 220 Times in 176 Posts
    Rep Power
    63
    Sorry cant help as have never used VMWare Workstation

    Quote Originally Posted by SpuffMonkey View Post
    Wouldn't it be easier to stuff a PC full of RAM and install ESXi on it, copy the vm's over - and run them all from that?
    Agree with that. Why use VMWare workstation to test things when you won't (I hope) be using it in production?? Grab a bog standard PC, chuck 8/16GB RAM in it put in the bootable ESXi CD and go for it!!

    Butuz

  7. #5

    Join Date
    Sep 2006
    Location
    West Midlands
    Posts
    410
    Thank Post
    73
    Thanked 75 Times in 58 Posts
    Rep Power
    44
    Assuming that the various "virtual servers" have fixed IP addresses that are unique and valid on your network, you should be able to change their network adapters (under VM Workstation in the Virtual Machine Settings for each server) to be "Bridged" rather than "Host-only". That way they will appear on your "live" network just like any other (physical) machine.

    At least that is how i think that it is supposed to work

    mb

  8. Thanks to Martin from:

    davidmcgill (6th January 2011)

  9. #6
    Butuz's Avatar
    Join Date
    Feb 2007
    Location
    Wales, UK
    Posts
    1,579
    Thank Post
    211
    Thanked 220 Times in 176 Posts
    Rep Power
    63
    Be careful as if you introduce your test network onto your live network you may run into problems by having multiple networks/domain controllers/dhcp servers etc running on the same network.

    You'd be better off using a 4 port switch and connecting them that way I would guess?

    Butuz

  10. Thanks to Butuz from:

    davidmcgill (6th January 2011)

  11. #7

    Join Date
    Jan 2011
    Posts
    2
    Thank Post
    4
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Yes, thank you all for your assistance - I tried the bridged yesterday, and it picked up the DHCP address from the host servers' network - and that solution seems to be the best one at this point.

    For the other posts about adding more RAM and using ESX - I would do that, but this is for my office, testing out a solution, and you would think that as "tight" as they are, you'd get diamonds from coal and we'd be able to spend some money... In the short term, I am using crappy workstations with 4gb each. Working on getting ones with 8 or 16gb, but you know how hard it is to order stuff in an office... Maybe I can do ESX down the road. Again, thanks for all your suggestions.

    Dave

SHARE:
+ Post New Thread

Similar Threads

  1. VMWare Workstation
    By 01hanstu in forum Thin Client and Virtual Machines
    Replies: 1
    Last Post: 21st August 2010, 05:50 PM
  2. New to VMware workstation
    By andyturpie in forum Thin Client and Virtual Machines
    Replies: 9
    Last Post: 4th June 2010, 11:43 AM
  3. Vmware Hosts compatibility with new generation of Kit
    By ranj in forum Thin Client and Virtual Machines
    Replies: 3
    Last Post: 6th July 2009, 08:01 AM
  4. VMWare workstation 6?
    By PiqueABoo in forum Thin Client and Virtual Machines
    Replies: 1
    Last Post: 13th May 2007, 12:03 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •