Outlook 2016 will not connect to Exchange server
-
@wls-itguy I would think they have to be on the domain to use regular Outlook 2016. That is the way it is here where i am at. It communicates through the domain. Students here use either O365 or the web version of Outlook.
-
@jmoore said in Outlook 2016 will not connect to Exchange server:
@wls-itguy I would think they have to be on the domain to use regular Outlook 2016. That is the way it is here where i am at. It communicates through the domain. Students here use either O365 or the web version of Outlook.
Why would that be a requirement? Outlook can handle it's own authentication.
-
@jmoore said in Outlook 2016 will not connect to Exchange server:
@wls-itguy I would think they have to be on the domain to use regular Outlook 2016. That is the way it is here where i am at. It communicates through the domain. Students here use either O365 or the web version of Outlook.
No domain needed. I was using O16 with O365 for a long time. normally just sets up using Autodetect. However, I have run into issues where there is 'some disconnect'
AH - also check CredManager... I had some conflicts between the Domain and O365 entries.
-
@dashrender That could be however it works the same here. If a desktop/laptop is not on the domain then people have to use a web version. For clarity I am talking about the installable Office 2016 if that was not clear.
-
@jmoore said in Outlook 2016 will not connect to Exchange server:
@dashrender That could be however it works the same here. If a desktop/laptop is not on the domain then people have to use a web version. For clarity I am talking about the installable Office 2016 if that was not clear.
If that were the case BYOD devices wouldn't work at all. My Mac has no issues connecting, just to add some info.
-
@wls-itguy Ok it must be how it is setup then. That must be the variable. Yes our phones/tablets can authenticate but a laptop that is not on the domain can not unless students are using a web version.
-
On the non domain computer are you authenticating using upn, email address, or domain\username
I would guess youre using upn/email, try domain\username.
edit: i @'d the wrong person -
@momurda said in Outlook 2016 will not connect to Exchange server:
@jmoore On the non domain computer are you authenticating using upn, email address, or domain\username
I would guess youre using upn/email, try domain\username.I've tried both and neither work on my end.
-
But doesn't autodiscovery help with connecting Outlook to Exchange?
-
@black3dynamite said in Outlook 2016 will not connect to Exchange server:
But doesn't autodiscovery help with connecting Outlook to Exchange?
This was my thought. If you don't have autodiscover configured for your external DNS then Outlook will default to local configuration. Which is also blank...
-
@jmoore said in Outlook 2016 will not connect to Exchange server:
@dashrender That could be however it works the same here. If a desktop/laptop is not on the domain then people have to use a web version. For clarity I am talking about the installable Office 2016 if that was not clear.
Outlook 2016 from O365 is definitely designed to work in non local AD environments.
-
@dashrender We do not use O365 though. Sorry thats what I meant earlier.
-
@jmoore said in Outlook 2016 will not connect to Exchange server:
@dashrender We do not use O365 though. Sorry thats what I meant earlier.
even so - Domain joined or not should not matter. what happens if you try to use an external DNS like google?
Perhaps the autoconfig info is messed up.
-
@dashrender said in Outlook 2016 will not connect to Exchange server:
@jmoore said in Outlook 2016 will not connect to Exchange server:
@dashrender We do not use O365 though. Sorry thats what I meant earlier.
even so - Domain joined or not should not matter. what happens if you try to use an external DNS like google?
Perhaps the autoconfig info is messed up.
This is the answer as there are zero restrictions with Office and AD to connect to an Exchange Server. Never has been.
The autodiscover.domain.com is probably hosed on the public DNS. Domain devices use the internal AD DNS for DNS and thus work.
-
You can test the autodiscovery with the Microsoft Connectivity test, you can also check if the SCP lookup is the culprit
