I use AT&T Broadband in the Sacramento area. When I first hooked up to the cable connection, I noticed my Kazaa 1.72 was downloading ONLY .7k/sec, and very few search results would come through. After very thorough testing, and the help of other people in the Sacramento area, it was determined that AT&T is throttling port 1214 (I don't know if it's incoming, outgoing, or both).
A new version of Kazaa was released, 2.0, the other day. This version allows you to change INCOMING ports to whatever port you desire. Here's my issue.
When connected directly to the cable connection, I change the port to some other port, like 21. Downloads now SCREAM. When I run a netstat command, nothing is going through 1214. Now, I put my wireless WAP back in place again. I enable port forwarding for 21 and 1214 (just in case). I connect up to Kazaa, and find that SOME downloads from some users scream. 95% of the other connections go just as slow at .7k/sec. I ran a netstat command from DOS, and found a majority of the P2P connections are STILL going through 1214, and not 21 like I told it. The one connection that was going fast is going through 21. I've disabled port 1214 forwarding in the router, and it still insists on going through 1214. I've even gone as far as to filter port 1214. That pretty much kills any download attempts.
Now I'm totally confused here where the problem lies. Kazaa 2.0 allows me to change incoming ports, but if I'm still going on 1214 with my ROUTER in place, does this mean that Kazaa is getting confused by my use of a router? Is the router not using the ports that I specify in Kazaa for some reason? I can't remember the model number of the wireless router, but it has version 2 on the end of it, and I think there's only one router that has version 2 on the end of it.
P.S. Yes, there is throttling on AT&T's side. Plenty of testing on multiple machines, multiple connections (DSL, cable, dialup), and multiple people have confirmed it to be port 1214 throttling on AT&T's side, though it seems to be in Sacramento only.
A new version of Kazaa was released, 2.0, the other day. This version allows you to change INCOMING ports to whatever port you desire. Here's my issue.
When connected directly to the cable connection, I change the port to some other port, like 21. Downloads now SCREAM. When I run a netstat command, nothing is going through 1214. Now, I put my wireless WAP back in place again. I enable port forwarding for 21 and 1214 (just in case). I connect up to Kazaa, and find that SOME downloads from some users scream. 95% of the other connections go just as slow at .7k/sec. I ran a netstat command from DOS, and found a majority of the P2P connections are STILL going through 1214, and not 21 like I told it. The one connection that was going fast is going through 21. I've disabled port 1214 forwarding in the router, and it still insists on going through 1214. I've even gone as far as to filter port 1214. That pretty much kills any download attempts.
Now I'm totally confused here where the problem lies. Kazaa 2.0 allows me to change incoming ports, but if I'm still going on 1214 with my ROUTER in place, does this mean that Kazaa is getting confused by my use of a router? Is the router not using the ports that I specify in Kazaa for some reason? I can't remember the model number of the wireless router, but it has version 2 on the end of it, and I think there's only one router that has version 2 on the end of it.
P.S. Yes, there is throttling on AT&T's side. Plenty of testing on multiple machines, multiple connections (DSL, cable, dialup), and multiple people have confirmed it to be port 1214 throttling on AT&T's side, though it seems to be in Sacramento only.