Outlook 2016, Win 10 cannot connect to Exchange

[MobileTechie]

I've a new Win 10 machine and a new Office 365 home subscription so new Outlook 2016 client.

When I try to set up an email account on a hosted Exchange service they use it cannot connect - tried encrypted connection and fails, tries unencrypted and fails. The "manual" section allows manual entry of the exchange server - this doesn't work producing unknown error: 0x8004011c

I can set up this account just fine on my own Windows 7 laptop so I know the details are correct.
I've spoken to the hosted exhange firm and they have checked the autodiscover cname record pointing to them and they're happy with it.
It's just on this one Win 10 machine that it doesn't work.;

I've tried to call MS about 5 times now and each time they end up routing me to an Indian support group where the call volume is so low neither of us can hear each other and we cannot continue.

Already tried
reinstalling office
sfc /scannow
Microsoft Support and Recovery Assistant for Office 365

 

[YeOldeStonecat]

Try unchecking IPv6
Try this Office troubleshooting utility
https://diagnostics.outlook.com/#/

 

[MobileTechie]

Thx for the input

IPv6 hasn't helped unfortunately.

That is the same troubleshooter I tried but on trying any of the options that seem relevant its saying it only supports Office 365 environments

 

[YeOldeStonecat]

Hmmm...guess that makes sense (re: the troubleshooter). Did you reboot after disabling IP6?
Does this network have a history of local Exchange?

 

[MobileTechie]

I did yeah.

I'm setting it up at my own home and it's not connected to the company network via.

 

[nlinecomputers]

https://testconnectivity.microsoft.com/

That might help see if the autodiscovery really is setup correctly. Outlook 2016 is very picky about it.

 

[MobileTechie]

I've done the test connectivity thing and it passes, with some details:


The Microsoft Connectivity Analyzer is attempting to test Autodiscover for xxxx@xxxx.com
Autodiscover was tested successfully.

Additional Details

Test Steps

Attempting each method of contacting the Autodiscover service.
The Autodiscover service was tested successfully.

Attempting to test potential Autodiscover URL https://xxxxxxco.uk:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.

Attempting to test potential Autodiscover URL https://autodiscover.xxxxxxxco.uk:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.

Attempting to contact the Autodiscover service using the HTTP redirect method.
The Autodiscover service was successfully contacted using the HTTP redirect method.

Attempting to resolve the host name autodiscover.xxxxxxxxx.co.uk in DNS.
The host name resolved successfully.

Testing TCP port 80 on host autodiscover.xxxxxx.co.uk to ensure it's listening and open.
The port was opened successfully.

The Microsoft Connectivity Analyzer is checking the host autodiscover.xxxxxxxx.co.uk for an HTTP redirect to the Autodiscover service.
The redirect (HTTP 301/302) response was received successfully.

Attempting to test potential Autodiscover URL https://autodiscoverredirect.messageexchange.com/Autodiscover/autodiscover.xml
Testing of the Autodiscover URL was successful.

Also it works fine on other computers, just not this one.

 

[nlinecomputers]

Also it works fine on other computers, just not this one.

Define IT. The M$ test site works correctly on other computers but not this one? Or other computers can connect but not this one. And what version of Office are THEY running? Outlook 2016 has issues. I avoid it when I can.

 

[MobileTechie]

Define IT. The M$ test site works correctly on other computers but not this one? Or other computers can connect but not this one. And what version of Office are THEY running? Outlook 2016 has issues. I avoid it when I can.

What I mean is that this same account connects, sets up and works fine on Outlook 2016 on my own Win 10 laptop

Obviously the Testconnectivity site offers up the same results whatever computer I use with autodiscover by http method being the one that works after the 2 https ones fail.

 

[callthatgirl]

There are many ways to try to troubleshoot this, I avoid using 2016 for any new or fresh client based upon my past history of failures and attempts and wasted time. If you have to use it, I would try a few more things.

Try removing the OST that the first fail made, it's 16,464K in the appdata folder. That might help. The first fail leaves a copy and after that, even after troubleshooting you won't get through.

You can try removing the windows credentials and other stuff, here is my full length blog about it
http://callthatgirl.biz/outlook-cannot-log-on-verify-you-are-connected-to-the-network/

 

[YeOldeStonecat]

yeah that's a good point CTG makes....the Windows Credentials. I don't see it often..but I have seen it....and removing existing ones clears it. This has been with any version of Office.

 

[AndyM]

yeah that's a good point CTG makes....the Windows Credentials. I don't see it often..but I have seen it....and removing existing ones clears it. This has been with any version of Office.

Had that with a client that couldn't log in to OneDrive for Business on his Sharepoint account. Could sign in to the website, but as soon as he tried to sync anything, it wouldn't play ball. Ended up deleting the stored credentials, and he's been happy ever since.

Andy

 

[callthatgirl]

Yeah, I have beat the crap out of Outlook to get this fixed. I don't even go there anymore. 2 choices for the client....they downgrade themselves and have Microsoft do it, or I do it and I'm swift about it. I don't have time to fix crappy software. 2016 is crapola.

 

[Frick]

How are you adding the account?

Starting outlook and using the fist run wizard?

When I can't get an account to setup this way I go to the Control Panel - Mail section and create a new profile and add the account there. This has worked every time for me. As dumb as it is, this has really worked almost every time.

 

[AnthonyK]

I agree with @Frick
Creating a new profile in the control panel has always worked for me when everything else fails.