the forums at degreez.net

I have been having problems with some tracker and after many experiments, it appears to be problem with NAT.

regardless you are behind router or software firewall, when the tracker server DISABLE NAT CEHCKING, you will probably get a yellow light.

to solve this issue, just go to preference, advance, key in your WAN IP into the LOCAL IP field.
your WAN IP is something that not started with 192.168.xxx.x , it should look like this 68.xxx.xxx.xxx or 210.xxx.xxx.xxx

save changes and restart BT. you will see remote connection in short period.

for those who are behind router, go to your router config page. eg:192.168.2.1, 192.168.0.1, etc
check your WAN IP, put it into the BT Local IP field

for those who has dynamic IP, remember to remove BT local IP, leave it blank, before you close BT as your next assigned dynamic IP will probably be different.

good luck

Don't most trackers ignore the IP parameter coming from clients anyways unless it is coming from someone on their same subnet?

Apparently not. try that yourself if you are behind router or software firewall with port forwarding enabled. try some NAT disabled tracker. with and without the WAN IP in the IP field. and you will see the difference.

tried several times on many different trackers to come out with this workaround.

good luck

Apparently not. try that yourself if you are behind router or software firewall with port forwarding enabled. try some NAT disabled tracker. with and without the WAN IP in the IP field. and you will see the difference.

tried several times on many different trackers to come out with this workaround.

good luck

If the tracker has disabled the ip override, it will not work, depends all on the tracker's configuration.