Changing NIC causes IP address warning

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

Hi,

I had to change a nic in my Windows 2k server and assign it the same range
of IP addresses as the failed one. However, I continually get warning
messages all the time I edit the nic config.

Since the old nic is fried and never coming back, how can I erase all
vestiges of the old nic in the server?

Thanks.
 
Hello Paul,

What did you mean with same range? A NIC should normally have one IP address.
Please post your config you are trying.

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
 
Windows 2000 allows a NIC to have multiple IP addresses, e.g.

NIC 1: 192.168.1.1
192.168.1.2
192.168.1.3
...

NIC 2: 10.0.0.10
10.0.0.11
10.0.0.12
...

One of the NICs failed, so I decided to replace both NIC 1 and NIC 2 with
new ones. When I assigned them the same IP address ranges, W2K warns of
potential conflicts if one of the old NICs is re-enabled. I understand this
is an issue and appreciate the warning, but I want to get rid of this
annoying message as it may confuse me, or another admin, who may not
remember that there was a hardware change previously.

By practical design, W2K should warn the user once, and then allow the new
NICs to inherit the old IP addresses without further warnings. But
unfortunately W2K continues to warn the user to much annoyance everytime the
TCP/IP properties is opened.

I am upgrading to W2003 soon and I hope this is addressed in the new
version. But before I upgrade, I want to get the current installation
working perfect.

Thanks.
 
Hello Paul,

It is possible but you should not configure it on a server. What is the reason
and what will you achive with this kind of config? Please give us more info
about the network (servers, roles etc) that we can help you better.

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
 
I don't want to go into details of all the possibilities of why one would
configure a server this way. If you are hosting web sites, running
proxies/reverse proxying, or running a muiltitude of services on a single
server you will have port contention, so you will need to utilise this
function. Thanks for your help, but at this point I doubt your networking
credentials if you do not understand these TCP/IP networking basics.

The question is not about this however, it is about removing the annoying
warning message. Can anyone help me with this problem?

Thanks.
 
Does the old nic show up in the device manager when you boot into safe mode?
If so, uninstall it from there.
Just a thought.
Louis
 
This just keeps getting better and better. I can't believe MS support has
stooped so low.

I try to seek advice on a design bug in W2k; a bug that requires a registry
fix.

First guy to respond I ended up giving advice back on the intricacies of the
TCP/IP stack.

Now this response takes the cake, the car, the house and all my life
savings. If the network adapater is no longer physically in the server (i.e.
it is now 50 feet in landfill), how on earth can it show up in the device
manager?

Is this a put on? Am I being taken the mickey out of? Come on guys...cut the
games!
 
If you want help don't insult everybody at the start gate, remember that
no one here caused the problem. This group is made up of peer users,
volunteers who offer their knowledge and advice without renumeration or
benefit from anyone. It is *not* staffed by the Microsoft support team.
Sometimes the helpers make mistakes or misinterpret the questions.
You can tell posters that their fix didn't help without resorting to
insults, be mindful of your comments to those who would help you.

You should know that yanking a device from the computer doesn't
"uninstall" it! Being that you did not properly remove it, it is now a
"ghosted" or "phantom" device, a device which is not currently connected
to the computer. To see it in the device manager copy this to a .bat
file and run it:

====================================================
set devmgr_show_nonpresent_devices=1
start devmgmt.msc

====================================================

When you run the batch file the Device Manager will open. Click on the
"View" menu and select "Show hidden devices" and uninstall the old
"phantom" NIC.

Device Manager Does Not Display Devices Not Currently Present in Windows
2000
http://support.microsoft.com/kb/241257

John
 
Thanks for the info.

Your flaming comments however should be left out of forums for the sake of
civility among peers, even if the advice offered is generous in nature.
Refer to advice from the first person and you will realise how wrong, and
dangerous it is.

I already get better advice from LUG, even though it comes with a rant about
how much this and that sucks. However, at least it fixes problems.

Thanks anyhow, even though it comes at cost.
 
*plonk*

Thanks for the info.

Your flaming comments however should be left out of forums for the sake of
civility among peers, even if the advice offered is generous in nature.
Refer to advice from the first person and you will realise how wrong, and
dangerous it is.

I already get better advice from LUG, even though it comes with a rant about
how much this and that sucks. However, at least it fixes problems.

Thanks anyhow, even though it comes at cost.
Click to expand...
 
Your advice did squiddly-dit!

I did exactly as you advised. The broken network adapter is not hidden as
you suspect it was. Nada, zilch, nil, nought, nothing...

However, the packet scheduler for that device is still there, and will not
uninstall, with a warning that the device is required to boot the server.

Thanks for trying anyhow.
 
Exactly who is the ****ing moron who yanked the card without uninstalling
it? Oh, that's right, you are!
(With apologies to the group.)
Louis
 
Hello Paul,

This happened because you didn't remove the IP'S before you removed and
unninstalled the old NICS. This kind of thing happens in W2K servers. If you
remove ip's, then save and turn off your server to place the new nics, then
you can assing the old ip's again in your new nics with no hussle. Even if
you try to place new nics in another PCI slot you'll get the ip conflict
error if you didn't remove the ip's from the old NICS before. But that's not
the issue right now. As for the error message, removing the "ghost" nics
must be the next thing to do, sorry i can't tell you how since i can't
figure right now how to do it, maybe a third party app.....

This is only to explain how that IP address warning originates in your case.

JR.
 
Remove the IP#s from the new nic (if they are there yet)
Use Regedit to find and remove any reference to the offening IP# and the "Name"
of the old Nic. There may be a few things it won't let you delete.

--
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.
-----------------------------------------------------
 
Back
Top