"Authenticate failed" problem

[newwingater]

I have set up a wingate server on my machine.
I start www proxy with Java Authenticate and in policies, I allow an user can visits this service,he must authenticate with his username/password. When i open an IE and visit an URL, the Java Authentication window display and then i logon and surf the Internate.It's all ok.
But when i use MSN(the user not logon to wingate before),I set this httpproxy and input username,password,domain and test connection.It's can't connect to MSN .
I can comfirm it's not MSN's Problem beacause when i use the user logon to wingate first by IE,it's can connect to MSN without any problem.And I tried some other applictations that use proxy ,all of them can't work .

At last I find when i use MSN or other applications to connect internate,they all authenticate with Guest the build in account,not the user i set,so they rejected by wingate. I find this by see wingate's system messages.

So, how to resolve this problem?

[Pascal]

If you connect with MSN through a HTTP proxy it will also need to authenticate. It cannot serve the Java Client back to MSN (Or WinGate can - but MSN does not understand the response!)

If you login with IE first, your machine is already authenticated and then when MSN connects it does not need to authenticate.

So:

1. Use something other than Java authentication OR
2. Setup MSN to not use the HTTP Proxy. (NAT? Or WGIC if you need that level of authentication) OR
3. Setup more advanced policies to allow MSN through, but to require authentication for all others.

[newwingater]

Hi,Pascal!
I'm not use Java Authenticate now, but the problem isn't resolved. My request is rejected by wingate,because my request is send with Guest account not the account i set in MSN or other Applications.

[Pascal]

Hi,

Yes, that would be the case if you require authentication. You still need to authenticate / identify the connection as coming from a user then - but there are several ways around that.

First, you could use user assumptions. (Basic authentication is also 'assumed')

Second, you could move to using the OS Userdatabase (If your OS + license allows it). That should allow you to use NTLM authentication which is fairly transparent.

Third, you could use the WinGate Internet Client.

Fourth, authenticate with a remote Gatekeeper login.