Outlook Issue "Allow this Website to configure server settings"

Hi Guys,

We have a couple of mailboxes on Exchange, divided into two sites.
The SSL and AutoDiscover settings for both sites are exactly the same.

Recently the one site started using a new internet domain name.
We added the domain to the Exchange server list of accepted domains and added a new reply address to each user mailbox in Exchange of site 2.

All worked well, except the users of site 2 are now receiving a message in Outlook:
"Allow this website to configure mailbox.newdomain.com server settings?

It wants to redirect the AutoDiscover config to the hosting company of the new domain, which has nothing to do with our Exchange server.  Mail for the new domain is already being delivered to our Exchange server.

AutoDiscover and other settings should stay exactly the same.
Rupert EghardtProgrammerAsked:
Who is Participating?
 
ChrisConnect With a Mentor Commented:
you should look at the "Test Email auto Configuration" on Outlook client and look at the logs.
It will recurse through various DNS lookups before it find the settings.

can you query the DNS to see if they already have any records that might be interfering, if not then you should create them to correctly push the email autoconfiguration in the right direction
0
 
Valentina PerezConnect With a Mentor Exchange ServersCommented:
HI Rupert,

If you accept the "Allow this website to configure mailbox.newdomain.com server settings", you continues to have the issue in Outlook. It seems to be DNS issue, you have some redirection.

Regards
Valentina
0
 
Rupert EghardtProgrammerAuthor Commented:
Thanks,

The problem was DNS related,

The ISP hosting the new domain had setup an SRV record for AutoDiscover (in their configuration).
Apparently, if a workstation is not on the Exchange domain, the second check Outlook does is referencing to the DNS of the user's Exchange e-mail address, in this case the "new domain"

Hence the ISP's AutoDiscover settings was used for site 2 and not working, while site 1 on the same Exchange server was fine.
0
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.