Issue connecting Email profile. Outlook 2016

[Sir Asvald]

Hello Guys, I'm having trouble connecting my mailbox to Outlook. When I open up outlook, it finds my name and email when I click next, it says this error: "we're sorry we couldn't set up your account automatically outlook 2016" I'm using Exchange 2010

Can someone help.  

[Agent32277]

@Abdul201588 With Outlook 2016, the ability to manually configure exchange profiles was removed. I would make sure the exchange server has the proper DNS records and autodiscover settings. The server should have a tool to run to test the autodiscover settings. 

[NelizMastr]

Is the server on your local network or is it remote? If it's a remote server, you need to make sure there is an autodiscover record pointing to your domain and the exchange server in it. If you have a 3rd party managing your DNS, contact them to verify your configuration.

[Sir Asvald]

3 minutes ago, NelizMastr said:

Is the server on your local network or is it remote? If it's a remote server, you need to make sure there is an autodiscover record pointing to your domain and the exchange server in it. If you have a 3rd party managing your DNS, contact them to verify your configuration.

Local Sever. Domain registered at godaddy, everything points to my IP at home. I've got a Domain controller and of course, an Exchange.

[NelizMastr]

7 minutes ago, Abdul201588 said:

Local Sever. Domain registered at godaddy, everything points to my IP at home. I've got a Domain controller and of course, an Exchange.

Take a look at this article:

 

https://technet.microsoft.com/en-us/library/mt473798(v=exchg.150).aspx

 

And verify you have the correct records set in your DNS server. Also make sure your clients use THAT DNS server as their primary DNS, if they're set to Google DNS or your ISPs DNS, your DNS records can't be resolved, as they're not publicly available.

[Guest]

20 hours ago, Abdul201588 said:

Local Sever. Domain registered at godaddy, everything points to my IP at home. I've got a Domain controller and of course, an Exchange.

Is there a valid SSL certificate referencing auto discovery? 

 

Better question though: why are you running A) Exchange 2007 and B) On-premise Exchange?

 

If you're trying to learn about Exchange, why 2007 over 2016? 

 

See https://technet.microsoft.com/en-us/library/bb124251.aspx and https://blogs.technet.microsoft.com/exchange/2015/11/19/outlook-2016-what-exchange-admins-need-to-know/

[Sir Asvald]

2 hours ago, Windspeed36 said:

Is there a valid SSL certificate referencing auto discovery? 

 

Better question though: why are you running A) Exchange 2007 and B) On-premise Exchange?

 

If you're trying to learn about Exchange, why 2007 over 2016? 

 

See https://technet.microsoft.com/en-us/library/bb124251.aspx and https://blogs.technet.microsoft.com/exchange/2015/11/19/outlook-2016-what-exchange-admins-need-to-know/

I've got Exchange 2010. Not 2007.. I'm using a certificate from LetsEncrypt

[Guest]

55 minutes ago, Abdul201588 said:

I've got Exchange 2010. Not 2007.. I'm using a certificate from LetsEncrypt

Typo on my behalf; had to double check Exchange 2010 was supported but it was 07 that got kicked. 

 

Does that SSL certificate include auto discover?

[Sir Asvald]

2 hours ago, Windspeed36 said:

Typo on my behalf; had to double check Exchange 2010 was supported but it was 07 that got kicked. 

 

Does that SSL certificate include auto discover?

It is working now. Other is issue I'm facing is that I'm getting an error. Which is this:" outlook 2016 the name on the security certificate is invalid or does not match the name of the site"

It's trying to connect via the server's name. But it's suppose to be using this:

 

Spoiler

EDIT: It's working. Had to change the Certificate in the IIS Manager.