Low Speed, Port Tests Failing

[Jake0]

I recently downloaded Vuze because μTorrent was giving me very low download speeds. Vuze gives me the exact same problem, however. I normally download at 120 kB/s, but Vuze is giving me short bursts of 60 kB/s, and then almost 0 kB/s for the majority of the time. At this rate it will take me about 12 days to torrent the 30 GB item I'm currently working on.

 

My TCP and UDP listen ports are both set to 49161. I'm running 64-bit Windows 7 and I've instructed Windows Firewall to ignore Vuze. I've also created two Inbound Rules in Firewall to open those ports, just in case. However, after restarting my computer, Vuze's Help > NAT / Firewall Test prints an NAT error due to the connection timing out for both the TCP and UDP ports. Also, http://www.canyouseeme.org returns an error for port 49161. I've also run Vuze's test on a few other ports with the same results (although I didn't make rules for these ports in Firewall).

 

I am attempting to follow this guide: http://www.techsupportalert.com/content/optimizing-vuze-speed.htm

 

I'm pretty much out of ideas since I'm not experienced with torrents. Any suggestions?

 

EDIT: Oh yes, and I followed the guide's steps for enabling UPnP.

[Harold Feit]

Whatever it is, either something on your computer, in your router or at your isp is actively interfering.

[Jake0]

Given that those are the only three things involved in connecting to the Internet, I realize that. I'm just not experienced enough to know where to begin looking for the problem(s).

[Harold Feit]

Internet security software on your machine is simple.

Programs like Norton, McAfee and ZoneAlarm.

In your router, the SPI firewall typically (some specific router models such as the asus N56U and that family require the SPI firewall to be on, but it's coded so that it plays nice) causes major problems in getting online as well as in using torrent applications.

ISP interference is a lot harder to test for and work around.

[Jake0]

I'm using the free version of avast! with no firewall, so that shouldn't be a problem.

 

How would I know if my router's SPI firewall was causing problems? Didn't I address this by enabling UPnP? Or is this a separate issue?

[Harold Feit]

I'm using the free version of avast! with no firewall, so that shouldn't be a problem.

Avast might have a p2p scanner or something similar that can interfere.

How would I know if my router's SPI firewall was causing problems? Didn't I address this by enabling UPnP? Or is this a separate issue?

It's a separate issue that UPnP doesn't solve.

[Jake0]

How do I check to see if my router's firewall is interfering?

[Harold Feit]

Turn it off.

In a large percentage of cases, the router's firewall ends up wasting the limited CPU cycles available on the device.

[Jake0]

Well, I disabled my router's firewall and Vuze gave me the green face, but the NAT tests still failed, and after a few minutes, I got the yellow face again. I guess I'm going to give up for now and follow these steps when I have more time, and then post on the Vuze forums if that guide doesn't work. Thanks for your help, though!