Added note. The Host connection is on the DMZ VLAN side of the ASA 5505 and the ASA is not running DHCP on the VLAN.
do an ip audit. an check the ip address on the vm machine.
I had verified that none of the VM machines had a dup IP but I went ahead and recreated everything.
1 - Delete host Windows SBS 2008 and re-installed Windows Small Business Server 2008. Assigned static IP's to both the WAN and LAN NIC's.
2 - Reinstalled VMware Server 2. 3. Set up VMware Virtual Networks. Created Windows Server 2003 x32 Machine.
4 - Installed VM Tools.
5 - Set static LAN IP. No problems
6 - Set status WAN IP. As soon an I did a repair Host displayed "Windows has detected an IP address conflict".
Before reinstalling everything I had swapped patch cables and the IP conflict stayed on the side connected to the ASA 5505.
The MAC address listed as having the same IP is a Cisco MAC address 00-1F-CA.
Are you bridging or NATing the virtual LAN?
what are the DMZ IP's of the host, the VM and the ASA's DMZ interface?
Try pinging the IP address that says is in conflict from the ASA. Then shutdown the VM and see if it goes away.
Then ping it again with the VM online and after you've changed the DMZ ip of the host to something on a different subnet.
You should at least be able to identify which system is the culprit.
Be sure that you set the gateway address on the guest OS to the 2nd available address in the network not the first. ie. 192.168.1.2 not 192.168.1.1. This should work if the network is NATed to the host.
It ended up that the ASA was causing the problem. Everything is working properly now.
Can you tell me what you did on the ASA to correct the issue? I'm having the exact problem.
Thanks in advance.
The ASA had a bad NAT address which was causing the ASA to respond like it had the IP address.
I really appreciate the reply. They're rare.
We are having the exact same issues within our VM environment are you able to elaborate more on what the exact issue was with the NAT address. A few weeks ago the network team upgraded from a PIX firewall to an ASA now on one specific VLAN we cannot assign IP addresses to the guest machines without getting an IP address conflict.
I ran into the same issue. Seems to deal w/ a setting that turns off a proxy arp setting. Called VMWare support and got some instructions on how to fix this type issue. I've posted info on my blog below.