HELP Unable to Authenticate NEW users for Wingate 4.4.0 Pro!

[amurphy]

We're running Wingate 4 Professional version 4.4.0 for about a year now.
(We originally purchased through Deerfield and took 2 months figuring out crashed until we had to back rev to 4.4.0).

Anyway the version we've been running has been stable and running for almost a year.

System Info screen shows:
# of users : Unlimited
Expiry Date: does not expire
OS: Windows 2000 (Server)

Issue:
Any new user created cannot be authenticated.
Any existing user can be modified with rules currently in place (via groups).

I don't know if I can add sites/groups right now because I haven't tested.

Problem occurs on Wingate Java login.

If you type the username and no password or wrong password it comes back as login failed.

If you type username with the correct password it basically looks like it refreshes the login prompt with Guest and no password.

I've tried rebooting the server (It reboots every night as well) and still no effect.

I've tried deleting the user and recreating. No effect.

It doesn't matter if the user is restricted or unrestricted access using groups that already exist.

If on that same login prompt I use an existing user Wingate signs in that user.

[neil]

Very Strange! If you make a copy of gatekeeper.exe and run this from a remote machine (making sure you have changed the bindings for the RCP service to both 127.0.0.1 and 192.168.0.1 or whatever your internal IP is first). Then try to login in with a new user through Gatekeeper does this work!? You could also try logging in to Gatekeeper on the same mcahine as wingate runs, with a newly created user. Can't see why it would only be java auth that would be effected?! Also try deleting / purging the WinGate cache.

Regards

Neil

[amurphy]

I'm not running RCP in Wingate.
Services are:
DHCP (DISABLED)
Winsock Redirector
GDP
Remote Control Service
Caching
Scheduler
Dialer (Not used)
Extended Networking (Not Installed)

When I try logging into Gatekeeper as the user (Remotely or on the Wingate Server) if I used the wrong password it says wrong password. If I used the correct password it comes back with Connection with Gatekeeper disconnected.

How do I purge the cache?
I have it caching everything with the MAX set to 1MB which is the lowest setting I could set.

This affects any new user I create currently.

[labull]

We saw a problem with new users not being successfully authenticated when using assumed users.

Only thing we could figure was the the registry was corrupted so we deleted everyone and started over.

Very painful but it worked OK.

Larry

[amurphy]

Performed the Stop Wingate Engine and deleted the history.cdx and history.dbf and it didn't change anything.

Hopefully there is a way to do this without deleting everyone and starting over.

You wouldn't believe how many groups and rules there are!!!

I do have it backing up the registery every 3 days.

[amurphy]

All users must be authenticated (Except for accessing the company website that the user may be unknown)

[amurphy]

Any other ideas?

[neil]

Still stuck for ideas, it seems like WinGate isn't realising that user exists, or is enabled. If you open up the properties for one of these non-working users, and UNtick user is enabled, then click OK then Save, and then re-enable the user, and try again. Also if you stop the WinGate engine, open regedit and manually create a user in the registry, then restart the engine, can you then use this manually created user to login to GK and auth via java?!

Regards

Neil

[adrien]

When you log in with the java client, it then sends a command to the web browser to open the page that was originally requested.

This is where you see the refresh of the java login with Guest and no password.

What would appear to be happening, is that the login succeeds (!!!) and then the connection is terminated immediately. This correlates to what you see with GateKeeper. You should be able to validate this by looking in the Remote Control Service log file.

So, something about the new user you are creating is being declined by the policies, or similar. You should be able to see this in the remote control service log as well.

When you create this new user, is it a member of the groups you require for access? Is it possible you may have for instance banned access by anyone in the "Users" group in the system policies?

Adrien

[amurphy]

Ok... now I found the solution.....

For some reason it wasn't autochecking the Account Enabled check box.

I don't know how I missed it (after doing these for over a year) but I did.

Thanks for the help.