Wingate WWW Proxy failing

Dec 20 07 10:24 am

I've been getting a frequent failure of clients ability to connect through the WWW proxy - they report the proxy is refusing connections. Sometimes I can restart the Wingate engine and cure it, others the engine refuses to stop and have to reboot the machine (latest Wingate version, XP on latest service pack etc). The Wingate machine itself is also unable to access the internet.

The machine itself is still running and clients can collect mail okay (not set to be handled by Wingate)

There are log entries that coincide with some of the freezes :

12/17/07 16:48:26 192.168.1.3 Guest 0000002461 Requested: http://www.google.co.uk/search
12/17/07 16:48:26 Error: Caught unknown exception in CTCPServiceSocketCallback()
12/17/07 16:48:38 192.168.1.3 Guest 0000002463 Requested: http://www.google.co.uk/search
12/17/07 16:48:38 192.168.1.3 Guest 0000002463 Error: Caught unknown exception in CWWWSession::OnRead() - terminating
12/17/07 16:48:38 192.168.1.3 Guest 0000002463 Traffic 0 969 0 0 0s
12/17/07 16:48:44 192.168.1.3 Guest 0000002464 Traffic 342 995 0 0 0s
12/17/07 16:48:55 192.168.1.3 Guest 0000002465 Traffic 342 995 0 0 0s
12/17/07 16:50:02 Error: Caught unknown exception in CTCPServiceSocketCallback()
12/17/07 16:50:20 Error: Caught unknown exception in CTCPServiceSocketCallback()
12/17/07 16:50:31 Error: Caught unknown exception in CTCPServiceSocketCallback()
12/17/07 16:52:08 Error: Caught unknown exception in CTCPServiceSocketCallback()
12/17/07 16:52:50 Error: Caught unknown exception in CTCPServiceSocketCallback()
12/17/07 16:53:49 Error: Caught unknown exception in CTCPServiceSocketCallback()
12/17/07 17:03:38 Error: Caught unknown exception in CTCPServiceSocketCallback()
12/17/07 17:04:13 Error: Caught unknown exception in CTCPServiceSocketCallback()
12/17/07 17:04:24 Service stopped

12/19/07 17:41:51 192.168.1.3 0000005177 Error: Caught unknown exception in CWWWSession::OnRead() - terminating
12/19/07 17:41:51 192.168.1.3 0000005177 Traffic 16822 562 495 16824 1s
12/19/07 17:41:51 192.168.1.3 Guest 0000005181 Error: Malformed Request
12/19/07 17:46:24 Service started successfully

12/19/07 17:56:49 192.168.1.3 Guest 0000000143 Error: Caught unknown exception in CWWWSession::OnRead() - terminating
12/19/07 17:56:49 192.168.1.3 Guest 0000000143 Error: Caught unknown exception in CWWWSession::OnRead() - terminating
1
12/19/07 18:03:27 Service started successfully

Ideas please? I was thinking of uninstalling/reinstalling to see if it helps as this and other freezes have been happening since I built this machine a short while back.

BTW, I reported on another thread that I was getting DNS flood lookups, subsequently solved. I just noticed that the log file for that day was 2Gb!

Tony

Dec 20 07 4:17 pm

Hi Tony

those log messages don't look good. Is this a common occurence?

Couple of things to check on that machine.

1. Are you running any other antivirus software on it that is scanning the WinGate folders? This can cause problems as WinGate frequently touches log files etc.

2. Are you running any other firewall software on that machine.

3. Do you have more than one default gateway specified for any adapter or more than one adapter with a default gateway (quick check is if you type "route print" from the command prompt, do you get more than one line with a network address of 0.0.0.0)

4. Is the system highly loaded? what sort of CPU usage is WinGate using?

regards

Adrien

Dec 20 07 9:37 pm

Hi Tony
those log messages don't look good. Is this a common occurence?

It is with this machine, sometimes two or three times a day.

