Autodiscover working but outlook not connecting
Hi
I have an exchange 2016 server which has stopped accepting outlook 2016 connections.
I have tested the autodiscover which is fine but if i set an account up it autodiscovers and then says it cannot connect to the folders.
I have checked the internal and external urls and all seems fine.
I can connect using my iphone with out an issue if i manually put server name and domain etc in.
Please help
thanks
I have an exchange 2016 server which has stopped accepting outlook 2016 connections.
I have tested the autodiscover which is fine but if i set an account up it autodiscovers and then says it cannot connect to the folders.
I have checked the internal and external urls and all seems fine.
I can connect using my iphone with out an issue if i manually put server name and domain etc in.
Please help
thanks
I think you're talking about local outlook connection from same LAN
iPhone is using probably outside connection so autodiscover is pointing to your External MX with your External IP
Try create additional forward lookup zone in your internal DNS and name it like your server
email.yourdomain.com
inside put A record pointing to your local Exchange IP
(same as parent folder) A 192.168.1.10 {for example}
Create second Forwart lookup zone
autodiscover.yourdomain.co
Inside point A record to your local Exchange IP:
(same as parent folder) A 192.168.1.10 {for example}
Refresh DNS on workstation and start setup outlook again
iPhone is using probably outside connection so autodiscover is pointing to your External MX with your External IP
Try create additional forward lookup zone in your internal DNS and name it like your server
email.yourdomain.com
inside put A record pointing to your local Exchange IP
(same as parent folder) A 192.168.1.10 {for example}
Create second Forwart lookup zone
autodiscover.yourdomain.co
Inside point A record to your local Exchange IP:
(same as parent folder) A 192.168.1.10 {for example}
Refresh DNS on workstation and start setup outlook again
Lead email system administrator
CERTIFIED EXPERT
try to test connection setting using MS site https://testconnectivity.microsoft.com
You will see all errors :-)
You will see all errors :-)