WinGate Client blocks Terminal Server Connection

[Steven]

Hello,

I'm using WinGate V5.2 an a Windows 2003 Server (German). If I install the WinGate Client on my Workstation, I'm not able to connect my PC to a Windows Server at our network. I get an error message, that a connection is not able at this moment. If I deinstall the WinGate Client again, a Terminal Server Connection is possible. How can I solve this problem?

Thank you for your help.
Steven

[neil]

It is possible that some file is being intercepted by the WGIC when you try and make this connection. If you look in Gatekeepers activity when you are trying to make this connection and see if your machine shows up there, it should say what file is being intercepted. If you then add this file to the WGIC applet, under the 'Applications' tab and set it for local access you should no longer find you have a prob. For example, for XP, its a good idea to add winlogon.exe and userinit.exe to teh WGIC and set those for local access only. This means the WGIC wont try and intercept them.

Regards

Neil

[francescmas]

Hi :

I've add a lot of software to the list of "applications to be treated specially, just for local access" in Wingate Internet Client Applet (WGIC), but since 6.0 version it doesn't really work...

I mean... I was a happy user till then, but when WGIC 6.0 appeared with separated list for User Applications and System Applications, the problems began.

Since then I have tried everything but some 'set for local access list' software awake WGIC when they musn't.

I have added, for example, a software like GoogleDesktopIndex.exe to the list, but anyway EVERYTIME I start Windows I have to see the WGIC password window. If I reinstall the old 5.0 version of WGIC with just one list, it seems to work better.

I just want the WGIC password window to appear when some not-listed software is trying access to internet. You have it perfectly working with 4.0 and 5.0 WG version for years, why not since 6.0 ?

Please, help me.

Best regards,

Francesc Mas