Comments on: pc shuts down on LAN, works fine without LAN

By: r vishaal

r vishaal — Mon, 31 Aug 2009 16:41:09 +0000

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

By: kevinbeaver

kevinbeaver — Fri, 28 Aug 2009 20:20:26 +0000

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

By: petkoa

petkoa — Thu, 27 Aug 2009 19:09:30 +0000

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.

By: teicneoir

teicneoir — Thu, 27 Aug 2009 16:53:00 +0000

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?

By: dwiebesick

dwiebesick — Wed, 26 Aug 2009 15:55:14 +0000

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.

By: blankreg

blankreg — Wed, 26 Aug 2009 15:47:46 +0000

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.

By: carlosdl

carlosdl — Wed, 26 Aug 2009 13:41:26 +0000

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 ?