VMware Communities
Joffenb
Contributor
Contributor

Windows 7 Host bridging - A Temporary Solution till VMWare fixes.

After grumbling and cussing and researching on the problem with Windows 7 RTM as a host for VMWare Workstation (ver 6.5.2) and internet access, I finally have the system working (after a few gotchas).

The following is a step by step procedure that should let the normal user utilize Windows 7 as a host for VMWare Workstation (works on 6.5.2 - untested with other versions) who is connected to the internet via a normal router (computer uses a private IP e.g. 192.168.1.100).

On the host computer, reconfigure your network as a Work network rather than a Home group. Home group requires IPV6 to communicate and the virtual portion of VMWare does not support IPv6. (found this out after getting all else to work and then not being able to connect to internet from host - virtuals worked fine.) To do this, click start --> Network and Select Network and Sharing Center. In the middle of the screen under your active network, you probably see Home Group. Double click it and change the location to Work network.

  1. Set your internet connecting network with a static IPv4 address outside the range of your router's DHCP and manually set up your provider's DNS. With the Linksys, DHCP uses 192.168.1.100-149, so I set IP to 192.168.1.99 with a gateway of 192.168.1.1 and netmask of 255.255.255.0. You can check gateway, netmask and DNS servers with an "ipconfig /all" from a cmd prompt.

  2. Open VMWare and click "edit" then Virtual network editor. Click the Host Virtual Adapters tab and remove all that are present. Click Apply. When all are empty, click "Add..." and use VMnet2. You should see a "Local Area Connection X" appear. Click the Host Virtual Network Mapping tab and click the right arrow to the Right of the VMNet2 line and select Subnet. Set the subnet equal to the subnet of your router. (in my case it's 192.168.1.0 and 255.255.255.0). Click Apply. Click the same right arrow again and select DHCP. Set the Start IP address and End IP address to a range outside that of your router and not including the static IP you set your internet access NIC to. I used 192.168.1.150 and 192.168.1.200. You can change the lease times, but I left them at the default. Click OK and Apply. Click the DHCP tab and insure that DHCP is started. If not, start it and click Apply. Click the NAT tab and select disable and stop the service. Click Apply.

  3. On the host computer, do a start --> Network and Select Network and Sharing Center. Click the "Change adapter settings" in the left pane. You should see at least two items. The NIC you normally use to connect to the internet with, and the VMWare Virtual Adapter. Highlight one, then hold the control key while highlighting the other. Right click and select "Bridge" Your host machine is now set up to just use IPv4 and should bridge the VMWare adapter and your internet NIC correctly. (Well, maybe not correctly, but with a static IP, it will work.) Now on to the virtual machines.

  4. On each virtual machine, devices tab, double click the "Network Adapter" line. Highlight the radio button on the "Custom" line and select VMnet2. Click OK and the virtual machine should start, get it's IP from VMWare's DHCP, and bridge through the host machine to the internet. (At least it's working for me.)

The above should work, however, if you're running additional 3rd Party firewall software, you may need additional changes. If so, recommend you disable them till you get VM working, then re-enable and adjust configurations till you get all working.

Let me know if anyone has problems with this. Just got it working and think the above should be complete enough to follow...

Reply
0 Kudos
6 Replies
raul761
Contributor
Contributor

Thanks for the info.

Not sure though from post which VM network mode you have problems with ?

In my case VM bridged networking works just fine without needing any changes (Win 7 RTM 32bit + Workstation 6.5.2)

NAT is the problem one and for that i found another way that depending on your needs might be easier especially if you use your computer on different networks.

See this link for details : http://www.archy.net/2009/08/10/vmware-workstation-nat-problem-on-windows-7-rtm/

Basically it uses a private ICS (internet connection sharing) IP subnet thru the host IP and can hence easily be used in various networks without having to change Ip ranges or such (host can be DHCP and does not need to be static).

The only catch is that if you use different adapters (wired vs wireless) you need to enable ICS on whatever one is live at the moment. This is a pretty simple though as ICS is just a checkbox on network adapter properties page.

Hope this helps somebody

Raul

Reply
0 Kudos
Joffenb
Contributor
Contributor

Had found your solution, tried it, and couldn't get it to work correctly. (Not sure exactly why...) I think the problem was that packets wouldn't route from the Host Physical NIC to internet, but this could have been caused by the fact that the NIC was not getting a default gateway from the Linksys router. That's why I eventually went to static IP. Was basically using a standard bridged setup, but the Win 7 is an upgrade from Vista which was an upgrade from XP. This might have been the problem. Still don't understand why M$oft decided to require IPv6 for a Home Group... haven't seen any homes that run out of IPv4 addresses yet...

Reply
0 Kudos
raul761
Contributor
Contributor

> Still don't understand

why M$oft decided to require IPv6 for a Home Group... haven't seen any

homes that run out of IPv4 addresses yet...

Don't know either but i can just see lot of people getting a recommendation to purchase a new router since old one has "networking problems" with Windows 7

Raul

Reply
0 Kudos
Joffenb
Contributor
Contributor

Additional compatibility info:

After discovering that "Home Group" requires IPv6 and only communicates with Windows 7, set up and played with a copy of Windows 7 Home Basic in a vm and found that "Home Group" is not a requirement. The "work group" option is available in Windows 7 Home Basic, so the original solution should work for Home, Pro, and Ultimate versions of Windows 7. I was afraid that M$oft had made "Home Group" a requirement for home versions, but they didn't.

Reply
0 Kudos
edgrigson
Enthusiast
Enthusiast

It probably wasn't their choice - the government require any product they use to have IPv6 nowadays, and as Microsoft want them to use Windows 7 its a foregone conclusion.That's why things like ESX have IPv6 too - it's not customer demand!

Ed

Reply
0 Kudos
Axky
Contributor
Contributor

Thank you very much, this works for me!

Reply
0 Kudos