Owa 2007 with 2003 cohabitation

After 7 hour of test i finally get it, it almost works ... ;)
I m transitoining from Exch 2003 to Exch 2007.
i redirect 443 request on CAS only server (just for exprox feature)

on my CAS server
/owa : OK for 2007 user NOK for 2003 everything ok :)
/exchange OK for 2003 user NOK for 2007 user !!! i get an this site require https (but i m already using https to go in !)

anyone can help me ?
i just want to have my 2007 user using /exchange directory and be redirect on /owa.

tkx in advance
kilz3mAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LeeDerbyshireCommented:
Can you post the IIS log file entries generated by the attempt to log onto /exchange ?
0
kilz3mAuthor Commented:
external user try to log on https://mail.x.com/Exchange
Exchange 2007 user get an 403 error

IIS log on CAS server
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2009-07-14 14:13:32 W3SVC1 192.168.0.228 GET /Exchange - 443 - 192.168.69.254 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 401 2 2148074254
2009-07-14 14:13:33 W3SVC1 192.168.0.228 GET /owa/auth/logon.aspx url=https://mail.pointex.com/Exchange&reason=0&replaceCurrent=1 443 - 192.168.69.254 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0
2009-07-14 14:13:44 W3SVC1 192.168.0.228 POST /owa/auth/owaauth.dll - 443 - 192.168.69.254 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 302 0 0
2009-07-14 14:13:44 W3SVC1 192.168.0.228 GET /Exchange - 443 ptxgestion\ptxgestion 192.168.69.254 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 403 0 0

On 2003 Mailbox server
Nothing related to this

On 2007 Mailbox server (also have CAS role)
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2009-07-14 14:13:44 W3SVC1 192.168.0.226 GET /Exchange - 80 - 192.168.0.228 Exchange-Server-Frontend-Proxy/6.5+Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 403 4 5

thank you for your reply.
0
LeeDerbyshireCommented:
The 403;4 status on the MBX server indicates that the proxied request is failing because SSL is required on the Exchange VDir.  If E2007 is anything like E2003 in this respect (and I've no reason to believe that they rewrote WebDAV for E2007, since they intend to drop it soon), then you will not be able to require SSL on the MBX Exchange VDir when CAS/FE servers are proxying OWA requests into it.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

kilz3mAuthor Commented:
yes this is what i read here :
http://msexchangeteam.com/archive/2007/09/04/446918.aspx
http://technet.microsoft.com/en-us/library/bb310763.aspx
http://msexchangeteam.com/archive/2007/02/07/434523.aspx

and according to this post :
https://secure.experts-exchange.com/index.jsp?srid=Xj82DAh4/F8s32L28nMg3g%3D%3D&redirectURL=/Software/Server_Software/Email_Servers/Exchange/Q_22645871.html&rsid=130&pid=3373168#a19365178

i removed :
1) ssl certificate
2) forced ssl requirement on exchange 2003 mailbox server

3) changed auth metode on
Exchange and ActiveSync VDir (with integrated methode)

is it possible to use only /exchange ? for 2007 and 2003 user ?
0
LeeDerbyshireCommented:
When an E2007 user goes to /exchange, the server will redirect them to /owa.  When an E2003 user goes to /exchange, it will behave as before.  So, it's best to ask E2007 users to go directly to /owa, since it will remove a possible point of failure, i.e. the redirection.
0
kilz3mAuthor Commented:
well yes i agree with the fact that Exchange 2007 user with /owa is the best choice :)
but i wanted to leave like it s now, with auto redirection to /exchange VDir when all my users go to https://mail.x.com (i implemented this on CAS server and removed it from Exch 2003 FE)
no one has to think "is the /echange or /owa vdir ... ?"

from msechangeteam blog
"Because there are multiple servers and virtual directories involved in these coexistence scenarios, it can be difficult to understand which virtual directories users should access. Users should access virtual directories as follows:
Users who have mailboxes on Exchange 2007 computers should access /owa or /exchange on the Client Access server.
/owa will take the user directly to Outlook Web Access.
/exchange will use DAV to redirect the user to /owa."

i know that with /owa it works but they said that this have to work with /exchange vdir for both Exch 2003 and 2007 users :/
i want to understand why i get an 403 error.
with IIS log i don t have enough informations, how can i trace this ?

0
LeeDerbyshireCommented:
Well, this is my guess.  From your IIS log entries, you can see a logon on your CAS server:

2009-07-14 14:13:44 W3SVC1 192.168.0.228 GET /Exchange - 443 ptxgestion\ptxgestion 192.168.69.254 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 403 0 0

which results in this proxied request on the MBX server:

2009-07-14 14:13:44 W3SVC1 192.168.0.226 GET /Exchange - 80 - 192.168.0.228 Exchange-Server-Frontend-Proxy/6.5+Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 403 4 5

The proxied request can only take place on port 80, but it appears to get a 403;4 response (i.e. SSL Required) response.  So, can you check your E2007 MBX server, and see if it has SSL required on the Exchange VDir?  The IIS log says that it has, but it should not have.  If you have already unchecked the SSL checkbox, and it still doesn't work, then you will have to post the new IIS log file entries.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kilz3mAuthor Commented:
YESSSSSSSSSSSSSSSSSS on my MBX 07 server i forgot that i enabled SSL on Default Web Site !!!
big tkx :))))
now everything is ok (i just have to test that activesync and rpc also work :p)

once again thank you very much for your help
0
kilz3mAuthor Commented:
exactly
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.