Workstation 6.5 on Windows 7 Host

pjc007 · ‎11-12-2008

Hi,

so - I got the Windows 7 pre-beta 6801 build at the PDC, and I'm now testing all the stuff I normally use just to see how much works.

Well - VMWare sort-of works, but Bridged Networking doesn't.

On starting up a VM with Bridged Networking in VMWare 6.5 on Windows 7, VMNet0 fails to connect. Looking at 'Edit Network', I can't see any of my Network Interfaces as being valid for the bridge. Looking at the Network Interfaces themselves, they do have the VMWare Bridge Protocol on them, so that's a bit odd.

Has anybody else tried VMWare 6.5 running on Windows 7 as a host? If so, were you able to resolve the bridged ethernet issue?

Thanks in advance,

Paul.

onegeronimo · ‎11-17-2008

I am having the exact same problem. windows 7 6801 and xp pro guest

TheVMaster · ‎12-08-2008

I'm running the 6956 build and have the exact same problem. Will the problem be solved in a new VMWare Workstation version?

mdunn-vmware · ‎12-08-2008

Workstation 6.5.x doesn't currently work on a Win 7 host. I'm surprised you got a VM to power on, all other reports I've seen said that VMs won't even power on. We know about this problem and we're investigating it.

pjc007 · ‎12-08-2008

Thanks for the official reply - just FYI, I initially upgraded from Vista to 6801, found that VMNet0 didn't work, so uninstalled & reinstalled.

Again, VMNet0 didn't work, but in both cases everything else worked perfectly.

I don't have any later builds of Windows 7, so I can't test.

PJC

onegeronimo · ‎12-08-2008

Are you talking about the problem vmware won't power on or my problem vmware vmnet0 will not connect to the internet no matter what you do. I tried it with vista as a host too and its a no go ... What is the mystery. How come there is no ready solution? I am going in circles over this. All I can use vmware is to test malware with it. an expendable chopping block.

Date: Mon, 8 Dec 2008 16:02:38 -0800
From: communities-emailer@vmware.com
To: decker7961@msn.com
Subject: New message: "Workstation 6.5 on Windows 7 Host"
,
A new message was posted in the thread "Workstation 6.5 on Windows 7 Host":
http://communities.vmware.com/message/1118796#1118796
Author : mdunn-vmware
Profile : http://communities.vmware.com/people/mdunn-vmware
Message:

onegeronimo · ‎12-08-2008

But vmnet0 will not connect to the internet on vista... I am using vista again because of bugs in 6801. So the message says vmnet0 is not working and can not work at this time etc. etc. I have seen this problem posted all over the world.. what is the answer? I mean how can vmware expect people to buy this if it cant even connect to the internet.?? you know what I mean?

Date: Mon, 8 Dec 2008 16:07:21 -0800
From: communities-emailer@vmware.com
To: decker7961@msn.com
Subject: New message: "Workstation 6.5 on Windows 7 Host"
,
A new message was posted in the thread "Workstation 6.5 on Windows 7 Host":
http://communities.vmware.com/message/1118798#1118798
Author : pjc007
Profile : http://communities.vmware.com/people/pjc007
Message:

onegeronimo · ‎12-08-2008

But vmnet0 will not connect to the internet on vista... I am using vista again because of bugs in 6801. So the message says vmnet0 is not working and can not work at this time etc. etc. I have seen this problem posted all over the world.. what is the answer? I mean how can vmware expect people to buy this if it cant even connect to the internet.?? you know what I mean?

Date: Mon, 8 Dec 2008 16:07:21 -0800
From: communities-emailer@vmware.com
To: decker7961@msn.com
Subject: New message: "Workstation 6.5 on Windows 7 Host"
,
A new message was posted in the thread "Workstation 6.5 on Windows 7 Host":
http://communities.vmware.com/message/1118798#1118798
Author : pjc007
Profile : http://communities.vmware.com/people/pjc007
Message:

pjc007 · ‎12-08-2008

@onegeronimo - please don't hijack this discussion with your vista issues.

For the record, I have had absolutely NO problems with vmnet0 on Vista. The ONLY problem/issue I have is with vmnet0 not being 'discovered' as a valid network at all with Workstation 6.5 on Windows 7 6801.

-PJC

onegeronimo · ‎12-08-2008

