Utorrent Port Forwarding Problems

Utorrent Port Forwarding Problems
Links: home · search · speed test · login · more ·

Links: Reply New Topic
Forums » Canadian » TekSavvy » Utorrent Port Forwarding Problems

shikotee @ 6th Nov 05:15PM:
Utorrent Port Forwarding Problems

Was wondering if someone would be able to help me with some port forwarding woes that I seem to be experiencing. When I set things up ages ago, I could swear everything was OK, though now I am second guessing. The only big change that I am for sure aware of was that I opted for a static IP MLPPP with Teksavvy during the summer.

Utorrent seems to be working OK - there is the green check mark, and the speeds do not seem to be a problem. However, I have noticed that some trackers mark me "No" for "Connectible". When I try the utorrent Port Forwarding test, it is not successful. I tried another similar service, with the same result

My hard wired configuration is as follows:

1) Upstairs ST516 modem (Bridge mode)
connected to
2) Upstairs Linksys WRTSL54GS (running Tomato/MLPPP Version 1.21-mp3alpha4, which I should upgrade) via Internet/WAN port.
connected to
3) Downstairs Dlink DI-624 (DHCP disabled) (not using WAN port - Ethernet 1 to Ethernet 1)
connected to
4) Downstairs XP Desktop PC (Ethernet 2 to Ethernet card)

Configurations for each device:

4) Downstairs XP Desktop PC
The computer that seems to blocked (according to tests) is running XP, Eset security with the windows firewall shut off. I disabled Eset, and the results seemed the same. I checked utorrent - the port is set to XXXXX.

3) Downstairs Dlink DI-624
As mentioned, DHCP is disabled, and this router is connected to the other router via an ethernet port. WAN port is unused. As DHCP is disabled, do I even have to forward the port here? XXXXX is setup for both protocols.

2) Upstairs Linksys WRTSL54GS

Single Connection MLPPP is enabled, so this device is handling my DSL connection.

Tomato Port Forwarding:
On Both XXXXX XXXXX 192.168.0.106 XP

So, port forwarding is ON for both protocols, (no src address) and the internal and external port# is the same XXXXX as above, and the Int Address is the static IP for my XP machine. Is there anything else that needs to be configured?

1) Upstairs ST516 modem (Bridge mode)

Since the Linksys is handling the connection, do I need to setup "Game & Application Sharing" on the actual modem? Just in case, I setup a rule for uTorrent. In the "Game & Application Sharing" settings, UPnP is set to YES, while Extended Security is set to NO.

Any suggestions on what I might be missing?
Is this happening because of my router-router connection?

Would really appreciate some advice....
reply

Oinktastic @ 10th Nov 05:43PM:
Re: Utorrent Port Forwarding Problems

If the modem is in bridged mode, it shouldn't need any firewall adjustments, as far as I'm aware.

I have trouble getting Tomato to forward ports correctly over wireless sometimes, but that doesn't seem to be your problem since you appear to be using wires.

Try using port 1723 with encryption enabled.

Does your Dlink router have the same type of IP as your Linksys... as in 192.168.0.x ? It shouldn't matter since you're using it as a switch, but I'm not sure exactly how port forwarding works. It may be important to have the two routers communicate differently.

Also, if you already have the port forwarded properly, try disabling uPnP in uTorrent just in case there's some sort of conflict.
reply

shikotee @ 11th Nov 12:44AM:
Re: Utorrent Port Forwarding Problems

Hey....

Thanks for the response.

The port I am using is in the 5XXXX range, and encryption is enabled.
Why specifically 1723? So long as nothing else is using the port, it should be OK, right?

The assigned IP's are:

ST516 - »192.168.1.254/
Linksys - »192.168.0.1/
Dlink - »192.168.0.2

I'm wondering - could the problem be due to the routers and the modem not being on the same subnet?

Anyways - I removed the Dlink from the equation, so now my PC is connected by cable to the Linksys.

The problem still ensues. The speeds are seemingly fine, but various trackers mark me as NO for connectible.

I did start reading up on this a bit, but opted to leave things for a few days as now is not the time for a significant disruption of service.
reply

RobP @ 11th Nov 01:32AM:
Re: Utorrent Port Forwarding Problems

Win XP box with a dhcp address? if so set the router to hold the same ip for the box. (Edit 1) If you directly connected to the tomato router and are still blocked enable DMZ to test the connection. If it works via dmz for sure you have issues with the port forwarding.

(Edit 2) Also sometimes the client will not register the port being connectible even though speeds are fine. If speeds are not an issue (DL||UL) and you can connect to peers and seeders than there is no issue.
reply

Oinktastic @ 11th Nov 07:14AM:
Re: Utorrent Port Forwarding Problems

said by shikotee :

Why specifically 1723?

Port 1723 is the default VPN port and sometimes if you use it for encrypted traffic, Bell's DPI boxes will give you a break and let your data through that port unthrottled. At least this is what many users on DSLR are reporting.

Also, does anyone know if the trackers need certain ports forwarded correctly to work? I'm wondering if uTorrent uses the same port for connecting to the tracks that it does for actually sending and receiving data.

I've had trouble with trackers being unreachable in the past as well, but it turned out they were just busy or down at the time.
reply

InvalidError @ 11th Nov 10:06AM:
Re: Utorrent Port Forwarding Problems

