Jump to content

Recommended Posts

Posted

We have a frustrating issue with Desktop Outlook connecting to Office 365. We have around 6-8 laptops that have suddenly done the following;

 

- Emails get struck in the outbox

- User restarts Outlook but when starting up again it says "Outlook cannot log in, verify you are connected to the network and are using the proper server and mailbox name. The microsoft exchange information service in your profile is missing required information. Modify your profile to ensure that you are using the correct exchange information service". After pressing ok, they get "System resources are critically low. Close some windows". After clicking ok. "Cannot start Microsoft Outlook, cannot open the Outlook window. The set of folders cannot be opened. The information store could not be opened"

 

As i said above, this has happen on a number of standalone laptops (not connected to a domain) and all running Office 2016.

 

I've ran a check DNS in the Office 365 management panel and it reports everything is ok. To me this looks like an autodiscover issue, when trying to re-add an account it keeps asking me for the password again. But the server address is mail.domainname.com which i'm fairly sure it shouldn't be. It should be pointing to office 365's servers, we don't have an DNS records on our hosting for mail.domainname.com

Posted

Have you used the built-in autodiscover test tool thingy? Should show any issues up easily.

 

If you wonder what test, hold control and click the outlook icon in the taskbar (not the program the mini-one) and click test auto configure

 

Steve

Posted (edited)
Have you used the built-in autodiscover test tool thingy? Should show any issues up easily.

 

If you wonder what test, hold control and click the outlook icon in the taskbar (not the program the mini-one) and click test auto configure

 

Steve

 

I've ran the test on testconnectivity.microsoft.com and it all passes other than when trying to connect to autodiscover with SSL - this fails but the it says the overall test succeeded.

 

I had to create a dummy POP3 account to get into Outlook, but when running the test it continues to try and connect via mail.domainname.com, imap.domainname.com and smtp.domainname.com. We have no DNS records matching them so i'm unsure where they are getting that from.

Edited by nathan
Posted (edited)
These are standalone staff laptops, not connected to any domain. We started our of Office 365 and never used an on-premise Exchange and we are not using McAfee Edited by nathan
Posted

Mine will show a lot different as it's with autodiscover/domain etc.

 

But if you check in C:\Users\\AppData\Local\Microsoft\Outlook\ what's the autodiscover file show in there?

 

Might be a hidden file too depending on setup

 

Steve

Posted
Have you checked the autodiscover record using nslookup?

 

Non-authoritative answer:

Name: autodiscover-emeawest.outlook.com

Addresses: 132.245.76.232

132.245.195.168

132.245.226.40

132.245.77.24

40.101.40.56

132.245.226.56

132.245.36.104

132.245.176.72

132.245.27.40

Aliases: autodiscover.domainname.com

autodiscover.outlook.com

autodiscover.geo.outlook.com

autodiscover.outlook.com.glbdns2.microsoft.com

 

They look ok to me, in that they are point to MS servers

Posted
Delete the mail profile from the laptop and outlook will download the emails again.

 

No, they won't reconnect.

 

Just spoke with Microsoft, our hosting provider uses Cpanel that has a autoconfig/autodiscover feature. I'm wondering if this is causing issues - i presume it's turned off but will raise a support ticket with them.

Posted

Fixed it!

 

It was an issue with Cpanel email routing, for some reason when it was set to "Automatically Detect" it wouldn't work, i changed this to "Remote Mail Exchanger" and it is now working. This is really strange in that it has always been set to auto. The only reason i can think of is if theres been an update to cpanel that has introduced a bug.

 

cpanel.jpg

Posted
Fixed it!

 

It was an issue with Cpanel email routing, for some reason when it was set to "Automatically Detect" it wouldn't work, i changed this to "Remote Mail Exchanger" and it is now working. This is really strange in that it has always been set to auto. The only reason i can think of is if theres been an update to cpanel that has introduced a bug.

 

[ATTACH=CONFIG]39437[/ATTACH]

 

Does cPanel control your MX Records then somehow?

Posted
Does cPanel control your MX Records then somehow?

 

When automatically detect is selected on email routing it tries to work out the correct setting based on the MX records used, in our case for some reason it wasn't working it out correctly and would use the local mail exchanger instead of the the remote mail exchanger.

 

This caused the autodiscover to use the cpanel version instead of the office 365 version and gave the incorrect settings to clients

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...