I have exchange 2013 and 2010 installed and I'm in co-existence mode. Everything is working correctly except OWA. When I login with an account that has been moved to 2013 it works perfect but when I try to login with an account that is still on the 2010 server I get the ":( Sorry, something went wrong" message.

Outlook Anywhere and ActiveSync also works fine to access mailboxes on either server.

Any ideas on what I might be doing wrong?

Thanks!

Hi

I've been trying to reproduce this and the only way I've managed to break it so far (I'm sure there are others) is by disabling Basic authentication for the OWA virtual directory on the 2010 CAS.  Could you check if Basic Auth is enabled?

Cheers, Steve

Edit: Actually it was removing Windows Authentication that broke the OWA proxying.  Can you check that Windows Authentication is enabled on your OWA virtual directory.

• Edited by steve siyavayaMicrosoft community contributor Tuesday, April 09, 2013 4:50 PM

Thanks for the quick response!

I was using forms-based authentication, but I switched both servers to Integrated Windows and Basic Auth now. Still having the same issue though.

Are both severs in the same AD site?

Ryan I am having the same issue.   I have also verified that my settings match *technet*/en-us/library/jj150489(v=exchg.150).aspx   Certificates look good.  Have you come up with anything yet?

Same problem here.  Two servers in the same AD domain (sitting on the same ESX server).  Both are using their external certificates for *.domain.com and the correct authentication options are ticked for owa, ews, and autodiscover.

I've also setup another site like this everything worked perfectly.

The major annoyance is there aren't any error messages pointing where to look next.

As with the other replies once a mailbox has been moved OWA works correctly.

• Edited by The-Kevster Monday, April 15, 2013 11:12 AM

Have you made sure that 2010 OWA is configured for basic and integrated authentication?

Here's the auth setup across both servers.  I believe everything is correct.

• Edited by The-Kevster Monday, April 15, 2013 12:07 PM

To add to this I have just found an event id 3005 - Task Category: Core.

[Owa] Marking ClientAccess 2010 server servername.domainname (https://servername.domainname/owa) as unhealthy due to exception: System.Net.WebException: The operation has timed out
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)

and

[OwaCalendar] Marking ClientAccess 2010 server servername.domainname (https://servername.domainname/owa/Calendar) as unhealthy due to exception: System.Net.WebException: The operation has timed out
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)

I can assure you that clicking on the URL linked in the event log brings up the login page in internet explorer.

Thanks for your help.

• Edited by The-Kevster Monday, April 15, 2013 12:26 PM

Hello,
 
Is there any error code in the IIS log?
 
Thanks,

If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

I don't see anything I would class as an error.  Here are the last few lines from inetpub\LogFiles\ when I try to login.

2013-04-15 13:09:56 127.0.0.1 GET /owa/default.aspx &ActID=c1f0474f-c122-4c25-bada-19f2c392ca67 444 company\SM_31dc664bbcbc435da 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 200 0 0 25
2013-04-15 13:09:56 127.0.0.1 GET /owa/15.0.620.29/owa2/scripts/preboot.0.js - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 1 2148074254 9
2013-04-15 13:09:56 127.0.0.1 GET /owa/15.0.620.29/owa2/scripts/preboot.0.js - 444 company\SM_31dc664bfbfa435da 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 200 0 0 11
2013-04-15 13:09:56 127.0.0.1 GET /owa/logoff.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 1 2148074254 2
2013-04-15 13:09:56 127.0.0.1 POST /owa/service.svc action=GetFolderMruConfiguration&ActID=8322e948-ee18-40fb-93d3-f9abcfe5ce86 444 company\SM_31dc664bfbfa435da 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 200 0 0 37
2013-04-15 13:09:56 127.0.0.1 GET /owa/logoff.owa - 444 company\SM_31dc664bfbfa435da 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 302 0 0 3
2013-04-15 13:09:59 fe80::45fc:3bda:2fc6:ea96%12 GET /ecp/ ActID=5933db1b-8623-47d3-9715-457d52ffb1b3 444 company\SM_8d8efc2da88a4e739 fe80::45fc:3bda:2fc6:ea96%12 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING) - 200 0 0 140
2013-04-15 13:09:59 fe80::45fc:3bda:2fc6:ea96%12 POST /ecp/RulesEditor/InboxRules.svc/GetList msExchEcpCanary=6-3V-hBN0kO_uABmFVMGxhLvH6vxB9AIPijh9PT5CtMP7Op7ilIugGGeK5HF-2IX7ZZElFBYNlI.&ActID=84b124c7-dd3b-4804-b4be-0e28596ce923 444 company\SM_8d8efc2da88a4e739 fe80::45fc:3bda:2fc6:ea96%12 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING) - 200 0 0 74
2013-04-15 13:09:59 fe80::45fc:3bda:2fc6:ea96%12 GET /ecp/logoff.aspx ActID=ddb3ca46-e02f-4fbc-88c3-a9308bfd4518 444 company\SM_8d8efc2da88a4e739 fe80::45fc:3bda:2fc6:ea96%12 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING) - 302 0 0 3

