![Cannot connect to hosted exchange server in outlook 2016 for mac windows 10 Cannot connect to hosted exchange server in outlook 2016 for mac windows 10](https://support.content.office.net/en-us/media/13dff9fe-9e4e-4899-9491-cd3d47cbf7a7.png)
Title kind of sums it up, but here's the scenario. I've been able to connect Outlook 2010 from a remote system to my Exchange 2010 server which is hosted on SBS 2011, but am failing to do so with Outlook 2016. I've seen that others have had this problem, but I can't get a clear picture of how to fix this. I'm connecting through our SonicWALL VPN. This is all kind of complex, but I can't isolate the problem.
I'm getting an error stating that the certificate is not valid and read an article stating that CAs are not giving out certs for domains based upon the SBS default of.local which is how our system is configured. I also read somewhere where Outlook Anywhere is supposed to be enabled. It is on our installation, but I'm not sure it configured correctly, if that's possible. Turbotax system requirements for mac in 2018. I don't know enough about this. I'm not sure that the cert issue (specifically for autodiscover) is causing me to be unable to finish the Outlook configuration either,even though I can choose the prompt to install it and/or click Yes to move past the warning), but maybe. Since Outlook 2016 no longer supports a manual configuration, i can't force it through either. Or do I need to open up something on the SonicWALL firewall?
Also the remote system is Windows 10. Not sure if this info is pertinent, but I'm pretty sure it doesn't make it any simpler. Has anyone had any luck configuring Outlook 2016 to connect to Exchange 2010 on SBS 2011 via VPN?
Open Outlook 2016. Follow ‘Tools' > 'Accounts’. Type your password. Enter the Exchange server address: exchange.powermail.be. Click on 'Add Account'. Allow our server to configure your Outlook.
If so, how did you do it? Thanks ahead of time. So one of the questions not addressed yet is how up to date is your patching for Exchange and SBS Are you using a Self Signed Cert (hopefully no) or trusted third party cert (which you can get for about 5 dollars a year) SBS 2011 needs to be updated to Update Rollup 4 to deal with the.local certificate issue and Exchange should have the latest UR. If you have not created a new cert (local self signed or trusted 3rd party) since applying those updates, you need to do that first as that will get rid of the.local piece. Then go here. Run the Outlook Connectivity and the Outlook Autodiscover tests.
I don't get prompted for a certificate when I access OWA (nor do I get any errors regarding autodiscovery), but I checked my certificate (public/downloads) and the 'Issued To', 'Issued By' and 'Subject' are all the same: -CA. The expiration is 2/24/17. Does this mean that it's self-signed and I should get one from a certified third-party? If so, what are your recommendations for a CA? I do have RU 4 for SBS 2011 installed. Exchange is SP3 RU 11.
Looks like I've got 14 new security updates to install for the OS and Exchange RU 14. I can't be sure that the latest cert was installed after RU4 for SBS 2011. Probably not.
Is this where my problem lies? I looked at setting up the SRV record through our Domain Hosting provider, Network Solutions.
They are asking for a 'Target' for the configuration. I'm guessing that this is the FQDN of my server, correct? However, I'm not sure if I should be using.com or.local on that. I'm assuming that it should.loca l for my FQDN, correct? When you access owa, check the details of the https certificate used. If it is issued by --CA, then it is self-signed. The certificate you found in download folder can be a remaining from old times.