Loading

×Sorry to interrupt
CSS Error

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

My Subscriptions

Loading

Knowledge Base

Automatic Private IP Addressing (APIPA) on Microsoft Windows virtual machines on ESXi (1028373)

Last Updated: 5/14/2021Categories: TroubleshootingTotal Views: 263154Language:
Chinese (Simplified)JapaneseEnglish

62 like this article

Subscribe to get an email
newsletter with new updates

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

Symptoms

You see an APIPA address (169.254.X.X) IP listed when you run the command:

ipconfig /all

You may see both a false duplicate and a preferred IP in the output. You may also notice any of the following:

Assigning an IP address, you see a duplicate IP address conflict.

The VM is assigned a 169.254.x.x Iaddress.

When you set up the same virtual machine on a vSwitch with no uplink port on the vSwitch, the IP address is assigned successfully.

When you assign the same IP address to another virtual machine on the same vSwitch, the IP address is assigned successfully.

Cause

This issue occurs when the physical switch has gratuitous ARPs enabled or the ArpProxySvc replied to all ARP requests incorrectly. This is an issue between Windows and the physical switch. The solution below is performed at the Windows level or on the physical switch.

Resolution

To resolve this issue, use one of these solutions:
Turn off gratuitous ARPs on the physical switch
Turn off gratuitous ARP in the guest operating system

Turn off gratuitous ARPs on the physical switch

This is the quickest was to resolve this for multiple VM's. The commands to disable this are specific to the manufacturer, refer to the manufacture documentation.

Turn off gratuitous ARP in the guest operating system

If the issue only happens on a few VMs, disabling it may be easiest to turn off gratuitous ARPs in the guest operating system of each VM affected.

Caution: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393.

To turn off gratuitous ARP in the guest operating system:

Shut down the guest operating system and power off the virtual machine.

Change the virtual machine to a network vSwitch with no uplink. You can create one for this procedure.

Power on the virtual machine and log in.

Click Start, type regedit, and click OK.

Locate this registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Click Edit > New, and click DWORD Value.

Type ArpRetryCount.

Right-click the ArpRetryCount registry entry and click Modify.

In the Value box, type 0 and click OK.

Exit the Registry Editor.

Shut down the guest operating system and power off the virtual machine.

Change the virtual machine back to a network vSwitch with the uplink.

Power on the virtual machine.

For more information, see the Microsoft TechNet Article ArpRetryCount .

Note: The preceding links were correct as of February 22, 2021. If you find a link is broken, provide the feedback and a VMware employee will update the link.

Related Information

As of TAC document release 116529, duplicate addressing is identified to cause this issue in some scenarios this is caused by IP device tracking. Duplicate IP Address 0.0.0.0 error message is received by clients that run Microsoft (MS) Windows Vista and later versions.

The primary method used to work around the issue is to delay the probe from the switch, so that Windows has time to finish duplicate IP detection. This is not a VMware issue. Ensure to refer the preceding TAC document for more information before proceeding.

From a SSH or Telnet session to the switch, enter this command to delay the probe:

IP device tracking probe delay 10

Note: This issue can also occur because of gratuitous ARP on an ASA firewall. Run this command to disable gratuitous ARP on an ASA firewall:

sysopt noproxyarp inside

環境で Cisco デバイスを使用していると、ESX/ESXi 上の Microsoft Windows Vista 以降の仮想マシンで重複した IP アドレスが誤って検出される
在环境中使用 Cisco 设备时，在 ESX/ESXi 上的 Microsoft Windows Vista 及更高版本虚拟机上检测到假重复 IP 地址

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
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

Take Our Survey

Support Assistant