Jump to content

Having uTorrent listen for incoming torrent connections on port 80


Liquid5n0w

Recommended Posts

Posted

I've recently moved to South Korea, and my internet connection here rocks. I've achieved 8mbytes/s on multiple occasions. But it seems that I can't have any ports open except 80 and 443. When I test those two it works, but when I setup utorrent to use it the icon on the bottom says 'Listen error, You should change your listen port'.

I'm still doing port scans on my connection, but it seems that only those two ports are open. If anyone has a resource to portscan with I would be greatful.

But my main problem is that utorrent doesn't seem to work with the HTTP and HTTPS ports, which are the only ones that work. Help?

Posted

Do you actually have a connection of your own? Or are you just plugging into a wall or something (with no control over the router that goes to)?

It doesn't sound like it's a 'real' connection if all the ports are closed.

In addition, do you have a firewall?

Posted

No router, it's straight Tbase100 into the wall. It seems to configure a little bit weirdly though:

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : kornet

Link-local IPv6 Address . . . . . : fe80::5899:317e:9263:7e8b%10

IPv4 Address. . . . . . . . . . . : 221.151.250.229

Subnet Mask . . . . . . . . . . . : 255.255.255.128

Default Gateway . . . . . . . . . : 221.151.250.254

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . : kornet

Link-local IPv6 Address . . . . . : fe80::200:5efe:221.151.250.229%13

Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . :

IPv6 Address. . . . . . . . . . . : 2001:0:d5c7:a2ca:47a:3fc5:2268:51a

Link-local IPv6 Address . . . . . : fe80::47a:3fc5:2268:51a%11

Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . : kornet

IPv6 Address. . . . . . . . . . . : 2002:dd97:fae5::dd97:fae5

Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301

Posted

Well, it seems that whoever controls the router that you're plugged into (the port on the wall goes there) is blocking your ports.

Can any program actually get an incoming connection on this connection?

Posted

I use the port test built into utorrent, the one that goes through the browser, and it shows that 80 and 443 are both open. But utorrent can't listen on those ports it seems.

Also, I did host a listen server for the left 4 dead demo and people connected fine without and configuration, but that could be for other reasons, like there was a lobby first and they could have set it up to make the connections from my computer to the other players.

Posted
Vista with all security features disabled.

I'd be a little worried about viruses/trojans if your ports 80 and 443 are still open. Windows Vista's firewall alone is probably sufficient to block incoming stuff.

Of those 2 ports, I'd figure uTorrent would be 'better off' trying port 443.

Is UPnP and NAT-PMP working in uTorrent?

You should see that in logger at uTorrent start if they're enabled.

Posted

listenerrorwz5.jpg

There's the error I'm getting, and I'm quite sure it has nothing to do with the port not being open because that error is different from the error I get eventually with port 6881 or anything else. And this error comes up immediately, unlike the normal one. I think it's a problem with uTorrent not being allowed to listen on port 80 or 443, not to do with those ports being open or not.

Posted

µTorrent can listen on any port.

The only reason it would be unable to is if a) something else is already listening on that port B) your firewall is blocking it. In certain cases, it can also happen if you set an invalid net.bind_ip.

Look at the Logger tab and see if there's any error.

Posted

Hmm, seems it might have been skype. I'm going to test it out today and if it works with skype closed I'll be quite happy.

Edit: Well, uTorrent isn't getting any connections now, it seems to just stay in the yellow state. That was on port 80, I'll try it on port 443 now.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...