Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Networking Error: IP address already assigned to another adapter (1179)

Last Updated: 6/19/2020Categories: TroubleshootingTotal Views: 471063Language:
Chinese (Simplified)JapaneseEnglish

39 like this article

Subscribe to get an email
newsletter with new updates

39 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Details

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.

Solution

Cause

Under certain conditions, you may see this error message from a Windows guest operating system:

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.

This issue occurs if a network adapter with the same IP address is in the Windows registry but is hidden in the Device Manager (My Computer > Properties > Hardware > Device Manager). This hidden adapter is called a ghosted network adapter.

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.

Using the Show hidden devices option in the Device Manager (View > Show hidden devices) does not always show the old virtual NIC (ghosted adapter) to which that IP Address is assigned.

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.

Resolution

To resolve this issue, make the ghosted network adapter visible in the Device Manager and uninstall the ghosted network adapter from the registry:

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

For example:

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.

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

Alternatively, you can also resolve this issue using the DevCon utility. This is a command-line utility that acts as an alternative to Device Manager. When you use DevCon, you can enable, utility disable, restart, update, remove, and query individual devices or groups of devices.

To resolve the issue using DevCon:

Download the DevCon tool.

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

or

devcon 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\name

For 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.

Note: If you did not get the Device Instance ID or the OCI name from devcon, search for the adapter name in the registry using Find by clicking Start > Run and typing regedit. Then copy the Device Instance ID for the appropriate adapter. When you locate the device, use the command from Step 6.

For related information, see:

Virtual NIC settings on a Windows guest are lost after a virtual hardware upgrade (1015572)

IP address already in use error on a converted virtual machine (1012255)

Additional Information

For translated versions of this article, see:

日本語: ネットワーク エラー：IP アドレスが別のアダプタにすでに割り当てられている (2078876)

简体中文: 网络错误：IP 地址已分配给其他适配器 (2061917)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Sistemas de arquivos baseados em Linux tornam-se somente leitura (51306)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workstation

VMware vSphere ESXi

VMware vCenter Converter Standalone

VMware vCenter Converter

VMware ESX Server

VMware Converter

Related Versions:

VMware P2V Assistant

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant