Michael Lahrkamp
December 11th 03, 01:39 PM
Thanks for the idea... no joy though. Any other ideas?
Mike
>-----Original Message-----
>Try and exclude the local domain name IE: *.domain.local
>in your Internet Explorer proxy exceptions list.
>
>Dylan Nelsson
>
>>-----Original Message-----
>>We have a corporate lan with Win2K servers and pro
>>clients and IM installed on Exchabge 2K. Everything
works
>>well. We set up a single computer to evaluate WinXP,
>>loaded up the required IM version and get the following
>>error when attempting to connect to the Exchange 2K IM
>>server: "SOCKS 5 proxy authentication failed. Check the
>>SOCKS 5 setting for User name and Password on the
>>Connection tab." We've tried every possible combination
>>for our network with no success. I'm suspecting that
>>Exchange needs to know that there's an XP client which
is
>>probably trying to connect in a new way. Outlook had a
>>similar problem that was corrected with some registry
>>settings.
>>
>>I should also point out that this XP client
successfully
>>connects to a .NET Passport Account - just the inhouse
>>Exchange IM has the problem.
>>
>>Looking for any suggestions.
>>
>>Thanks.
>>Mike
>>.
>>
>.
>
Mike
>-----Original Message-----
>Try and exclude the local domain name IE: *.domain.local
>in your Internet Explorer proxy exceptions list.
>
>Dylan Nelsson
>
>>-----Original Message-----
>>We have a corporate lan with Win2K servers and pro
>>clients and IM installed on Exchabge 2K. Everything
works
>>well. We set up a single computer to evaluate WinXP,
>>loaded up the required IM version and get the following
>>error when attempting to connect to the Exchange 2K IM
>>server: "SOCKS 5 proxy authentication failed. Check the
>>SOCKS 5 setting for User name and Password on the
>>Connection tab." We've tried every possible combination
>>for our network with no success. I'm suspecting that
>>Exchange needs to know that there's an XP client which
is
>>probably trying to connect in a new way. Outlook had a
>>similar problem that was corrected with some registry
>>settings.
>>
>>I should also point out that this XP client
successfully
>>connects to a .NET Passport Account - just the inhouse
>>Exchange IM has the problem.
>>
>>Looking for any suggestions.
>>
>>Thanks.
>>Mike
>>.
>>
>.
>