Look I think I just realized you appear to not work for Vmware in some way.[http://gfx2.hotmail.com/mail/w3/ltr/emoticons/smile_wink.gif]

Date: Mon, 8 Dec 2008 16:52:12 -0800
From: communities-emailer@vmware.com
To: decker7961@msn.com
Subject: New message: "Workstation 6.5 on Windows 7 Host"
,
A new message was posted in the thread "Workstation 6.5 on Windows 7 Host":
http://communities.vmware.com/message/1118836#1118836
Author : pjc007
Profile : http://communities.vmware.com/people/pjc007
Message:

onegeronimo · ‎12-08-2008

I mean your trying to insult my intelligence right.[http://gfx2.hotmail.com/mail/w3/ltr/emoticons/smile_wink.gif]

Date: Mon, 8 Dec 2008 16:52:12 -0800
From: communities-emailer@vmware.com
To: decker7961@msn.com
Subject: New message: "Workstation 6.5 on Windows 7 Host"
,
A new message was posted in the thread "Workstation 6.5 on Windows 7 Host":
http://communities.vmware.com/message/1118836#1118836
Author : pjc007
Profile : http://communities.vmware.com/people/pjc007
Message:

ks13 · ‎12-19-2008

I'm in the same boat...Workstation works fine for me under Windows 7 build 6801, but no bridged networking!

In a way, glad to see it's not just me...been fighting with it and trying everything I could think of with no success.

michael_finocch · ‎03-20-2009

I am unable to get out of my VM images while running on a Windows 7 host. I have tried lots of stuff (re-installing VMnet1 and VMnet8, deleting VMnet8, using ICS on the host, the PowerShell trick for getting the adapters recognized by Windows 7 networking) but no dice. For the moment, Bridged doesn't get an address, NAT doesn't get an address, Host-only gets an address but cannot ping or surf outside of the VMware image.

The VMware adapters now show up as Enabled but only get Limited connectivity on IP V4 and IP V6. How do I get them to be fully enabled like my Wifi card. I noticed that in the properties of the adapter, the VMware Bridge Protocol was not enabled. Does this matter?

I can't possibly be the only geek that can't get this working. Or...

darco · ‎03-20-2009

I am able to run my vm w/bridge mode on my Win7 x64 (7057) host .....What I did was, run setup, chose repair, rebooted the host and now I have internet access on Win 7 7048 vm.

Previously I was getting an error that the network drivers were incompatiable and it said to reinstall vmware...also the vm image was "moved" from my Linux host if that matters.

good luck

darco

michael_finocch · ‎03-20-2009

Hmm, I am assuming you did a repair on the host machine right? Problem is that the system doesn't complain, it just doesn't allow the VMnet adapters access to the web and keeps them in limited state and this despite following the instructions provided elsewhere to exempt them from firewalling. There has got to be a good answer here - or perhaps a VMware Workstation 6.5.2 or 6.6 or 7.0 that works around this? It is a real showstopper for me. Don't have this issue under Leopard...

michael_finocch · ‎03-21-2009

I'll answer my own question: I'm an idiot. So here's the thing:

Follow the instructions here:

And ensure that, unlike me, you don't have two firewalls (Kaspersky and Windows Firewall) blocking the traffic out of the VM.

The

idea is to have one VMnet1 adapter running DHCP and to share with ICS

your adapter (Wifi in my case) to VMnet1. Then set all VMs to use

Host-Only networking and you are golden.

If you need access from outside the VM into the VM, use Port Forwarding in the Network Editor of VMware. Works like a charm

androidtopp · ‎05-13-2009

I have an interesting wrinkle on this.

I'm still running Windows 7 build 7000, along with Workstation 6.5.2 build 156735. I can power up and build VMs, just fine, but networking is goofy. This is only a laptop, so there's a bunch of different scenarios that happen:

Host wireless card connected

Bridged network gives me some jazz about having recieved a DHCP address that's already in use. It just sits and does nothing after that.
NAT sort of works. I get a DHCP address, and I can ping outbound, but browsing don't work, and I can't telnet to anything over port 80.

Host wired card connected

Bridged network gives works 100%. I have an IP address, and I can ping, browse, etc, etc.
NAT sort of works. I get a DHCP address, and I can ping outbound, but browsing doesn't work, and I can't telnet to anything over port 80.

Is anyone else experiencing this kind of halfway success with the networking? I unfortunately cannot always be wired, nor do I always want to bridge, so this isn't a very good solution for me. I should mention that my host and guest firewalls are 100% off. My host is experiencing zero issues with browsing, telnet, etc.

Thanks, Andrew

senojnai · ‎05-16-2009

I have a Windows 7 RC host with VMWare Workstation installed.

If you go into Computer Management -> Device Manager and select More Actions -> View -> Show Hidden Devices a new list of 'hardware' appears called "Non Plug-n-Play Drivers". In here there are two VMWare drivers with an exclamation mark against them, the details stating that "This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)", those drivers being "VMWare Bridge Protocol" and "VMWare Network Application Interface". This was following an upgrade from Vista to W7.

Prior to the upgrade, the installer of W7 warned of compatability issues with VMWare too.

As an earlier reply states, there are issues with these drivers that VMware people are looking into. I don't know about you but I'm waiting for a patch

Harti4ever · ‎05-18-2009

I did install a XP on my VMWARE under Windows 7, updated it and I never had any problems: I installed a USB network card (WN121) first, because this VMWARE should never have any connection to its host.

But when I tried to create new VMWares (and I tested an old image too): Ping works with host shared networking adapter, everything else not.

/Harti

timothyweaver · ‎07-20-2009

Check out this link to a Powershell script which fixes the problem for NAT'd VMs. Essentially, it sets a registry key which is necessary for Vista (and also Windows 7) that informs the Windows networking stack that the two VMnet interfaces (usually 1 and 8 for host only and NAT) are endpoint interfaces, meaning they don't need to be blocked or processed b the Windows firewall. Unfortunately, it does not fix the problem for bridged networking in VMs.

http://www.nivot.org/2008/09/05/VMWareVMNETAdaptersTriggeringPublicProfileForWindowsFirewall.aspx