|
||
| KB | 0000635 | |
| Dated | 17/07/12 | |
| Revision | 0.01 | |
IP Address Conflicts with VMware ESX and Cisco ASA |
||
Problem |
||
My colleague was setting up a DMZ server for one of our clients, it was a virtual server that was presented to the DMZ of a Cisco ASA 5510. Every time he gave it a static IP address it popped up an IP address conflict (no matter what the IP address was). Windows has detected an IP address conflict He asked me to set up DHCP for the DMZ to see if that would cure the problem, which I did. However that also refused to work either. Windows IP Configuration |
||
Solution |
||
Turns out this is a known problem, and is pretty easy to rectify. Option 1 (On the ASA)1. Connect to the ASA via command line, log in and then go to enable mode. |
||
| User Access Verification Password: Type help or '?' for a list of available commands. PetesASA> enable Password: ******** |
||
| 2. Enter configure terminal mode then disable proxy ARP on the interface that's presented to the problem network, (in this case the interface is called DMZ). | ||
| PetesASA# configure Terminal PetesASA(config)# sysopt noproxyarp DMZ |
||
| 3. Save the changes. | ||
PetesASA# write mem 7424 bytes copied in 1.710 secs (7424 bytes/sec) |
||
Note: You can also disable proxy arp in the nat tranlation, with the no-proxy-arp like so, nat (inside,DMZ) source static Inside-LAN Inside-LAN destination static Inside-LAN Inside-LAN no-proxy-arp
|
||
Option 2 (On the affected machine)Note: This is is for Windows based clients. 1. Start > Run > regedit {Enter}. 2. Navigate to;
3. Create a new DWORD value called 'ArpRetryCount' and set its value to 0 (Zero). 4. Reboot. |
||
| Related Articles, References, Credits, Or External Links | ||
| Thanks to Andrew Dorrian for giving me an interesting problem, and thanks to David Mulholland for patiently waiting while we fixed it. | ||














