 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Applications / September 2006Rehoming OWA to different Exchange 2003
I currently have a FE exchange server running IIS for OWA, pointing to our back end exchange server. It works flawlessly. I have built an exchange cluster, that I want to move users to, but when I put my test user in it, outlook works fine. Mail is sent and received. But I cannot connect to it via OWA. Is there a pointer in OWA I am not aware of? Thank you for your help, Ron Actual problem is between the basic and premium services. > I currently have a FE exchange server running IIS for OWA, pointing to our > back end exchange server. It works flawlessly. I have built an exchange [quoted text clipped - 4 lines] > Thank you for your help, > Ron what does that mean? basic works to the new server and premium doesn't? > Actual problem is between the basic and premium services. > [quoted text clipped - 8 lines] >> Thank you for your help, >> Ron If you connect using owa basic client i can atache and read mail folders etc... But if you select Premium Client it starts to load and then lock up nothing works. I don't think it is the front end, because it works going to the original Exch server, but not to the new exch server > what does that mean? basic works to the new server and premium doesn't? > [quoted text clipped - 10 lines] > >> Thank you for your help, > >> Ron what shows up in the HTTP logs on the new BE? Verify the authentication mechanisms are all set the same between the two BE servers. This seems to be authentication related more often than not. Is there a certificate involved? what else is different in the IIS config between the two BE servers? If you use OWA directly against the new BE does Premium work? > If you connect using owa basic client i can atache and read mail folders > etc... [quoted text clipped - 20 lines] >> >> Thank you for your help, >> >> Ron Your FE server should point to EVS. It seems you dont have DNS entry for your EVS. Registering your EVS namespace with your local DNS should solve your problem. Rakesh > I currently have a FE exchange server running IIS for OWA, pointing to our > back end exchange server. It works flawlessly. I have built an exchange [quoted text clipped - 4 lines] > Thank you for your help, > Ron I don't have it in DNS, i am tryin g to hit it directly first to verify that it works before putting an entry in DNS, that the customers will get. > Your FE server should point to EVS. It seems you dont have DNS entry > for your EVS. [quoted text clipped - 11 lines] > > Thank you for your help, > > Ron |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.