Always have problem with Messenger

Apr 19 05 5:36 pm

Hello Qbik Engineer,

I really need your expertise and help to solve this once for all.
The Yahoo and MSN messenger always can't connect to internet through Wingate proxy.

The users database and authentication are integrated with Windows 2003 AD database.

I observed that the connection failed due to authentication which the messenger always login using GUEST (authentication failed). It should logon as DOMAIN/USER.
All workstations are joined to domain.

Appreciate your prompt respond and reply on this. Need any more details, please email me at dax.yap@gmail.com

Thank you very much.

Apr 20 05 12:55 pm

It should, but that depends on how the application attempts to authenticate. I think you will find that if you say, run GateKeeper and login from the remote machine (Or authenticate in some other way) BEFORE running the messengers that they will actually work 100%.

Apr 20 05 1:23 pm

Pascal wrote:It should, but that depends on how the application attempts to authenticate. I think you will find that if you say, run GateKeeper and login from the remote machine (Or authenticate in some other way) BEFORE running the messengers that they will actually work 100%.

Well Pascal,

I tried. Each time I logged on to the network/domain before I sign in to Messenger but failed. Not even that, I'm logged on as domain ABC\Dax,
when I check the gatekeeper activitied tab, it showing me I'm a assumed user but in the user policies I set "Must Authenticate User" Please advise. Thanks

Apr 20 05 1:46 pm

Yes, that means you are authenticated with the domain. It does not mean you are authenticated with WinGate. WinGate needs to see a connection from your machine coming to it which is authenticated. Simply running a messenger will not do that (I do not believe that the messengers will negotiate NTLM successfully, even though WinGate will be sending the correct responses back).

So, you need to ensure that you get authenticated with WinGate somehow.

Apr 20 05 4:46 pm

Pascal wrote:Yes, that means you are authenticated with the domain. It does not mean you are authenticated with WinGate. WinGate needs to see a connection from your machine coming to it which is authenticated. Simply running a messenger will not do that (I do not believe that the messengers will negotiate NTLM successfully, even though WinGate will be sending the correct responses back).

So, you need to ensure that you get authenticated with WinGate somehow.

Authenticated with Wingate somehow?? You mean I have to find my own solutions??? I can't see why it's happened strangely.

Apr 20 05 4:53 pm

daxyaphw wrote:Authenticated with Wingate somehow?? You mean I have to find my own solutions??? I can't see why it's happened strangely.

By no means am I suggesting you should find your own solution. I am trying to get the message across that there is a difference between authenticating with your AD controller and being authenticated with WinGate. Logging in to Windows (And thus to AD) does not automatically authenticate you with WinGate. Your browser will, if you are using NTLM, transparently auth you in most cases.

That said, there are several methods to authenticate with WinGate. They are:

1. Through an authenticated session such as HTTP. This requires the client side application to support NTLM negotiation, which I suspect those messengers do not.
2. Through the WinGate Internet Client.
3. Through Remote GateKeeper login.

There might be more, but those are the ones that come to mind from the top of my head.