![]() I also read that Outlook 2016 requires autodiscover to be working. But then I found out he has the older version of Office 365 on his pc. This is the only person having an issue and only on his Surface tablet. Exchange server virtual directories for both Internal and External URLs are set up with the same URL which is our external URL. I can do nslookup and it finds the Exchange server but not through Outlook. Both Office 2016 and Exchange serverĢ016 are up to date with patches. Also i am using UPN logins which match the email addresses. I know i have set up the different Autodiscover records for both Internal and external clients and they resolve properly. Only If the workstation is joined to the domain and try to add Exchange profile to Outlook 2016, it keeps prompting for username/password to be put in during the last step of the Outlook configuration (Log onto server) It sets up auto-discover records in the registry that prevent it from looking for the real autodiscover DNS settings. This was because it doesn't give the option to connect to an exchange server. It works fine with Outlook 2013 regardless of scenario. This was a common issue, connecting exchange to Outlook 2016, when it was first released. It works if the workstation is NOT on the domain but on the same network, it will find the autodiscover record and add the Exchange profile ![]() Keeps asking for credentials to be put in and will not let me add the Exchange profile. I have an issue with Outlook 2016 clients connecting to On-premises Exchange 2016.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |