Re: Help: Network Cable Unplugged -- But It Is Plugged In And Working
- From: smlunatick <yveslec@xxxxxxxxx>
- Date: Mon, 24 Sep 2007 11:13:48 -0700
On Sep 23, 7:35 pm, Stewart Berman <sabm...@xxxxxxxxxxxx> wrote:
Windows XP SP2 With All Critical Updates
I have a machine with a Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller. The
machine has two IDE hard drives -- one with Windows XP and the other with a Linux deriv. If I boot
from the Windows XP drive the system tells me there is a network cable unplugged. If I boot from
the Linux drive the system has no trouble using the network controller and connecting to my Linksys
router. Since the Linux system is using exactly the same network controller it is clear that the
cable is plugged in and functioning.
I don't recall any changes to the system that might have caused the Windows XP system to be unable
to access the network. I have tried uninstalling the controller and reinstalling -- still says the
cable is unplugged. (Please note that I do a full power down before switch between Linux and
Windows.)
Any suggestions as to what might cause the Windows XP system think the network cable was unplugged
when it isn't would be appreciated.
Have you considered "changing" the cable for a test? Gigabit network
adapters are extremely "fussy" on the type of cables used. You might
be able to "tweak" the Windows driver, but this requires a "hit or
miss" style of testing.
.
- References:
- Help: Network Cable Unplugged -- But It Is Plugged In And Working
- From: Stewart Berman
- Help: Network Cable Unplugged -- But It Is Plugged In And Working
- Prev by Date: Re: Annoying "computer must be restarted" message - Update
- Next by Date: internet explorer
- Previous by thread: Help: Network Cable Unplugged -- But It Is Plugged In And Working
- Next by thread: Re: Help: Network Cable Unplugged -- But It Is Plugged In And Working
- Index(es):
Relevant Pages
|