TCPIP Connection patch ????

[Everlong]

You need to change it yourself within utorrent.

Go to preferences then advanced.

There should be an option for max connections.
net.max_halfopen. Change this to 50.

I'm not at home, so I can't check now, but there should be an option where you can put your ip address in to help direct connections to your computer, and that can help speed up utorrent. If you can't find it, then I'll have a look myself when I get home later.

Have you also set the port you've opened for utorrent as the same port it is on Vista?

With these changes, I went from getting a maximum of 200kb/s to getting 600kb/s to 1.3mb/s.

Chappy is right, and a lot of the "tweaks" that are suppost to speed up download speeds don't work with torrents. They're more for http downloads, and not torrents. To speed up torrents, you need to tweak options within the client itself.

Also, if there's a lot of trackers that aren't connecting (check the tracker list when downloading), then disable these as it gets them out the way and just uses the trackers that do connect.

 

[medhunter]

Hey guys

Ummm...I hate to be the stick in the mud, but the limit on Half Open Connections has absolutely NO EFFECT on your torrent d'load speeds!
As the name states, it only limits Half open connections and not Established ones, so only the number of connections sitting and waiting for the Ack/Syn handshake to complete is affected, and if they reach their timeout they're probably not going to connect anyway. But that matters not because as sson as they are dropped, the max is immediately reached again and as handshakes complete they move OUT of that limit. You can have any number of Completed connections so the only thing the limit slows down is how fast you build your swarm and not how many you can have or their d'load speeds.

These TCP/IP patches are all smoke and mirrors, and the 64bit ones made the OS unbootable. Just use the Good Speed Settings for your particular P2P app and don't worry about any Half open limit. The most you lose is AT MOST 1 or 2 minutes in building your connections and then there is absolutely no effect on your downloads.

This myth has been disproven many times, and by many people much smarter than us...like Mark Russinovitch (probably the smartest Windows guy on the PLANET)

Sounds logic , so why all the fuss!!!!

 

[Everlong]

The ip address thing is net.bind_ip. I've put my LAN address in here, and it seems to work great.

 

[TripOG]

i beg to differ the half open connection limit does affect torrent speeds after setting everything up when i swaped to win 7, ports n utorrent settings i was maxing out about 180 once i remembered to patch my half open connections it boosted it right back up to 400kbs

 

[Everlong]

Well you need to have the TCP patched for the parameter in utorrent to work.

After doing all OS tweaks, I was still getting pretty low speeds, but after doing the client tweaks, I was getting 600kb/s and up, and when I downloaded Windows 7 via torrent (due to the MS download server being full) I downloaded that at 1.3MB/s.

 

[TripOG]

either way the tcp hack helps iv been using it for years, in many clean installs and been hearing for years it doesnt but when you look at 220kbs give or take every time ill take that for something that supposedly doesnt work

 

[LordTakyon]

While I appreciate the patch should make no real difference, real world experience shows otherwise.

I understand how it works from a technical standpoint, and the first thing you notice is that, obviously, peers can connect faster (rather more can try to connect at any one time, same difference), the whole thing just gets going faster because it can. As to why it makes the max download I hit so much better is anyones guess.

It is important to remember that certain tweaks may have to be made to the client to benefit.

It has zero impact on internet browsing however.

This is one of those issues of much debate, a mass debate if you like, many of us understand the more technical side and yet many people, myself included, can show results to the contrary.

 

[Chappy]

This is one of those issues of much debate, a mass debate if you like, many of us understand the more technical side and yet many people, myself included, can show results to the contrary.

Really?

Can we see them?
(not meant to be sarcastic LordTakyo, but there is Zero proveable data out there on this, whereas there is a ton of proveable disclaiming it)

There is no difference in your download speeds period...the only thing that is affected is how quickly you build your peers list. It is a "Half Open Connection Limit" and Half-Open connections are not established yet so therefore you can not get data from it. This limit has no effect on Established connections.

