• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

XP SP2 tcpip.sys fix??

M

Monkey muppet

Golden Member
I've heard of a fix for the problem in windows XP SP2 where only 10 connections
per second are allowed by the operating system.

(apparently by modifying the tcpip.sys file under the system32/drivers location.

Could any persons shed some light into this for me please
 
It's a myth. There is a 10 connection TCP/IP queue that will not affect the performance of any networking applications. The queue is designed to slow the spread of malicious worms that attempt to make thousands of simultaneous outbound connections.
 
Originally posted by: MrChad
It's a myth. There is a 10 connection TCP/IP queue that will not affect the performance of any networking applications. The queue is designed to slow the spread of malicious worms that attempt to make thousands of simultaneous outbound connections.
Click to expand...

The reason I was asking is due to very poor performace on ftp's , P2P's, etc. I've a 512 pipe 256 up, 256 down.

No found malicous ware, spy ware, etc, etc.

Outgoing (internet) activity never goes above 15%,

FF is also very slow - I was thinking this might be caused by the number of con-current TCP connections windows is trying to make.

Or could it be due to using ICS and running azurues on the client machine?

Was 50 the maximum that windows could allow from the network controller (even though most controller could handle a lot more)
 
The "cap" is only on incomplete outbound connection attempts per second. Unless your applications are trying to connect to multiple invalid IP addresses simultaneously, the SP2 change is not your problem.

ICS and your BitTorrent client sound like much more likely culprits.
 
Thanks for your reply I'm now off to either Network or apps to see if I can find answers on the settings within Azureus;

The setting up of Internet Gateways (windows ICS won't work - I have to set it up manualy pointing the client PC to the default gateway of the ISP to work);

and any possible advice on ADSL modem routers (cheap - like the duck)
 
"XP Anti-Spy" includes an option for adjusting the "maximum connections per SERVER" (not "per second"):
Text
 
I've noticed in the event veiwer under System I get the following:

TCP/IP has reached the security limit imposed on te number of concurrent TCP connect attempts"

Is this related at all???
 
Yes, I believe that is related to connection queue. You've scanned your computers for viruses using an up-to-date virus scanner?
 
Outgoing (internet) activity never goes above 15%,
Click to expand...

That scale can be very misleading. That scale is based on what your card can (in theory) do, not what your upstream connection supports. 15% of a 100mb connection is pretty fast upstream 😉

Bill

 
Ad-ware v6.0 with the latest reference files: I find about 2-5 tracking cookies every 3-ish days

Spybot v1.3 latest updates: I find DSO Exploitx5 every time I scan then delete them

Zonealarm v5.5.062.011: software firewall always running

AVG v7.0.3: Always running with auto updates & holistic scanning

Internet connection is provided by Pipex through a USB DSL modem on a 512kb pipe (256 split)

I followed the Windows knowledge base for the above mentioned issue under the event viewer (from the Command prompt: "netstat -no" and there are no "SYN_SEND" entries).

The more & more I think about this - the more I'm thinking it's relating to the javaw.exe process required for Azurues to run.

Therefore I set the number of outgoing connection attempts to 30 about a week ago and still receive the event viewer warnings.

What to check next?????
 
The more & more I think about this - the more I'm thinking it's relating to the javaw.exe process required for Azurues to run.
Click to expand...
I've never seen Bittorent clients cause this. Since you're connecting to known hosts the connections are going to become fully established very quickly (within a matter of miliseconds).

Even if your half-open connection queue was reached due to a P2P application it wouldnt matter because of how quickly the queue would flush the connections to the good hosts.

I'll give you an example of what I mean here. Lets say your average connection time to other bittorent clients in the swarm was 100ms (a fairly conservative estimate if you're on a decent broadband connection). If that were the case your machine should be able to open connections to ~100 remote hosts per second using the default 10 unestablished tcp connection queue.

I believe MrChad is on the right track that this may be malware related. The only time that the half-open tcp connection queue should fill up is when your machine attempts to make a lot of connections to non-existant hosts (i.e. connecting to random addresses) since the application would have to wait for each connection attempt to time-out before trying another.

AVG doesnt exactly have a good track record for catching things, you might want to see if you get differant results with Trend Micro's Housecall:
http://housecall.trendmicro.com/
You could also try Microsoft's AntiSpyware (free):
http://www.microsoft.com/athome/security/spyware/software/default.mspx

Good Luck,

-Erik
 
I've never seen Bittorent clients cause this. Since you're connecting to known hosts the connections are going to become fully established very quickly (within a matter of miliseconds).
Click to expand...

I would think this would be a problem for P2P connections where the remote party is behind a NAT/PAT device and has port forwarding turned off. They 'appear' to be a legitimate host to connect to, however the connections will fail...

Bill

 
FTP shouldn't be affected by any of the above mentioned, once you make the connection it should "just work", barring problems with active/passive FTP and such, but that wouldn't cause it slow down, it wouldn't work at all.

I don't run BT, but I've gotten ~7-8 MB/Sec both up and downstream on both FTP and DC.
 
No I didnt. But the TCP problem he said he gets in event viewer is because of that link I posted. This doesn't necessarily fix his speed problems on FTP, but it should help solve connecting issues on p2p.
 
Originally posted by: ImDonly1
No I didnt. But the TCP problem he said he gets in event viewer is because of that link I posted. This doesn't necessarily fix his speed problems on FTP, but it should help solve connecting issues on p2p.
Click to expand...

If the remote sites don't exist or aren't reachable, no patch is going to address that. And that is the ONLY time the change comes into play. Perhaps you SHOULD READ THE THREAD before responding next time.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top