chazzy2501 Posted November 20, 2017 Posted November 20, 2017 (edited) I'm seeing an issue with remote users (teachers going home) where outlook 2013 is unable to connect. I see a certificate warning that lists the local domain exchange server... all mailboxes are in the cloud. now I can only assume that the duff certificate is being provided by the local exchange server as its "exchangeserver.domainname.local" and exchange certs can't use the .local so of course it's invalid. I'll assume this is a direct access issue, although I'm seeing strange results from my autodiscover. (just a redirect to office365 ip addresses.) edit: ok so the cert source has the "exchangeserver.domainname.local" instead of the "mail.internetdomain.sch.uk" Edited November 20, 2017 by chazzy2501
chazzy2501 Posted November 21, 2017 Author Posted November 21, 2017 no the cert is good but is for the external name not the internal.
chazzy2501 Posted November 21, 2017 Author Posted November 21, 2017 well, I turned off the local exchange and this didn't help. When I remove the direct access features (on guest internet) outlook works fine. maybe a dns issue?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now