Home > IT Answers > Networking > pc shuts down on LAN, works fine without LAN
Don2010
10 pts.
 pc shuts down on LAN, works fine without LAN
LAN, Network connectivity, Windows XP
If i use the pc without lan, it works fine no problem at all. But the moment i connect the pc on LAN, it shuts down. Using cross cable i can connect it to another desktop. But not possible to connect to LAN using straight cable. Tried changing port and cable but no use OS - win xp

Software/Hardware used:
OS - Winxp
ASKED: August 26, 2009  9:32 AM
UPDATED: August 31, 2009  4:41 PM
RELATED QUESTIONS
Answer Wiki:
This is extremely odd behavior. I would apply all updates to this problem computer (XP service pack 3) and update the network interface card (NIC) drivers. You will probably have to download these updates to another computer and use a CD/DVD or USB drive to copy the files to the problem computer. You should also scan the computer for malware. The <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=AD724AE0-E72D-4F54-9AB3-75B8EB148356&displaylang=en">Microsoft Malicious Software Removal Tool</a> is a good tool to start with. Did this computer ever work on a LAN? Do you remember when this problem started? If so, then maybe do a system restore to a date prior to the problem starting. If the problem continues after updating the system, then you are probably at the point of reinstalling the system from original media.
Last Wiki Answer Submitted:  August 26, 2009  11:53 am  by  Labnuke99   32,645 pts.
All Answer Wiki Contributors:  Labnuke99   32,645 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

Have you checked event logs ?
When exactly does the machine shut down ? when you plug the network cable ? when you try to join it to a domain ?

carlosdl
 63,535 pts.
 

You could try changing the NIC card, and see if you get the same issue. That should eliminate the hardware as the cause of this very strange behaviour.

BlankReg
 12,265 pts.
 

I just had this on a customer site. The computer was an HP dc5750. When NO cable was connected to the NIC, it would boot and run AOK. When we connected the NIC, the system some times would boot some times hang. If we booted with NO NIC connection into the XP Pro, and then connected the network cable, the system would immediately lock and sometime the screen would go to vertical blue strips.

The system was under warrenty so we changed the system board after we tried the usual things like BIIOS updates, NIC, video and other driver updates. We even played around for over a week with different NIC settings 10/100 full and half-duplex. In the end, system board was the fix.

I have been doing computers since 1979 and this was a first for me.

Dwiebesick
 2,220 pts.
 

I first thought that the NIC is creating a short when you connect the cable but you said that the NIC worked when you connect to another pc using a crossover cable. You were connected to the other pc through the NIC? If you were, then it is probably a software problem. Have you tried turning off your firewall and/or antivirus software to see if there are any conflicts?

Teicneoir
 220 pts.
 

Hi,

are you sure that some sasser is not shutting your UNPATCHED WINXP ? If it’s patched at SP2 level, don’t bother about sassers…

Petko A.

petkoa
 3,120 pts.
 

This sounds like a hardware issue…I’m experiencing a similar scenario with a Wi-Fi PC Card. Try changing the NIC.

KevinBeaver
 10,840 pts.
 

reset Internet Protocol (TCP/IP) using netsh

1. Click Start, and then click Run.
2. In the Open box, type cmd, and then click OK.
3. At the command prompt, type the following command, and then press ENTER:
netsh int ip reset resetlog.txt
NOTE: In the preceding command, “int” is the shortened form of the interface command.
4. Type exit, and then press ENTER.

reboot n try

R vishaal
 355 pts.