Link to home
Start Free TrialLog in
Avatar of infedonetwork
infedonetwork

asked on

Outlook 2016 and Exchange 2016 won't connect

Hi
I have an Exchange 2016 and all clients are using Outlook 2016
From inside the network everything works perfect.
Now I have a new user that work remotely and his laptop is not join to the domain and I try to setup Outlook 2016 to work with Exchange.
Since Outlook 2016 does not support manual mode anymore how do I go around this.
I setup autodiscover on public DNS as follow:
CNAME autodiscover.domain.com mail.domain.com
When I run the Exchange analyzer toold for autodiscover I get an error about the certificate not having autodiscover.domain.com
Certificate is for mail.domain.com
Bellow is the error message I get when I try to setup Outlook 2016 outside the domain.
For the server I have mail.domain.com

Log onto Exchange ActiveSync mail server (EAS): Could not locate the specified server. User name and/or password are not valid. Please verify the information is correct.
ASKER CERTIFIED SOLUTION
Avatar of Scott C
Scott C
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of infedonetwork
infedonetwork

ASKER

I was wondering if I can create a self sign for autodiscover.domain.com and just add it but leave the mail.domain.com for OWA
If it's possible what services should I assign it to?
Now it's completely broken.
I did get a multidomain certificate that has both mail.domain.com and autodiscover.domain.com and I assign the smtp and IIS services to that new certificate and delete the old one then reboot and now OWA get me to log in but both OWA and ECP has a blank screen once I Logon.
Exchange management shell give me pages of errors and it asking for the server name
Sorry, I missed the thread on this.  Can you post the screenshot of the EMS error screen.  Also, try to open a PS window and post the results from that.
Problem was solved a while ago.
The certificate was missing on IIS front end transport I believe.
thank you for your help
Issue was with cert.