Gatekeeper problem

[trashben]

Hi all,

I'm using wingate 6.0.4 build 1025 running on windows xp. I've just reinstalled my wingate, and now it's working normally. Except that everytime I open gatekeeper after PC shutdown, I have a connection error to wingate.
Restarting wingate engine from the systray icon doesn't help either. But if I killed wingate.exe from the task manager and start the engine, I can connect to the gatekeeper seamlessly.

Now, everytime initially I run gatekeeper from remote pc I always have a connection error. I'd have to vnc to the server, kill the wingate.exe, start the engine, and then I could successfully connect from remote pc. It's happening only during the first time connection.

Anybody could help ?

[MattP]

That sounds like a pretty strange problem. What happens if you try to log in from the remote machine using GateKeeper? Are you able to log in then? (To do this, just copy the GateKeeper.exe file from the server to the remote machine and double click it to run it. You'll have to change the login options from login to localmachine and enter the server's IP address).

If logging in remotely works, it could be that you have some software running on the server that is blocking the connection, are you running ZoneAlarm or something similar?

[trashben]

It's the same thing. This is what I did to test this :
- restart the wingate server.
- start gatekeeper at the remote pc.
- connection failed.
- vnc to the server, kill wingate.exe, start the engine
- start gatekeeper at remote pc, connected successfully

I'm not using any firewall on the server machine. Any hints ?

[jamesc]

Hmm, that’s a hard one for to troubleshoot. But here are some suggestions; please let us know how you get on.

1. Had you ever upgraded WinGate?
2. (long shot) Is the Windows Firewall enabled?
Right click My Computer --> Manage --> Services and Applications --> Services --> Windows Firewall/Internet Connection Sharing (ICS)
3. Why did you have to reinstall WinGate, what issues were you having?
4. What is the exact connection error?
5. Does your WinGate system log give any hints to the error? C:\Program Files\WinGate\Logs\System\System.log
6. Does the Windows event viewer indicate any problems? (Windows) Start menu --> run --> eventvwr
7. Is the WinGate.exe listening on port 808 when you cannot connect?
(Windows) Start menu --> cmd --> netstat -b -v

[trashben]

I've tried ur steps .. it seems that the last one is true. netstat doesnt show that the server is listening on port 808.
Killing wingate.exe and restarting the engine makes it listens on port 808.

How do I fix this ?

PS. Yes this problem occured after I upgraded wingate.

[jamesc]

Can you remember what your previous version of WinGate was?

[trashben]

must be the version before 6.0.4 build 1025 ( this is the current version I'm using ).
I've upgraded several times before and never have this problem.