windows 2003 terminal services / gatekeeper icon

[snuffy]

Hello

I have noticed that when terminal servicing in to our wingate server, it appears that the wingate engine is stopped (red square etc)

When logging on actually at the machine, it shows the blue square.

Is this fixed in version 6?

Thanks

[adrien]

Hi

We'll have to check this. I imagine it is to do with shared user access to mutexes (OS objects used to determine if WinGate is running).

Adrien

[Pascal]

What version of WinGate are you using ? We've just tried it on version 6.0.1 and behavior is correct for the Engine Monitor. (I.e. you can stop/start the engine, see its correct status, etc.) The one exception is the VPN Monitor, which will not allow a Terminal Server user to connect / disconnect a VPN - this should be fixed in our next release.

This was with the Terminal Server running on Windows 2000 AS with an XP client connecting in. What OSs were you using in your setup? (Never mind, saw the OS was 2003 from the subject)

Edited: More on this - it is a problem when running in a Windows 2003 Terminal Server environment. The default behavior for synchronisation objects have changed slightly. This should be resolved in our next release.

[Alexmillo]

I had the same problem. But I discovered that if you start the terminal server application using the /console suffix fixes the issue.