Plug the disabled nic into a (separate) hub or switch so that you can enable
it. Go into the TCP/IP settings of that nic and remove any leftover
configuration,...apply the changes,...then set the Nic to use DHCP,...apply
the changes,...then disable it again and unplug it from the switch/hub and
get rid of the switch/hub.
Then,...assuming there are no static routes in the OS's routing
table,...from a command prompt type:
"c:\> route /f"
This clears the routing table.
Reboot,...the table will rebuild accoriding to the Nic(s) configuration.
Recreate any legitament static routes in the table if there were any.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"James" <(E-Mail Removed)> wrote in message
news:1915F5AE-F383-4D61-858D-(E-Mail Removed)...
> I've got a problem. I have two NIC's on a Windows 2003 server but the
> second
> one is disabled. If I look at the TCP/IP settings under the GUI, it shows
> the correct gateway. This applies under the GUI where you can add
> multiple
> gateways as well. However, when I run ipconfig /all it lists two gateways
> under the same interface! Now, if I change the gateway under the GUI to
> something else and then back to the correct gateway, it appears correctly
> when I run ipconfig /all. However after rebooting, the two gateways once
> again return when I run ipconfig /all!
>
> The invalid gateway that keeps showing up is an old router from our
> recently
> updated infrastructure. The reaon why there are two NIC's on this server
> so
> we can add a SAN volume that's on a different subnet. Is this some sort
> of
> corruption? This is one out of four terminal servers. The others don't
> have
> this problem.
>
> Thanks in advance for your help.
>