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.

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

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.


"Myweb" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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.
>
> > 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,

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.

> 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.
>
> "Myweb" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> 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.
>>
>>> 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.
>>>

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.



"Myweb" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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.
>
> > 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.
> >
> > "Myweb" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> 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.
> >>
> >>> 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.
> >>>
>
>

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

"Paul" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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.
>
>
>
> "Myweb" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > 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.
> >
> > > 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.
> > >
> > > "Myweb" <(E-Mail Removed)> wrote in message
> > > news:(E-Mail Removed)...
> > >> 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.
> > >>
> > >>> 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.
> > >>>
> >
> >
>
>

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!



"3c273" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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
>
> "Paul" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > 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.
> >
> >
> >
> > "Myweb" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > 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.
> > >
> > > > 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.
> > > >
> > > > "Myweb" <(E-Mail Removed)> wrote in message
> > > > news:(E-Mail Removed)...
> > > >> 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.
> > > >>
> > > >>> 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.
> > > >>>
> > >
> > >
> >
> >
>
>

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

Paul wrote:

> 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!
>
>
>
> "3c273" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>
>>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
>>
>>"Paul" <(E-Mail Removed)> wrote in message
>>news:(E-Mail Removed)...
>>
>>>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.
>>>
>>>
>>>
>>>"Myweb" <(E-Mail Removed)> wrote in message
>>>news:(E-Mail Removed)...
>>>
>>>>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.
>>>>
>>>>
>>>>>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.
>>>>>
>>>>>"Myweb" <(E-Mail Removed)> wrote in message
>>>>>news:(E-Mail Removed)...
>>>>>
>>>>>>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.
>>>>>>
>>>>>>
>>>>>>>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.
>>>>>>>
>>>>
>>>>
>>>
>>
>
>

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.



"John John" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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
>
> Paul wrote:
>
> > 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!
> >
> >
> >
> > "3c273" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >
> >>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
> >>
> >>"Paul" <(E-Mail Removed)> wrote in message
> >>news:(E-Mail Removed)...
> >>
> >>>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.
> >>>
> >>>
> >>>
> >>>"Myweb" <(E-Mail Removed)> wrote in message
> >>>news:(E-Mail Removed)...
> >>>
> >>>>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.
> >>>>
> >>>>
> >>>>>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.
> >>>>>
> >>>>>"Myweb" <(E-Mail Removed)> wrote in message
> >>>>>news:(E-Mail Removed)...
> >>>>>
> >>>>>>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.
> >>>>>>
> >>>>>>
> >>>>>>>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.
> >>>>>>>
> >>>>
> >>>>
> >>>
> >>
> >
> >

*plonk*


Paul wrote:

> 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.
>
>
>
> "John John" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>
>>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
>>
>>Paul wrote:
>>
>>
>>>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!
>>>
>>>
>>>
>>>"3c273" <(E-Mail Removed)> wrote in message
>>>news:(E-Mail Removed)...
>>>
>>>
>>>>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
>>>>
>>>>"Paul" <(E-Mail Removed)> wrote in message
>>>>news:(E-Mail Removed)...
>>>>
>>>>
>>>>>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.
>>>>>
>>>>>
>>>>>
>>>>>"Myweb" <(E-Mail Removed)> wrote in message
>>>>>news:(E-Mail Removed)...
>>>>>
>>>>>
>>>>>>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.
>>>>>>
>>>>>>
>>>>>>
>>>>>>>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.
>>>>>>>
>>>>>>>"Myweb" <(E-Mail Removed)> wrote in message
>>>>>>>news:(E-Mail Removed)...
>>>>>>>
>>>>>>>
>>>>>>>>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.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>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.
>>>>>>>>>
>>>>>>
>>>>>>
>>>
>
>