You rebooted your worker facilitated in VMware ESXi climate and got mistake "false duplicate ip address detected on your organization" explicitly when you are utilizing Cisco switches for your directing requirements. Indeed, you don't have to stress any longer, we have a workaround for you.
The Problem
With Microsoft Windows Vista and later forms, Microsoft presented another instrument that is utilized to identify copy addresses on the organization when the DHCP interaction happens. This new location stream is portrayed in RFC 5227.
One of the triggers for this location stream is characterized in area 2.1.1:
What's more, if during this period the host gets any ARP Probe where the parcel's 'target IP address' is the location being examined for, and the bundle's 'sender equipment address' isn't the equipment address of any of the host's interfaces, then, at that point the host SHOULD comparatively regard this as a location struggle and sign a mistake to the arranging specialist as above. This can happen if (at least two) has have, for reasons unknown, been unintentionally designed with a similar location, and both are at the same time during the time spent examining that location to check whether it can securely be utilized.
Cisco IOS® utilizes the Address Resolution Protocol (ARP) Probe that is sourced from a location of 0.0.0.0 to keep up the IP gadget following store during IP gadget following, and an element that utilizes it is empowered, (for example, 802.1x) on a Cisco IOS switch. The motivation behind IP gadget following is for the change to get and keep a rundown of gadgets that are associated with the switch by means of an IP address. The test doesn't populate the following section. It is utilized to enact and keep up the section in the table after it is learned. This IP address is then utilized when an Access Control List (ACL) is applied to the interface to substitute the source address in the ACL with the customer IP address. This capacity is basic at whatever point access records are utilized with 802.1x or some other Flex-Auth work on Cisco switches.
Main driver of Duplicate IP Address
In the event that the switch conveys an ARP Probe for the customer while the Microsoft Windows PC is in its copy address recognition stage, then, at that point Microsoft Windows distinguishes the test as a copy IP address and presents a message that a copy IP address was found on the organization for 0.0.0.0. The PC doesn't get a location, and the client should either physically deliver/reestablish the location, disengage and reconnect to the organization, or reboot the PC to acquire network access.
The Ultimate Solution
There are different techniques that are utilized to work around this issue. Here is a rundown of conceivable workarounds:
The best strategy that is utilized to forestall this issue is to arrange the switch so it's anything but a non-RFC agreeable ARP Probe to source the test from the Switch Virtual Interface (SVI) in the VLAN where the PC lives. In the event that a SVI is arranged for the VLAN and both of the two orders that follow are utilized, then, at that point the sender IP address in the IPDT tests won't ever be 0.0.0.0. In this way, it is sure that the copy IP address mistake won't happen.
