TRansparent proxy problems

[christiant]

Hello, I've recently installed wingate, and it works fine untill I enable tranparent proxying on port 80. the browsers using wingate as a proxy have a "socket error 10107" message. I then stop the transparent proxying of port 80 and things work again.

I can't afford not to have transparent proxying through port 80, because the whole purpose of having wingate is to denigh and alow web traffic to specific users.

I had wingate trial running on a different computer and it worked fine, so I'm sure the problem is either my configuration or a program conflicting with wingate however I'm not sure where to start.

here is an example from the log of the error ocuring (I had to edit out the websites in it because of forum rules)..........

7/03/07 08:55:37 Service stopped
07/03/07 08:55:38 Service started successfully
07/03/07 08:55:38 Configuration changed
07/03/07 08:55:41 192.168.10.120 archiving 0000002015 Created:
07/03/07 08:55:41 192.168.10.120 archiving 0000002015 Requested:
07/03/07 08:55:41 192.168.10.120 archiving 0000002015 Debug: [] Copy to use: SERVER
07/03/07 08:55:41 192.168.10.120 archiving 0000002015 Debug: WWW Session sending server request in thread 83c
07/03/07 08:55:41 192.168.10.120 archiving 0000002015 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10107 {Thd 2108} [socket #F28] - terminating
07/03/07 08:55:41 192.168.10.120 archiving 0000002015 Traffic 322 1370 0 0 1s
07/03/07 08:55:41 192.168.10.120 archiving 0000002015 Terminated exit code 2
07/03/07 08:55:41 192.168.10.120 archiving 0000002016 Created:
07/03/07 08:55:41 192.168.10.120 archiving 0000002016 Requested:
07/03/07 08:55:41 192.168.10.120 archiving 0000002016 Debug: [] Copy to use: SERVER
07/03/07 08:55:41 192.168.10.120 archiving 0000002016 Debug: WWW Session sending server request in thread b90
07/03/07 08:55:41 192.168.10.120 archiving 0000002016 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10107 {Thd 2960} [socket #F34] - terminating
07/03/07 08:55:41 192.168.10.120 archiving 0000002016 Traffic 322 1350 0 0 0s
07/03/07 08:55:41 192.168.10.120 archiving 0000002016 Terminated exit code 2
07/03/07 08:55:44 192.168.10.120 archiving 0000002018 Created:
07/03/07 08:55:44 192.168.10.120 archiving 0000002018 Requested:
07/03/07 08:55:44 192.168.10.120 archiving 0000002018 Debug: [] Copy to use: CHECK CLIENT CACHED
07/03/07 08:55:44 192.168.10.120 archiving 0000002018 Debug: WWW Session sending server request in thread a10
07/03/07 08:55:44 192.168.10.120 archiving 0000002018 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10107 {Thd 2576} [socket #CE0] - terminating
07/03/07 08:55:44 192.168.10.120 archiving 0000002018 Traffic 322 332 0 0 0s
07/03/07 08:55:44 192.168.10.120 archiving 0000002018 Terminated exit code 2
07/03/07 08:55:54 Service stopped
07/03/07 08:55:54 Service started successfully
07/03/07 08:55:54 Configuration changed

Thanks.
Christian.

[adrien]

error 10107, is WSASYSCALLFAILURE which according to MS means

"A system call that should never fail has failed."

not very helpful.

When you have intercepts enabled on the WinGate machine, are you able to still surf from the WinGate machine with a browser?

I'm wondering if you have some interesting filtering software on this machine which is messing with the socket stack - some AV software installs socket filtering stuff which can cause all sorts of problems.

just to clarify - the clients that see the error are those configured to use WinGate as a proxy, but the clients that aren't configured to use WinGate as a proxy don't see the error?

Regards

Adrien

[christiant]

Hi,

When you have intercepts enabled on the WinGate machine, are you able to still surf from the WinGate machine with a browser?

Yes, I got the socet failure on a client machine, but I was able to get to msn.com on the wingate machine.

I'm wondering if you have some interesting filtering software on this machine which is messing with the socket stack - some AV software installs socket filtering stuff which can cause all sorts of problems.

I checked, and I couldn't see anything. I had Apache installed, but I un-installed it. I went into controll panel, and couldn't see any services that looked like they would be keeping any ports open. I had AVG running, so I ditched that, still had the same problem. so I'm at a loos to what it could be.

just to clarify - the clients that see the error are those configured to use WinGate as a proxy, but the clients that aren't configured to use WinGate as a proxy don't see the error?

That's right, so

* If the clients have a direct connection to our router - they get web content
* The Wingate Server can browse websites no matter what the Transparent proxy settings are.
* If the clients have the wingate server in there gateway configuration, and the transparent proxy on port 80 is off they get websites
* If the clients have Wingate in there gateway - and - the transparent gateway is turned on for port 80 they get a socket error
[/quote]

[christiant]

hello?