VMware Cloud Community
cngoh
Contributor
Contributor

Duplicate IP address for different NIC adapter after conversion

Hi all,

I am running ESXi 4.1 server. Recently I converted 1 win 2003 x64 server into VM. When I tried to change the IP address (same IP address for physical machine before conversion), I encountered the error message of duplicate IP on another NIC adapter. Please refer to error1 print screen. Actually I already refer to KB doc from VMware (Networking Error, IP Address Already Assigned to Another Adapter) but it doesn't work on my problem.

So far, I can change the IP address but each time I open the network properties windows, this error message windows is prompt out.

The Broadcom adpater is used for Trend Mirco Common Firewall drvier. Please refer to pic 1 & 2.

Even I uninstall the Trend Mirco Common Firewall driver, I am still getting this error. Please refer to error1 print screen.

Any impact to the system with this error?

Please share your advise and recommendation.

Thanks.

0 Kudos
10 Replies
mittim12
Immortal
Immortal

That sounds like you have a disconnected hidden old adapter that was there physically before the conversion. I've seen this numerous times and the fix is exactly what was listed in, http://kb.vmware.com/kb/1179, which I believe you already tried. After entering the command to show non present devices and opening devmgmt.msc you should show all kinds of dimmed device that were present on the physical box but not the virtual copy. Did you see that at all?






If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

0 Kudos
cngoh
Contributor
Contributor

Hi,

Actually I also fix this problem for my previous migrated VM but having problem on this server.

I don't see any dimmed NIC at device management which I showed in the print screen.

Thanks.

0 Kudos
mittim12
Immortal
Immortal

Have you cleaned up the non present devices from this computer before? I'm just wondering if something didn't go correctly the first time you ran through the KB. I've actually never seen a machine that had been p2v and didn't include some of those non present devices.






If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

0 Kudos
cngoh
Contributor
Contributor

No, I didn't clean any non-present devices because after conversion, there is no non-present devices (no dimmed devices). Please refer to pic1 for the device manager after conversion. Try to unistall broadcom devices at device manager but failed due to this device is required during system bootup.

Therefore I uninstalled the trend mirco common firewall driver from network properties and the few lines for broadcom devices disappeared from device manager. I think the broadcom driver has been uninstalled if I'm right. Please refer to error1 for the device manager after uninstalling trend mirco common firewall driver from network properties.

Thanks.

0 Kudos
mittim12
Immortal
Immortal

I'm going to move this to the Virtual Machine and Guest OS forum to see if anyone can assist.






If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

cngoh
Contributor
Contributor

Appreciate your kind assistant.

0 Kudos
a_p_
Leadership
Leadership

I usually consider this message a "Don't care message" and answer it with "No". This way the IP address gets assigned to your new virtual NIC. There may remain an obsolete entry in the registry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces) however, usually nothing to worry about.

André

Forum Upgrade Notice:

VMware will be upgrading VMware Communities systems between 10-12 December 2010. During this time, the system will be placed in READ-ONLY mode.

cngoh
Contributor
Contributor

Thanks for your explanation.

I understand it doesn't harm the system.

But is there any way to totally delete these entries from registry?

By the way, how this error occurs? My practise for machine conversion is I will disable the NIC first during conversation. After conversation completed, I will shut down physical server and then enable the NIC in VM.

Any recommendation way for conversation to prevent this error happens?

Thanks.

0 Kudos
a_p_
Leadership
Leadership

You can delete the entries by removing the physical NICs from the device manager after conversion. In your case - according to pic1.jpg - it looks like you still have the two Broadcom NICs in the system which most likely had the IP address.

After you removed the "old" physical NICs from the VM's devices, you can assign the IP address to the "new" Intel NICs without getting the message.

André

0 Kudos
cngoh
Contributor
Contributor

Actually I already uninstalled the 2 broadcom NIC from device manager. But the problem still persists.

Thanks.

0 Kudos