VirtuallyAware

Experiences in a Virtual World

Warning – Multiple Default Gateways…

with one comment

I have seen this warning many times when doing P2V migrations or doing manual V2V migrations from my Virtual Server 2005 environment to Hyper-V, so I decided to share my solution.  It is caused by having orphaned NIC settings within your registry.  This is most commonly reveals itself when you try to reapply an IP Address after a migration but can happen in real hardware if you pull one NIC card and insert another.  By trying to give the new NIC card the same IP as the old one you will receive this warning since the system thinks you have two NIC on the same gateway.  Even though you cannot see the old NIC graphically, all of its previous settings are still in the registry.  Due to the wonders of plug and play, the system is waiting for, someday, the old NIC to return.  You can simply say yes to this message if the old NIC is not there or will not return, but every time you open up your NIC settings you will be presented with this message.  More of an annoyance than anything else, but here is how to remove it.

*Do the following all before you configure the IP Address of your server.

1. Run Regedit

2. Click Edit and then Find

3. Enter the Previous IP Address of your server in the Find dialogue box

4. Delete out all GUID Keys in the following locations that include the IP Address you are searching for. (Keep hitting F3)

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\Tcpip\Parameters\Interfaces\{NIC DEVICE GUID}

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\Tcpip\Parameters\Interfaces\{NIC DEVICE GUID}

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\services\Tcpip\Parameters\Interfaces\{NIC DEVICE GUID}

 

 

If you fill in your IP Address information now, you should not get the multiple gateways error.  If you do, go back through the registry and search for the previous IP address again.

 

-Rob

About these ads

Written by VirtuallyAware

May 2, 2010 at 10:40 PM

One Response

Subscribe to comments with RSS.

  1. Nice fix. Been fighting this on some P2V and V2V going back and forth between ESXi and Hyper-V. My other problem was hidden NIC. I followed this article to fix that. Your article and the below should help most people with this issue I believe. Thank you!

    Hi,

    You can try this:
    http://support.microsoft.com/kb/315539/en-us

    To work around this behavior and display devices when you click Show hidden devices:

    Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
    At a command prompt, type the following command , and then press ENTER:
    set devmgr_show_nonpresent_devices=1
    Type the following command a command prompt, and then press ENTER:
    start devmgmt.msc
    Troubleshoot the devices and drivers in Device Manager.

    NOTE: Click Show hidden devices on the View menu in Device Managers before you can see devices that are not connected to the computer.
    When you finish troubleshooting, close Device Manager.
    Type exit at the command prompt.

    brian

    April 24, 2013 at 12:01 AM


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 283 other followers

%d bloggers like this: