Wingate 5.2.3 NAT & xDSL Connection.

[lucasdavid]

Hi!

I´m a xDSL Connection 24Hs. and WIngate 5.2.3 with NAT, The clients are configures only with the GATEWAY AND STATIC IP INFORMATION.

Sometimes the wingate stop responding everything (inclusive Gatekeeper not connect) I must stop engine, restore registry settings from a backup and start engine again to start to work... What´s the problem here!!!

I´m Using:
**NAT
**Static IP
**Windows 2000 DNS Server
**xDSL Connection (Dial-Up with RAS PPPoE)
**Wingate User Database

PD: The connection is established OK between server and internet the problem is Wingate and the LAN.

Please Help me.

Thanx.

[Pascal]

Hi,

Will the WinGate Engine stop at that time? My first thought reading your post seems to indicate a deadlock somewhere in the WinGate Engine, but as far as I know all deadlocks were resolved by 5.2.3's release.

Have you considered upgrading to 6.0.3? There has been a number of improvements in 6.0.3 that will affect

**NAT
**xDSL Connection (Dial-Up with RAS PPPoE)

You can use your existing 5.2.3 license key with 6.0.3. If you don't wish to upgrade, a few questions:

1. Can you resolve DNS when WinGate is in this state?
2. Can you ping through WinGate?
3. Are you able to open a proxy connection by just temporarily setting your browser to use proxy?

[lucasdavid]

Resolve DNS OK only in LAN because the connection with internet (managed by wingate) is death.

I Can´t Connect with Gatekeeper too.

The engine is Running but dead!

[Pascal]

That definately sounds more and more like a deadlock. To confirm / deny that:

A deadlock of the WinGate Service occurs when it stops serving clients, you are unable to log in with GateKeeper and unable to shut the engine down. You can enable the following registry keys for additional debugging information:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Settings

Values: UseDeadlockDetection
CheckLockPrecendence

Both of these are REG_DWORD types and should have the value of 1. Note though, all applicable warnings apply when editing the registry. Make sure you have an appropriate backup, etc.

The debug output are in two files called LockAnalyserDumpFileEng.txt and LockAnalyserDumpFileGK.txt. . Please send this file to Qbik / the email address in my profile for analysis. That should help us track it down for you. (If it is a deadlock)

Although I would strongly urge you to upgrade to 6.0.3.