adamant40
asked on
My Exported Server 2008 VM gets an "IP Address Conflict" when set to original IP, works with DHCP
Using VMWare ESXi 5.0. I had to move a 2008 server vm to another hypervisor. Found that I could not use VSphere to Migrate the VM, had to use VMware Stand Alone Converter.
Original VM is shut down.
If I set the IP address of the moved VM to it's original value, I get a "IP Address Conflict" message and networking stops. If I set the IP to a different value than everything works.
I've verified that there is nothing on the network using this IP, issue is internal to this moved vm.
I know that on migrating Linux vms you need to delete /etc/udev/rules/70-persist
Original VM is shut down.
If I set the IP address of the moved VM to it's original value, I get a "IP Address Conflict" message and networking stops. If I set the IP to a different value than everything works.
I've verified that there is nothing on the network using this IP, issue is internal to this moved vm.
I know that on migrating Linux vms you need to delete /etc/udev/rules/70-persist
Nothing that I know of that needs to be deleted on a 2K8 machine.
Presumably you've confirmed the IP address doesn't exist by pinging it when you have the "new" machine set to a different address. Try flushing the ARP cache of your switch(es)?
Aside from that, got the following from the VMware KB:
Resolving TCP/IP stack issues on the virtual machine
To resolve TCP/IP stack issues on the virtual machine:
Remove and reinstall your virtual network adapter driver.
Verify, using the vSphere/ VI Client, that the ethernet adapter is connected and powered:
Enable and disable the NIC and ping test.
Uninstall VMware Tools and ping test.
Connect to host using the vSphere/ VI Client.
Turn off the virtual machine.
Remove the ethernet adapter.
Turn on the virtual machine. TCP/IP is not loaded.
Turn off the virtual machine again.
Add the ethernet adapter – at this point either auto assign a MAC or manually assign one.
Assign a different IP address to eliminate the possibility of duplicate IP and do a ping test.
Reinstall VMware Tools and do a ping test.
Presumably you've confirmed the IP address doesn't exist by pinging it when you have the "new" machine set to a different address. Try flushing the ARP cache of your switch(es)?
Aside from that, got the following from the VMware KB:
Resolving TCP/IP stack issues on the virtual machine
To resolve TCP/IP stack issues on the virtual machine:
Remove and reinstall your virtual network adapter driver.
Verify, using the vSphere/ VI Client, that the ethernet adapter is connected and powered:
Enable and disable the NIC and ping test.
Uninstall VMware Tools and ping test.
Connect to host using the vSphere/ VI Client.
Turn off the virtual machine.
Remove the ethernet adapter.
Turn on the virtual machine. TCP/IP is not loaded.
Turn off the virtual machine again.
Add the ethernet adapter – at this point either auto assign a MAC or manually assign one.
Assign a different IP address to eliminate the possibility of duplicate IP and do a ping test.
Reinstall VMware Tools and do a ping test.
if this is Windows 2008 R2, have you removed all the Hidden Devices, and network interface.
ASKER
Just one ethernet card in vm
Arroryn,
unfortuntately can't clear arp cache on switches. Have confirmed by ping and other that there is nothing using IP. Thought for sure your instructions would work, forgot about version of VMware tools. Unfortunately, no change.
Arroryn,
unfortuntately can't clear arp cache on switches. Have confirmed by ping and other that there is nothing using IP. Thought for sure your instructions would work, forgot about version of VMware tools. Unfortunately, no change.
ASKER
Checked and did not find any hidden devices to remove.
ASKER
I've deleted the copied vm. I've set the original to DHCP and am going to try copying it over (8 more hours) and then deleting the VMWare tools, and then setting a static IP. Gonna close this ticket until I find out if this works or not.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for adamant40's comment #a39475043
Assisted answer: 500 points for arroryn's comment #a39474885
for the following reason:
I did not get a solution, but I did get good help from arroryn. Gave me another idea to try.
Accepted answer: 0 points for adamant40's comment #a39475043
Assisted answer: 500 points for arroryn's comment #a39474885
for the following reason:
I did not get a solution, but I did get good help from arroryn. Gave me another idea to try.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
JUST found that answer (after 10 hours of google searching). It does make sense for it to be selected as answer but would still like points left as assigned.
Thanks.
Thanks.
e,.g. ifconfig at the console when VM is booted, do you have eth0 and eth1?
there is an issue with Linux, and the udev rules based on mac address, when cloning on a Hypervisor.
I would delete all the udev rules, and apply IP address.