All here is my current setup.  

 Exchange 2010 Server -

       OWA - Anon/BASIC/Windows Auth Enabled
       ECP - Anon/Basic/Windows Auth
       ECP/14.3.X - Anon/BASIC

       Default - Forms Authentication is also turned on.
       I also tried changing to BASIC Auth/No Forms

Hope this helps some troubleshooting.

To add to this I have just found an event id 3005 - Task Category: Core.

[Owa] Marking ClientAccess 2010 server servername.domainname (https://servername.domainname/owa) as unhealthy due to exception: System.Net.WebException: The operation has timed out
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)

Are you able to login to the 2010 owa from the exchange 2013 machine ?

This error looks like a firewall between the servers ?

I quite agree. But they're on the same vlan, on the same ESX server so traffic doesn't even leave the virtual switch. Nowhere near a firewall. I can login to the exchange 2010 server using the internal URL from the 2012 server.

• Edited by The-Kevster Monday, April 15, 2013 6:14 PM

Has anyone managed to fix this issue? I've reset the authentication and SSL settings for all virtual directories as per MS guidelines but this hasn't fixed the issue.

Thanks,

Kev

I haven't, my installation is in a production environment, so I have to work on it after hours.   Every change I make I need to revert it.  So far nothing has worked.  I'd open a support ticket with microsoft but not sure they have the fix yet.... - Joe

I quite agree. But they're on the same vlan, on the same ESX server so traffic doesn't even leave the virtual switch. Nowhere near a firewall. I can login to the exchange 2010 server using the internal URL from the 2012 server.

I have a similar setup and am running into the same issue.  It actually works when I reset IIS for the 2013 server for a few minutes but then reverts back.  I dug into the logs and found the following in the HTTP Proxy logs:

