<div>
Does it work internally i.e you only have this when you access owa remotely?
</div>


<div>
I only see red x's in boxes where all of the buttons should be. <br />
==&gt; do you see this issue for all the E2k3 mailboxes via E2k7 CAS URL?<br />
<br />
Can you try accessing the same OWA from another computer\browser...still same issue?<br />
<br />
How is the OWA Experience for the E2k7 users? Is that good?<br />
<br />
<br />

</div>


<div>
It is the same both internally and externally.<br />
<br />
I do see this issue for all E2k3 mailboxes via E2k7 CAS URL. &nbsp;For the E2k7 users everything works perfectly. &nbsp;
</div>


<div>
Can you please check @ the IIS logs on the CAS server<br />
<br />
By any-chance do we see any errors other than the 200? (at the end of the each-n-every lines)<br />
<br />
Note:<br />
Concentrate @ the image file access on the CAS servers<br />
<br />
<br />
Reference:<br />
=======<br />
The HTTP status codes in IIS 7.0 and IIS 7.5<br />
<a href="http://support.microsoft.com/kb/943891" rel="ugc">http://support.microsoft.com/kb/943891</a>
</div>


<div>
Ok. &nbsp;I looked in the logs and when I try to log into a user account that is still on the 2003 mailbox using the url: https://exchange07.domain.com/exchange&nbsp;I get a status code of 403 with a substatus of 0. &nbsp;All other access methods have a status code of 200.
</div>


<div>
Ok, so when you access e2k3 directly, are you using the http or https?<br />
&gt;&nbsp;If you are having the E2k3, IIS to have just http...then the CAS might be trying to access the E2k3 MBX using https..which could be the issue<br />
<br />
&gt;&nbsp;Check if you are having the correct\valid cert. @ the E2k3 IIS<br />
<br />
Note:<br />
403 is just a forbidden<br />
any clue for the sub-status in other locations<br />
<br />
<br />

</div>


<div>
The next field in the log which is supposed to be substatus is 0. &nbsp;We have both the 2003 and 2007 set to require SSL, however, I was starting to think it may be something with the relay that it does not ssl. &nbsp;The cert on the both 2003 and 2007 are valid and work fine if you hit the boxes directly.
</div>


<div>
Just being curious I looked in the logs on the 2003 box. &nbsp;The entries when I try to access an account on that server are 403.4 which are SSL Required. &nbsp;So apparently the proxy process between 2007 and 2003 is not using SSL yet until we take the 2003 box off the public access we have to have this enabled. <br />
<br />
I am trying to find an article that i read indicating the /exchange and /Microsoft-Activesync-Serv<wbr />er directories on the 2003 box must have integrated windows authentication enabled. &nbsp;I have done that but nothing has changed. &nbsp;Not sure if I need to restart any services for this change to take full affect of not.
</div>


<div>
Normally for the HTTP communication, we dont have any relay which stops\removes the SSL.<br />
<br />
What is the application which is relaying the HTTP traffic between the E2k7 and E2k3 servers<br />
<br />
Work-around:<br />
Try by=passing that device to get the correct behaviour.
</div>


<div>
The exchange 2007 server is relaying the traffic between itself and the E2k3 server. &nbsp;This is a function of the CAS server. &nbsp;I do not have anything that I can bypass. &nbsp;
</div>


<div>
<a href="http://blogs.technet.com/b/exchange/archive/2007/02/07/3399727.aspx" rel="ugc">http://blogs.technet.com/b/exchange/archive/2007/02/07/3399727.aspx</a><br />
<br />
Do you want to refer the above URL<br />
(which example closely resembles your setup?)
</div>


<div>
On that URL example #3 is the one closest to my setup.
</div>


<div>
getting out of the crux.<br />
<a href="https://cas-server/public" rel="ugc">https://cas-server/public</a>&nbsp;--&gt; is that working fine?<br />
<br />
Want to check the settings @ the MBX server?<br />
<a href="http://blogs.technet.com/b/exchange/archive/2008/02/01/3404755.aspx" rel="ugc">http://blogs.technet.com/b/exchange/archive/2008/02/01/3404755.aspx</a><br />
<br />
Check @ the settings on the MBX servers too
</div>


<div>
Tried every suggestion that was made to no help. &nbsp;This solution fixed the problem for me.
</div>


<div>
<div class="content wysiwyg-content">
I have setup a new exchange 2007 environment along side a 2003 server as follows:<br />
<br />
1 2003 server in place already<br />
<br />
Added 2 new CAS/HT servers running server 2008 RS and Exchange server 2007 sp3 rollup 5.<br />
2 mailbox servers in a CCR setup running the same version of Exchange 2007.<br />
<br />
I have migrated my account from 2003 to 2007 for testing and everything works perfect. &nbsp;If I want to access my account using outlook, phone or owa it works fine. However, the problem is access for users still on the 2003 server. &nbsp;If I browse to https://ex2007.domain.com/exchange&nbsp;I log in with one of those accounts and then I only see red x's in boxes where all of the buttons should be. &nbsp;The message list does not display. &nbsp;I have removed the CAS role and IIS from both servers rebooted and then installed IIS and CAS again. &nbsp;I have deleted and recreated the virtual directories. &nbsp;If I connect directly to the 2003 server owa site those users work fine. &nbsp;Any help is greatly appreciated.
</div>
</div>


I have setup a new exchange 2007 environment along side a 2003 server as follows:

1 2003 server in place already

Added 2 new CAS/HT servers running server 2008 RS and Exchange server 2007 sp3 rollup 5.
2 mailbox servers in a CCR setup running the same version of Exchange 2007.

I have migrated my account from 2003 to 2007 for testing and everything works perfect.  If I want to access my account using outlook, phone or owa it works fine. However, the problem is access for users still on the 2003 server.  If I browse to https://ex2007.domain.com/exchange I log in with one of those accounts and then I only see red x's in boxes where all of the buttons should be.  The message list does not display.  I have removed the CAS role and IIS from both servers rebooted and then installed IIS and CAS again.  I have deleted and recreated the virtual directories.  If I connect directly to the 2003 server owa site those users work fine.  Any help is greatly appreciated.

Exchange 2007 to 2003 owa

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.