Wednesday, December 14, 2005

Disabling the VMWare network adapters

When you are not running a VMWare session, you may want to disable the VMware virtual network adapters. I have found that they can slow down network operations on the host. Anything doing a UDP broadcast that is sentg over all adapters will take much longer to run if they broadcast over the VMWare adapters. The ListAvailableSQLServers function call in the SQLDMO library is one example that I came across that slowed down dramaticly with the VMWare adapters running.

You have at least three ways of enabling and disabling the network adapters. You can open up the Device Manager (click the "Start" button, select "Run...", enter devmgmt.msc), select the "VMware Network Adapter VMnet1" and "VMware Network Adapter VMnet8" adapters and press the disable button in the tool bar. The second option is to right click on "My Network Places" in the Start menu and select "properties". You can then right click on the "VMware Network Adapter VMnet1" and "VMware Network Adapter VMnet8" adapters and enable or disable them. The third method is via the command line, so that you can script it.

Microsoft, in it's infinite wisdom, does not provide a command line means of enabling or disabling network adapters out of the box. For that, you'll need DevCon.exe, the command line alternative to Device Manager. You can get from Microsoft as Knowledge Base article Q311272. With devcon, you can disable/enable a netwoirk adapter by it's hardware id. You can get the id from Device Manager, or by running devcon.exe like this:

devcon hwids =net

That will spit out a great deal of information, the ID's that you are looking for are *VMnetAdapter1 and *VMnetAdapter8. You can disable them individually or do both with a wildcard

devcon disable *VMnetAdapter1
devcon disable *VMnetAdapter8

or

devcon disable *VMnetAdapter*

The former probably executes faster, the latter is simpler. I run with the adapters disabled and I only enable them whem I am running a VMWare session.

9 comments:

Armin said...

Another reason why I usually disable the VMware NICs in WXP is because of offline files. As long as Windows sees a "live" NIC in the system, it will try to synchronise any offline files you might have set - very annoying when you're on the road and not logged in to your corporate network.

Btw. - devcon is nice and usefull, but not required to do this. Use netsh if you don't want or need the reskit tools:

netsh interface set interface /?

Chris Miller said...

I started with netsh, but I couldn't get it work. What was the syntax that worked for you?

I tried this:
netsh interface set interface name = "VMware Network Adapter VMnet8" admin = DISABLED

That comes back with a syntax error.

Anonymous said...

YEY!!! Thank you for this post Chris. I have to diable VMware NICs in order to use our VPN. I found devcon, then this blog entry. How convenient and informational. rickj

Anonymous said...

I had to disable the VMware Network Adapters VMNet8 and VMNet1 in order to use my broadband card.

Anonymous said...

The correct syntax to disable the VMware network adapters on my system using netsh is:
netsh interface set interface name="VMware Network Adapter VMnet1" admin=disabled
netsh interface set interface name="VMware Network Adapter VMnet8" admin=disabled

To enable them, I use:
netsh interface set interface name="VMware Network Adapter VMnet1" admin=enabled
netsh interface set interface name="VMware Network Adapter VMnet8" admin=enabled

I had to disable them to receive Whozz Calling? Ethernet Link messages.

-Bill Root

Anonymous said...

Man thanks a lot i was looking for this problem, vmware is amazing program but have so many problems ( lots of progresses etc )

big.bald.dave said...

One annoying side effect of leaving the adapters enabled is that Windows Vista/7 shows a connection with "limited connectivity" in the system tray if the VMware adapters are the only active ones. I always disable the adapters when VMware isn't running.

Anonymous said...

Vmware doesn't seem to connect to the internet. It was working about a week ago...

I currently running Fedora 11.

Any help on this? (thanks)

Chris Miller said...

@anonymous: I'm sorry, but I have no idea what could be causing your problem. Have you tried the Vmware support forums? You should include more information when you post to their forums. I would suggest including the Vmware version number and saying if it ever worked or that it stopped working.

Post a Comment