locked
Win 2008 R2 Servers will not connect to network, says duplicate IP RRS feed

  • Question

  • We have 3 new 2008 R2 servers for our new Exchange 2007 system. They all are running on ESXi 4 and our building had a power shutdown this weekend. We shut down our complete network and then restarted all the servers. All our 2003 servers are running fine, the 3 2008 servers will not conect to the network at all. We have tried resetting the TCP/IP stack and even giving the one of the servers a new IP address causes the same problem. We keep getting duplicate IP adress errors and the servers. These servers were all fine 24 hours ago and we did not install any new patches from what I've been told.

    Anyone come across this problem.

    Thanks

    Vic McClelland

    Sunday, April 25, 2010 9:03 AM

Answers

  • Turns out the we had to use the fix for the Cisco Pix firewall, we don't use Cisco, we use Sonicwall.

    Had to run NetSh int ip reset, then reboot the server. Readd the correct IP infor and then run the reg hack.

    As discussed over phone earlier , for conflict detection, the client computer uses the Address Resolution Protocol (ARP) request to determine whether the IP address is being used. However, a ProxyArp device might incorrectly answer the ARP request, and an IP address conflict is reported.

    When this problem occurs, the ProxyArp device responds to all ARP requests.
    To work around this problem, we can turn off gratuitous ARP by setting the value of the ARPRetryCount registry entry to 0. To do this, follow these steps.

     

    1.  Click Start , type regedit in the Start Search box, and then press ENTER. 

    2.  Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters 

    3.  On the Edit menu, point to New , and then click DWORD Value . 

    4.  Type ArpRetryCount . 

    5.  Right-click the ArpRetryCount registry entry, and then click Modify . 

    6.  In the Value data box, type 0 , and then click OK . 

    7.  Exit Registry Editor. 

    (Reboot)

    Since we don't use Cisco we didn't even try this fix. But it worked for us.

    • Marked as answer by CP140 Monday, April 26, 2010 6:37 PM
    Monday, April 26, 2010 6:37 PM

All replies

  • You can try setting a static ip for all the server and the gateway plus the DNS server. After you have finish setting all the IP address in your orgaization it will work and will not have an error like duplicate IP or IP conflicts.

    Hope it help!

    • Proposed as answer by Jeremy Legend Monday, April 26, 2010 6:48 AM
    Monday, April 26, 2010 3:29 AM
  • The are all set with a static IP, Gatway and DNS settings, they were configured that way. Before this they were being shutdown and restarted without any problems. It's only after we shut done the entire network for the power shut down that this problem came up. I have tried removing the nic card and adding it again via virtual center but as soon as we add it back it comes up as a duplicate IP address, I have reset the TCP IP stack and even tried giving it an different IP address but I get the same error.
    Monday, April 26, 2010 2:45 PM
  • Turns out the we had to use the fix for the Cisco Pix firewall, we don't use Cisco, we use Sonicwall.

    Had to run NetSh int ip reset, then reboot the server. Readd the correct IP infor and then run the reg hack.

    As discussed over phone earlier , for conflict detection, the client computer uses the Address Resolution Protocol (ARP) request to determine whether the IP address is being used. However, a ProxyArp device might incorrectly answer the ARP request, and an IP address conflict is reported.

    When this problem occurs, the ProxyArp device responds to all ARP requests.
    To work around this problem, we can turn off gratuitous ARP by setting the value of the ARPRetryCount registry entry to 0. To do this, follow these steps.

     

    1.  Click Start , type regedit in the Start Search box, and then press ENTER. 

    2.  Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters 

    3.  On the Edit menu, point to New , and then click DWORD Value . 

    4.  Type ArpRetryCount . 

    5.  Right-click the ArpRetryCount registry entry, and then click Modify . 

    6.  In the Value data box, type 0 , and then click OK . 

    7.  Exit Registry Editor. 

    (Reboot)

    Since we don't use Cisco we didn't even try this fix. But it worked for us.

    • Marked as answer by CP140 Monday, April 26, 2010 6:37 PM
    Monday, April 26, 2010 6:37 PM