Carlosdl
29770 pts. | Aug 26 2009 1:41PM GMT
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 ?
BlankReg
11270 pts. | Aug 26 2009 3:47PM GMT
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.
Dwiebesick
1760 pts. | Aug 26 2009 3:55PM GMT
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.
Teicneoir
165 pts. | Aug 27 2009 4:53PM GMT
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?
Petkoa
1005 pts. | Aug 27 2009 7:09PM GMT
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.
KevinBeaver
7610 pts. | Aug 28 2009 8:20PM GMT
This sounds like a hardware issue…I’m experiencing a similar scenario with a Wi-Fi PC Card. Try changing the NIC.
R vishaal
355 pts. | Aug 31 2009 4:41PM GMT
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






