Wingate suddently stop sharing connection with clients

[JeF]

Hello

I have Wingate 6.0.0 working on a Windows 2000 Server.
Clients are Windows 2000 PC.

Wingate is working fine but suddently it stop sharing the internet connection for the clients (Get error 404 on clients). At this time
Internet connection on the Server itself is working fine.

I can resolve the problem by stopping Gatekeeper and starting it again.
Then it works fine for a few hours, day or even weeks sometimes.
But then suddently internet connection stops for the clients and I have to restart gatekeeper again.

In the WWW Proxy log in can see those lines when it starts to fail and when connection is no more available on clients.

..
08/27/04 12:13:14 192.168.0.116 Guest 0000000621 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Host name lookup for 'www.google.ch' failed - terminating
08/27/04 12:13:14 192.168.0.116 Guest 0000000621 Debug: Client closed connection in thread 61c
08/27/04 12:13:14 192.168.0.116 Guest 0000000621 Traffic 0 585 0 0 106s
08/27/04 12:13:14 192.168.0.116 Guest 0000000621 Terminated exit code 1
08/27/04 12:13:15 192.168.0.116 Guest 0000000632 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Host name lookup for 'www.google.ch' failed - terminating
08/27/04 12:13:15 192.168.0.116 Guest 0000000632 Debug: Client closed connection in thread 5a0
08/27/04 12:13:15 192.168.0.116 Guest 0000000632 Traffic 0 585 0 0 55s
08/27/04 12:13:15 192.168.0.116 Guest 0000000632 Terminated exit code 1
08/27/04 12:13:15 192.168.0.116 Guest 0000000639 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Host name lookup for 'www.google.ch' failed - terminating
...

Thank's a lot for your help.

JeF

[adrien]

Hi Jef

This sounds like a DNS resolver issue.

WinGate's DNS resolver keeps track of all known DNS servers in the system, and uses them in a priority order based on their responsiveness.

If your main DNS server for instance stops responding for a while, WinGate can fail over to another server.

This can happen especially if you use Active Directory on your network, and have allocated internal DNS servers to the TCP/IP properties of your adapters. In some cases WinGate can start using these and stop working.

There is a utility that ships with WinGate called wgutil.exe (I think) which allows you to specify which IP addresses NOT to use for DNS. We recommend you enter any DNS server IP addresses in here that are on your network that are not able to resolve names on the Internet.

Then if you manually specify the IP address of a DNS server to use on the Internet, WinGate should always choose the correct server.

Adrien

[JeF]

Hello Adrien,

Thank's for your answer.

On my network I have a main server (called Saturnin) working as the internal DNS server for LAN address.

Another server (Polux) is working with Wingate for sharing the Internet connection available with an ADSL modem connected on it.
On this server (Polux) the DNS settings of the external TCP/IP adapter are set on a DNS server of my Internet Provider.
The DNS Server of the internal TCP/IP adapter is set on the Saturnin server (LAN DNS)

Is this configuration correct regarding Wingate ?

Unfortunately I can not found the "wgutil" in order to specify the IP adress NOT to use for DNS.

One more time, thank's for your help.

[Darrynf]

Hi.
I am having similar problems myself. I will test this putting our AD DNS Servers in the exclusion list via WGOPTIONS.EXE program and see how that goes.
The strange thing I have found on testing this is that if I point the wingate server's IE software to use Wingate as the proxy server it works fine. I can see in Gatekeeper the connections from it'self going out on the net.

Any clients inside our LAN that try to connect fail. I don't even see them appearing in Wingate which suggests that wingate may not be listening on the NIC card or our hardware Firewall that the Wingate server is connected to is suddendly stopping the traffic.

This is only a problem in 6.0.1 that was installed on Sunday night. Does 6.0.1 listen / work differently on requests etc that may cause a firewall to timeout a connection?

Cheers