WinGate 5.2.x service start failure

[laterizi]

Hi,

i have a problem: i would run WinGate 5.2.2 or WinGate 5.2.3 in a gateway PC with Microsoft Windows 2000 Server SP3.

My hardware configuration is:

- CPU: AMD Duron 1200 MHz
- RAM: 256 Mb SDRAM
- Mo/Bo: MSI K7T Pro2-A (based on VIA KT133A)
- HDD: Maxtor 40 Gb 7200 RPM, EIDE, ATA 100
- CDROM: LG 32X EIDE, PIO 4
- ETH0: IBM Netfinity 10/100 Ethernet Adapter (for internal network, trusted interface)
- ETH1: IBM Netfinity 10/100 Ethernet Adapter (for Ericsson ADSL Modem, untrusted interface)

My software configuration is:

- Microsoft Windows 2000 SP3
- HotFix KB823980 (Blaster Worm patch)
- HotFix KB824146 (RPC vulnerability)
- WinZip 8.1 SR1
- Kaspersky AntiVirus Server version 4.5.0.58
- RealVNC 3.3.6
- LavaSoft AdAware 6

With WinGate 5.2.2 and 5.2.3 at boot time the ''Qbik WinGate Engine'' service failed to start and the WinGate Monitor on the system tray leave yellow state and after timeout an error message communicate the service start failure. In this moment only WinGate 5.0.0 build 510 work properly.
I don't have any ideas; any help is appreciated!!

JeanLuc

P.S.: Excuse me for my bad english!! ;-D

[adrien]

Have you tried deleting the history files? We have had reports that corrupt history files can sometimes stop WinGate starting.

To delete them, stop WinGate, delete History.* from the WinGate directory, then restart it.

Adrien

[neil]

Two things you should try. Firstly, you could disable your Kaspersky AntiVirus Server (temporarily) and reboot your server, and see if WinGate starts normally (we have had some probelms with anti virus systems in the past).

Additionally you can also enable some debug logging. To do this make sure your WinGate engine is stopped then in the registry go to

HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Settings

and create 2 DWORD values. The first should be named

UseDeadLockDetection

and the second

CheckLockPrecedence

set each of these DWORDs to a value of 1.

Now try to restart your engine. You should get 1 (or 2) files named something like LockAnalyserDumpFileEng.txt in your WinGate directory. These could have some useful insights into why your engine is hanging.

I would try diabling the AV first though.

Regards

Neil

[laterizi]

Thank you for support!! At the first useful moment i will try and i will make to know you...

Best Regards...

JeanLuc

P.S.: My english is terrific...

[laterizi]

Ok, in this moment WinGate 5.2.3 Trial Version work properly with external antivirus installed.
Kaspersky AntiVirus Server version 4.5.0.58 was in conflict with Kasperky AntiVirus PlugIn for WinGate.
The solution to the problem is:

- Set Qbik WinGate Engine service to start manually in the SERVICES.MSC (in Microsoft Windows 2000/XP/2003) console.
- Restart the PC
- Delete Antivirus for WinGate folder (in Plugins folder of the installation of WinGate)
- Start REGEDIT.EXE
- Search the key HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Data Scanning Plugins\Installed\
- Delete Antivirus key
- Close REGEDIT.EXE
- Set Qbik WinGate Engine service to start automatically in the SERVICES.MSC (in Microsoft Windows 2000/XP/2003) console.
- Start Qbik WinGate Engine service.
- All work perfectly and no error messages are given.

Thanks!!! Thanks 1000!!!

Best Regards

JeanLuc