Yahoo Messenger

[rodcudal]

We use wingate as internet proxy server and users are authenticated through the AD. We also created a group "Internet Users" in the AD and allowed only members of this group to access the internet. Apart from that, we also configure the policy of the WWW Proxy Server to enable "Users must be authenticated".

RESULT: Internet surfing has no problem but Yahoo Messenger users have. Sometimes on sometimes off. Some totally have no connections. Before we implemented AD authentication, YM users have no problems.

Please help

[logan]

Yahoo Messenger doesn't handle NTLM authentication very well at all, so when you require NTLM authentication in WinGate, Yahoo messenger will often either not work, or will take a very long time to log in.

There are three ways you can get around this problem.

1. You can authenticate with WinGate using a different method before logging in to Yahoo.

e.g. browse to a webpage using internet explorer and then login to Yahoo Messenger. Yahoo should sign in successfully and will have no trouble maintaining your NTLM authentication session.

2. You can set your Internet Explorer to use HTTP 1.1 through proxy. This improves the way Yahoo handles authentication, but it isn't perfect. Yahoo will take a long time to log in and you may recieve about 6 authentication failures in WinGate before it works.

3. You could setup another WWW Proxy in WinGate especially for Yahoo Messenger that doesn't require authentication. Alternatively you could use the Socks Proxy in Wingate.


If you have set this policy that requires authentication in the System Policies, then the policy will also be applied to the ENS. NAT has no standardised method of requesting/recieving authentication from a client computer.

If your Yahoo Messenger is configured to use a NAT connection method, then you will either need to make an exception for the Yahoo Messenger ports, or authenticate using a different method first.