TCP/IP problems in windows XP

[W]

I seem to have a problem with my network drivers in Windows XP, at random times the transfer of data to my comp via TCP/IP connections just stop. Like giant lag; sometimes it's enough to disconnect the connections, sometimes now. If I keep a ping -t running in the background, it keeps getting replies, and UDP packets still get trough, but someone pinging me from the outside will get "Request timed out".

Now I've tried reinstalling the drivers for my 3com 3c990-TX card, also downloading the newest drivers off 3coms website, so I can be fairly sure that's not where the problem is. But I've never reinstalled TCP/IP in XP nor figured out how to do it.

[edit]Google is my friend and found http://support.microsoft.com/default...b;en-us;299357, I'll try that when I get home. Does anyone have any other ideas?

[zenopus]

Sounds like the issue might very well be external to your PC.
How is your PC connected to the internet?

[W]

Originally posted by zenopus
Sounds like the issue might very well be external to your PC.
How is your PC connected to the internet?

I forgot to say, when diagnosing the connection from the outside (from work) the problem is always before the last gateway and my comp. Anyway, if it weren't a TCP/IP problem why would I still be able to ping other computers while they can't ping me?

I have a very stable line with catchcom.no, the line also holds several webservers, which I've not seen have any problems

[zenopus]

Originally posted by W
I have a very stable line with catchcom.no, the line also holds several webservers, which I've not seen have any problems

So you are on 24/7 - with a decent pipe (2mb E1, or cable, or summat).

... when diagnosing the connection from the outside (from work) the problem is always before the last gateway and my comp.

That last gateway - is that located at your ISP or is it local (on your LAN)?

... if it weren't a TCP/IP problem why would I still be able to ping other computers while they can't ping me?

Well, some equipment can be configured to drop ICMP packets - incoming and/or outgoing - but if incoming ICMP packets are dropped, incoming pings should never work - maybe your ISP is having problems or is experimenting with various configurations.

I would install a packet sniffer on another machine on the LAN and check if the pings reach the LAN.

[W]

Originally posted by zenopus
So you are on 24/7 - with a decent pipe (2mb E1, or cable, or summat).
That last gateway - is that located at your ISP or is it local (on your LAN)?
Well, some equipment can be configured to drop ICMP packets - incoming and/or outgoing - but if incoming ICMP packets are dropped, incoming pings should never work - maybe your ISP is having problems or is experimenting with various configurations.

I would install a packet sniffer on another machine on the LAN and check if the pings reach the LAN.

The packets go out, but my comp don't accept the incomming packets. It's definately a TCP/IP problem, but XP is gay and don't have any easy way to really reinstall it.

Oh, it's a 2Mbit SDSL and the symptoms are the same with servers on the lan as with servers on the outside. Defo not an ISP problem.
And no, no gateway here, I use a switch, and I've tried switching ports on the switch.

[zenopus]

Quite, if the behaviour is the same locally, the problem is likely to be on the PC.

But looking at the 3com webby, unless I'm mistaken, the XP drivers for the 990 series NICs are
UNSUPPORTED - 3Com does not offer technical support for UNSUPPORTED drivers.

So maybe you should try with another card.

[W]

Originally posted by zenopus
Quite, if the behaviour is the same locally, the problem is likely to be on the PC.

But looking at the 3com webby, unless I'm mistaken, the XP drivers for the 990 series NICs are
UNSUPPORTED - 3Com does not offer technical support for UNSUPPORTED drivers.

So maybe you should try with another card.

It worked fine for about a year, and as I said, I've already reinstalled the driver, so I doubt that's it...

[zenopus]

OFC it could be a hardware failure.
Sometimes a card seems to work fine but shows intermittent failures once it gets hot.
The NIC could have developed this flaw recently or maybe you put in a new card recently - or something else is causing a temperature increase.

Just trying to help you avoid having to reinstall XP.

[W]

Originally posted by zenopus
OFC it could be a hardware failure.
Sometimes a card seems to work fine but shows intermittent failures once it gets hot.
The NIC could have developed this flaw recently or maybe you put in a new card recently - or something else is causing a temperature increase.

Just trying to help you avoid having to reinstall XP.

Yes, that's pretty much what my options comes down to; buying a new nic and trying, or reinstalling XP. I was hoping there was some easier way to fix the TCP/IP if that's it, but I guess I'd rather get a new card (or possibly some more cooling equipment, my HD's generate excessive heat atm)

[EDIT so I don't look like a fool]: The HDs are OUTSIDE the case atm, so that's not what's causing the NIC to fail. Tho it might just be heat related just the same

[W]

Pinging 213.142.64.170 with 32 bytes of data:

Request timed out.
Request timed out.
General failure.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Reply from 213.142.64.170: bytes=32 time=4ms TTL=247
Reply from 213.142.64.170: bytes=32 time=4ms TTL=247
Reply from 213.142.64.170: bytes=32 time=5ms TTL=247
Reply from 213.142.64.170: bytes=32 time=6ms TTL=247
Reply from 213.142.64.170: bytes=32 time=4ms TTL=247
Reply from 213.142.64.170: bytes=32 time=4ms TTL=247
Reply from 213.142.64.170: bytes=32 time=4ms TTL=247
Reply from 213.142.64.170: bytes=32 time=4ms TTL=247
Reply from 213.142.64.170: bytes=32 time=4ms TTL=247
Reply from 213.142.64.170: bytes=32 time=20ms TTL=247
Reply from 213.142.64.170: bytes=32 time=3ms TTL=247
Request timed out.
Hardware error.
Hardware error.
Hardware error.
Reply from 213.142.64.170: bytes=32 time=4ms TTL=247
Reply from 213.142.64.170: bytes=32 time=3ms TTL=247
Reply from 213.142.64.170: bytes=32 time=4ms TTL=247

Etc...

The plot is pretty clear now. XP is inocent.