said by Oinktastic :

Also, does anyone know if the trackers need certain ports forwarded correctly to work? I'm wondering if uTorrent uses the same port for connecting to the tracks that it does for actually sending and receiving data.

Normal tracker updates are done over HTTP/HTTPS, no forwarding there. The only port that needs port-forwarding is your incoming connection ports.

As for outbound connection ports, the standard programming practice is to let the OS assign them for TCP/IP - applications rarely need to know about them since the OS is handling all the low-level details before presenting the data to the application layer.
reply

Craig M @ 11th Nov 10:24AM:
Re: Utorrent Port Forwarding Problems

If you have eliminated the routers from being the problem, try opening windows firewall.

I recently had this problem with my port forwarding.

When I tried launching windows firewall (which I don't use, it's always just disabled) it said the service was not running. I hit ok for it to start the service, ensured it was still disabled, then tested my ports again and they were clear and tested as open.

Worth a try. :)
reply

RobP @ 11th Nov 12:14PM:
Re: Utorrent Port Forwarding Problems

said by Craig M :

If you have eliminated the routers from being the problem, try opening windows firewall.

I recently had this problem with my port forwarding.

When I tried launching windows firewall (which I don't use, it's always just disabled) it said the service was not running. I hit ok for it to start the service, ensured it was still disabled, then tested my ports again and they were clear and tested as open.

Worth a try. :)

Good point. The windows firewall service is bundled with NAT so if the service is disabled or stopped it could effect the tracker not seeing you
reply

shikotee @ 11th Nov 02:38PM:
Re: Utorrent Port Forwarding Problems

Ok...

I decided to upgrade my router to Tomato/MLPPP v1.25-mp3alpha6.
I completely reset the NVram (as advised), and am manually setting everything up again.

For setup, I used the settings as detailed here:
»mlppp.teksavvy.com/tomato_sl.html

I have started a separate thread for problems I am having with setting up Bandwidth monitoring:

»TomatoMLPPP Bandwidth Monitoring

Now - back to my figuring out my port forwarding problems....

For now, I am sticking to only using the ST516 and Linksys.
So - I am using »https://192.168.1.1 to access the Linksys.
My PC has a static IP set to 192.168.1.106
Previously, I would access my modem via 192.168.1.254, but I cannot set this anymore (message - Modem IP address may not be within your local address space).
I tried entering 192.168.0.254, which tomato accepts, but when I enter this in a browser, I am not connecting.
How do I configure things so I can once again access the modem?

Anyways - The only way I could get CFIS to mount (bandwidth monitoring) was by disabling Eset Smart Security. I enabled Windows firewall, and added an exception for utorrent, and for the 5XXXX port number that I am using for uTorrent. I also

Tomato Port Forwarding is set to TCP, with "ext ports" and "int ports" both set to 5XXXX, and "Int Address" is my static PC - 192.168.1.106

Now, when I use the utorrent port forwarding test, everything seems OK.

I will tinker around.....
reply

Oinktastic @ 11th Nov 04:46PM:
Re: Utorrent Port Forwarding Problems

The ST516 has two internal IP addresses for some reason. The one you've been using and also, 10.0.0.138. You can use that one if the first one is giving you conflicts.
reply

shikotee @ 11th Nov 05:22PM:
Re: Utorrent Port Forwarding Problems

said by Oinktastic :

The ST516 has two internal IP addresses for some reason. The one you've been using and also, 10.0.0.138. You can use that one if the first one is giving you conflicts.

Awesome! Communication with Router established!

I am getting rid of Eset Smart Security....
reply

shikotee @ 11th Nov 06:26PM:
Re: Utorrent Port Forwarding Problems

Update:

I believe the problem lay with uTorrent 1.8.4

When I would test with it running, I would get error.
When I would test with it shut down, no problems.

I have now updated to uTorrent 1.8.5, and my ports test fine with it running.
reply

Oinktastic @ 11th Nov 09:34PM:
Re: Utorrent Port Forwarding Problems

Ah the light at the end of the tunnel. Things are looking up for you.

So, do your trackers connect properly now?
reply

shikotee @ 11th Nov 10:21PM:
Re: Utorrent Port Forwarding Problems

From what I have checked, trackers now see me as connectible.
Speeds are exactly the same from what I can tell, though I am not really DL-ing anything right now - just seeding.

Any security recommendations, now that Eset Smart Security is gonzo?
I'm just using nod32 for anti-virus, and Windows firewall for now.
I'm the only person using this computer, and it is on 24/7.
reply

anon @ 12th Nov 02:10AM:
Re: Utorrent Port Forwarding Problems

The older version of nod32 used to have problems with utorrent. I haven't had any issues with the newer version of nod32.

I am using utorrent 1.9 beta and I can tell you using port 1723 with encryption forced and bt.transp_dispositon=10 (under advanced), works wonders for getting around throttling. You do want to uncheck dht and legacy connections also.
reply

shikotee @ 13th Nov 06:58AM:
Re: Utorrent Port Forwarding Problems

Things seem OK with nod32 and utorrent 1.8.5.

Xizor - are you using utorrent 1.9b along with MLPPP?

Things seem fine for me (speed wise) with MLPPP, so I have not looked into using 1.9. Will wait til the bugs get sorted......
reply