Go with Comodo instead of any other Windows Firewall. It actually respects the rules you make like e.g. making your client a trusted app with full in/out access.
You of course need to configure your router like Cabalo says as well.
Go with Comodo instead of any other Windows Firewall. It actually respects the rules you make like e.g. making your client a trusted app with full in/out access.
You of course need to configure your router like Cabalo says as well.
test the port you forwarded with these sites:
http://www.utorrent.com/testport.php?port=nnnn where nnnn = port number
http://www.canyouseeme.org/
if both of them show the port as open, ignore any non-connectable messages that trackers throw at you. the tracker is wrong if those sites say the port is properly forwarded.
utorrent says its good
and i get an error on the other site.
i turned off windows firewall and i still get "not connectable" on both trackers. i'll try the nod32 firewall too. and on testmyports.com it says im not connectable etc. so i definitely got a problem. what could it be if its not the firewalls? considering i dont have a router but a modem??
Last edited by Jiggles; 01-24-2009 at 11:00 PM.
then you have nothing to worry about. it connected to you on that port. end of story.
I am not a member of SCT but I think it's something to do with the router. Just google it and there are a lot of ways to tweak modem.
Last edited by toxic; 04-05-2009 at 11:24 PM.
i will ask you again, what's the model of the modem/router.
there are routers with only one RJ45 port. I had a Thompson one just like that.
piece of garbage.
I used to get the same issue even after opening the good port in my router so i finally activated uPnP and it works fine until now.
whenever people agree with me, i always feel i must be wrong.
Bookmarks