To fix the external records (more than likely, autodiscover is the one that doesn't exist and needs to be created), on your domain's name servers create an A record for and point it to the external IP of your mail server (eg. These should resolve to your external IP of your mail server (eg. To confirm that Split-DNS is working correctly: They should both respond externally to your external IP of the mail server (eg. Then from an external source, ping the OWA URL and AutoDiscover URL (eg. These should both respond from an internal computer to the internal IP of your Exchange server (eg. To make sure Split-DNS is working properly, ping the OWA URL and AutoDiscover URL (eg. Please also turn on SSLOffloading.Īs DNS is a vital component in any network, please make sure that Split-DNS is setup first before doing anything else. As you follow this guide, you will set the ClientAuthenticationMethod (Internal and External if on Exchange 2013) to NTLM and IISAuthenticationMethods to Basic,NTLM (and Basic,NTLM,Negotiate for Exchange 2013). On Exchange 2013, you also have a new option called Negotiate, which is recommended. You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |