Network Adapter -- at my wits' end.

  • Thread starter Thread starter dsc
  • Start date Start date
D

dsc

I have three machines linked by ethernet, accessing an ASDL connection
through a hub and a modem. Under Win98, they were working fine.

I took the plunge and bought a copy of XP home. With a couple of minor
glitches, it installed fine and was networking with the two Win98 computers
no problems.

Encouraged by this, I bought another copy of XP Home and installed it on
another computer, and that's when things went to heck in a cute little
yellow handbasket.

The second machine is an ASUS A7V8X motherboard, Athlon 2400+, 1Gb Ram, 80G
hard drive. The mother board has an onboard Broadcom Gigabit 5702 Ethernet
controller. As I said, everything was working fine under Win98, but I can't
connect to anything under XP.

I have tried and retried and retried the "Wizards."

For one thing, XP recognizes the Broadcom controller as a "1394" generic
adaptor, and automatically installs a generic driver. I downloaded the
latest XP drivers from Broadcom, but XP reports that these drivers don't
match my hardware, and refuses to install them. I can find no way to force
XP to install these drivers.

In any event, there is no communication coming out of the ethernet adaptor,
though XP reports that it is working properly. My hub shows one light for a
properly functioning connection, but for some reason now there are three
lights for this connection, even plugged in to a different port on the hub.

I tried plugging in an old ethernet card from before I changed to this
motherboard, and when plugged in to that card, the hub shows one light as it
should. XP refuses to use it, though, even after the onboard ethernet
adapter is disabled in system. It shows up in system with that yellow "not
working" symbol on it.

I can't even "activate" this copy of XP because I can't get on the net.

If anybody has any ideas of something else to try, I would be very grateful.

dsc
Yokohama
 
dsc said:
I have three machines linked by ethernet, accessing an ASDL connection
through a hub and a modem. Under Win98, they were working fine.

I took the plunge and bought a copy of XP home. With a couple of minor
glitches, it installed fine and was networking with the two Win98 computers
no problems.

Encouraged by this, I bought another copy of XP Home and installed it on
another computer, and that's when things went to heck in a cute little
yellow handbasket.

The second machine is an ASUS A7V8X motherboard, Athlon 2400+, 1Gb Ram, 80G
hard drive. The mother board has an onboard Broadcom Gigabit 5702 Ethernet
controller. As I said, everything was working fine under Win98, but I can't
connect to anything under XP.

I have tried and retried and retried the "Wizards."

For one thing, XP recognizes the Broadcom controller as a "1394" generic
adaptor, and automatically installs a generic driver. I downloaded the
latest XP drivers from Broadcom, but XP reports that these drivers don't
match my hardware, and refuses to install them. I can find no way to force
XP to install these drivers.

In any event, there is no communication coming out of the ethernet adaptor,
though XP reports that it is working properly. My hub shows one light for a
properly functioning connection, but for some reason now there are three
lights for this connection, even plugged in to a different port on the hub.

I tried plugging in an old ethernet card from before I changed to this
motherboard, and when plugged in to that card, the hub shows one light as it
should. XP refuses to use it, though, even after the onboard ethernet
adapter is disabled in system. It shows up in system with that yellow "not
working" symbol on it.

I can't even "activate" this copy of XP because I can't get on the net.

If anybody has any ideas of something else to try, I would be very grateful.

dsc
Yokohama
Click to expand...
1394 is firewire. Maybe you have firewire capability on you motherboard (not
necessarily hooked up, though) and XP is recognizing that and trying to
install it. When you try to change use the Broadcom drivers for the
firewire, of course it sees it as the wrong hardware.

If the hub is showing that there's a problem with the card, maybe there is.
The OS "sees" different things than the hub would. With the NIC with the
"not working" if you go into properties, it should give you some hint as to
why it's not working.

It might just be a matter of buying a new, cheap NIC and plugging it in and
seeing what happens. You should be able to get one for $10-15, with XP
drivers (if needed, most of the new ones just recognize automatically) which
may be better than tearing your hair out only to find that you've got one
defective NIC and one that XP won't support.
 
I am having the same issue but with the new 64bit edition of XP. I have contacted via email the mother board vendor and Microsoft support over the phone. If I ever resolve this I will let you know what the solution was.
 
Back
Top