Windows XP and TCP/IP dieing..

dawks

Diamond Member
Oct 9, 1999
5,071
2
81
Ok, twice today out of nowhere, my 3com card in this system has lost its TCP connection. I can ping loopback, but nothing else.

Oddly enough IPX/SPX (which I use for LAN connections) on this same card still work fine.

After disabling, and re-enabling the LAN connection, TCP/IP works fine right after.

Nothing has changed in the system recently, no driver changes, no hardware updates.. no significant software installs.. So I'm not sure what the cause could be. Any ideas?

This system has been network trouble free for over two years now.
 

drag

Elite Member
Jul 4, 2002
8,708
0
0
Sounds like a simple bug.

WinXP is a lot better then Win98 when it comes to "spontanious corruption", but it's still their. More then likely a unanticipated combination of unusual effects broke it.

Like you had a periodical unchecked contention in the ethernet network and it created a corrupt TCP packet or something that the TCP/IP protocol stack couldn't rap it's brain around. ;)

Or maybe the latest service pack or patch didn't install as cleanly as the designers thought it did.

Or maybe a cosmic ray penitrated the computer case and flipped a bit around inside the ram (seriously weird stuff like that happens, that's why we have things like ECC and parity RAM. Ram errors like that supposedly happens about a average 2-3 times over a period of a year of continious usage for the average computer)

Who knows.

Just remember that if it happens agian you can reset the TCP/IP settings back to as-installed settings buy going:

netsh int ip reset logfile.txt
 

oLLie

Diamond Member
Jan 15, 2001
5,203
1
0
Might be something really trivial that you would never expect. My guess: bad cat5.
 

dawks

Diamond Member
Oct 9, 1999
5,071
2
81
I just looked in my Event Viewer and in the Application tab, I am getting tons upon tons of:
Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 5/24/2004
Time: 10:09:28 PM
User: N/A
Computer: UPSTAIRS
Description:
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 80070005 from line 44 of d:\nt_qxp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.[/quote

messages. They've just started in the last 3-4 hours. My connection has still be working fine.

Its also been taking about 3-4 minutes to log off now. I click the Log Off button, the screen clears normally, except the desktop background, then it just sits there, eventually playing the logoff music and finally returning to the login screen.
 

drag

Elite Member
Jul 4, 2002
8,708
0
0
That error means something is trying to run NTBackup or some other backup program.

Does that ring a bell? Did you scedual something to run that may of geeked out when TCP/IP failed or something?

If not it sounds suspicious.

Don't know what to do to fix it though...

source here
 

dawks

Diamond Member
Oct 9, 1999
5,071
2
81
The only thing I've messed with scheduleing wise is Diskeepers defrag scheduler.

i've done a few tweaks to the system and it appears to be alright. I'll check it out again over the next few days and see what happens.
 

Walay

Senior member
Apr 25, 2001
705
0
76
Err...interesteing, the same thing just happend to me over the week...
so i thought is a trojan or virus.. but coudln't find anything....
I can't even access my router....but i know the router is fine.