Tuwoki
New Member
- Reaction score
- 0
- Location
- Cairns, Australia
Hi, I have a client who has a desktop (Dell something) running Windows XP. She reported that the LAN port is no longer working. Did the usual over the phone tests (change cables and router ports, confirm it works on another computer) and it appeared to be limited to the particular PC.
Thinking that the LAN port is dead (surge/spike?), I did a quick visit while on another job and established the following:
- The builtin LAN port when no cable is connected is active and blinking. The Windows XP network connection indicates that it is searching for a DHCP server and eventually self assigns (yes with no cable connected)
- Plug in a LAN cable is the port goes dead instantly and Windows XP indicates no cable connected. Unplugging the cable and the LAN port goes back to the above point
- Uninstalled, restarted, reinstalled the LAN port drivers, same
- Installed a PCI Ethernet card, but no reaction when connecting a LAN cable. Tried different PCI ports, cables, ports on the router. XP indicates no cable connected. Confirmed the card worked in another XP machine onsite.
- Not having anything else with me at the time, I did a system restore back 2 months thinking if it is a software issue (maybe a bad DLL/Windows/Driver Update?) this may fix it, but no difference.
- Disabled the onboard LAN in BIOS and disconnected/pulled everything not essential from the system (additional PCI cards, DVD, etc) and again same problem.
- Mem test showed no issues
- Thinking that more likely a hardware issue, maybe PCI but the PC also has a Firewire and TV card which confirmed working fine (tried the ethernet card in both those slots and same problem)
I am doing a revisit next week to try a bootable copy of XP or/and a USB-Ethernet adapter.
Has anyone seen something this before?
Thinking that the LAN port is dead (surge/spike?), I did a quick visit while on another job and established the following:
- The builtin LAN port when no cable is connected is active and blinking. The Windows XP network connection indicates that it is searching for a DHCP server and eventually self assigns (yes with no cable connected)
- Plug in a LAN cable is the port goes dead instantly and Windows XP indicates no cable connected. Unplugging the cable and the LAN port goes back to the above point
- Uninstalled, restarted, reinstalled the LAN port drivers, same
- Installed a PCI Ethernet card, but no reaction when connecting a LAN cable. Tried different PCI ports, cables, ports on the router. XP indicates no cable connected. Confirmed the card worked in another XP machine onsite.
- Not having anything else with me at the time, I did a system restore back 2 months thinking if it is a software issue (maybe a bad DLL/Windows/Driver Update?) this may fix it, but no difference.
- Disabled the onboard LAN in BIOS and disconnected/pulled everything not essential from the system (additional PCI cards, DVD, etc) and again same problem.
- Mem test showed no issues
- Thinking that more likely a hardware issue, maybe PCI but the PC also has a Firewire and TV card which confirmed working fine (tried the ethernet card in both those slots and same problem)
I am doing a revisit next week to try a bootable copy of XP or/and a USB-Ethernet adapter.
Has anyone seen something this before?