There are tons of other reasons that you may not hit your "expected" results and this can change faster than you can restart your client (and does). There are tweaks within the client that can help and most have a "Good Speed Settings" Wiki or other form of help, so that's the best place to look when you feel your speeds are slow.
But remember, it's not always your d'load speeds that matter, it's what others are upping it at...
You can have 200 peers in your swarm but if they all have a pile of seeds going, they probably have them limited to a few kB's a second and not full throttle so as not to get a note from their ISP about their bandwidth usage. (I know )

 

[Airbot]

I think a lot of the thinking that this patch works is all in the mind of the user. You use the patch hoping, thinking it's going to make it faster, better but it really doesn't. You just imagine it and it seems to be to the user. Wishful thinking IMO.

 

[LordTakyon]

Chappy, as I said their is no impact on internet browsing speeds. I also understand how P2P works.

Tweaks to my client, uTorrent in this case, make some difference, but it is still held back and takes forever to build a substantial list of peers that I can use. The patch allows this list to build much faster and hence things get going much faster.

I also stated I have no idea why max speed is higher, but I have a suspicion. I have a fast connection with low latency and like to set it to connect to 1000 or so peers per download, great if they are there to be had LOL

One possibility I have considered is this, with standard settings it can take a long time to get a decent set of peers, sometimes over half an hour, yet with the tweak it takes just a minute or so to have a huge list. I can download a 700 meg AVI in 12 or so minutes with the tweak, provided enough peers are present, it will always take alot longer without the tweak, sometimes 1 or 2 hours on the same torrent.

I honestly do think it is simply a case of modern connections are so fast that, as I said, I can download a file so fast if it can work how I want it to, that it can be finished before a standard connection has finished building the list.

I reset my TCP file back to default and started to grab a well seeded file, it took roughly 25 minutes to get upto 1000 connected peers and download about 25% of the file, with the tweak it is connected and downloaded in under 15 minutes.

 

[Chappy]

great if they are there to be had LOL

No argument there..

I can get 500 kBps from 3 seeders and then 45kbps from 100 of them. I think the longest my client took to build a good swarm was 8 or 10 minutes, which I don't really mind the time. The speeds are so subjective to so many different factors, it's almost impossible to know just what kind of speeds you should see.
I can take a 500MB file and start it, let the swarm build, and watch the speeds change from 100's to under 10 kBps within seconds, and then jump to 500 again a few minutes later. The swarm size doesn't change (too much) so how do we know that any changes we make have made a difference (truly) with such fluctuations?
All I know for sure is this, that limit has no effect on how many established connections you can have, and therefore cannot adversely affect speeds. I guess as long as the patch you're using doesn't kill the stack like the 64bit edition does, then if you feel it helps..go 4 it. But DO stay away from the 64bit patches as they fail the system file signature check run during bootup and causes a dead system.

 

[TripOG]

No argument there..

I can get 500 kBps from 3 seeders and then 45kbps from 100 of them. I think the longest my client took to build a good swarm was 8 or 10 minutes, which I don't really mind the time. The speeds are so subjective to so many different factors, it's almost impossible to know just what kind of speeds you should see.
I can take a 500MB file and start it, let the swarm build, and watch the speeds change from 100's to under 10 kBps within seconds, and then jump to 500 again a few minutes later. The swarm size doesn't change (too much) so how do we know that any changes we make have made a difference (truly) with such fluctuations?
All I know for sure is this, that limit has no effect on how many established connections you can have, and therefore cannot adversely affect speeds. I guess as long as the patch you're using doesn't kill the stack like the 64bit edition does, then if you feel it helps..go 4 it. But DO stay away from the 64bit patches as they fail the system file signature check run during bootup and causes a dead system.

if your talking about the 64 bit patch i posted it does not kill the system i know because i installed it on friends 64bit vista and 7 and it has never broke any os, you must not of followed the directions... or else your talking about some other patch.

i encourage anyone who wants to get the most out of their connection for p2p/torrents to install tcp-z and yes configure your torrent client for the patch aswell. read the readme before installation theres a reason its included.

