Exchange 2013 in a disjointed domain

Hi All,

I have a client with  new installation of exchange 2013. Mail flow is working but there are some issues with outlook connecting, current users have a password prompt that wont accept their credentials and autodiscover for new users resolves their names but then also promts for passwords and never accepts them.

What I know and have read about this seems to stem from the fact that the client has a disjoined domain. here is what they have, they are Johannesburg (JHB)

domain name = domain.local
DNS = domain.local and
NetBIOS = domainJHB

Their external mail address is

I have set the outlook anywhere to user NTLM, outlook has been updated to the supported service packs for exchange 2013 ie outlook 2010 with SP2.

I have tried some things in dns, such as remove the autodiscover.domain.local and created a SRV record to point to Thus far the only way I have managed to get outlook online is to do a manual setup and make sure outlook anywhere is set up.

any advise would be appreciated.
Who is Participating?
ThiaanConnect With a Mentor Author Commented:
Thanks for all your help Simon.

I managed to figure it out, it was indeed the certificate causing the issue but not because the certificate was wrong. I eventually discovered that the outlookproviders where set to look at Hence why I got the error mentioned above, as the cert name is servername.domain.local. If you run get-outlookprovider in the exchange powershell on a working exchange you get something like this

Name                          Server                        CertPrincipalName             TTL
----                          ------                        -----------------             ---
exch                                                                                      1
expr                                                                                      1
web                                                                                       1

however on my problematic exchange the certPrincipalNames were all set to

to reset them you need to enter set-oulookprovider EXCH -CertPrincipalName $Null.

thanks for your time though. its greatly appreciated.
Simon Butler (Sembee)ConsultantCommented:
Having a domain in the way that you have described is not a problem, as long as you have a split dns system and configure Exchange correctly to use the external name internally.
That is easily done, my Exchange 2010 instructions apply to Exchange 2013 as well.

Autodiscover DNS records are not used internally, unless the clients are not members of the domain. The clients query the domain for the value that you can see here:

get-clientaccessserver | select indentity, autodiscoverserviceinternaluri

The host name needs to resolve to the Exchange server and be listed on the SSL certificate.

I suspect that is the core of your problem. That will be the reason Autodiscover doesn't work and the authentication prompts.

ThiaanAuthor Commented:
Hi Simon,

Thanks for the reply.

I have changed the URLs as you suggested so both internal and external are now[respective virtual directory] but there is no change. If I specify the MSSTD then the client connects but not if I try use plan autodiscover during the outlook setup. I also get a certificate error that states:

There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name on the target site
Outlook is unable to connect to proxy server. (Error code 0)

I have never seen an error code 0, 8 and 10 I have seen and that usually is an issue with the certificate.  The certificate issued on the server looks like so:

subject: CN=servername.domain.local

It is a web server cert and is valid on the machine. I am no expert when it comes to certificates but as far as I understand between the subject name and the sans the names should match one of them when outlook tries to connect?
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Simon Butler (Sembee)ConsultantCommented:
That cannot be a trusted certificate.
You cannot get trusted certificates with the local names on them unless it expires before November 2015. Are you using a trusted certificate?

Autodiscover is different to the name sued for Outlook Anywhere, so you have different issues, although most likely the same cause - trust on the certificate.

ThiaanAuthor Commented:
Its an internal CA which has been there for heaven knows how long. It is not linked in any public CAs
Simon Butler (Sembee)ConsultantCommented:
I will drop off the question then. I don't do anything with internal CAs. For public facing services like this they are more hassle than they are worth and I will not have anything to do with them.

Md. MojahidCommented:
What about owa? is working fine? If yes then try to reset once account password and figure it out what is status. And also check your credentials setting and sll certificate.
ThiaanAuthor Commented:
I managed to figure this out in my own clean lab environment with a green fields deployment
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.