2013-04-24T02:21:47.187Z,f87aa9d3-1750-44c2-9756-d95c3c5af55b,15,0,620,16,,Owa,,,FBA,True,DOMAINNAME\tdoris,,,Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0),69.204.247.252,RMDHSRV1,302,,,,,,,,,,,,123,,,,1,,,,,,,,,0,,,,,-1,1,,,,1,,,OnBeginRequest=0;,
2013-04-24T02:21:47.187Z,73c05b95-03ef-4572-9b1f-1d2e946c5c51,15,0,620,16,,Owa,,,FBA,True,DOMAINNAME\tdoris,,,Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0),69.204.247.252,RMDHSRV1,302,,,,,,,,,,,,123,,,,1,,,,,,,,,0,,,,,-1,1,,,,1,,,OnBeginRequest=0;,
2013-04-24T02:21:47.265Z,ceae28f4-7474-4ac3-bd4f-1c33d2562530,15,0,620,16,,Owa,/owa/,,FBA,True,DOMAINNAME\tdoris,,Sid~S-1-5-21-2978734823-3142686834-1291340043-2777,Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0),69.204.247.252,EXCHANGE2013SERVER,500,,ServerNotFound,GET,,,,,WindowsIdentity,,,,0,,,,13,12,,0,,0,,0,0,31.1826,1,,-1,12,1,28,,,,27,,,OnBeginRequest=13;DownLevelTargetHash=0/-1/1;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException: Unable to find proper back end service for Sid~S-1-5-21-2978734823-3142686834-1291340043-2777 in site CN Default-First-Site-Name CN Sites CN Configuration DC domainname DC nyc. ---> Microsoft.Exchange.HttpProxy.NoAvailableDownLevelBackEndException: Unable to find proper back end service for Sid~S-1-5-21-2978734823-3142686834-1291340043-2777 in site CN Default-First-Site-Name CN Sites CN Configuration DC domainname DC nyc.    at Microsoft.Exchange.HttpProxy.DownLevelServerManager.GetClientAccessServiceFromList[ServiceType](List`1 serverList  ServiceTopology topology  AnchorMailbox anchorMailbox  Site targetSite  ClientAccessType clientAccessType  Predicate`1 otherFilter  RequestDetailsLogger logger)    at Microsoft.Exchange.HttpProxy.DownLevelServerManager.GetClientAccessServiceInSite[ServiceType](ServiceTopology topology  AnchorMailbox anchorMailbox  Site targetSite  ClientAccessType clientAccessType  Predicate`1 otherFilter  RequestDetailsLogger logger)    at Microsoft.Exchange.HttpProxy.DownLevelServerManager.GetDownLevelClientAccessServer[ServiceType](AnchorMailbox anchorMailbox  BackEndServer mailboxServer  ClientAccessType clientAccessType  RequestDetailsLogger logger  Boolean calculateRedirectUrl  Uri& redirectUrl)    at Microsoft.Exchange.HttpProxy.BEServerCookieProxyRequestHandler`1.GetDownLevelClientAccessServer(AnchorMailbox anchorMailbox  BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.LatencyTracker.GetLatency[T](Func`1 operationToTrack  Int64& latency)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon beacon)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass2b.<OnCalculateTargetBackEndCompleted>b__2a()    --- End of inner exception stack trace ---;

Meanwhile, a successful login (right after running IISRESET results into this:

2013-04-24T02:07:21.244Z,e01e883b-adc1-4afb-9720-bcc8faca600f,15,0,620,16,,Owa,/owa/ev.owa,,FBA,True,DOMAINNAME\tdoris,,Sid~S-1-5-21-2978734823-3142686834-1291340043-2777,Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0),69.204.247.252,RMDHSRV1,200,200,,POST,Proxy,EXCHANGE2010SERVER.domainaname.nyc,14.03.0123.000,IntraForest,WindowsIdentity,Server~EXCHANGE2010SERVER.domainaname.nyc~1937997947~4/24/2013 2:17:19 AM,,,120,136,1,,1,0,,0,,0,,0,0,0,0,5,5,7,0,3,,,,8,?oeh=1&ns=PendingRequest&ev=FinishNotificationRequest&Fn=1&UA=0,,OnBeginRequest=0;ProxyToDownLevel=True;,
2013-04-24T02:07:21.260Z,93560b1c-544b-4958-b071-656032aa5980,15,0,620,16,,Owa,/owa/ev.owa,,FBA,True,DOMAINNAME\tdoris,,Sid~S-1-5-21-2978734823-3142686834-1291340043-2777,Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0),69.204.247.252,RMDHSRV1,200,200,,GET,Proxy,EXCHANGE2010SERVER.domainaname.nyc,14.03.0123.000,IntraForest,WindowsIdentity,Server~EXCHANGE2010SERVER.domainaname.nyc~1937997947~4/24/2013 2:17:17 AM,,,0,383,1,,1,0,,0,,0,,0,0,3463.3724,0,4,3454,3456,0,3,,,,3457,?UA=0&oeh=1&ns=PendingRequest&ev=PendingNotificationRequest&canary=D-Af2mBolkS2W2vHq2syNnb7J7AnFNAIzqsWynJrW9BlMJEIZ2A4so5Ppu9_Hi41aKz5U8Qhmk8.,,OnBeginRequest=0;ProxyToDownLevel=True;,HttpException=ClientDisconnect;
2013-04-24T02:07:21.322Z,a1a8e26f-d84e-457f-aec7-b0865f2078af,15,0,620,16,,Owa,/owa/logoff.owa,,FBA,True,DOMAINNAME\tdoris,,Sid~S-1-5-21-2978734823-3142686834-1291340043-2777,Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0),69.204.247.252,RMDHSRV1,302,302,,GET,Proxy,EXCHANGE2010SERVER.domainaname.nyc,14.03.0123.000,IntraForest,WindowsIdentity,Server~EXCHANGE2010SERVER.domainaname.nyc~1937997947~4/24/2013 2:17:21 AM,,,0,172,1,,1,0,,0,,0,,0,0,46.7744,0,23,29,30,1,3,,,,32,,,OnBeginRequest=0;ProxyToDownLevel=True;,

The event logs appear what the people above are describing.  Gonna do a bit more digging and testing...

• Edited by Ed Cho Wednesday, April 24, 2013 2:34 AM
• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Thursday, April 25, 2013 3:19 AM

Not sure why my post was marked as answered as it reverts back to the problem state about 5-10 minutes after IISRESET.

I am trying to force it into redirection instead of proxying but unable to (doesn't seem like LegacyRedirectType and RedirectToOptimalOWAServer is being respected).

The iisreset doesn't work for me. As soon as the server responds it shows the sorry screen.

I completely uninstalled my Exchange 2013 server server today and built a brand new 2012 server even with a new computer name. Still no joy. I'm leaning towards a problem with the 2010 server now. 

Not sure what to check though.

The iisreset doesn't work for me. As soon as the server responds it shows the sorry screen.

I completely uninstalled my Exchange 2013 server server today and built a brand new 2012 server even with a new computer name. Still no joy. I'm leaning towards a problem with the 2010 server now. 

Not sure what to check though.

Actually, when I played around with it this morning, it stops working after the first login.  If the first login, it returns a 500 error for any subsequent login that resides on the 2010 box.

Opened up a case and the tech took 4-5 hours troubleshooting the issue today with no resolution (also mentioned this thread as all the symptoms above are present in my environment).  He is escalating it and will hear back tomorrow.  I'll update here at what they find. 

Actually, when I played around with it this morning, it stops working after the first login.  If the first login, it returns a 500 error for any subsequent login that resides on the 2010 box.

Opened up a case and the tech took 4-5 hours troubleshooting the issue today with no resolution (also mentioned this thread as all the symptoms above are present in my environment).  He is escalating it and will hear back tomorrow.  I'll update here at what they find. 

Update #1: Troubleshooted several hours on Friday (and actually made our 2010 unstable by accidentally reactivating IPv6 when resetting the network settings).  Ran a few more tests this morning and gathered more logs.  Will update when I have something with more substance. 

• Edited by Ed Cho Monday, April 29, 2013 8:57 PM grammar

Thanks for the updates. Nice to know even MS are struggling with this one. If they need another setup to look at please let me know.

@ed Thanks for the updates.   Still struggling with this as well.

Can someone test out this solution?

Open up c:\windows\system32\drivers\etc\hosts file and add the following lines on the 2013 server?

IPADDRESS ServerName2010
IPADDRESS ServerName2010.domainname.com

Also let me know if you are using VMWare or not.

Thanks. 

• Edited by Ed Cho Wednesday, May 01, 2013 8:14 PM

Ed,

I tried Forcing IPv4 in the hosts file with you updates and nothing still the "Sorry something went wrong" error.

Updated "192.168.X.X My2010Server My2010Server.domainname.com" in hosts file
restarted IIS
Closed Browser, ReopenedStill get error.

Not using VMware.

Thanks,

Joe

Added the hosts entries but still no fix.  Rebooted the server after updating the host file just in case.

I am using vmware.  Did this fix the issue for you?

Any news on this, I am in the same boat, in a production environement with half the users on a 2010 box.

This fix indeed worked for me but i'm not exactly sure what other changes they made.  I am using a VMWare box but also disabled IPv6 (via the registry AND in the control panel) for both 2010 and 2013.

HKLM\System\CurrentControlSet\Services\TCPIP6\Parameters

DWORD: DisabledComponents (ffffffff)

However, I got an e-mail late last night as they are trying to analyze the situation further. They state that IPv6 is required for 2013 and they want me to enable IPv6.  However, enable IPv6 results in an unstable environment for 2010 so I haven't done it yet. 

EDIT: Also make sure that the DNS and DHCP servers has IPv6 disabled as well.

• Edited by Ed Cho Thursday, May 02, 2013 8:32 PM

This fix indeed worked for me but i'm not exactly sure what other changes they made.  I am using a VMWare box but also disabled IPv6 (via the registry AND in the control panel) for both 2010 and 2013.

HKLM\System\CurrentControlSet\Services\TCPIP6\Parameters

DWORD: DisabledComponents (ffffffff)

However, I got an e-mail late last night as they are trying to analyze the situation further. They state that IPv6 is required for 2013 and they want me to enable IPv6.  However, enable IPv6 results in an unstable environment for 2010 so I haven't done it yet. 

EDIT: Also make sure that the DNS and DHCP servers has IPv6 disabled as well.

Just as a follow-up and clarification to this issue -- MS stated that IPv6 is required to be ALL enabled  -OR- ALL disabled. I will keep mine disabled but the tech said to make sure 2010 + 2013 + DC/DNS/DHCP server has IPv6 all the same settings in regards to having the registry key + IPv6 box unticked in the Network properties for the network card that I am utilizing. 

Hope this helps someone -- they are also actively monitoring this thread as well so feel free to post more information here.  Thanks.

Just disabled IPv6 on both exchange servers without any luck.  Host entry is still present.  Might have to open a support case if yours is now fixed :(

Just disabled IPv6 on both exchange servers without any luck.  Host entry is still present.  Might have to open a support case if yours is now fixed :(

Sorry to hear that --  it might save some time to perform the following traces for them (as they were able to determine my cause from these traces):

Extra Trace:

--------------

On Exchange 2013 server-Go to start-run-type extra.exe

Choose 'Trace Control'

Select the path you want the trace file to go to. Hit 'Set manual trace tags'

Under 'Trace Types', select all 8 checkboxes at the top.

Under 'Components to Trace' please select all the following components;

         ActiveMonitoring

         HttpProxy

         NetworkingLayer

         OWA

         SystemLogging

b. De-select any other components from a previous trace

 

c. From the Exchange 2010 server run the ExTrace with the following tags;

         Owa

         SystemLogging

 

Hit 'Start Tracing' on both the Exchange servers. Reproduce the issue, then hit 'Stop tracing now'

Good luck to you!

• Edited by Ed Cho Friday, May 03, 2013 10:15 PM

Ed,

Did you have to register extra.exe in EX2013CU1?   I can't find an Extra.exe anywhere in my 2013 installation. Extrace.dll exists but no way to lauch extra.  Even scanned the Exchange install files.

Thanks,

Joe

Sorry -- I think MS loaded ExTRA.msi (Microsoft Exchange Troubleshooting Assistant) onto the server while I wasn't looking.  I can provide the zipped msi if you want as I still have it. 

Just keep in mind that Extraces generate a binary file (.ETL) which contains all the proprietary & confidential information.  Customers currently cannot analyze the extraces themselves.

• Edited by Ed Cho Wednesday, May 08, 2013 8:35 PM

I have the exact same issue doing IISReset doesnt fix it and I already have IPV6 Disabled.

Any of you guys have any fixes maybe after working with MS?  

 

• Edited by pslager Wednesday, July 31, 2013 6:20 PM

I have been suffering from this exact same problem for weeks.

Coexistence scenario with Exchange 2010 and Exchange 2013.
Mailboxes hosted on 2013 are no problem... but mailboxes which are still on 2010 receive an HTTP 500 error immediately after logging into OWA on the 2013 CAS server.

I have eventually determined that the problem does not lie directly with the Exchange 2013 CAS server or the 2010 CAS server (or IPV6 as some seem to think)... the issue is with the 2010 Mailbox server.

I provisioned a new 2010 mailbox server and moved some users over to it (no DAG on the new server).
As soon as their mailboxes had moved... the HTTP 500 error disappeared and the CAS proxy works 100%!

There is either something wrong with my original 2010 mailboxes or DAG (even though they are working fine in all other respects)

Hope this helps some of you!

• Proposed as answer by Gregg Dolby Thursday, September 12, 2013 4:17 AM

I am now experiencing this identical problem - Did anyone in this thread ever find a solution?

Hi Guys,

I am now experiencing a simular problem with a customer of ours.

Have tried the following things:

Rebuild and move mailboxes to new 2010 CAS/HT/MBX server

Create new Exchange 2013 servers.

I'm still receiving the same generic 'Something went wrong' error on OWA.

Did anybody manage to fix this issue?

Cheers,

Jack

owa and ECP virtual directories (external) for all CAS servers should point to 2013 CAS server.

Then proxy should be correct.

if still doesnt work,please run the following command (run as admin) in CMD on CAS servers:

%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe i

Then

Iisreset

We have facedthe sameerror
Aftermany attempts, we foundthat the problem liesin the

server certificate & OWA authentication problem

• Proposed as answer by mhmoud Tuesday, December 09, 2014 7:22 AM

My solution to this problem was that under 2010 exchange > IIS/owa > authentication > Windows Authentication > Providers > was blank. 

I added 1. NTLM 2. Negotiate and now it proxies from 2013 to 2010! 

• Proposed as answer by Artem R Tuesday, May 05, 2015 9:04 AM

My solution to this problem was that under 2010 exchange > IIS/owa > authentication > Windows Authentication > Providers > was blank. 

I added 1. NTLM 2. Negotiate and now it proxies from 2013 to 2010! 

Great thanks to Geislinn.

I have 4 CAS 2010 servers, one of which was missing NTLM or Negotiate in the Windows Auth's Providers field.  This caused some E2010 users not being able to access their mailboxes via CAS 2013 URL

After adding these two, my CAS 2013 servers working beautifully when accessing E2010 mailboxes.

Geislinn's reply should definitely be marked as one of the solutions.