Problems logging on (not p/w related)

[xtreme69]

V5.1

I've been running Wingate for over two years now, and recently I've happened upon a problem I've never seen before (nor can I find any real explanation for). I'd like to say to start though that during that two year period I have had maybe two complaints about my Wingate server, and considering the relative complexity and size of the application, that is a pretty big compliment.

I hope the solution to this problem is something stupid that I missed, as these things often are...anyway, here goes:

When attempting to log onto my Wingate server, and using the correct password, I receive the message "Connection with Wingate server terminated". With an incorrect password, the server responds properly with the generic "Bad pass/user" message. I have nothing running on this server besides DNS, Logfile server, ENS, and a single TCP mapping service. DHCP is disabled, the other default services (the ones listed with DHCP) are all enabled. I run no proxy services of any kind, besides the forementioned TCP map. Also, all services are restricted to an assumed user, assumed by "192.168.1.*" (LAN users). TCP maps are restricted by the location the incoming requests are generated from, and also routed based on that information.

I don't know that any of that information was necessary to help me resolve this issue, I get the sense that this type of problem is related more too possible corruption of some kind. I have tried re-installing Wingate, and I can log in fine the initial time. But, once I change my Administrator pass, set up the initial configuration, and exit, I run into the same problem all over again. It's quite frustrating only because I have to alter TCP map security and location restrictions occasionally, and as it stands now everytime I need to do that I am stuck performing a re-install. Not too cool. Anyway, any help I can get on this subject would be greatly appreciated. Thanks all.

[tim]

V5.1

I've been running Wingate for over two years now, and recently I've happened upon a problem I've never seen before (nor can I find any real explanation for). I'd like to say to start though that during that two year period I have had maybe two complaints about my Wingate server, and considering the relative complexity and size of the application, that is a pretty big compliment.

Hi, it sounds very much like you are using a different version of GateKeeper to connect to the engine. Unfortunatly we forgot to change the internal protocol number to prevent this happening when we released 5.1.

As it's happened since you installed 5.1, it is likely that this is the issue.

Are you connecting from a remote machine>? Make sure you update GateKeeper from the Wingate machine, and try again.

Tim

[xtreme69]

Actually, I upgraded to 5.1 in the hopes it would resolves my problem. I have tried installing 5.1 again, both by uninstalling first and then re-installing, and by upating the setup...and neither one resolves the issue.

It's very strange really. Is there a way to insure I do a complete uninstall so I can be sure that no registry values or other config files are left behind? Anyway I can check for the GateKeeper issue you mentioned without having to actually log into GK (which I can't do anyway :) )? Thanks for the help thus far.

[xtreme69]

Oh, and below is what the syslog shows whenI try too login:

This is what is logs when I use my correct password:

11/20/03 11:25:11 Authentication Authentication failed - user Administrator on 127.0.0.1 requested WinGate Remote Control Login

And this is what it logs when I use a bad password:

11/20/03 11:25:43 0C5vFNAvtxoAAAAAAQAAAAEAA0fqEeMAArml2/cIAEUAAFy7XQAAdAHEttAubxTQL7caAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAVLCqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=

Don't know if this will help, but I'm grasping at straws now...trying to give any info I can :)

[xtreme69]

Hah! After checking the syslog messages I realized that it was my own stupidity that caused the problem. When I reconfigured the WinGate quickly after a re-install, I locked things down a bit too much and excluded 127.0.0.1 from the accepted login addresses.

The only allowed addresses were in the 192.168.1.* range...guess I was just moving a bit too quickly the last time I configured ;). Anyway, I've fixed the settings now and everything is running smoothly again, sorry for taking up your time with something like this. Thanks for the help.

[ChrisH]

I hate when that happens to me. Glad I'm not the only one!