locked
Exchange Server 2013 to 2010 mailbox proxy is not working RRS feed

  • Question

  • I have exchange server 2013 and exchange server 2010 in co-exist. I have 3 cas server and 3 mbx server 2013 on windows server 2012 standard, 2 hub/cas server and 2 mbx server 2010 on windows server 2008 r2. when I try to access owa of exchange server 2010 mailbox using exchange 2013 url, I am getting the error as "something went wrong. sorry, we can't get that information right now, please try again later. If the problem continues please contact your helpdesk"

    Vishal C. Kalal | MCITP: Exchange 2010-2007 | Windows Server 2008

    Tuesday, January 28, 2014 3:59 PM

All replies

  • Hi,

    To narrow down the cause, I recommend the following troubleshooting:

    1. Check if the issue happens on all users.
    2. Try to directly login OWA 2010  and check if it works well.
    3. Check the IIS log on CAS 2013 server and find the error related to OWA.

    Thanks,


    Angela Shi
    TechNet Community Support

    Wednesday, January 29, 2014 3:56 PM
  • Dear, thank you very much for your suggestions, please find the below comments for the same-

    Yes, none of the exchange 2010 user is able to access using exchange 2013 owa. if I try to access directly using exchange 2010 owa its working fine. Also verified the logs but no luck.

    Anything else which I need to check or test.


    Vishal C. Kalal | MCITP: Exchange 2010-2007 | Windows Server 2008

    Wednesday, January 29, 2014 4:17 PM
  • Try going to IIS on your Exchange 2010 server go to the OWA Virtual Directory right click Windows Authentication and go to providers. Add Negotiate to the providers list with NTLM. Do an IIS reset and see if you can proxy connections.
    Tuesday, April 8, 2014 10:06 PM
  • Verify your external OWA URLs are populated:

    Get-OwaVirtualDirectory | ft servername, *externalurl* -a

    Exchange 2013 uses the externalurl value of your Exchange 2010 CAS servers to try to redirect. I found in my lab this value was not populated and caused a similar error.

    Good luck! 

    Tuesday, April 8, 2014 11:36 PM