Qbik Wingate keeper - Problem connecting to Server

[iamproxy]

We are using Qbik Wingate proxy server ( Version 6.6.2 ) in our network for Internet browsing and everyday morning, we experience a strange issue that the Qbik Wingate service will get automatically stopped. Suddenly Wingate disconnect, when I want to login in the Gatekeeper to see what is wrong, I have the next message:

"There was a problem connecting to the server. No data was received from the server during authentication. Check the spelling of your user name "
and then I cant login in the Gatekeeper !!!! I have to restar my server to fix this problem. Somebody can help me ???

[logan]

Sorry for the delay. Can you try upgrading to the latest version, (which at this time is 6.6.4)? There were a couple of fixes related to instability/crashing so it would be good to rule them out as causes. If the problem persists after upgrading, let the forum know and we'll take it from there.



Version 6.6.4 Build 1338 (Released 14 October 2009)

1. Fixed an issue with the DHCP server where if an old lease referred to a scope that had been deleted, WinGate would not make an offer.

2. Signed the Wgengmon and wgvpnmon applications so they can be loaded in 2k8 server without disabling UAC.

3. Added full minidump capability for troubleshooting.

4. Fixed an issue in the WWW proxy where serving files from disk with a space in the URL.

5. Fixed an issue in the WWW proxy where accessing FTP servers which use UTF-8 filenames would cause problems.

6. Fixed an issue in the WWW proxy with Basic authentication causing some sessions to hang.

7. Fixed an issue in the WWW proxy relating to policy that checked server ip address.

8. Fixed an issue in SMTP delivery - no longer try A record when MX record lookup times out.


Version 6.6.3 Build 1321 (Released 12 August 2009)

1. Fixed an issue with the WWW proxy server where certain boundary conditions with chunked responses would cause WinGate to crash if data scanning plugins were installed.

2. Fixed an issue with the WWW proxy server in reverse-proxy mode where it would break URLs with a space in them.

3. Added a registry option to enable all unknown HTTP commands in the WWW proxy.

4. Changed the WWW proxy to strip invalid headers from HTTP responses unless a registry value is set (off by default).

5. Fixed an issue relating to SSL connections where a buffer was improperly deleted.

6. Fixed an event handle leak in sockets class.

7. Fixed several buffer overwrites in SSL certificate generation code.

8. Fixed a potential buffer issue in the DHCP server.

9. Updated WinGate Advanced options applet to handle watchdog thread.[/code]