PDA

View Full Version : SP2 wipes out my NICs in Network connections and device manager


Sandy
October 2nd 04, 08:47 PM
After insalling SP2, I can't see any my ethernet
adapters... 2 are Intel Pro100's and one is a LinkSys
10/100 with a realtek chip. I took out the LinkSys and
moved one of the Intel's to different slot hoping trigger
plug-and-play. This had no effect. I can't see them
with the device manager or in Network connections.

However ifconfig from command line does see them and the
one configured for dhcp has received an address.

Hans-Georg Michna
October 3rd 04, 09:28 AM
On Sat, 2 Oct 2004 12:47:08 -0700, "Sandy"
> wrote:

>After insalling SP2, I can't see any my ethernet
>adapters... 2 are Intel Pro100's and one is a LinkSys
>10/100 with a realtek chip. I took out the LinkSys and
>moved one of the Intel's to different slot hoping trigger
>plug-and-play. This had no effect. I can't see them
>with the device manager or in Network connections.
>
>However ifconfig from command line does see them and the
>one configured for dhcp has received an address.

Sandy,

please have a look at http://www.michna.com/kb/wxnet.htm.

Hans-Georg

--
No mail, please.

Sandy
October 6th 04, 07:08 PM
re:
>please have a look at http://www.michna.com/kb/wxnet.htm.
>

Sorry that did not help.

Spend most of Saturday on phone with Microsoft support.
Problem was not solved. I rolled back to a checkpoint
before the install to SP1 and finally got things working
again.

I guess I will wait longer for SP2.

Hans-Georg Michna
October 7th 04, 08:07 AM
>>please have a look at http://www.michna.com/kb/wxnet.htm.

On Wed, 6 Oct 2004 11:08:11 -0700, "Sandy"
> wrote:

>Sorry that did not help.
>
>Spend most of Saturday on phone with Microsoft support.
>Problem was not solved. I rolled back to a checkpoint
>before the install to SP1 and finally got things working
>again.
>
>I guess I will wait longer for SP2.

Sandy,

thanks for reporting back.

I fear that waiting will not help. The cause of the problem is
not in Service Pack 2. The cause is most likely that something
is wrong with the existing installation, and it will probably
not go away on its own.

Since your problem at first looks like the well-known one
described on the linked page, but the equally well-known
solution didn't work, I'd be very curious to learn about a new
solution if you find one.

Hans-Georg

--
No mail, please.

Google