- An error message indicates that the IP already exists in the network, but no other virtual machine in the network is sharing the IP.
- On a Windows virtual machine, you see this error:The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter
- After rebooting the virtual machine, the guest operating system NIC is assigned a private IP address.
- After a physical to virtual (P2V) conversion of a machine, you cannot assign an IP address to a NIC.
- After removing and re-adding a virtual NIC, the previous device is no longer visible in Device Manager.
- The NIC is re-enumerated in the guest operating system.
- After a P2V conversion, installed devices such as a Universal Serial Bus (USB) device or ghosted device, are not connected to the computer.
- The Show Hidden Devices option in Device Manager does not display the devices.Note: To view the hidden devices, navigate to My Computer > Properties > Hardware > Device Manager > View > Show Hidden Devices.
The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter Name of adapter. Name of adapter is hidden from the network and Dial-up Connections folder because it is not physically in the computer or is a legacy adapter that is not working. If the same address is assigned to both adapters and they become active, only one of them will use this address. This may result in incorrect system configuration. Do you want to enter a different IP address for this adapter in the list of IP addresses in the advanced dialog box?
In this message, XXX.XXX.XXX.XXX is the IP address you are trying to set and Name of adapter is the name of a network adapter that is present in the registry but hidden in Device Manager.
This error can occur when you change a network connection’s TCP/IP configuration from DHCP to a static IP address if:
- You have upgraded VMware virtual network adapters (for example, when you migrate a virtual machine from an older to a new version of VMware software). This can also include updating the virtual machine hardware version and/or upgrading the version of VMware Tools.
- You have added and removed network adapters multiple times.
- You may see this if you recently performed a P2V and the resulting virtual machine still has the physical NICs and drivers for those NICs present. These ghost NICs have the old IP address and the virtual NIC cannot be assigned the same IP address.
- Click Start > Run.
- Type cmd and press Enter.
- At the command prompt, run this command:
Note: In Windows 2008 and Windows 7, open the command prompt using the Run as Administrator option.set devmgr_show_nonpresent_devices=1
Note: If this command does not work (a possibility in Windows Server 2000 and 2003), you may need to add the parameter to Windows and set its value:
- Right-click the My Computer desktop icon and choose Properties.
- Click the Advanced tab and select Environment Variables.
- In the System variables section, click New.
- Set the Variable name to devmgr_show_nonpresent_devices and set the Variable value to 1 to enable the parameter.
- Click OK to add the variable to Windows.
- Start the Device Manager by running this command from the same command prompt:start devmgmt.msc
- Click View > Show Hidden Devices.
- Expand the Network Adapters tree (click the plus sign next to the Network adapters entry).
- Right-click the dimmed network adapter, then click Uninstall.
- Once all of the grayed out NICs are uninstalled, assign the IP address to the virtual NIC.Note: To assign the IP address to the virtual NIC on the command line, run the command:netsh interface ip set address “Local Area Connection #” static IP_Address Subnet_Mask Default_Gateway
netsh interface ip set address “Local Area Connection 2” static 192.168.1.101 255.255.255.0 192.168.1.1
- Close the Device Manager.Note: In some Windows versions, a reboot may be necessary to apply the changes.
For more information, see the Microsoft Knowledge Base article 241257.
Note: The preceding link was correct as of August 20, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.
Resolve issue using DevCon utility
- Download the DevCon tool from Microsoft Knowledge Base article 311272.Note: The preceding link was correct as of August 20, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.
- Unpack the 32-bit or 64-bit DevCon tool binary to a local folder.
- Click Start > Run, type cmd, and press Enter.
- Type CD:\path_to_binaries to navigate to where the devcon.exe file is located.
- Use this syntax to find installed network adapters:devcon findall =net
ordevcon listclass net
Note: In the output of the previous commands, there is a line for the ghosted network adapter that is similar to PCI\.
- Run this command to remove the adapter:devcon -r remove @device\nameFor example:
devcon -r remove “@PCI\VEN_14E4&DEV_1600&SUBSYS_01C21028&REV_02\4&378EDFA4&0&00E2”
Note: IDs that include an ampersand character (&) must be enclosed in quotation marks as seen in the example.
- Reboot the system and you no longer see the ghost network adapters.