1. Are you running any other antivirus software on it that is scanning the WinGate folders? This can cause problems as WinGate frequently touches log files etc.
Yes, I run AVG on it. Although the scheduled daily scan doesn't coincide with any failures over the past few days ... I can probably exclude the dir

2. Are you running any other firewall software on that machine.
Nope.

3. Do you have more than one default gateway specified for any adapter or more than one adapter with a default gateway (quick check is if you type "route print" from the command prompt, do you get more than one line with a network address of 0.0.0.0)

No, that only shows the external card as having 0.0.0.0 as the destination

4. Is the system highly loaded? what sort of CPU usage is WinGate using?

Quite lightly, it's only currently running three full time PCs, most of which are not doing a lot other than monitoring. Over the past half hour it hasn't gone above 15% and is around 0 - 5% most of the time.

In the past it has run up to 18 PCs and been really used hard - then it ran flawlessly for the majority of the time but that was on a different machine. A much slower Pentium with less memory, currently it's on a spare Dell Precision 530 of which I have four left from a previous project, 2 x 2.6Ghz or 2.8 Pentium 4s, 1Gb+ memory. Spare memory on the Machine is about 70% most of the time. There's buckets of spare disk space/swap file etc.

The only software running permanently is KLS backup for my whole system. It does back up the Wingate c: dir but, again, doesn't coincide with crashes. I can disable covering that dir if it might help?

A couple of things I did last night based on my memory of past problems when I first use Wingate many years back:

1) Added Memory Guard just in case

2) Stopped running Gatekeeper permanently

3) Checked and adjusted my TCP settings using SG TCP and it did change my MTU. This had been done on the previous machine but not so far on this one

Interestingly, it's still all running this morning which it hasn't always been. So I'll leave it so for a while as is and see what happens. I'll keep you informed.

I also notice that the option to move the history log dir is greyed out for some reason when I try it? I was going to try and run it on a network share instead of C to find out if this would get remote history running for me ... I can change the appropriate registry entry if needs be.

BTW, I've been asked to set up a mail server, gateway, basic secure web server via a VPN etc and intend using Wingate to do this. However, it'll be under Linux and haven't used that version of your software that I see you supply. Important part is that it allows domain whitelisting for mail - does the Linux version allow this?

Thanks for your help so far. Off out into a white -7 deg C to walk the dog now!

Last edited by tb on Dec 23 07 6:56 am, edited 2 times in total.

Dec 21 07 1:49 am

Checking the WWW log, there have been a few more this morning but haven't proved fatal (yet) - these have some error codes - in fact these are due to an error typing the URL so don't know if relevant.

In fact, should I see these on screen, would have thought they'd have been converted to a 'user-friendly' error message - as, if I type in a non-existent domain, ['http://www.crapdomainz.com/' in this example], the browser displays:

