• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Help! XP shows Cable unplugged ...

dandruff

Golden Member
Help! XP Home shows Cable unplugged for onboard LAN ... i have already checked the wall jack and the cable with another computer and it works .. so i know its not the cable and the wall jack ... so i got a D-Link DFE-530TX+ NIC ($15 at Office max) ...

under device manager both are shown as working properly - uninstalled and reinstalled drivers on both ...

i disabled the onboard LAN under BIOS .. installed the new NIC and still the same thing ... says cable disconnected ...

since it is unplugged ... it wont let me do ipcfg / renew or anything ...

what am i missing ehre .. turned off windows firewall .. nothong ..no green llights ...

any help would be really appreicated .. TIA!


 
Are you sure the cable disconnected is for the right NIC? If the two were running, then the one that isn't plugged in should report that it is unplugged.
 
The "Cable Unplugged" has nothing to do with a firewall or protocol settings. There are a few possibilities for this...

1. If one end of the cable is plugged in, but the other end is not.

2. If the cable is wired improperly. If you are connecting peer to peer with only two clients and no hub, then you need to cross the signal. IIRC, the 3rd and the 6th wire.

So there you have it... Actually, for purposes of Troubleshooting, the new "Cable Unplugged" is totally awesome and saves a lot of troubleshootig.

Edit ** Just so I am clear on the matter, you have a cable problem.
 
thanks ... but if both NICs are enable - i get 2 cable unplugged icons ...

the cable is working fine with another computer - so why not with this one? i ahve tried with other cable and same thing ...

i searched something on google which recommended changing the speeds - 10 half duplex .. then 100 half and so on ... i tried that - and the icon changes breifly to a yellow dot circling and back to unplugged ...

right now i left it at auto-negotiation and the yellow dot is back - says limited or no connection - shows 10 as speed and a yellow triangle with exclamation - tried repair - went back to unplugged ...

the onboard NIC used to work fine with the same wall jack and the cable till friday .. came to work monday ..not working ... 🙁 please help ....
 
Not doubting you here, but I am doubting that source... Perhaps I just have never seen it. But I certainly attest to not having a DHCP Server and networking a peer to peer where "specify address" was NOT checked and the cable did NOT say "cable disconnected". Translation, I doubt it is DHCP. I am not the know-it all tech, but I am quite verse on home, small business networks and I guess I have only seen "media disconnected" point to cable issues. Basically, nearly 1,000+ times it has been cable related and never protocol related. But I do leave it open as a possibility now.

Edit ** In fact, I was walking a guy through a network on the phone with that problem and he must have recrimped that cable end (both of them) 20 times... He said he was absolutely positive it was wired correctly. I was like, it can't be... Then he asked me if giving the computers IP's would fix it. I told him "No, it won't... But we can try, I have been wrong before"... So, we specified the IP's within the normal range of 192.168.100.1 (.2 for the other machine) same subnect mask and all that junk... The result? Still "Media Disconnected". Something was wrong with the cable... Fixed now and working fine a few days later.

The only way I could see the DHCP server causing this is if the DHCP server is physically powered off and that is the only source that the computer connects too. But that would be the result of the PC being powered off, rather than anything to do with DHCP.
 
most likely it is the cable.

some nics are smart enough to detect improper wiring, some are not.

not getting a link on either side of the wire is 99% a cabling problem. If this is a homemade cable or user mucked with cable then it is 100%. So trust the link lights on both sides of the link and not what windows is telling you. That will get the cabling problem out of the way, then we can focus on bad hardware and drivers.

As far as speed/duplex - leave this alone an make it auto.

-edit- sorry to be so blunt, this is stricly a layer1 problem and can be nothing else except possibly driver. just because the cable "works" with one nic doensn't mean it is good.
 
I have had pesky cable problems a couple of times. Once my network card wasn't centered into the case slot. The case kept the little lock that snaps in from moving to the locked position. When I would move the computer or the vibration of the fans would work the connector out. The other time I had the problem the lock had actually broken on the connector and the same thing would occur.

You may have a broken wire in the cable. If the other computers lan connector is in a different position ( ie higher or lower to the desk) it may be moving the wire enough to short the wire. When you plug it back in your computer it goes back to open. Just a theory but you should try a new wire or at least another one.
 
i have tried with other cables (that work elsewhere - i have now checked with 3 working cables and three working outlets 🙁 please help ...

any settings that i need to play with ?

everytime i reinstall - windows comes up with a new number for the Lan connection - like Lan Connection 6 or 7 and so on ... how can i delete any references to old lan connections? where does windows store that info? TIA!
 
The old network connections are Not doing any thing, it is just cosmetics.

Removing them is Not just a registry issue it is a combination of changing attributes of hidden devices in the device manger and a lot of Rebooting. I would leave it alone, too many people mess-up when they trying it.

Otherwise, in General you can debug the Network?s Setting of the computer by following these steps.

Step One. Check the Network parameters in the Computer?s Device Manager. Make sure that the drivers are installed correctly; there is No IRQ conflict, and No Ghost installation. http://www.ezlan.net/faq#ghost

Step Two. Verify the Basic network setting in the OS, http://www.ezlan.net/Installing#verify

If the above two Steps indicates that every thing looks good but functionally it does not work.

Step Three. Check (and repair if necessary) the Socket Layers, Winsock, and or refresh the TCP/IP Stack. http://www.ezlan.net/clean#refreshnet

If need to Reinstall; Log to this page it have a lot of links to instructions to Windows Network Settings, http://www.ezlan.net/Installing.html

:sun:
 
Back
Top