Quantcast
Viewing all articles
Browse latest Browse all 8719

Setting Out Of Office from Outlook not working with exchange 2010

Hi 


We have an exchange 2010  server with 2 load balanced CAS server and Mailbox servers in a DAG.  We have a few domain names accepted (will call it firstdomain.com and seconddomain.com)  but only one is in certificate (firstdomain.com).

The issue is - when user with default email @seconddomain.com try to set “Out Of Office” from outlook (2010 with all service packs and updates) he is getting “ Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later”  where setting it from webmail works fine and setting it from outlook for users with @firstdomain.com reply address works fine.

we have both internal and external urls for all virtual directories set to external host address (https://mail.firstdomain.com  etc). All the users are on intranet with local ip subnets (sites connected via vpns ), all the routing is in place and DNS points to correct ip addresses.

Autodiscover works fine (tested in outlook ) and giving correct address for OOF link ( https://mail.firstdomain.com/ews/exchange.asmx) wich opens fine if entered into address bar in IE so its NOT AN AUTODISCOVER issue .

I enabled  logging in outlook and thats what I am getting in there:

We have an exchange 2010  server with 2 load balanced CAS server and Mailbox servers in a DAG.  We have a few domain name accepted (will call it firstdomain.com and seconddomain.com)  but only one is in certificate (firstdomain.com).

The issue is - when user with default email @seconddomain.com try to set “Out Of Office” from outlook (2010 with all service packs and updates) he is getting “ Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later”  where setting it from webmail works fine and setting it from outlook for users with @firstdomain.com reply address works fine.

we have both internal and external urls for all virtual directories set to external host address (https://mail.firstdomain.com  etc). All the users are on intranet with local ip subnets (sites connected via vpns ), all the routing is in place and DNS points to correct ip addresses.

Autodiscover works fine (tested in outlook ) and giving correct address for OOF link ( https://mail.firstdomain.com/ews/exchange.asmx) wich opens fine if entered into address bar in IE so its NOT AN AUTODISCOVER issue .

I enabled  logging in outlook and thats what I am getting in there:

1600       0x49763D20        02/02/15 16:50:44           +++++++++++++++++++++++++++++++

1600       0x49763D20        02/02/15 16:50:44            OWINHTTP SEND HTTP REQUEST BEGIN

1600       0x49763D20        02/02/15 16:50:44             Profile=Outlook

1600       0x49763D20        02/02/15 16:50:44             SMTP=test.user@seconddomain.com

1600       0x49763D20        02/02/15 16:50:44             URL=https://mail.firstdomain.com/ews/exchange.asmx

1600       0x49763D5F        02/02/15 16:50:45            GetLastError=0; httpStatus=401.

1600       0x49763D5F        02/02/15 16:50:45            OWinHtpp disabled auth schemes:

1600       0x49763D5F        02/02/15 16:50:45           <NONE>

1600       0x49763D5F        02/02/15 16:50:45            OWinHtpp supported auth schemes:

1600       0x49763D5F        02/02/15 16:50:45            Negotiate

1600       0x49763D5F        02/02/15 16:50:45            NTLM

1600       0x49763D5F        02/02/15 16:50:45            Basic

1600       0x49763D5F        02/02/15 16:50:45            OWinHttp attempting Auto-Negotiate with Desktop Credentials.

1600       0x49763D5F        02/02/15 16:50:45            OWinHttp USING pcreds->dwAuthScheme:

1600       0x49763D5F        02/02/15 16:50:45            Negotiate

1600       0x49763D9D       02/02/15 16:50:45            GetLastError=0; httpStatus=500.

1600       0x49763DAD       02/02/15 16:50:45            OWINHTTP SEND HTTP REQUEST END

1600       0x49763DAD       02/02/15 16:50:45            -----------------------------

Last thing - we are using proxy server and with proxy off it works fine although all possible exchange server hosts/domains/ip addresses excluded from proxy.  

Aside from obvious question - what can be wrong and what to test next, another question is - how can I check/monitor setting OOF on server side (log files etc)?

Last thing - we are using proxy server and with proxy off it works fine although all possible exchange server hosts/domains/ip addresses excluded from proxy.  

Aside from obvious question - what can be wrong and what to test next, another question is - how can I check/monitor setting OOF on server side (log files etc)?

Thanks


Viewing all articles
Browse latest Browse all 8719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>