Quantcast
Channel: Exchange Server 2013 - General Discussion forum
Viewing all articles
Browse latest Browse all 13303

Exchange 2010 Coexisting with Exch 2013 – strange behaviour for internal and external outlook clients.

$
0
0

I installed exchange 2013 with an existing exchange 2010 on domain.local, planning on migrating to 2013 and eventually eliminate exchange 2010.
I notice when I configure an outlook client on a pc on domain.local, for a user that has a mailbox on the exchange 2013, the proxy setting for exchange are automatically set (like outlook anywhere). That was new for me, usual with ex 2010, you don’t need “proxy settings” for a domain.local outlook client, only for external once. I presumed it was an exchange 2013 thing.
But now a few months later a want to set outlook anywhere on the ex 2013 as well.
And now I have problems with the authentication method.

Ex2010\rpc (default web site)
ExternalClientAuthenticationMethod
Basic
InternalClientAuthenticationMethod
Ntlm
IISAuthenticationMethods
Basic

Ex2013\rpc (default web site)
ExternalClientAuthenticationMethod
Negotiate
InternalClientAuthenticationMethod
Ntlm
IISAuthenticationMethods
Basic, Ntlm , Negotiate

When I try to connect to a mailbox on ex2013 with outlook anywhere on no-domain computer, the autodiscover configure the proxy settings with Ntlm. The autoconfiguring makes no sense it should be Negotiate. I know in this link, https://support.microsoft.com/en-us/kb/2754898 Microsoft explains that it’s “normal” to see the internal hostname when you using outlook anywhere on an outlook client that is not a your domain. But why it’s also taken the authentication method of the internal one?!?


Viewing all articles
Browse latest Browse all 13303

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>