Jump to content

Using internal tracker on LAN only, no WAN


siroj

Recommended Posts

In our organisation we are setting up uTorrent (v3.4.2) as a method of distributing large amounts of data across about 100 pc's.

What we have setup is a windows machine (Server 2012) with uTorrent running as a service and acting as a tracker (bt.enable_tracker). Connection port is changed to port 443.

A new torrent file is created and marked as private, tracker url is added (http://ip_of_server:443/announce)

 

Whenever we add this torrent file to a uTorrent client it's not working. The client shows a HTTP error 400.

 

What i read is that uTorrent is using and accepting connections on the WAN ip adress when using the internal tracker. Our server has no internet connection, so no WAN ip is available.

 

Internal firewall is no issue, all ports are open. If i enable the WEB UI on the same port as a test it is working as expected.

 

Does anyone have an idea what's going wrong here?

 

Link to comment
Share on other sites

In addition to my previous post, the server DOES have an internet connection and what i am noticing is that the clients are trying to connect to the server on the WAN ip address. That is not going to work as there are no ports open to the server from the internet and opening those up is no option.

Is there a method of binding the tracker to the LAN address?

Link to comment
Share on other sites

After further testing it seems the clients are attempting to indeed connect to the WAN address of our server instead of the LAN address. When manually adding the LAN address of the server as a peer it starts downloading immediately.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...