VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1 2 3 ... 29 Previous Next 431 Replies Last post: Nov 1, 2009 7:07 PM by amyweaver29  

Bridged networking just quit! posted: Jun 28, 2007 2:57 PM

Click to view SrMarcos's profile Novice 10 posts since
Jun 28, 2007
All:

I've found several threads on this with no real resolutions, so I'm posting this in the hopes someone has since found a resolution and can share it...or that VMWare has found the bug and fixed it.

I had been accessing some test VMs on my machine using VMWare Server regularly, then didn't for a couple of weeks. When I tried to do so yesterday, none of the guests can communicate with the host or other guests...and the host can't even ping any of the guests. Guest OSes include Win2003 and CentOS...and they all have the same problem.

Any ideas? I did try to switch to Host-only, as that had been mentioned in one of the threads. No go.

Please advise. I was testing this to provide a go/no-go on deploying VMWare at a client site, and now I feel I must strongly advise against its use in anything resembling a production environment...a shame, as until now, I had no major reservations with it. Ugh.

Thanks in advance...
Mark

Re: Bridged networking just quit!

1. Jun 28, 2007 3:00 PM in response to: SrMarcos
Click to view esiebert7625's profile Guru 6,794 posts since
Oct 23, 2006
fyi...this post has been moved to the VMware Server forum.

Eric Siebert
VMTN User Moderator

Re: Bridged networking just quit!

2. Jun 29, 2007 2:14 AM in response to: SrMarcos
Click to view devzero's profile Master 2,749 posts since
Dec 27, 2004
i have had the same issue quite often - also if VMs weren`t accessed for some longer time.

what is the type of network card inside the host ?

you could workaround that by installing some scheduled job inside the VM which is pinging another machine from time to time.

Re: Bridged networking just quit!

3. Jun 29, 2007 2:17 AM in response to: SrMarcos
Click to view spastor's profile Enthusiast 59 posts since
Apr 3, 2007
Regarding the ping issue this is strange...
Are you sure your guests machine are in the same Ip range than your
host ?

The time you didn't use you VMs, did you change anything on your host ( Service pack, updates, anything ?)

What is your host os ?
I had similar issues for network communications between Host and guests but it was sending / Receiving files ping was working fine.

Re: Bridged networking just quit!

5. Jun 29, 2007 6:07 AM in response to: SrMarcos
Click to view spastor's profile Enthusiast 59 posts since
Apr 3, 2007
Did you test to ping one VM with another, and ping one VM with other machine on your network ?

Also can you test to ping any machine on your network from your host ?

Re: Bridged networking just quit!

6. Jun 29, 2007 6:22 AM in response to: spastor
Click to view devzero's profile Master 2,749 posts since
Dec 27, 2004
The wireless is an Intel; the wired one is a Broadcom,
I believe. I'll check later and let you know.

please post exact model and also post operating system + driver information.
please also post the type of network switch where the system is hooked to.

there are guesses,that this problem is not related to vmware alone.

so - the only way to get deeper into this and systematically trying to catch this error is to collect statistical information to see, if the problem is specific to certain setup constellations.

what about starting to compile such list within this thread ?

Re: Bridged networking just quit!

8. Jun 29, 2007 8:53 AM in response to: SrMarcos
Click to view spastor's profile Enthusiast 59 posts since
Apr 3, 2007
Maybe try this ?

1. Click Start, click Run, type regedit , and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. On the Edit menu, point to New, click DWORD Value, and then type EnableRSS
4. Double-click EnableRSS, type 0 , and then click OK.
5. Exit Registry Editor.

If you are still experiencing problems (like slow file copying), you should also disable Offloading support:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. In the right pane, make sure that the DisableTaskOffload registry entry exists. If this entry does not exist, follow these steps to add the entry:
a. On the Edit menu, point to New, and then click DWORD Value, and then type DisableTaskOffload .
4. Double-Click DisableTaskOffload, type 1, and then click OK.
5. Exit Registry Editor.

Re: Bridged networking just quit!

9. Jun 29, 2007 8:53 AM in response to: spastor
Click to view spastor's profile Enthusiast 59 posts since
Apr 3, 2007
ON your host ...

Re: Bridged networking just quit!

10. Jul 3, 2007 9:00 PM in response to: spastor
Click to view tonyqa's profile Novice 9 posts since
Jul 3, 2007
I'm having the same problem and it appears to have happened in the same timeframe that other people are having similar problems, about 7-10 days ago.

I first thought it was my host OS (Win XP) that had problems and so I did a reinstall (my PC needed it anyway), but this didn't help. I've tried an XP guest and a Knoppix guest and they both exhibit the same behaviour.

The problem is that they are able to get an IP address from the DHCP server, but nothing after that works. From the guest I can ping the IP of the host and from the host I can ping the guest. From the guest I can't get to anything else on the network. My host PC works fine (network wise).

I've read all of the threads and tried changing the EnableRSS & DisableTaskOffload registry keys with no success (yes, I rebooted).

Something that is interesting is that up until I reloaded my PC I was using VMware Server v1.0.0 (don't know the build number), so it's not just the current version of VMWare that has the problem. This makes me believe that it could well be a Windows update that has caused this problem as nothing else changed on my PC when the problem occurred (prior to the reload).

Re: Bridged networking just quit!

11. Jul 3, 2007 10:18 PM in response to: tonyqa
Click to view devzero's profile Master 2,749 posts since
Dec 27, 2004
This makes me believe that it could well be a Windows update that has
caused this problem

i don`t think so, since this problem also exists on linux

Re: Bridged networking just quit!

12. Jul 3, 2007 10:54 PM in response to: devzero
Click to view tonyqa's profile Novice 9 posts since
Jul 3, 2007
The reason I'm blaming Windows is that I didn't change anything on my PC and it just sopped working. I was using an old version of VMware, so it wasn't a VMware update that caused it (ie. I hadn't updated VMware). I'm happy to be proven wrong though.

I'm not really worried about what t he problem is, or blaming MS, VMware, Linux or someone else, I just want to find a resolution for it !

Re: Bridged networking just quit!

14. Jul 4, 2007 3:31 PM in response to: SrMarcos
Click to view tonyqa's profile Novice 9 posts since
Jul 3, 2007
Good idea, I hadn't thought to use NAT. This allows me to continue to use my VM as it mostly used for outbound network traffic which NAT is fine for. If I was using it to host a server (inbound connections) I wouldn't be nearly as happy to use NAT.
1 2 3 ... 29 Previous Next Go to original post

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities