Help: Network Cable Unplugged -- But It Is Plugged In And Working

[Stewart Berman]

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.

 

[smlunatick]

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.

 

[John Wunderlich]

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.

The main difference between Linux and Windows is the driver that is
used. What version of Windows driver are you using for your Yukon
card? From their website, the latest Windows 32-bit driver for a Yukon
card was dated Sept 17, 2007 (ver 10.22.6.3). If your driver is older
that that, you should connect to the Marvell website and
download/install their latest Windows driver.

<http://www.marvell.com/drivers>

HTH,
John

 

[Stewart Berman]

Booted the machine -- cable unplugged.

Updated driver -- cable plugged in.

It's amazing how the driver could reach out of the machine and plug the cable in.

Thanks.

 

[John Wunderlich]

Booted the machine -- cable unplugged.

Updated driver -- cable plugged in.

It's amazing how the driver could reach out of the machine and
plug the cable in.

Thanks.

.... actually, I think they found a way to keep your computer from
spitting-out the cable.

I'm glad you're up and running again.
-- John