Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

Gatekeeper not showing URLs

Aug 21 06 4:36 am

Hi all,

I've had to recently re-install Windows on my Wingate server and AFAIK the setup is exactly the same as before, but now gatekeeper doesn't show the URLs that the clients access, just the IPs:port
They are all working fine, so DNS is running o.k.

What can I check to fix this? Most clients run through proxy, although some use ENS/NAT

Thanks

Aug 21 06 3:06 pm

Hi there

You'll see the "IP address:Port" format when clients are strictly using NAT.
(i.e NAT is not being redirected through the proxy (transparent proxy under the sessions config in the appropriate proxy service.)

Turning on transparent proxy this way will display full url details.

Or alternatively having clients specify a proxy in their browsers will also display full details. (Since the WWW proxy service in wingate is handling the request). So you should this type of client activity.

Regards
Erwin

Aug 21 06 8:46 pm

Thanks for the reply.

Some websites (like banking sites) doesn't like the proxy to much (it seems). When proxy is enabled, it sometimes log them off and they must re-logon, or just gives 'page cannot be displayed'. Could it be that, or am I making the wrong assumpion?

Also, things like Windows Auto-update shows the URL, but 'normal' websites doesn't, from the same client.

Ekkas

Aug 22 06 12:34 pm

Hi Ekkas

Haven't heard of any reported issues with users who make with bank connections being logged out of the bank while going through the proxy.

HTTPS(SSL type connections) are handled automatically by the proxy, and of course you can set specifc ports to be used for ssl connections under the HTTPS config of the WWW proxy.

How long are the clients logged into the bank, as secure sites usually have quite strict time outs.

Also seems strange that activty shows for Windows update and not for normal sites.

Have you tried clearing the cache both in WinGate and on client's browsers, so you know that when they access a site WinGate needs to grab a fresh version of all the page info, and can see it in the activity screen in GateKeeper, (which I take you have set to "View by machine")

Regards
Erwin
Post a reply