Greenbeast Posted November 13, 2012 Author Posted November 13, 2012 yeah i'm internal, it presents me with a OWA2003 login page (actually i guess it might be a ISA2006 page) which i then put in my credentials and get through to OWA2003
sukh Posted November 13, 2012 Posted November 13, 2012 If there's ISA in the play here then yes, that would depend how it's been setup internally.
Greenbeast Posted November 13, 2012 Author Posted November 13, 2012 currently any internal or external web requests to https://webmail.externaldomainname/exchange are forwarded to our OWA2003 box i think i need to undo the redirect from 2010 to 2003 for now to make sure OWA 2010 will function, at the moment i'm not even seeing it. I just can't figure out how to do that yet.....
Greenbeast Posted November 13, 2012 Author Posted November 13, 2012 ok i had the OWA2010 external URL set to webmail.externaldomainname and it must have been going straight to 2003 regardless of the /owa host header. anyway, that's now changed and i'm able to log in to the test mailbox i moved to EXC2010 using OWA2010
sukh Posted November 13, 2012 Posted November 13, 2012 Only internally though right, as you haven't exposed the 2010 namespace externally or moved it and used a legacyURL.
Greenbeast Posted November 13, 2012 Author Posted November 13, 2012 i guess the next task is to test ISA forwarding to OWA2010 instead I've changed the ISA rule properties to look at my 2010 server instead of 2003 server but the traffic still heading straight to OWA2003
Greenbeast Posted November 13, 2012 Author Posted November 13, 2012 Only internally though right, as you haven't exposed the 2010 namespace externally or moved it and used a legacyURL. yes if i type https://exchange2010servername.domain.internal/owa i get OWA2010 and can log into the one mailbox just tested a 2003 mailbox and it pushed my over to OWA2003
Greenbeast Posted November 14, 2012 Author Posted November 14, 2012 ok i found this guide: ISA 2006 SP1 Configuration with Exchange 2010 - Exchange Team Blog - Site Home - TechNet Blogs Followed the procedure but when i switch the rules over i lose connectivity to OWA, i get a 403 error for both /owa and /exchange
sukh Posted November 14, 2012 Posted November 14, 2012 Some sort of authentication isn't setup correctly. What exactly has changed? Where does ISA point to now 2010 or 2003? If 2010, look at the IIS Logs and post relevant section so I can see. Check logs on ISA too. Run ExchRCA and lets see if that gives anymore info.
Greenbeast Posted November 14, 2012 Author Posted November 14, 2012 ok attempting to simplify and make testing easier i've made two new publishing rules that are identical to the existing ones apart from they point to the new E2010 servername. when i switch the rules i get 'IE cannot display the page' (if i browse directly to the internal server name it gives me OWA2010 correctly)
sukh Posted November 14, 2012 Posted November 14, 2012 Do you get this error internally joined client or externally? If internal, can you flushdns and test again, restart IE and test again?
Greenbeast Posted November 15, 2012 Author Posted November 15, 2012 (edited) Internally, i'll keep it simple and deal with just internal stuff for now. So just tested, switched the rule from OWA2003 to OWA2010, did flushdns and opened new IE window and i get 'page cannot be displayed' Edited November 15, 2012 by Greenbeast
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now