• 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.

sp 2 slowed my net connection way down

waylman

Diamond Member
just installed sp2 and my net connection sucks now. im getting about 40k...normally get 250k. I tried reinstalling mobo drivers, but no luck. any ideas?
 
I always check my msconfig after any new install

Also I look at my "services"

blackviper.com

Stuff just shows up 🙂
 
Originally posted by: MrChad
What applications? P2P? Straight HTTP downloads?
My situation is when I'm using the following: Internet Explorer, Mozilla, and Outlook. Don't use any P2P programs. For example, I go to download.com to get Spybot Search and Destroy and it dl's it slower than usual and I'm on High Speed. My system is Adware/Spyware/Malware/Virus free. I'll try to disable the firewall, maybe the TCP Optimizer, any other ideas?

 
Originally posted by: Yanagi
disable the XP firewall?

Tried this but still the same results, I'm getting around 60-50KB/Sec of download. When I start the download it starts off at around 250+KB/Sec, just like before, then it slows down to a crawl of 60-50KB/Sec.
 
Originally posted by: powerMarkymark
I did a Google and found this.

Evidently SP2 limits TCIP connections and I guess for most people the limit is enough.

Marc

Wrong.

Read bsobel's explanation of SP2's TCP/IP connection queue in this thread

The people claiming that their is a TCP/IP connection limit in SP2 are spreading FUD (this isn't directed at you elkinm, I'll explain what MS did in a second). I've seen this 'limit' quoted on a zillion sites, and it simply not true.

What was added was a queue (not a limit) of the number of uncompleted TCP connection outstanding. The default queue size is 10. Which means you can attempt to establish 10 TCP connection at once and their is no change in the behaviour. If you try to establish 20 at once, the first 10 are put on the wire while the next 10 are queued and released as those first 10 either complete or fail (e.g. first connection is built, #11 is put on the wire, #4 fails, #12 is put on the wire, and so on).

In 'normal' usage, TCP connection establish quickly and you simply won't notice any difference. Where you will see a difference is if you try to create a large number of connections to sites which are not listening/responding to your requests (so in your examples "Multiple IE or other active browsers, multiple downloads, multiple email, telnet, ftp, ssh clients and others may run. Norton update, weatherbug, VPN, terminal services, and a telnet and web server on my PC, and possibly multiple multisource download clients and programs, by own or something like steam or fileplanet." there are all services which will respond quickly and even if you tried really hard, I do not believe you would ever be able to determine if the queuing happened.)

So, why the change? Flash worms that utilize TCP connections typically sit and loop while connecting to a random IP (they then attempt to infect that machine and they go back to picking another random target). Some of these worms can literally eat up your entire connection while they sit and pump packets out, since many of the destinations are not going to be valid targets (since the selection was random) this queue will kick in and help throttle how quickly the worm can leave the box.

Even throttled the worm will still spread quickly, but more importantly (and the reason for this feature), your connection will not become so unusable that you will be unable to access updates/repair tools/patches/etc.

Bill
 
As others have said, it could be the limit on incomplete connection requests.

If you have a virus/port scanner/other malware that's attempting to open numerous TCP connections, your TCP stack will be rate-limited by those half-complete connections.

Do a virus scan and take a network trace to see if your machine is attempting to make outbound TCP connections.
 
Back
Top