Socket Error
Socket Error 10049 {Thd 3188} [socket #DCC, 0.0.0.0:2515 to :0]

Here are the WWW log versions:

Code:: 12/20/07 11:28:12 192.168.1.3 Guest 0000000890 Requested: http://www.jaguarautomobila.com/ 12/20/07 11:28:12 192.168.1.3 Guest 0000000890 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 1208} [socket #FF4, 0.0.0.0:2156 to :0] - terminating 12/20/07 11:28:12 192.168.1.3 Guest 0000000890 Traffic 342 455 0 0 0s 12/20/07 11:28:12 192.168.1.3 Guest 0000000891 Requested: http://www.jaguarautomobila.com/favicon.ico 12/20/07 11:28:12 192.168.1.3 Guest 0000000891 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 1568} [socket #E00, 0.0.0.0:2157 to :0] - terminating 12/20/07 11:28:12 192.168.1.3 Guest 0000000891 Traffic 342 386 0 0 0s 12/20/07 11:28:49 192.168.1.3 Guest 0000000892 Requested: http://www.jaguarautomobila.com/ 12/20/07 11:28:49 192.168.1.3 Guest 0000000892 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 3216} [socket #FC4, 0.0.0.0:2161 to :0] - terminating

Dec 22 07 12:45 am

I was hoping for some bright ideas on the exceptions ...

It ran for about 40 hours before locking up again.

When I got back this morning, the machine was almost frozen, except for a couple of seconds every 15 seconds or so when I could access the mouse. Task Manager wasn't showing much activity.

I managed to stop the Wingate engine - and the machine returned to normal. After a few minutes, I restarted it - but it locked up again immediately in the same way.

Restarting the machine and all is currently normal. I have been watching Wingate memory usage - normally it's around 9Mbyte +/-. Before I stopped it was was just over 12MByte.

Here's the WWW Proxy log entries - they show similar errors to before but this time with some error codes... None of the terminals had any manual activity during the period shown:

Code:: 12/21/07 10:16:07 192.168.1.3 Guest 0000002746 Traffic 4289 949 892 4283 118s 12/21/07 10:16:17 192.168.1.3 Guest 0000002746 Traffic 0 0 0 0 10s 12/21/07 10:32:29 192.168.1.3 Guest 0000002750 Requested: http://sb.google.com/safebrowsing/update 12/21/07 10:33:18 192.168.1.3 Guest 0000002750 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Connection to Remote Host timed out - terminating 12/21/07 10:33:18 192.168.1.3 Guest 0000002750 Traffic 314 649 0 0 49s 12/21/07 10:36:50 192.168.1.250 Guest 0000002757 Requested: http://en-gb.fxfeeds.mozilla.com/en-GB/firefox/headlines.xml 12/21/07 10:37:40 192.168.1.250 Guest 0000002757 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 4044} [socket #D74, 0.0.0.0:4564 to :0] - terminating 12/21/07 10:37:40 192.168.1.250 Guest 0000002757 Traffic 342 699 0 0 65s 12/21/07 10:43:58 192.168.1.250 Guest 0000002776 Requested: http://sb.google.com/safebrowsing/update 12/21/07 10:44:31 192.168.1.3 Guest 0000002778 Requested: http://bmsgs.ebay.co.uk/ws/eBayISAPI.dll 12/21/07 10:44:31 192.168.1.3 Guest 0000002777 Requested: http://bmsgs.ebay.co.uk/ws/eBayISAPI.dll 12/21/07 10:45:21 192.168.1.3 Guest 0000002778 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 2564} [socket #CA4, 0.0.0.0:4569 to :0] - terminating 12/21/07 10:45:21 192.168.1.3 Guest 0000002777 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 992} [socket #E34, 0.0.0.0:4568 to :0] - terminating 12/21/07 10:45:21 192.168.1.3 Guest 0000002778 Traffic 342 2417 0 0 65s 12/21/07 10:45:21 192.168.1.3 Guest 0000002777 Traffic 341 2387 0 0 65s 12/21/07 10:45:38 192.168.1.3 Guest 0000002779 Requested: http://bmsgs.ebay.co.uk/ws/eBayISAPI.dll 12/21/07 10:45:38 192.168.1.250 Guest 0000002776 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 2804} [socket #E30, 0.0.0.0:4570 to :0] - terminating 12/21/07 10:45:38 192.168.1.3 Guest 0000002780 Requested: http://bmsgs.ebay.co.uk/ws/eBayISAPI.dll 12/21/07 10:45:38 192.168.1.250 Guest 0000002776 Traffic 342 678 0 0 134s 12/21/07 10:46:28 192.168.1.3 Guest 0000002779 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 2920} [socket #F0C, 0.0.0.0:4571 to :0] - terminating 12/21/07 10:46:28 192.168.1.3 Guest 0000002780 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 1616} [socket #E30, 0.0.0.0:4572 to :0] - terminating 12/21/07 10:46:28 192.168.1.3 Guest 0000002779 Traffic 342 2417 0 0 67s 12/21/07 10:46:28 192.168.1.3 Guest 0000002780 Traffic 342 2387 0 0 67s 12/21/07 10:46:44 192.168.1.3 Guest 0000002781 Requested: http://sb.google.com/safebrowsing/update 12/21/07 10:47:18 192.168.1.250 Guest 0000002782 Requested: http://sb.google.com/safebrowsing/update 12/21/07 10:48:25 192.168.1.3 Guest 0000002781 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 3748} [socket #A1C, 0.0.0.0:4575 to :0] - terminating 12/21/07 10:48:25 192.168.1.3 Guest 0000002781 Traffic 342 949 0 0 134s 12/21/07 10:48:58 192.168.1.250 Guest 0000002782 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 2964} [socket #FB8, 0.0.0.0:4576 to :0] - terminating 12/21/07 10:48:58 192.168.1.250 Guest 0000002782 Traffic 342 678 0 0 133s 12/21/07 10:50:09 192.168.1.3 Guest 0000002792 Requested: http://sb.google.com/safebrowsing/update 12/21/07 10:50:42 192.168.1.250 Guest 0000002798 Requested: http://sb.google.com/safebrowsing/update 12/21/07 10:51:49 192.168.1.3 Guest 0000002792 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 3308} [socket #CA0, 0.0.0.0:4579 to :0] - terminating 12/21/07 10:51:49 192.168.1.3 Guest 0000002792 Traffic 342 949 0 0 134s 12/21/07 10:52:22 192.168.1.250 Guest 0000002798 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 2008} [socket #DDC, 0.0.0.0:4580 to :0] - terminating 12/21/07 10:52:22 192.168.1.250 Guest 0000002798 Traffic 342 678 0 0 133s 12/21/07 10:53:29 192.168.1.3 Guest 0000002852 Requested: http://sb.google.com/safebrowsing/update 12/21/07 10:55:09 192.168.1.3 Guest 0000002852 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 2312} [socket #E74, 0.0.0.0:4582 to :0] - terminating 12/21/07 10:55:09 192.168.1.3 Guest 0000002852 Traffic 342 949 0 0 133s 12/21/07 11:11:12 192.168.1.3 Guest 0000003067 Requested: http://sqm.microsoft.com/sqm/windows/sqmserver.dll 12/21/07 11:12:02 192.168.1.3 Guest 0000003067 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 3664} [socket #F18, 0.0.0.0:4586 to :0] - terminating 12/21/07 11:12:02 192.168.1.3 Guest 0000003067 Traffic 0 630 0 0 80s 12/21/07 11:13:09 192.168.1.3 Guest 0000003082 Requested: http://sqm.microsoft.com/sqm/windows/sqmserver.dll 12/21/07 11:13:10 Service stopped 12/21/07 11:14:43 Service started successfully 12/21/07 11:22:23 Service started successfully

Dec 22 07 4:38 am

I decided to uninstall/reinstall and kept a copy of the registry export so I could import that.

It lasted 90 mins this time before Wingate virtually froze as it did before....

I've now uninstalled everything on the machine that isn't needed and there are no other apps running (although I've not had any problem in the past on the previous machine). So Wingate is now running virtually by itself.

BTW, that socket error that displays when I enter an unknown domain never used to happen on the old machine...

Here's the log from the last lock up:

Code:: 12/21/07 13:38:31 192.168.1.3 Guest 0000000230 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Connection to Remote Host timed out - terminating 12/21/07 13:38:31 192.168.1.3 Guest 0000000230 Traffic 314 649 0 0 49s 12/21/07 13:46:40 192.168.1.3 Guest 0000000248 Requested: http://sb.google.com/safebrowsing/update 12/21/07 13:48:20 192.168.1.3 Guest 0000000248 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 3828} [socket #C5C, 0.0.0.0:1354 to :0] - terminating 12/21/07 13:48:20 192.168.1.3 Guest 0000000248 Traffic 342 949 0 0 133s 12/21/07 13:49:54 192.168.1.3 Guest 0000000249 Requested: http://sb.google.com/safebrowsing/update 12/21/07 13:51:34 192.168.1.3 Guest 0000000249 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 2476} [socket #BE0, 0.0.0.0:1355 to :0] - terminating 12/21/07 13:51:34 192.168.1.3 Guest 0000000249 Traffic 342 949 0 0 134s 12/21/07 13:53:06 192.168.1.3 Guest 0000000250 Requested: http://sb.google.com/safebrowsing/update 12/21/07 13:54:46 192.168.1.3 Guest 0000000250 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Socket Error 10049 {Thd 2828} [socket #BB4, 0.0.0.0:1357 to :0] - terminating 12/21/07 13:54:46 192.168.1.3 Guest 0000000250 Traffic 342 949 0 0 132s 12/21/07 15:10:31 192.168.1.3 Guest 0000000632 Requested: http://sqm.microsoft.com/sqm/windows/sqmserver.dll 12/21/07 15:10:51 Service stopped 12/21/07 15:12:13 Service started successfully 12/21/07 15:14:13 Service stopped 12/21/07 15:23:01 Service started successfully

Dec 22 07 8:02 am

Within an hour, Wingate failed twice more with the same errors.

I've now taken a different approach in an effort to get a working system.

I deinstalled 6.2.2, then installed 6.2.0 - the latter I'd used for some time with few problems. I also have NOT imported the old registry settings. I've just left Wingate as it started up. Except for one change - adding the Wingate machine IP to the advanced options setting to get round the DNS flood problem. All services are enabled and everything is working okay for me.

The two network cards were identified correctly as Internal/External.

We'll see what happens. If it can run for some days, I'll upgrade back to 6.2.2.

I note that every time I install Wingate, it says it's found an instance of ICS on the machine. However, when I check, there are none set up.

The browser message that shows the actual TCP error rather than a 404 is still there.

Not a lot else I can do without some support assistance.

Tony

Dec 22 07 12:34 pm

Hi tony

We've been getting a few more reports of this issue lately where lockups affect not just WinGate, but the whole machine (i.e. mouse becomes unresponsive etc).

the only sort of software that can do that is a kernel driver, which is the ENS driver in WinGate.

So I'm suspicious that a recent windows update may be causing this problem, has your system installed any windows updates recently (i.e. coinciding with the start of the problem).

Regards

Adrien

Dec 22 07 1:08 pm

Thanks.

There have been a rash of updates recently and I have installed them all:

Code:: Windows XP Security Update for Microsoft XML Core Services 4.0 Service Pack 2 (KB936181) 16 December 2007 Automatic Updates Windows XP Cumulative Security Update for Internet Explorer 7 for Windows XP (KB942615) 12 December 2007 Automatic Updates Windows XP Security Update for Internet Explorer 7 for Windows XP (KB938127) 12 December 2007 Automatic Updates Windows XP Security Update for Windows XP (KB937894) 12 December 2007 Automatic Updates Windows XP Security Update for Windows XP (KB941569) 12 December 2007 Automatic Updates Windows XP Security Update for Windows XP (KB937894) 11 December 2007 Windows Update Windows XP Security Update for Windows XP (KB944653) 11 December 2007 Windows Update Windows XP Cumulative Security Update for Internet Explorer 6 for Windows XP (KB942615) 11 December 2007 Windows Update Windows XP Security Update for Windows XP (KB941569) 11 December 2007 Windows Update Windows XP Security Update for Windows XP (KB941568) 11 December 2007 Windows Update Windows XP Update for Windows XP (KB942840) 11 December 2007 Windows Update Windows XP Update for Windows XP (KB942763) 11 December 2007 Windows Update Windows XP Windows Malicious Software Removal Tool - December 2007 (KB890830) 11 December 2007 Windows Update Windows XP Windows Internet Explorer 7 for Windows XP 11 December 2007 Windows Update Windows XP Windows Genuine Advantage Validation Tool (KB892130) 11 December 2007 Windows Update Windows XP Security Update for Microsoft .NET Framework, Version 2.0 (KB928365) 09 December 2007 Automatic Updates Windows XP Windows Genuine Advantage Validation Tool (KB892130) 07 December 2007 Windows Update Windows XP Security Update for Windows XP (KB943460) 06 December 2007 Automatic Updates Windows XP Windows Malicious Software Removal Tool - November 2007 (KB890830) 06 December 2007 Automatic Updates Windows XP Root Certificates Update 11 October 2007 Windows Update

I commissioned the machine on the 6th December and there have been problems since then although it was initially set up back in October.

At the moment it's running fine re previous mail.

As I said earlier, the machine is only unresponsive when it has 'failed' and Wingate is running. If I stop the engine it reverts to normal. Restart manually and it locks up again. Wingate isn't using any CPU though...

BTW, would running Kaspersky AV 7.0 on the Proxy machine work - i.e. would it intercept mail and Port 80 before or after it hits Wingate?

Thanks.

Dec 22 07 9:26 pm

adrien wrote:I'm suspicious that a recent windows update may be causing this problem, has your system installed any windows updates recently (i.e. coinciding with the start of the problem).

FWIW, and as you'll have seen, one of the updates was to the .NET Framework 2.0.

I and other people had a LOT of trouble with this (see forums) since it wouldn't install properly under VISTA and XP properly. In the end, on one machine, I had to go though a long series of (Microsoft initiated) manual uninstalls, reboots and reinstalls of the entire framework code to get it working again properly. But I see that there are other complaints on programmer forums starting to appear over this upgrade plus there is this new MS Fix.

A file system that was case sensitive becomes case insensitive after you install an update for the .NET Framework 2.0

Otherwise, all is still running okay this morning. I've not had problems with the other machines (other than loss of Proxy connectivity) here since any upgrades although they are all Business Vista.

The reason I'm so keen to fix this is that I'm due to take over an existing Company LAN in the New Year and part of the upgrade is to build and install a Wingate machine as the Firewall and use the inbuilt mail server for the company mail (about 30 terminals used 24/7). And it will also provide a simple private secure Web Server for customer stock lookups.

I will not be a popular soul if it then keeps doing what it is here!

I've saved another route print - is there in fact any problem here?

Code:: Miniport 0x3 ...00 09 5b bb b5 b1 ...... NETGEAR FA311 Fast Ethernet Adapter - Packet Scheduler Miniport =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 218.158.178.91 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.1.0 255.255.255.0 192.168.1.250 192.168.1.250 20 192.168.1.250 255.255.255.255 127.0.0.1 127.0.0.1 20 192.168.1.255 255.255.255.255 192.168.1.250 192.168.1.250 20 218.158.178.88 255.255.255.248 218.158.178.91 218.158.178.91 20 218.158.178.91 255.255.255.255 127.0.0.1 127.0.0.1 20 218.158.178.255 255.255.255.255 218.158.178.91 218.158.178.91 20 224.0.0.0 240.0.0.0 192.168.1.250 192.168.1.250 20 224.0.0.0 240.0.0.0 218.158.178.91 218.158.178.91 20 255.255.255.255 255.255.255.255 192.168.1.250 192.168.1.250 1 255.255.255.255 255.255.255.255 218.158.178.91 218.158.178.91 1 Default Gateway: 192.168.1.1 =========================================================================== Persistent Routes: None

Thanks

Tony

Dec 23 07 2:03 pm

Hi Tony

Your route table looks fine.

If WinGate is still locking up reliably, we've been working on a few more diagnostics in the lab here to try and track down this problem, would you be willing to run an engine that will hopefully allow us to track this down?

regards

Adrien

Dec 23 07 9:31 pm

Adrien

Well it's still running okay at the moment and coming up to the max period it's run since i started with this machine in about 4 hours. I don't see any log errors at all at the moment.

I'll run a test if you want as long as the basic functionality is still there as I have to do some work occasionally!

Do you have any answer for that untrapped TCP error message when the domain doesn't exist please?

Tony

Dec 24 07 6:57 am

Unfortunately it failed again about an hour ago, roughly same run period as last time.

There are no log errors I can see this time though (except for a correctly caught timeout) but the symptoms are the same. Machine is frozen for every 10 secs out of 13 or so, stopping the engine puts the machine back to normal. Restart the engine and it locks up again - the only cure is a reboot.

I've now put it back to 6.2.2 again but not changed any config.

One other thing - I've been playing with the built in Web Server for some tests I want to do. I've been trying to access it from the internet but can't.

I noticed that the external adaptor wasn't bound to the WWW proxy - adding this and external internet access works fine (also, I only have 6 user licence so don't have any Hosts tab). Is it in fact only meant for use as an internal web server? I've removed the external binding in case this raises any dire security issues....

Tony

Dec 27 07 11:08 pm

I believe I've found the cause of all these problems, another memory resident startup program! I've had it running for over two days with no problems. I'll leave it for a longer period and report back whether it's still okay.

Dec 28 07 10:33 am

thanks for that.

Re some of your earlier questions -

1. TCP error messages.

You can override these in the registry, and normally WinGate ships with more descriptive text for most of the common TCP errors. These live in the registry under

HKEY_LOCAL_MACHINE\Software\Qbik Software\WinGate\ErrorStrings\SocketErrors

The name is the error number in decimal (e.g. 10022) and the value is the error message. For name lookup failures, the name of the reg value is "HostnameLookupFailed". Do you have values for these in the registry on that machine?

2. WWW proxy as a web server

One thing to keep in mind if you wish to use the WWW proxy as a web server for external access, is to block unauthorised use of the proxy functionality from the internet, else you'll find people start surfing through your proxy to anonymise their connections.

Adrien

Jan 02 08 12:51 am

tb wrote:I believe I've found the cause of all these problems, another memory resident startup program! I've had it running for over two days with no problems. I'll leave it for a longer period and report back whether it's still okay.

Well it's been running ever since (5 days or so) and I've reloaded and run all the programs that I used to run as well with no adverse effects so far - except for my backup program that is, this appears to be the culprit.

When I took everything out other than Wingate to debug this, I forgot to check Task Manager. What I hadn't spotted was that my backup program (KLS Backup) has a service manager running (loaded at startup) that is otherwise invisible. So backups were still running ....

I happened to be in front the terminal when a popup in the system tray said the backup had started a run - and at that instant the terminal went into frozen mode for about 10 secs etc!

Strange thing is that the backup had no connection to Wingate as such - it was actually synchronising an earlier backup to another backup on my LAN. the Wingate dir itself isn't backed up by this system.

With that program removed all returned to normal - including no more odd error messages in FireFox when a domain doesn't exist! Reload the service manager and back they come!!

So I have stopped using that backup program and moved to a RAID-1 type background process on the terminal that real-time syncs my backups without having to set much up. Doesn't seem to cause any problems.

I still cannot get the Remote History viewing to work though. Neither XP SP2 or Vista (with SP 1 RC1) will view it despite trying all sorts of ways. I used to be able to do this via the old Wingate terminal but this one won't play.

So apologies for the false alarm on Wingate although it was interesting debugging it.

Happy New Year!

Tony

Jan 02 08 12:52 am

adrien wrote:thanks for that.

Re some of your earlier questions -

2. WWW proxy as a web server

One thing to keep in mind if you wish to use the WWW proxy as a web server for external access, is to block unauthorised use of the proxy functionality from the internet, else you'll find people start surfing through your proxy to anonymise their connections.

Adrien

Could you elaborate on that please as to how to set up the block?

Thanks

Tony

Jan 15 08 9:49 am

Hi tony

The easiest way if you want to securely use WinGate as a webserver is to set up another WWW proxy which is bound to external.

The one that is installed by default should only be bound to internal adapters.

In the policy for the external server, you'd add 1 recipient, ignore system policies, and set an advanced filter for that recipient where the parameter "is non-proxy request" must be TRUE.

Sorry about the param name - it's a bit of a hangover from the old days when by default WinGate processed proxy requests, and anything that wasn't a proxy request was called a non-proxy request. We changed that to refer to server requests in a later version .