Exchange 2007 - users not able to access Out of office

[ranj]

Hi

We are running Exchange 2007 and it seems all of our users are not able to use the Out of office feature in Outlook.

 

Outlook 2010 users report that when clicking Out of office, outlook freezes for about 30 seconds, and the reports an error which says: 'Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.'

 

Outlook 2007 users just receive the error 'Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.'

 

We do have a number of users on different OS's. These are Windows XP pro and Windows 7 pro and they are on 2 domains with trusts setup between the 2. We are running an active directory version of 2003.

 

On the client WS we have ensured that all the windows updates have been actioned.

 

Does anyone have any suggestions?

 

Thanks

[FN-GM]

Is autodiscover working correctly?

[glennda]

I think it is todo with autodiscover. Can the users access the out of office via OWA?

[ranj]

I think it is todo with autodiscover. Can the users access the out of office via OWA?

 

Ahhhh Autodiscover.. Interesting...

 

Yes I can confirm works fine with OWA.

 

Any suggestions on best place to start?

[glennda]

Look through your DNS - do you have records for Auto discover pointing to your exchange server?

 

You should be able to run from the exchange power shell Test-OutlookWebServices I think

[Tallwood_6]

Hold down control and right click on the outlook icon in your quick launch and it should give you the option to test the connection. This will test the auto discovery and show you the failures, it's probably a DNS setting or the client trying to access your autodiscovery through your proxy which you can test by adding the autodiscovery address into the clients bypass proxy for local address list.

[sukh]

These types of issues are normally with autodiscover or certificates. Is the issue with internal/external clients?

 

 

Also, are you using split DNS? If yes have you created your zone and dns records?

 

 

 

Do the test autoconfig as mentioned above.

[marty]

I had a similar issue and had to add the fqdn for exchange in the IE proxy bypass list.

[Edu-IT]

I had a similar issue and had to add the fqdn for exchange in the IE proxy bypass list.

Same here.

[bart21]

To test auto discover from the Internet use http://www.testexchangeconnectivity.com

[ranj]

0

 

Hi an update. This issue is affecting local clients using full client Microsoft Outlook.

 

It is certainly an issue with autodiscover and we have confirmed this with the server provider.

 

Our Exchange server is hosted in a managed datacentre by the server provider. We do have full control of the server from our office location.

 

From testing using the outlook testemail autoconfiguration it seems autodiscover cannot connect successfully via our proxy.

 

as a tempoary fix we have had to resort to putting in a proxy exception *.domainname.com.

 

I have checked from our domain hosting side and we do have autodiscover.domainname.com. If I try to just put autodiscover....... in the proxy exception it doesnt work.

The problem I found is by putting in *.domainname.com in the exception it then breaks another web application which is used within the business.

 

Any suggestions?

[sukh]

what is the u r l for your water discover

[SYNACK]

what is the u r l for your water discover

 

http://tap.pipe.mains

Edited August 31, 2012 by SYNACK

[sukh]

think a call needs to be logged with thames water :-)

 

new techbology not quite working on the samaung.