Allowing Torrent Downloading

[agroda]

I have a fresh installation of WinGate and websurfing and everything is working fine through Port 80. However, I'd like to enable downloading of torrents through the WinGate proxy. At this time it does not work. I have tried a few things, such as goign into Extended Networking and changing default action to 'Allow' as well as disabling the firewall altogether. What do I have to do to make this work correctly?

[adrien]

Hi

most torrent clients just make a bunch of connections on various ports with TCP. This normally ends up using NAT.

For NAT to work, the client computer must be configured to use WinGate as its default gateway, and it will need the ability to resolve DNS names as well, so will need access to a DNS server (which WinGate has if you install it).

Regards

Adrien

[agroda]

This is still not working for me, let me explain topology a little bit. We have this server on our local LAN so we can use AD authentication. I was using only our internal DNS servers, although i've switched to use one (for AD) and to use the ISP's DNS server as the second. The server uses a Sonicwall router as it's default gateway. This has never been a problem in the past, and the router is configured to be wide open.

I can run a torrent client from the server itself, and it works perfectly. Even if i specify the torrent client to use a proxy and specify it's IP address. However when I try from my desktop PC, it does not work. I'm not able to set the Wingate server as the default gateway, this is for a secondary network so it's only partially used. I can specify it in proxy settings of the torrent client though, although it never seems to resolve any information. We used to do this with another software proxy and it worked fine. I think maybe the problem has to do with NAT, but I'm not sure.

[agroda]

One more comment on this, it seems that downloading from the server itself but forcing it to use itself as a proxy does NOT work as I previously said. The problem seems to be connecting to the trackers which use all sorts of different ports, 80, 3310, 6969, etc. They all just show as "Connectoin Timed Out".

Also, I did a packet trace, and when I download directly from the box and just run directly, I see all of the random ports going out (65523, 59313, etc). However when I run a trace while I am proxying through the server, I do not see that, just a bunch of encapsulated port 80 traffic. Nothing ever appears to go out to the internet though.

[adrien]

Hi

if you can't use WinGate as the default gateway for the torrent client computer, then it won't be able to use WinGate for NAT, and in fact won't go anywhere near WinGate unless you configure the torrent client to use a proxy.

Which client are you using? Most support SOCKS or HTTP tunneling, both of which WinGate has.

Regards

Adrien

[agroda]

So far I have mainly been using µTorrent although I have tried Vuze also with minimal success. Both of these support proxy servers, I've tried entering the details that I would normally use and it still always fails.

I've also added a SOCKS proxy from Wingate and I am getting the same results there. In Vuze, I will see clients show up, and then disappear right away, never establishing a connection.

[adrien]

hi

try checking the SOCKS server logs (maybe enable debug logging and log to own file).

It's possible it's a simple setting in the SOCKS server, e.g. if the client is using SOCKS4 and WinGate is configured not to allow SOCKS4, or you require auth.

Adrien

[agroda]

Well I noticed that enabling the SOCKS proxy actually seems to return some peers from the trackers, definitely not all of them. However it still fails to connect using a number of different programs. I have not found anything in the logs that is worthwhile yet.