Bridged network stops working after sleep/hibernate on Vista

[dbowmanNNA]

Running VMware Workstation 6.5 and Vista 32-bit with a wired NIC. My Bridged networking stops working after Vista sleeps or hibernates. A restart is required to restore its operation. NAT networking works fine.

Anyone have any ideas how to restore it without a reboot?

[KevinG]

Is the VM configured with Link State Propagation turned on?

When you say reboot, are you referring to just the guest OS or Host

[dbowmanNNA]

What is "Link State Propagation"? I can't find it in the help anywhere. Is it the same as "Replicate physical netywork connection state"? If so, that is off.

It corrects itself when I reboot the host. The guest OS is powered down (not suspended or hibernated) when the Vista host sleeps or hibernates. Unsleep / unhibernate, boot up the guest OS and no bridged network.Shutdown the guest OS. Reboot the host. Boot up the guest and bridged networking works again.

[vmjmelan]

same problem here, was this ever corrected? if so, what do i need to change?

[happyfirst]

Could you provide a bit more help on where we enable "link state propagation" ?

WS 6.5 on Win 7 64. My asus motherboard died and I replaced with a gigabyte mb. Everything worked great on the asus. But now this same thing is happening to me.

If the host goes to sleep but I immediately wake it, the vm networks are fine. If it's asleep a long time, then after I wake it, the vm networks are dead. Sometimes I can bring them back by changing some network setting. Some times I can't. Right now, my current scenario, they're dead and I even restarted the vm and still dead. And the vm's network connections says its "connected". There's a valid ip and everything but I can't ping a thing. The host network is always fine. Even remote desktop sessions that were still open when it went to sleep are immediately usable after it wakes.

Any ideas?

[continuum]

do this two commands in a cmd as administrator help ?

net stop vmnetbridge
net start vmnetbridge

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[happyfirst]

That's awesome! It worked! Thank you!

Host PC was sleeping over night. Sure enough, this morning, all the VMs had dead networks. Your commands fixed it. Why don't I see a vmnetbridge service?

Next questions would be:

1) Why wasn't this happening with my older Asus motherboard? Are the network drivers at fault even though the host pc network is fine after a waking?

2) Any easy way to automate that these commands execute after I wake from a sleep?

thanks again!

[continuum]

don;t know why this happens - anyway the command can be easily automated - just create a batchfile and put it on your desktop.

Then doubleclicking it will run it next time you need it again




___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[happyfirst]

Thanks. I've done that. I need to run it as administrator though and I can't seem to set batch files to always run as administrators.

Since my machine always prompts for a login after waking from sleep, I'm now trying to find a way to automate having the batch file called whenever I login.

[hebalder]

... same effects with

• VM Workstation 7.0.0/7.0.1

• host: Win 7 64bit Home Professional (german edition)

• guests: different Win XP SP2/3 32bit (all german editions)

running on a hp notebook dv6 2090eg with wired NIC (onboard, Realtek PCIe GBE, driver version: original and up to 7.11.1127.2009).

Only the procedures described above activates the bridge network.

any ideas?

cu

Hugo

[hebalder]

Hi,

after reading many, many VMWare Server and Workstation threads, here is my solution for users of Realtek NICs PCI(e) GBE Family Controllers (e.g. Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet - bold is my onboard type:

Changing the NIC Configuration

1. windows net connections, adapter properties: deactivate the VMWare Bridge Protocol

2. in the NIC properties dialog deactivate the entry "Offload Checksum" (in the germay dialog it is named "IPv4 Prüfsummenabladung")

3. (re-)activate VMWare Bridge Protocol

After these steps returning from the following energy modes will perfectly run:

• stand by

• hybrid stand by

• hibernate

Good luck

Hugo :smileygrin:

(sorry for my "german" english)

german readers: see

[happyfirst]

Still a problem with 7.1.3. My Win7 machined died due to a black screen of death (don't know if it was workstation or not, I was working in a vm) and I had to rebuild from scratch.

This morning, my VMs networks were dead when I woke it from sleep.  I remembered this post and came back to it since the fix way up above about restarting the service worked great for so long.  This time I started looking in "hebalder" possible fix, but I didn't like the idea of changing settings that would affect operations all the time. The restarting fix seems simple and safe and doesn't change any settings.  I noticed I never posted my full fix.

1) Create a batch file with the following two commands

net stop vmnetbridge
net start vmnetbridge

2) Create a scheduled task.

3) Allow it to run with highest priveleges.

4)  Set the trigger to logon (I require a relogin after sleep).

5) Set the action to the batch file.

Hopefully that should be it!

[quiettime]

This is still a problem with 7.1.5 build-491717. Ulli's solution works though.

[PericoPQN]

Can confirm this is still a problem on 9.0.2 build 1031769 , the solution on a AsusP6tv2deluxe and a Marvell Yukon NIC was to disable the wake-on-LAN feature within the driver dialog on windows 7 ,

[quiettime]

Yup I'm still having this problem. Now I have a different machine and entirely different hardware, and a different version of VMWare Workstation (same as you, 9.0.2 build 1031769). Host is Windows 7 Ultimate SP1 x64. Network adapter is Intel(R) 82579V Gigabit Network Connection using stock microsoft driver and all power management 'Wake' options in its device settings are disabled.

I wonder why this happens. Weird!

[quiettime]

Well several years after I encountered this problem it appears I have a fix. I was using VMWare's Virtual Network Editor (included with VMWare Workstation) and I noticed bridged mode was set to Automatic. I changed it to bind to my specific network adapter because I thought that might help. It does. I no longer have to issue "net stop vmnetbridge && net start vmnetbridge" on hibernate or sleep resume. This is in Workstation 9 on Windows 7 x64.

If anyone else encounters this problem you may want to try doing that. The disadvantage is if you use multiple network adapters is I guess it will not switch over automatically? In Workstation 9 that doesn't seem to work anyway (the whole reason I was using the network editor in the first place). What I've ended up doing is I have two virtual network adapters, one bridged to each physical adapter and I let the VM access them both. I imagine that could be pretty inconvenient if you have a lot of VMs though.