ianz105
Contributor
Contributor

Cannot add Host Vitual Adapter

I installed VMware Workstation 6.5.2 on a Windows Server 2008 EE SP1 for testing.

The 2 default virtual network adapters have been setup for 2 HOST-ONLY vlans and work fine. Now I need to add one more host vitual adapter for the third VLAN. After add it in and click apply, I got "An error occurred while updating the virtual network setting. Error code: 0". Anyone has got this issue? Thanks.

0 Kudos
8 Replies
jokke
Expert
Expert

You could try to open cmd as admin/elevated and browse to "VMware Workstation" directory. Then execute this command: "vnetlib -- add adapter vmnet5"

Joakim

0 Kudos
ianz105
Contributor
Contributor

I tried the follwoing and reboot:

vnetlib -- add adapter vmnet5

vnetlib -- set adapter vmnet5 addr 10.10.12.1

vnetlib -- set vnet vmnet5 mask 255.255.255.0

vnetlib -- update adapter vmnet5

nothing happend after hit enter on each line above. Don't see any virtual adapter created.

0 Kudos
jokke
Expert
Expert

Upload vminst.log. Remember to delete your serial from it!

0 Kudos
ianz105
Contributor
Contributor

Please see attachment.

0 Kudos
ianz105
Contributor
Contributor

I did a clean installation and got the same result. The following is the part of the log AFTER the installation. I am wondering if it is because of Windows 2008 as the host OS.

inst : 09/22/09 12:26:08 I1:VNL_InstallNetworkAdapter: Window not supplied, so creating one

inst : 09/22/09 12:26:08 I1:LogTokenPermissions: number of privileges: 22

inst : 09/22/09 12:26:08 I1:SetVnetParameter: Created vmnet subkey vmnet5\Adapter

inst : 09/22/09 12:26:08 I1:VNLCopyFileToSystemDir: copying 'C:\Program Files\VMware\VMware Workstation\vnetlib.dll' to 'C:\Windows\system32\vnetlib.dll'

inst : 09/22/09 12:26:08 I1:VNLWaitForPendingInstallEvents: No install events are pending

inst : 09/22/09 12:26:09 E1:VNL_InstallInfW2K: inf file copy failed: 0x00000005

inst : 09/22/09 12:26:09 E1:VNLInstallNetworkAdapterW2K: could not copy inf file: C:\Program Files\VMware\VMware Workstation\netadapter.inf

inst : 09/22/09 12:26:10 XX:VNL_InstallNetworkAdapter: Adapter install result FALSE needsreboot FALSE

inst : 09/22/09 12:26:10 I1:ParseCommand: operation: successful

inst : 09/22/09 12:27:08 I1:adapterSetFunct: (vmnet5, addr 10.10.12.1)

inst : 09/22/09 12:27:08 I1:adapterSetFunct: set adapter parameter: result TRUE

inst : 09/22/09 12:27:08 I1:ParseCommand: operation: successful

inst : 09/22/09 12:29:39 I1:vnetSetFunct: (vmnet5, mask 255.255.255.0 )

inst : 09/22/09 12:29:39 I1:VNL_SetVnetSubnetMask: bits in IP mask: 24

inst : 09/22/09 12:29:39 I1:standardized mask: 255.255.255.0

inst : 09/22/09 12:29:39 I1:vnetSetFunct: set vnet parameter: result TRUE

inst : 09/22/09 12:29:39 I1:ParseCommand: operation: successful

inst : 09/22/09 12:30:22 I1:VNL_UpdateAdapterFromConfig: Updating adapter config on vmnet5

inst : 09/22/09 12:30:22 XX:VNL_UpdateAdapterFromConfig: Adapter update result FALSE

inst : 09/22/09 12:30:22 I1:ParseCommand: operation: failed

0 Kudos
continuum
Immortal
Immortal

did you reboot after adding the new adapter with the vmnetcfg.exe GUI ?

That tool is buggy and often error-messages do not mean some operation failed.

It is probably wise to have no running VMs while trying vmnetcfg.exe

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
jokke
Expert
Expert

Did you, when installing, remember to right-click installer and run as administrator?

Could you try another command (also elevated cmd) in workstation directory;

"rundll32 setupapi,InstallHinfSection VMnetAdapter5.Install 128 %CD%\netadapter.inf"

0 Kudos
ianz105
Contributor
Contributor

Running vmnetcfg.exe got the same error as my first post.

Using Administrator account to run "rundll32 setupapi,InstallHinfSection VMnetAdapter5.Install 128 %CD%\netadapter.inf" does not help, I did reboot but no virtual network adaptor installed.

I did another clean install on a Windows XP SP2 machine. It works fine. I am wondering if some default local policy can cause this issue on Windows Server 2008 EE SP1.

0 Kudos