Exchange Connectivity

[GRitchie]

No luck.

 

Gives me "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."

[silvestre]

can you run this in a browser https://mail.domain.ca/Autodiscover/Autodiscover.xml

 

you may want to try with http as well instead of htttps

[GRitchie]

On my machine now, I've done that and I get a webpage (https only) showing

 

600

Invalid Request

[silvestre]

Http 600 means autodiscover service works and can be accessed properly.

 

 

[Check AutoConfiguration Status in Outlook]

===================================

a. While Outlook is running, click the CTRL key and then right-click the Outlook icon in the system tray and then select “Test Email Autoconfiguration”.

b. Confirm that your email address is in the address field, uncheck “Use Guessmart” and “secure Guessmart authentication” boxes. Then click the “Test” button.

c. Once it runs, please send me a screen shot of the Log tab and Results tab.

[GRitchie]

Results Tab:

 

Log Tab:

 

- - - Updated - - -

 

Bear in mind, I've just ran that on a client which IS connecting to exchange (my own machine, after re-installing office it worked, but doesn't on clients where I haven't re-installed office)

[silvestre]

Do you have outlook 2010 or 2013?

if 2010 do you have service pack 2 installed?

[GRitchie]

I'm on Outlook 2013 where it works, not sure about SP2. Is there any easy way to check? Or do I just have to try installing it?

[silvestre]

2013 is fine.

The other clients where it does not work, do they have outlook 2010?

you can check in Programs and features in the control panel and for the service pack you check in the install updates section in programs and features.

[GRitchie]

Just checked (using this https://support.microsoft.com/en-us/kb/2121559 to determine) and the 2010 client I'm testing on now has the version that is SP2

[silvestre]

Do this on a non working computer and post screenshots.

 

[Check AutoConfiguration Status in Outlook]

===================================

a. While Outlook is running, click the CTRL key and then right-click the Outlook icon in the system tray and then select “Test Email Autoconfiguration”.

b. Confirm that your email address is in the address field, uncheck “Use Guessmart” and “secure Guessmart authentication” boxes. Then click the “Test” button.

c. Once it runs, please send me a screen shot of the Log tab and Results tab.

[GRitchie]

@silvestre

Apologies it's stretched, screenshots from Impero:

 

Edited January 29, 2016 by GRitchie

[silvestre]

There seem to be no errors on that machine from the screenshots. Have you tried setting up outlook again.

[GRitchie]

I have, just gives me the same error about not being outlook needing to be online or connected to the exchange server etc.

[silvestre]

Can you check in your DNS if you have an autodiscover A record.

[GRitchie]

Internal DNS settings:

[silvestre]

Can you delete the local profiles for users on that machine and the server if you are using roaming profile and try again.

[GRitchie]

@silvestre - given that a shot, still same error on the client.

[GRitchie]

Any ideas? (Sorry for bump, but a bit desperate here!)

[silvestre]

check out this link.

Cannot connect to or resolve name Exchange server - MSOutlook.info

 

You would be better off using Office 365 than running your email server. Its free! and would save you the hassle updating.

[GRitchie]

Gave that registry update a shot, still same error :/

 

I know what you mean, however I've heard mixed reviews on 365, plus wouldn't migrating potentially cause more issues...?

[silvestre]

Gave that registry update a shot, still same error :/

 

I know what you mean, however I've heard mixed reviews on 365, plus wouldn't migrating potentially cause more issues...?

 

Can you connect by FQDN instead of using autodiscover?

 

I migrated exchange 2010 to office 365 and have had no major problems. if you are running internally it will be difficult to troubleshoot / solve quickly if you have major problems in the future. Also consider server costs, power failures, backups, maintenance!

[GRitchie]

Not sure, where would I try that?

 

It's something I'm looking into now. Don't want to continue with these Exchange problems, so it may be the best option! However, the main downside is if we have an internet failure, then there is no email access.

[zag]

Seriously just move to Office 365.

 

Nobody runs exchange servers any more for exactly this kind of reason. There are literally no disadvantages to it, especially as you already seem to be using webmail mainly.

[GRitchie]

True. True.

I would ideally get staff on the Outlook client. But you can do that with 365 anyway can't you?

[silvestre]

Manual configuration guide for Outlook 2010 (Exchange 2013) : Microsoft Exchange 2013 | SherWeb

Follow till step 9

for server enter FQDN of exchange server

 

True. True.

I would ideally get staff on the Outlook client. But you can do that with 365 anyway can't you?

 

You can use outlook with all Email providers.