Version 6.0.4 & Assumed Authentication

[dlcole]

I've been using the following for assumed authentication since version 4.x and just upgraded from 5.x to 6.0.4 and it no longer works.

I have system policies set to "Users may be assumed"

I'm using the WinGate User Database with all users having the same username as their Windows Domain Username, passwords however are different. Only users authorized for Internet access have a Wingate Username.

Prior to installing the upgrade all users in the Wingate database could access the Internet without entering a password. Since upgrading they are all being prompted for a password.

Anyway, to get back to my prior operation?

Thanks,

[dlcole]

Anybody from Qbik (or anyone else) have any idea what is causing this problem? I returned to version 5.2.3 and this is working ok, but I'm in the process of upgrading my Wingate server to a machine running Windows XP and version 5.2.3 will not install under XP SP2.

Thanks,

I've been using the following for assumed authentication since version 4.x and just upgraded from 5.x to 6.0.4 and it no longer works.

I have system policies set to "Users may be assumed"

I'm using the WinGate User Database with all users having the same username as their Windows Domain Username, passwords however are different. Only users authorized for Internet access have a Wingate Username.

Prior to installing the upgrade all users in the Wingate database could access the Internet without entering a password. Since upgrading they are all being prompted for a password.

Anyway, to get back to my prior operation?

Thanks,

[MattP]

Hi David,

Version 5.2.3 should install fine with XP SP2, are you getting a message about the Personal firewall being active? You may need to go to Control Panel>administrative tools>services and disable the Windows Firewall service to actually stop it. You should then be able to install fine.

However, it would be better if you use version 6, we should be able to get your authentication working. What are you using to authenticate your users? ie, java authentication or basic authentication.

You could use the Operating System user database and then you'd be able to use NTLM authentication. This way the users' NT authentication would be passed through to the WinGate server to see if they are allowed access to the services.

Regards,

Matt

[dlcole]

No the problem with 5.2.3 is that I get a BSOD with the error DRIVER_IRQL_NOT_LESS_OR_EQUAL on the qbikhkxp.sys driver during boot up.

Authentication is basic, and I has the profile set to users may be assumed. I use the WinGate Userbase.

I thought of one thing that may be causing a problem, the Wingate passwords and the Windows passwords are not the same, when using assumed users in the past this didn't matter, but it may now.

Thanks,

[Pascal]

Having assumptions should not require authentication. Is it possible for you to send me a copy of your WinGate registry, please? You can export thqt from Gatekeeper->Options->Advanced.

[dlcole]

Emailing it to you now.

Having assumptions should not require authentication. Is it possible for you to send me a copy of your WinGate registry, please? You can export thqt from Gatekeeper->Options->Advanced.

[Pascal]

About the only thing that looks strange about that is the multitude of subnets, but that by itself should not cause a problem. Policies also look good, so I do't think the problem is there. I'll need to check this in the lab on Monday (At home now) so I'll be able to give you a more definitive answer then.

[Pascal]

Ok, Erwin [qa] tried this in two ways. First was on a clean, fresh install of XP. Add SP1, 5.2.3 and set everything up. Then he upgraded to 6.0.4. It all worked as expected. Users from different subnets were assumed correctly, granted access as required.

The second way was the same, but with your registry in place. This one was a bit more difficult as the initial binding policies did not listen on any adapters. I suspect this might be part of the problem - you might want to double check the bindings for the services when you install 6.0.4 again. After we'd added that, however, everything seemed to work fine.

We did have to specify multiple IPs for the internal adapter to have clients connecting in from multiple subnets - do you have yours configured in a different way? (Multiple adapters?)

Now the question would be - how do your client machines connect through WinGate and how do you have the server setup? (For the different subnets)

[dlcole]

Sorry Pascal,

I missed your Reply, I will try this over the weekend and let you know the results.

Thanks,

Ok, Erwin [qa] tried this in two ways. First was on a clean, fresh install of XP. Add SP1, 5.2.3 and set everything up. Then he upgraded to 6.0.4. It all worked as expected. Users from different subnets were assumed correctly, granted access as required.

The second way was the same, but with your registry in place. This one was a bit more difficult as the initial binding policies did not listen on any adapters. I suspect this might be part of the problem - you might want to double check the bindings for the services when you install 6.0.4 again. After we'd added that, however, everything seemed to work fine.

We did have to specify multiple IPs for the internal adapter to have clients connecting in from multiple subnets - do you have yours configured in a different way? (Multiple adapters?)

Now the question would be - how do your client machines connect through WinGate and how do you have the server setup? (For the different subnets)