VMware Communities
kriemer
Enthusiast
Enthusiast
Jump to solution

VMware Workstation 7 - guest can not connect to host computer

My problem is compounded by the fact that I have upgraded to VMware 7 and added several virtual Win7 64 virtual machines at the same time so I don't know what (or which) is causing the problem.

I have 2 host computers running WinXP 64 and VMware 7. Firewalls are off on all computers, real and virtual, and antivirus software disabled to facilitate debugging.

I can "see" Host A listed in my network of machines but I can not connect any virtual machine (Win XP 64 or Windows 7 64 ) to drives or folders in Host A. Virtual machines of all flavors in Host B (as can Host B itself) can connect to drives and folders in either Host A or B computers.

I am really confused as this is a new problem in a network that has otherwise worked without issue for a long time.

Thanks

k

Reply
0 Kudos
1 Solution

Accepted Solutions
Scissor
Virtuoso
Virtuoso
Jump to solution

Scissor

I was using AVG v8.5 antivirus. I have since uninstalled in an attempt to fix the issue.

AVG should be ok. Other AV's cause problems even if "disabled".

I will try disabling NIC "offload" settings next Monday (this is my wifes computer and I'm sure you can guess the rest).

Not to be pedantic, but you mention that this disabling would be temporary. What if this does fix the problem, what am I giving up by maintaining the settings?

You would be giving up a tiny fraction of a percent of CPU time because your Host processor would be calcuating packet checksums instead of the NIC adapter. Any difference would be unnoticable on a modern desktop computer.

If a newer NIC driver becomes available you can always try enabling it again to see if the newer driver fixes it. Same if a newer version of Workstation comes out.

View solution in original post

Reply
0 Kudos
33 Replies
kriemer
Enthusiast
Enthusiast
Jump to solution

No resolution but a little more detail.

It appears that the problem is only between Host A and VMware.It appears that the problem is only between Host A and VMware.

I can not connect from ANY VM on Host A to folders or drives on Host A; but I can connect to any other machines real or virtual on the network. As I said previously, I can connect to Host A from any other machine on the network. And any machine on the network can connect to any Host A virtual machine.

So far as I can see all the network setting of all the machines are the same. The only difference I can see is that Host B VMware was installed as 6.5 the upgraded to v7; while Host A only had VMware v7 installed.

Thanks again

Reply
0 Kudos
nicolap8
Contributor
Contributor
Jump to solution

I've a similar problem:

after upgrading to ws 7 none of the VMs are are able to connect to host when in bridged mode.

The host is Win Xp sp3, tried with variuos different guests.

When the ethernet is in NAT or Host only all works like expected.

But when in bridged the guest cant see the host (no ping, nothing) and the host cans see the guest.

The only problem is from Host to Guest, other pc in the net are working correctly with both host and guests.

kriemer
Enthusiast
Enthusiast
Jump to solution

I'm glad to see I'm not alone with my problem (I hate that).

I find that I have a similar problem with using any of the other

network settings. I can now see Host A but other computers on the

network can not connect to the virtual machine in Host A. The message

is I lack permission to access.

Do you have network setting that work?

The real curiosity is if this is a VMware 7 "feature" then why do I not have the same or similar problems from Host B?

Thanks for the response.

k

Reply
0 Kudos
kriemer
Enthusiast
Enthusiast
Jump to solution

This is definitely a problem/feature with VMware 7.

I uninstalled version 7 from Host A and installed version 6 and I was able to connect my virtual machines with the Host. I tried to reinstalled VMware 7 to see if it would still work but with no success, so I'm back to using VMware 6.5. Of course this means that I can not run my Win 7 machines.

Why this is occurring on one Host and not the other is beyond my understanding.

If anyone has a better idea or a real solution please let me know.

Regards

k

Reply
0 Kudos
Scissor
Virtuoso
Virtuoso
Jump to solution

Check to make sure you are running the latest drivers for your NIC card on your Host. Then try (temporarily) disabling any "task offload" or other "offload" setings for your Host's NIC card.

Reply
0 Kudos
scsiking
Enthusiast
Enthusiast
Jump to solution

Can you peer share from any other real xp machine on your network to a Windows 7 share on your host.

In otherwords, can you ignore VMware all together and just connect an XP real machine to any share on your Windows 7 box?

kriemer
Enthusiast
Enthusiast
Jump to solution

The only peer share that I can not make is virtual machines to their host. Host to VM's work, as as do VM's on other hosts.

Strange ! ?

Thanks

k

Reply
0 Kudos
kriemer
Enthusiast
Enthusiast
Jump to solution

Drivers are all the latest. How/where do I change NIC settings?

Many thanks

k

PS, I now notice this is exactly the same problem and subject of a Dec 1 posting. Sorry for starting a new thread.

Reply
0 Kudos
Scissor
Virtuoso
Virtuoso
Jump to solution

Drivers are all the latest. How/where do I change NIC settings?

From your Desktop... Right Click Computer -> Manage -> Device Manager -> Network adapters -> right-click on your Network Adapter, properties -> Advanced Tab

Look for entries that mention "offload". Each adapter will be different. For example, my Broadcom adapter has "Large Send Offload", "Proxy ARP offload", "Proxy NS Offload", and "TCP/UDP Checksum offload" settings that can be enabled or disabled.

Reply
0 Kudos
Scissor
Virtuoso
Virtuoso
Jump to solution

... and antivirus software disabled to facilitate debugging.

Which AntiVirus program is installed that you disabled for testing?

Reply
0 Kudos
kriemer
Enthusiast
Enthusiast
Jump to solution

Scissor

I was using AVG v8.5 antivirus. I have since uninstalled in an attempt to fix the issue.

I will try disabling NIC "offload" settings next Monday (this is my wifes computer and I'm sure you can guess the rest).

Not to be pedantic, but you mention that this disabling would be temporary. What if this does fix the problem, what am I giving up by maintaining the settings?

Thanks

k

Reply
0 Kudos
Scissor
Virtuoso
Virtuoso
Jump to solution

Scissor

I was using AVG v8.5 antivirus. I have since uninstalled in an attempt to fix the issue.

AVG should be ok. Other AV's cause problems even if "disabled".

I will try disabling NIC "offload" settings next Monday (this is my wifes computer and I'm sure you can guess the rest).

Not to be pedantic, but you mention that this disabling would be temporary. What if this does fix the problem, what am I giving up by maintaining the settings?

You would be giving up a tiny fraction of a percent of CPU time because your Host processor would be calcuating packet checksums instead of the NIC adapter. Any difference would be unnoticable on a modern desktop computer.

If a newer NIC driver becomes available you can always try enabling it again to see if the newer driver fixes it. Same if a newer version of Workstation comes out.

Reply
0 Kudos
kriemer
Enthusiast
Enthusiast
Jump to solution

Scissor,

Right you were; that seems to have fixed it for me.

I had 2 Offload settings available; "Offload - CheckSum", and "Offload TCP_LargeSend". A little bit of testing and I determined that I only needed to disable "Offload - CheckSum" to be able to connect to the host machine. I figure in this case 1 is better than 2.

Many thanks for your help and patience.

Regards

k

Reply
0 Kudos
Scissor
Virtuoso
Virtuoso
Jump to solution

Scissor,

Right you were; that seems to have fixed it for me.

Woo Hoo! Great news.

Just out of curiosity, can you tell us what model NIC and what driver version is installed on your Host?

Reply
0 Kudos
kriemer
Enthusiast
Enthusiast
Jump to solution

Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC

Driver Version: 5.670.530.2007

There are more current driver versions v6.214.1211.2008 Rev.A, for Vista; and v7.009 for Win7. But as I am running WinXP64 on my host machine I have kept the older v5 driver version.

Many thanks

k

Reply
0 Kudos
vince100
Contributor
Contributor
Jump to solution

I had exactly the same problem.

Realtek Driver Date: 7/28/2009

Driver version: 5.736.728.2009 (lastest)

IMHO, blaming this problem on Realtek does not make any sense.

Why did VM 6.5 work?

This is obviously a VW 7 only bug and should be fixed by VM not anybody else.

And to label this question as "Answered" doesn't make any sense either, this is only a workaround.

Why should I waste my CPU time on some bug that should have been fixed?!

Reply
0 Kudos
kriemer
Enthusiast
Enthusiast
Jump to solution

I can't disagree tbat the problem was not completely resolved, but many software vendors would have resolved the issue by modifying the Realtec setting "sub-rosa".

By marking this as Complete I did not imagine that VMware would not continue to try to find a better solution to what is obviously a bug.

k

Reply
0 Kudos
rtayne
Contributor
Contributor
Jump to solution

Thanks Scissor,

Disabling NIC "offload" settings also fixed my upgraded VMware Workstation 7 bridge problems!

Host: Windows XP SP 3

Realtek RTL8168D\(P)/811D(P) PCI-E Gigabit

Driver Date: 1/22/2009

Driver Version: 5.714.122.2009

Reply
0 Kudos
tdk
Contributor
Contributor
Jump to solution

Another big thank you to Scissor!

I had the same issue on Vista Business x64 and changing the NIC settings got my VMs back on line again.

All of my bridged network interfaces stopped working from VM to host, from host to VM and from VM to VM. After disabling the offload settings on my Realtek PCI GBE Controller (driver version 6.228.1116.2009) things work again.

Host System: VMWare Workstation 7 on Dell E521: Athlon 64 X2 Dual Core 5600+ 2.8 GHz, 4 GB RAM, Vista Business x64

Host System: VMWare Workstation 7.0.1 on Dell E521: Athlon 64 X2 Dual Core 5600+ 2.8 GHz, 4 GB RAM, Vista Business x64
Reply
0 Kudos