WGIC keeps asking for password

[bench]

I asked this question in my previous post but it was closed before answered.

All client PC's are now being authenticated, I can see them as such in the activity window of gatekeeper.

The only problem some clients are complaining about is that after they log on to the domain the WGIC window pops up and asks them for their username and password. The username is deault to System but even after they input their info it pops up again until they have to click cancel 2-3 times so it can go away. They can surf the internet without a problem.

Gatekeeper is using the NT database for authentication so why is the window popping up and why does it keep asking them for their username and password after they enter it once?

Thanks

[jamesc]

1. I just researched our support system for this problem. I found a reply from Mattp; have you got similar symptoms?.

It sounds like there is a problem there, you shouldn't have to authenticate more than once per session. Can you watch the activity pane in GateKeeper when a user is accessing a web page, you should see the session become authenticated once they enter their login credentials. When they stop browsing the session will time out and you'll see the user drop back to an assumed state. After another 30 seconds you'll see the session disappear. Is this the behaviour that you're seeing?

2. What is the timeout value for the Winsock Redirector Service --> Sessions?

3. Can we have a look at your settings?
(Windows) Start menu --> Programs -> WinGate --> Registry --> Export Settings
Send it to sales@wingate.com and reference this forum post.

[adrien]

Hi

If you see the username SYSTEM showing up there, it's an indication of what the client thinks the username of the user context the application is running in. SYSTEM is used for system services. This means that a system service is running which hasn't been configured not to use the WinGate client.

If you look in GateKeeper when this happens, you will be able to see what the name of the application is that is running. then if you go into the WinGate client configuration on the client machine, you can add that application in the application tab, and set its access to local. That should stop the popup.

Adrien

[bench]

I think that's what is happening, there is an application trying to access the file server but it's trying to go through wingate to do it. I see that outlook is even listed in gatekeeper which should not be because the mail server resides on another server.

I'll try adding this applications to local as adrien suggested.

[bench]

OK, here's what gatekeeper reads in the activity tab.

W2KACT01[System] - (JohnH - Authenticated[NTLM])
WRP control session - Outlook.exe
WRP control session - spoolsv.exe

The thing is that in WGIC in the user applications I added outlook to have local network access only so it won't use the proxy gateway to access it but it still shows up.

How can I prevent that from happening?

[adrien]

hi

Because of the way Central configuration works, the WinGate Client must still connect to the server to get configuration.

The WinGate Client is still loaded by all applications that use TCP/IP, but may not redirect connections in or out if the settings for the application are set to "local", either on the client or the server.

This doesn't consume any license count, so apart from being able to see what applications people are running (and actually control it, since you can set an application to be terminated on the server), the WinGate client shouldn't actually be affecting the operation of the application.

Are you seeing some operating problems with these applications?

Also, do you have timeouts set up on the WinSock Redirection Service?

Adrien

[bench]

yes, I have the time out to 1000 seconds. I think this is how much time the application has being idle before wingate closes the connection and then WGIC has to reinitiate the connection again if the application becomes active again. Is this correct?

Should I disable the time out session option?

[adrien]

Hi

Yep, if the client application doesn't need the server for anything for a period of time, then the control channel can be closed. If it is needed again, it is just reopened by the client.

in early versions of WinGate it was common to time out the control channel quickly, like about 20s, because then a connection wasn't held open to the server consuming a WinGate license count.

With WinGate 6.0 though, the control connections no longer consume a license count, so you can take your pick whether you time them out or not - was just thinking if you didn't want to see them in GateKeeper, you could get them to time out.

Regards

Adrien