WGIC not working with Win Xp SP2

[Jens]

After upgrading Windows with SP2 on the client PC the log-on screen ceased to work so it was no longer possible to authenticate the user as required by the set policies. This in turn blocked all internet access from the client PC. The client PCs use WGIC and WinGate use its own user database. The WGIC was version 6.0 release 984 although when installing as client it claims to be a beta release only.
De-installing Win Xp SP2 restored the functionality of WGIC.

[Pascal]

I suspect this is not an XP SP2 issue. Just tested it, and with both NT and WinGate userdatabase, it works fine.

However, if you are not using an Enterprise license key with 6.0 build 984, you will have problems when using WGIC. We should be releasing an updated build tonight that will resolve this problem.

[Jens]

I am running WinGate Pro so that matches. Will try the update as soon as it is released.

[Pascal]

What you can do in the meantime is to request a trial license - if you have that it will temporarily elevate you to Enterprise - which should get you running with XP SP2 then until we release this.

[adrien]

PS, the update is now available.

Adrien

[Jens]

Thanks, I have just downloaded the new update and shall come back with the result.

[Jens]

Nah, no difference. I reinstalled XpSp2 and installed 6.0.1.995 both on server and client. After rebboting both PCs the client PC Windows indicates that the client application was in error. This only happened once (the same happened with 6.0.0.984). No login window appears on the clent PC and thus no connection to Internet since all users are required to be authenticated.

[Pascal]

One thought here - are you running an AMD64 ? If yes, it might be because of DEP.

(http://support.microsoft.com/default.as ... -us;875352)

[Jens]

No, I am running AMD Athlon on both server and client PCs.

[Pascal]

s the client PC Windows indicates that the client application was in error

Any chance you could get the exact text of that error message ? Or perhaps email me a screenshot, please ?

[kgoodknecht]

Did you add WGIC to the allowed applications list in the new Firewall in SP2?

[Jens]

The xp firewall is off so that should not be the cause. I uninstalled and reinstalled WGIC to try to reproduce the error message (left XpSp2 intact though). This did not produce the error message. However, the behaviour seems to have changed.
WGIC still does not ask for any user login when the PC is booted and I dont see the machine being listed in the history log as being switced on although it appears in the network window and can be browsed from the server. Default IP address is used for the server and DHCP for the client.
However, the login window pops up if the user try to access Internet and the user will then be logged in for the time being defined in the respective session timeout. Although this can be used as a workaround, it would be preferable to get back the login window when the machine is booted.

Jens

[kgoodknecht]

The xp firewall is off so that should not be the cause. I uninstalled and reinstalled WGIC to try to reproduce the error message (left XpSp2 intact though). This did not produce the error message. However, the behaviour seems to have changed.
WGIC still does not ask for any user login when the PC is booted and I dont see the machine being listed in the history log as being switced on although it appears in the network window and can be browsed from the server. Default IP address is used for the server and DHCP for the client.
However, the login window pops up if the user try to access Internet and the user will then be logged in for the time being defined in the respective session timeout. Although this can be used as a workaround, it would be preferable to get back the login window when the machine is booted.

Jens

I assume then that you did turn the Windows firewall off in the Security Control Panel?
Because under SP2 the Default is for the Windows Firewall to be on. There is an exception list and I'll be doing my testing with the firewall on. Right now, I don't have WGIC installed on it but I'll install it today to see if there is a problem. What version of Wingate are you using I'll be using build 995 which AFAIK is the latest build.
For my information though, is the XP client a domain member?

[Pascal]

WGIC will only ask for a login if an application tries to reach the Internet. It's not a general authentication tool. So, if XP has changed in such a way that it will not require an internet connection on startup / bootup / login - then you won't get the WGIC login popping up.

[Jens]

I did switch the firewall off in the security control panel. Also checked the setting several times. I am testing with build 995.
The client is not member of a domain.

If WinGate only asks for login when an application requires internet access, then it seems that the behaviour I experience is what I should expect. The login is different though, because the user was asked to log in emmediately after bootup before I installed SP2 and the login never timed out even if no relevant applications were running on the client.

I do however observe some strange behaviour, I open a browser on the client (with no WGIC user currently logged in) and the WGIC may or may not ask for authentication when I try to access different internet sites. If there is no request for login, the browser will eventually time out with the message "could not locate the remote server".
After having logged in, all the sites are reachable.
I am still somewhat puzzled.