µTorrent connecting to "strange" IP:port

[bohus]

Anyone else but me that gets connections like below from µTorrent 1.8.1 (build 12639)

Source Destination Proto

192.168.0.200, port 1787 92.55.102.56, port 8080 TCP

192.168.0.200, port 1779 92.55.102.56, port 8080 TCP

192.168.0.200, port 1753 92.55.102.56, port 8080 TCP

192.168.0.200, port 1750 92.55.102.56, port 8080 TCP

192.168.0.200, port 1706 92.55.102.56, port 8080 TCP

192.168.0.200, port 1694 92.55.102.56, port 8080 TCP

192.168.0.200, port 1646 92.55.102.56, port 8080 TCP

192.168.0.200, port 1603 92.55.102.56, port 8080 TCP

192.168.0.200, port 1583 92.55.102.56, port 8080 TCP

192.168.0.200, port 1581 92.55.102.56, port 8080 TCP

i.e. µTorrent is conneting to 92.55.102.56:8080

To see that it is µTorrent that are making those connetions I did like this

Find Process ID for µTorrent and then

netstat -b -n | find "<Process ID for µTorrent>"

i.e. for me

netstat -b -n | find "4572"

TCP 192.168.0.200:1891 92.55.102.56:8080 SYN_SENT 4572

[DreadWingKnight]

Is that IP:port combination in a peerlist for any of your torrents?

(right-click in the peer lists for each of your torrents and choose "copy peer list")

[bohus]

Yes DreadWingKnight, that IP:port combination is in one of my torrents peerlist.

I didn't check those torrents that didn't have "active" connections

Thanks

[vComet]

Maybe I am confused here but what is the problem with this connection?

All I see is you behind your NAT and someone using a good proxy which I am sure is

no longer good after being posted in a public forum.

Port 8080 is a common proxy port and proxies generate several connections much like AOL

used to do with their internal proxies.

=)