WWW in transparent mode again...

[inigoayo]

I'm so sorry but it's imposible. I've tried a lot of configurations but it does not work. It could not be so difficult to configure!
I can not get access to internet with authentication in a transparent way!

The WWW proxy has enabled transparent mode, intercepts port 80. The policies require authenticated user, the ENS drivers is active and working but when you run the navigator in the client computer, you get access to Internet without problem via NAT and the WWW Proxy service does not report any activity!

What I do wrong?

We're evaluating this software to purchase it but under this conditions I can not bet for it.

[erwin]

Hi there

Main things to check

Clients configured correctly to use NAT (GAteway/DNS pointed at the internal IP of WinGate server.

What userdatabase are you using to authenticate against
Operating System/Windows or the WinGate Userdatabase?

What authentication method are you using Java?, NTLM?
Is one of these ticked on the General config screen of the WWW proxy?

One more thing to check on the Policy config in the WWW proxy what is the Default rights (System policies) setting set to (Should be IGNORED so they arent overidden by a system policy which could cancel it out)

Let us know how you get on

Regards
Erwin

[inigoayo]

Gateway/DNS both point to the Wingate Server machine IP.

The user database I want to use is the Wingate database under Java authentication (ticked in config). I don't want NTLM authentication. In fact, the authentication works if I connect to Internet via proxy settings in the Navigator.

The WWW Service policies are "Everyone is restricted by security level" and the default rights (system policies) are ignored.

Another tip?

[Pascal]

That sounds as if you are not even getting NAT traffic through then, never mind intercepts. Are your adapters setup properly for Internal vs External? It sounds as if they are, because you can actually connect to a port the WWW Proxy has bound to, but doesn't hurt to double check that.

Double check in the client that it does not have any proxy settings, nor anything that will request automatic configuration. It should rely on the fact that it has a default gateway to get out to the internet for intercepts to work properly.