Topic: Bizarre Firewalling Issue with uTorrent & Windows & Comcast

[dactylus]

Here is the problem.  I have been a Comcast customer with service utilizing uTorrent with Windows for several years now without an issue of firewalling that I couldn't rectify.  I don't know what changed in the past few days but I cannot escape the firewall now.  I am a Comcast broadband user.  The Windows firewall exception is enabled on both of my machines with uTorrent and my Kaspersky AntiVirus Protection has "given permission" for uTorrent to operate.  That is the way I have downloaded torrents for several years now with no firewall problems.

Hypothetically I set my incoming port with uTorrent to be 49194 - I "open" that port on my router.  Save and close the uTorrent & router options.

When viewing a torrent after making those changes I see that I am still firewalled and being listed as being firewalled on port 49195.  One digit higher than the port that I assigned in Utorrent.  So I go back to uTorrent and my router and set the port for 49195 based on what I'm seeing on Trader's Den for example.  I save everything and then stop and resume the torrent with the new settings and the incoming port digit has increased by one once again to 49196 and of course I am still firewalled.  Totally fucking bizarre.   

Help please!!

[Fatah Ruark (aka MIKE B)]

Traders Den always shows me as firewalled. I'm almost certain I have everything set up correctly. Other sites don't show me as firewalled. I don't have any issue seeding. I think TD is fubar'd.

[dactylus]

Traders Den always shows me as firewalled. I'm almost certain I have everything set up correctly. Other sites don't show me as firewalled. I don't have any issue seeding. I think TD is fubar'd.

I am definitely firewalled on every site that I choose.  Not just Trader's Den.  The issue is that somehow the port digit that I have assigned in uTorrent is "bumped" one digit higher than what I have assigned it to be and thus I am firewalled.  I don't think that uTorrent will let you assign a range of ports, it is either a specific port or random.  And the whole random thing would interfere with my router settings, etc...

 

[Fatah Ruark (aka MIKE B)]

If your router supports UPnP then you should just be able to enable that and be good to go. Not exactly sure how it works though. I just enabled it on my router and I've been good to go since.

[Brian Skalinder]

Sounds like a uTorrent bug?  Does your router / firewall / AV support specifying a range of ports?  (Mine do.)  If so, that may allow you to work around the issue of the "bumped" port number in uTorrent.

[dactylus]

Sounds like a uTorrent bug?  Does your router / firewall / AV support specifying a range of ports?  (Mine do.)  If so, that may allow you to work around the issue of the "bumped" port number in uTorrent.

Yes Brian my router / firewall / AV support will allow me to specify a range of ports.  I have tried numerous range specific port assignmnents and they do not allow me to escape the "firewall".  I am stumped.

I think that is the uTorrent client that is the problem.  The port that I assign on uTorrent is bumped up by one digit, the "bumped up" port still falls within the router / firewall / AV range of ports and I am still firewalled.

[H₂O]

I thought that the port you specify is the first port in a range and that the client actually will use, so you need to open a range of ports (port specified through port specified + number of connections)

[newplanet7]

I thought that the port you specify is the first port in a range and that the client actually will use, so you need to open a range of ports (port specified through port specified + number of connections)

i ONLY HAVE EVER HAD ONE FORWARDED WITH UTORRENT.
hOWEVER dAVID MY UTORRENT DOES THIS ALSO BUT i AM STILL ABLE TO CONTINUE TO SEED LIKE NORMAL.
I noticed it when I updated utorrent.
Try rolling it back a few versions.

[dactylus]

I thought that the port you specify is the first port in a range and that the client actually will use, so you need to open a range of ports (port specified through port specified + number of connections)

I tried following your suggestion and I am still firewalled.  I think that I'll see if the uTorrent forums have addressed this problem.

Thanks for your advice guys!

[page]

I thought that the port you specify is the first port in a range and that the client actually will use, so you need to open a range of ports (port specified through port specified + number of connections)

I tried following your suggestion and I am still firewalled.  I think that I'll see if the uTorrent forums have addressed this problem.

Thanks for your advice guys!

have you tried a different client? I'm just curious if you've really isolated it at the client level.

[H₂O]

Did you open both your Internet router firewall and Windows firewall - do you have any funky Internet protection sw installed (i.e. Norton)?

[dactylus]

Did you open both your Internet router firewall and Windows firewall - do you have any funky Internet protection sw installed (i.e. Norton)?

Yes, the Internet router firewall, Windows firewall & Kaspersky AntiVirus firewalls are all open to uTorrent...

I'll try a different BT client today Page.

[dactylus]

Still a bizarro issue.  I just checked my status on a few BT sites and now everything looks normal again and I am no longer firewalled and my incoming port is NOT being bumped up by one digit.  Last night I was still firewalled on two machines.  Today, I have not made any changes since yesterday and all is back to normal.  Twilight Zone material.

[TimeBandit]

Same here got this port open on machine, OS, software and routers but BitTorrent and also DIME saying it´s firewalled.

But no problems with seed and share ratio.  So it´s like a bug ........

[Gordon]

what version of utorrent are y'all running?  I'm still in the dark ages of 1.8.8 (build 14458).  never had a problem and on one private tracker I'm on that is still the recommended version and build.

[sparkey]

You might try disabling the Windows firewall service, not just turning it off....

[dactylus]

what version of utorrent are y'all running?  I'm still in the dark ages of 1.8.8 (build 14458).  never had a problem and on one private tracker I'm on that is still the recommended version and build.

uTorrent 2.2.1

All is back to normal for me, for now.   

[H₂O]

one thing you can do to see what port uTorrent is actually trying to do is run a "netstat -na" from the command line - This will list all ports that are in use and what state they are in.

May help troubleshoot.

This command works with Windows, MAC OSX, Linux, etc

Ignore the IPv6 (show up as tcp6, udp6 or with the IP address with colon's ( - IPv4 are tcp4, udp4 IP address octets seperated by dots (.)) ports and also DNS domain sockets that may be listed - so you may have to scroll up a bit

[dactylus]

^
Thanks Richard!  +T

Using that command I see that uTorrent is now actually using the port that I assigned in uTorrent.  If I have that bizarro issue again I will use that command to help troubleshoot.