Realtime scenario: Windows 2003 server with two NICs in Mgmt and Dev networks started routing traffic via the Mgmt network

Realtime scenario:

We have Windows 2003 server which had two NICs, one each in a Mgmt network and Dev Zone network. This was essentially a Development server, and we used to connect to this server using the Dev Zone IP.

For some reason, its started acting up. When we connect the network cable to the management NIC on the server, the whole traffic started to route via the management network hence we were unable to connect to the server.

We tried changing the order of the NICs from Network Connections (ncpa.cpl) -> Advanced Menu -> Advanced Settings. This did not work.

So we changed the static routing from management IP to Development IP, as our network team suggested.

We reconfigure the routing as explained in a TechNet article below:


Add a static IP route

Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

To add a static IP route

  1. Open Command Prompt.
  2. At the command prompt, type: 

    route adddestinationmasksubnetmaskgatewaymetriccostmetricifinterface



Static IP route entry Definition


Specifies either an IP address or host name for the network or host.


Specifies a subnet mask to be associated with this route entry. If subnetmask is not specified, is used.


Specifies either an IP address or host name for the gateway or router to use when forwarding.


Assigns an integer cost metric (ranging from 1 through 9,999) to be used in calculating the fastest, most reliable, and/or least expensive routes. If costmetric is not specified, 1 is used.


Specifies the interface to be used for the route that uses the interface number. If an interface is not specified, the interface to be used for the route is determined from the gateway IP address.

  1. For example, to add a static route to the network that uses a subnet mask of, a gateway of, and a cost metric of 2, you type the following at a command prompt:

    route add mask metric 2


  • To open a command prompt, click Start, point to All programs, point to Accessories, and then click Command prompt
  • To make a static route persistent, you can either enter route add commands in a batch file that is run during system startup or use the -p option when adding routes.
  • Routes added by using the -p option are stored in the registry under the following key: 

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip \Parameters\PersistentRoutes

  • All symbolic names used for destination or gateway are looked up in the network and computer name database files (Networks and Hosts), which are stored in the local systemroot\System32\Drivers\Etc folder.
  • If a route addition fails, you can use the tracert command to verify that the gateway specified is directly reachable from the same subnet as this computer.


How to Find a Lost, Missing, Hidden or Removed Network Card (NIC) or Other Device and Even Remove it

How to Find a Lost, Missing, Hidden or Removed Network Card (NIC) or Other Device and Even Remove it

In a scenario where you have physically removed hardware from a machine you can no longer see it in device manager.  This does not mean that it is gone.  Evidence of that is, if for example you had a network card that had a Static IP address set and you remove the card and add a new one then try to set the IP address to the same as the old NIC you will get an error message. The error might look something like “The IP address you have entered for this network adapter is already assigned to another adapter (Microsoft Virtual machine Bus Network Adapter #3) which is no longer present in the computer.  If the same address is assigned to both adapters and they both become active, only one of them will use this address.  This may result in incorrect system configuration”.  In Windows Server 2008 R2 and Windows 7 it actually gives you an opportunity to “remove the static IP configuration for the absent adapter”. If you say Yes, this will eliminate the IP conflict problem but does not solve the problem of the adapter still being present in the machine.  In older versions of the OS, it was even worse because every time you go into network properties it gives you an error message.  Another way this comes up is if you move a virtual machine from one host to another.  Like in the case of moving from Virtual Server 2005 R2 to Hyper-V or perhaps you are moving from one Hyper-V machine to another but you did not do an export, you just moved the VHD’s and created a new machine. 

IP Address Already Assigned to another adapter


Getting rid of these old devices is actually very simple.  Well, it is simple if you know how 😉
Before you proceed, I recommend that you confirm that you have a good backup.  I have never had a problem with this but hey, it is your server not mine.
Description What to do
Step 1: You need to run a command prompt so you can set an environment variable prior to opening the Device Manager 
This will bring up a command window
Click Start – Type the following command and then press ENTER 

Step 2: We have the command window open.  We now need to set the variable (that is the “set” line and then with the variable set, we need to run Device Manager.  The file name for the Device Manager snap-in is devmgmt.msc.  The first line will not appear to do anything but it is setting the environment for next step.  The second command will actually open the Device Manager but it will be in a “special” mode which allows you to show devices that no longer exists.

Type the following commands pressing ENTER after each line

set devmgr_show_nonpresent_devices=1 
Step 3: Now all we have to do is show hidden devices and you will be able to access the devices that are not present in the machine.  This will also turn a checkbox on in front of the Show Hidden Devices menu option. In this Special Device Manager Window; on the menu, click View then Show Hidden Devices
Step 4: Now you can just go find the adapter or device that is missing and delete it!  
Expand the network adapter (or whatever category of device) and look for the device that needs to be removed.  The error message that you got should tell you the “name” of the device so you just have to go find that named device.  You may also notice while you are there that the icon for the “non-present” or missing device is slightly subdued so that will make it easier to find it if you have many devices in a category. 

See screen shot below

Expand the network adapter (or whatever category of device) and look for the device that needs to be removed. 

Right-Click the Device and select Uninstall

It IS easy if you know how.  Now you know how!!!
On the Warning “You are about to uninstall this device from your computer” just click OK
IMPORTANT Note: Lastly, if there are other devices that are subdued / hidden, please to not just go in and delete them all.  If you do, you are asking for trouble.  Just get rid of the things that you know are gone for good and are not coming back!  If you are not absolutely positive, do not remove it.  If you do anyway, better have that backup handy 🙂 

Also, remember, if you change too much stuff at once, you may have to reactivate Windows

Restore from Backup… Just kidding 🙂