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

Cannot make autodiscovery work internally - "401 The target principal name is incorrect"

$
0
0

Hi all

Im in process of migrating Exchange 2010 to 2013. I've alreay installed a two node multirole cluster of Exchange 2013. using the same cert i'm already using on the Exchange 2010.

My internal windows domain "internaldomain.lan" is different from the public domain "publicdomain.com".

In my exchange2010 environment the autodiscovery is working fine, and when i try to browse https://webmail.internaldomain.lan/autodiscover/autodiscover.xml, it works correctly (returns 600)

But when trying to browse Exchange 2013 autodiscovery through the same url (forcing dns resolution through hosts file), IIS returns 401 error. It never accepts the login credentials.

The Test-OutlookProviders command shows 401

ScenarioDescription : Autodiscover: Outlook Provider
Result              : Failure
Latency             : 61
Error               : System.Net.WebException: The remote server returned an error: (401) Unauthorized. ---> System.ComponentModel.Win32Exception: The target principal name is incorrect

"The target principal name is incorrect" seems to indicate there is a problem with the certificate.

My certificate has a "webmail.publicdomain.com" principal name, and lots of SAN: "autodiscover.<smtpdomains>" and one "webmail.internaldomain.lan"

Forcing hosts to resolve those names to CAS 2013 works for them except for the "webmail.internaldomain.lan"

Tried to force Outlook providers to "msstd:webmail.publicdomain.com" but with no result.

Any idea about what can be the problem or how can i solve this situation?

Thanks!


Viewing all articles
Browse latest Browse all 4521

Trending Articles



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