Problem with Proxy via Wingate.

[KurtDunn]

So I am behind a college firewall, and am attempting to use Wingate Client to access a relatives machine. I am running Wingate client, the other machine Wingate Server. We are attempting to use port 80 (an unblocked port) for all internet services, via winsock redirector.

We get a connection from my machine to his, but the connection window only displays Bytes sent, and no bytes returned. We're both pretty new to Wingate, but my relative is pretty well versed in networking. Any ideas to what the problem is?

[adrien]

Hi

the WinGate Client doesn't tunnel connections, so even though you can set it up to use a control connection on port 80 which might get through your firewall, subsequent connections can be on any port, which might then be blocked by the intermediary.

You might be better off with an auto-SOCKS client (i.e. sockscap) and use WinGate's SOCKS server, that makes all TCP connections through the same port.

Or you could set up a VPN, set the control channel to 80 - as long as the firewall passes UDP.

Regards

Adrien

[KurtDunn]

That was the first thing we tried, except the software I'm attempting to use is frivilously complicated, and uses atypical networking code. Sockcaps wasn't grabbing all of it.

What I'm attempting to do is to make it to where all internet traffic is funneled through the proxy server, and I had the impression that Wingate could do that.

[adrien]

VPN is probably a better bet.

that does it at the packet level, rather than proxies in WinGate which do it at the application protocol level, and therefore could miss some traffic you need.

That way you'll tunnel all IP packets (including ICMP, UDP and TCP and others).