Very strange torrent problem

[vincom2]

Hi everyone.

I'm using Deluge 0.5.9.3. Basically everything worked fine until a few days ago. Then I started getting "no incoming connections".

I'm quite sure I've done everything that needs to be done. I've definitely forwarded my bittorrent port, and when I use utorrent port checker it says "port open". When I run netstat -an that port is being listened on. Deluge is also definitely set to use that port, so I doubt it's any issue with the port forwarding.

I've googled my cable modem model (Motorola SBV5121) and am sure it isn't concealing any kind of firewall or such, so I doubt I'm double-NATed. I've also disabled zonealarm to test, and still "no incoming connections".

I'm also very sure that it's not a problem with my torrents, because in the first place I'm seeding a number of torrents that all definitely have peers, and yet am not doing much upload. Also, I'm leeching a torrent with 230 seeds and 136 peers, and yet I'm connected to a grand total of 4 seeds and 1 peer and getting a miserable download speed of around 4-15kbps.

If it matters, my router is a Linksys WRT54G running Tomato 1.21.

p.s. Yes, I have assigned my computer a static internal IP and am forwarding the port to the correct IP.

Thank you in advance. (This problem has really been frustrating me for days)

[shizuko]

well, you are using a very outdated version of the buggy client for windows - deluge, i recommend you to update:

http://deluge-torrent.org/downloads.php

[vincom2]

Ok, I installed uTorrent 1.8.1 and tested it out, and no good. Port open and all, but I still get "no incoming connections", and in my peer lists no peer has the 'I' flag...

Any ideas what might be going wrong?

Incidentally, I'm not sure if this has any bearing on the problem, but utorrent port checker says my port is open, but canyouseeme.org says it's not. ut port checker and canyouseeme also give different IP addresses - the one ut gives matches the WAN IP on my router config page and the IP address I found on the peerlist of a tracker (at least the first 2 octets), while the canyouseeme one matches a few other online IP address checkers. Before this incoming connection problem started the IP addresses also used to differ iirc, but on both checkers the port was always reported as open.

[PaRtH]

i think your port is closed...you can test uTorrent with a high seeded toorent file...so you will knwo that is is a problem with the torrent file or your port forwarding... Choose one torrent having a big number of seeders and try it...best of luck...

regards.

[vincom2]

i think your port is closed...you can test uTorrent with a high seeded toorent file...so you will knwo that is is a problem with the torrent file or your port forwarding... Choose one torrent having a big number of seeders and try it...best of luck...

regards.

Well, as I've said, utorrent port checker definitely reports my port open, I'm sure my router is configured to forward the right port and so on.

I tested the ubuntu 8.10 32-bit torrent yesterday. For about a minute or so I had an incoming connection; then that peer dced and I never got an incoming connection after that again.

So port forwarding I'm quite sure of, and I tested a well-seeded torrent...

Thanks anyway.

Anyone have any ideas?

[TurboTuna]

Do you have any other ports forwarded that work? perhaps RDP/webserver or something you can use to test your port forwards?

[PaRtH]

is it like your ISP is restricting something like torrents and etc.?I am asking as some ISPs take torrents as illegal... so...

Otherwise your port is ok, torrent is seeded properly... have you checked you personal firewall?You need to unblock port in it... pls also check that.

if everything id fine..then i thnk u shld try with different port num..take some big num...say 51200 or 52300 etc...

regards.

[vincom2]

is it like your ISP is restricting something like torrents and etc.?I am asking as some ISPs take torrents as illegal... so...

Otherwise your port is ok, torrent is seeded properly... have you checked you personal firewall?You need to unblock port in it... pls also check that.

if everything id fine..then i thnk u shld try with different port num..take some big num...say 51200 or 52300 etc...

regards.

I don't think they are, because someone else I know on the same ISP has no problems (although he says he did have the same problem for about 1 day a week or so ago :o).

And I'm already using a port in the 60000's.

Shut off my firewall too, but nothing happened.

Do you have any other ports forwarded that work? perhaps RDP/webserver or something you can use to test your port forwards?

That's an idea; I have an ssh port forwarded I think. I'll try and test it.

I may not have internet access for a while though, so I'll bump this thread after I test I guess. Hope that's allowed :\

Thanks.

[Lannister]

Might not be the answer, but have you tried simply restarting/powering off your router? I had a similar problem the other day and that (powering off) fixed it.

[vincom2]

Might not be the answer, but have you tried simply restarting/powering off your router? I had a similar problem the other day and that (powering off) fixed it.

Haha, I've restarted it (via the web interface) countless times :\ I even upgraded firmware version, and nothing happened.

I haven't tried pulling the power or wiping the NVRAM though. Perhaps I should.

[Lannister]

Haha, I've restarted it (via the web interface) countless times :\ I even upgraded firmware version, and nothing happened.

I haven't tried pulling the power or wiping the NVRAM though. Perhaps I should.

It's always worth a try :) , like I said, I had a similar problem and pulling the power out on the back of the router and powering on again fixed it.