NIC Conflict (?)

Windows Server 2003 R2 SP2 installed on an Intel server platform with
two (2) network interfaces (NICs) on the motherboard. Had disabled
NIC#2 in BIOS and using NIC#1. NIC#1 failed and is no longer
appearing in Device Manager. I have now disabled NIC#1 and enabled
NIC#2 in BIOS. After re-booting Windows, I configured the newly
discovered NIC (Local Area Connection 2)(the previous connection was
just Local Area Connection) the same as NIC#1 had been configured.
Upon closing the applet, an error message appeared stating the
assigned IP address was the same as a previously configured, but
inactive, NIC and asked if I wanted to change the IP or keep it. I
chose to keep it as many other devices on the network are configured
to use that IP address for accessing the server. Upon doing so, the
applet took quite a while to close and no error messages appeared in
Event Viewer. The server now seems to be working fine again. Upon
going back into properties of Local Area Connection 2 to change the
DNS setting to 127.0.0.1 and closing the applet, the same error
message was presented. This time, when answering "no" the applet
closed much faster than the first time. My question is how can I
delete any reference in Windows to the previously used NIC so as not
to have Windows believe there is a conflict between the previously
used NIC and the currently used NIC?

Thanks.
--
System Administrator
Sprotte + Watson Architecture and Planning
Vista, CA

"System Administrator" <(E-Mail Removed)> wrote:
<snip for space>
> My question is how can I
> delete any reference in Windows to the previously used NIC so as not
> to have Windows believe there is a conflict between the previously
> used NIC and the currently used NIC?

In Device manager, click on View | Show hidden devices. You should see the
disabled NIC there and uninstall it.

ThePro

Thanks for the suggestion, but the now disabled NIC does not appear in
Device Manager, even when Show hidden devices is invoked. Any other
suggestions? Thanks.


On Fri, 14 Dec 2007 16:09:01 -0500, "ThePro"
<mcthepro_@nospam.hotmail.com> wrote:

>"System Administrator" <(E-Mail Removed)> wrote:
><snip for space>
>> My question is how can I
>> delete any reference in Windows to the previously used NIC so as not
>> to have Windows believe there is a conflict between the previously
>> used NIC and the currently used NIC?
>
>In Device manager, click on View | Show hidden devices. You should see the
>disabled NIC there and uninstall it.
>
>ThePro

--
Bob Felton

Re-enable it in Bios and try again.

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

"System Administrator" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
> Thanks for the suggestion, but the now disabled NIC does not appear in
> Device Manager, even when Show hidden devices is invoked. Any other
> suggestions? Thanks.
>
>
> On Fri, 14 Dec 2007 16:09:01 -0500, "ThePro"
> <mcthepro_@nospam.hotmail.com> wrote:
>
>>"System Administrator" <(E-Mail Removed)> wrote:
>><snip for space>
>>> My question is how can I
>>> delete any reference in Windows to the previously used NIC so as not
>>> to have Windows believe there is a conflict between the previously
>>> used NIC and the currently used NIC?
>>
>>In Device manager, click on View | Show hidden devices. You should see the
>>disabled NIC there and uninstall it.
>>
>>ThePro
>
> --
> Bob Felton

"System Administrator" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
> going back into properties of Local Area Connection 2 to change the
> DNS setting to 127.0.0.1 and closing the applet, the same error

The DNS should be set to the actual IP# of the machine instead of 127.0.0.1.

I used to do it that way too, until people kept telling me to stop doing
that. Personally, it worked that way for me too, but there were supposed to
be some evil things that could happen if I used 127.0.0.1.

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

* Phillip Windell (Fri, 14 Dec 2007 16:27:38 -0600)
> "System Administrator" <(E-Mail Removed)> wrote in
> message news:(E-Mail Removed)...
> > going back into properties of Local Area Connection 2 to change the
> > DNS setting to 127.0.0.1 and closing the applet, the same error
>
> The DNS should be set to the actual IP# of the machine instead of 127.0.0.1.
>
> I used to do it that way too, until people kept telling me to stop doing
> that. Personally, it worked that way for me too, but there were supposed to
> be some evil things that could happen if I used 127.0.0.1.

Definitely a case for MTV's myth busters. The only problem I ever
encountered was with DNS' WINS forward lookup.

Thorsten

So, which is it? 127.0.0.1 or the actual IP address?


On Fri, 14 Dec 2007 22:45:02 -0000, Thorsten Kampe
<(E-Mail Removed)> wrote:

>* Phillip Windell (Fri, 14 Dec 2007 16:27:38 -0600)
>> "System Administrator" <(E-Mail Removed)> wrote in
>> message news:(E-Mail Removed)...
>> > going back into properties of Local Area Connection 2 to change the
>> > DNS setting to 127.0.0.1 and closing the applet, the same error
>>
>> The DNS should be set to the actual IP# of the machine instead of 127.0.0.1.
>>
>> I used to do it that way too, until people kept telling me to stop doing
>> that. Personally, it worked that way for me too, but there were supposed to
>> be some evil things that could happen if I used 127.0.0.1.
>
>Definitely a case for MTV's myth busters. The only problem I ever
>encountered was with DNS' WINS forward lookup.
>
>Thorsten

--
System Administrator
Sprotte + Watson Architecture and Planning
Vista, CA

OK, I will try. But won't that definitely cause an IP conflict
between the two NICs? Should I temporarily change the IP of NIC#2
while doing your suggestion?


On Fri, 14 Dec 2007 16:24:02 -0600, "Phillip Windell"
<(E-Mail Removed)> wrote:

>Re-enable it in Bios and try again.

--
System Administrator
Sprotte + Watson Architecture and Planning
Vista, CA

* System Administrator (Fri, 14 Dec 2007 15:45:15 -0800)
> So, which is it? 127.0.0.1 or the actual IP address?

As I said: both are fine and both are the "actual" IP addresses.

Thorsten

I did change the IP address of the active NIC, shutdown and booted to
BIOS. I then re-enabled the previously used NIC (keeping the
currently used NIC enabled) and booted to Windows. I could not delete
the previously used NIC in Device Manager as it did not appear, again.
I guess it has failed to the point where Windows no longer detects it.
So, I'm back to my original question.


On Fri, 14 Dec 2007 16:24:02 -0600, "Phillip Windell"
<(E-Mail Removed)> wrote:

>Re-enable it in Bios and try again.

--
System Administrator
Sprotte + Watson Architecture and Planning
Vista, CA