x86/x64
http://soft3.wmzhe.com/download/deepxw/TCPZ_20090108.zip

if you think your isp is throttling your torrent speeds.. test it here
http://broadband.mpi-sws.org/transparency/bttest-mlab.php

 

[LordTakyon]

No argument there..

I can get 500 kBps from 3 seeders and then 45kbps from 100 of them. I think the longest my client took to build a good swarm was 8 or 10 minutes, which I don't really mind the time. The speeds are so subjective to so many different factors, it's almost impossible to know just what kind of speeds you should see.
I can take a 500MB file and start it, let the swarm build, and watch the speeds change from 100's to under 10 kBps within seconds, and then jump to 500 again a few minutes later. The swarm size doesn't change (too much) so how do we know that any changes we make have made a difference (truly) with such fluctuations?
All I know for sure is this, that limit has no effect on how many established connections you can have, and therefore cannot adversely affect speeds. I guess as long as the patch you're using doesn't kill the stack like the 64bit edition does, then if you feel it helps..go 4 it. But DO stay away from the 64bit patches as they fail the system file signature check run during bootup and causes a dead system.

That is my point though, a fast connection and a relatively moderate sized file can be done in a matter of minutes with the patch. I completely understand it changes nothing regarding how many established connections you can have, this patch just lets you get there quicker and I think that is what I notice initially.

Just for the record, I have 64bit and the patch broke nothing for me.

 

[Chappy]

That is where you will notice any diff LT. I can't say I've really seen a big difference (I did try it with Vista 32bit) but when I went 64bit it was a system killer, and for a great many folks. They must have fixed it so that it passes the system check. Once I dug deeper into what the limit was and did, I just dropped it altogether and have never seen any horrendous slowdowns by leaving it.

 

[LordTakyon]

It is kind of reminiscent of of my old WIN 98 days, some tweaks work well for some, but do nothing good for others. I remember the settings I used to modify would often just break other people connections LOL

 

[TripOG]

That is where you will notice any diff LT. I can't say I've really seen a big difference (I did try it with Vista 32bit) but when I went 64bit it was a system killer, and for a great many folks. They must have fixed it so that it passes the system check. Once I dug deeper into what the limit was and did, I just dropped it altogether and have never seen any horrendous slowdowns by leaving it.

i take it you didnt read the readme because you disable system checks before your install.
most problems can be avoided by actually reading the read me and installing things properly

 

[Chappy]

i take it you didnt read the readme because you disable system checks before your install.
most problems can be avoided by actually reading the read me and installing things properly

LOL!!

Matters not, the file is useless, and yes, the system checks were disabled beforehand BTW.
TCP/IP patching is a Smoke & mirrors "feel good" patch for those who do not know how the limit works.
Problems come when people start hacking system files when no hack is needed, simply because they don't understand what it is they're trying to fix. Avoiding useless hacks is the best way to avoid problems IMO (and many others I would say)

 

[win7]

This one worked for me on 7000: http://soft3.wmzhe.com/download/deepxw/UniversalTcpipPatch_20090205.zip

 

[Digger]

This is a Utorrent issue... many ppl around are complaining about the 1.82 build..... its a beta, which is installed on a beta OS, using alot of beta ipv6/toredo support...

This is software related, not internet/network related IMO.... and also not a TCP/IP max connections issue internally with windows, as most routers have a limit on them as well, and hold on to "dead" connections for way too long, some over 48 hours.... google it all, its on there somewheres... and have a look on the utorrent forum troubleshooting the 1.82 bug build... most have went back to 1.81.... you can still enable utorrent protocol in that program in the advance settings... all this on their forum... not also to mention what other settings you could be using with the program, DHT local discovery etc

 

[TripOG]

dunno if this has been posted so i figured id go way back and post it in this old school thread

was just reading vista sp2 and windows 7 newer builds have removed the half open connection limit

How to enable the half-open TCP connections limit in Windows Vista with Service Pack 2 and in Windows Server 2008 with Service Pack 2

so no more need for tcp-z n all the others