Link to home
Avatar of wedelenbos
wedelenbos

asked on

OWA Problems

Dear All,

I have a problem with OWA.
We have 2 Exchange 2003 servers. One of them is just created and made it the front-end server.
On the other server, how is working for a while, i didn't do anything to make is an back-end server, so the first question is: How to create a back-end server?

For the creation of the front-end server i used this document: http://www.msexchange.org/tutorials/OWA_Exchange_Server_2003.html

I also created an certificate for publishing the mail server with ISA 2004.
I used several pages from www.isaserver.org. For al the folders (exchange, exchweb and public) i used basic authentication (as discribed in the articles)

When i go to the internal url (https://servername/exchange) i got the certificate warning and click yes to accept it and then i get the well-known 440 Login Timeout error. The seccond question is: How do i resolve this?

When i go to the external url (webmail.companyname.nl) i got the certificate warning and click yes to accept it and then i get Error Code: 500 Internal Server Error. The target principal name is incorrect. (-2146893022). The third questoin is, how do i resolve this matter.

I hope someone can help me with this.
Avatar of amaheshwari
amaheshwari
Flag of India image





1.)If you have enabled some server as Front end server then that server will recognise other servers as Back end servers.

2.)https://www.experts-exchange.com/questions/21024572/440-Security-Error-when-trying-to-access-OWA-on-Exchange2K3.html

3.)http://support.microsoft.com/?id=829167
Avatar of LeeDerbyshire
On the server that you have now made a BE server:

In Exchange System Manager:
- Make sure that Forms-based Authentication is not enabled on the Exchange Virtual Server.
- Make sure that the Exchange Virtual Directory still has both Basic and Integrated Auth enabled.

In IIS Manager:
- Make sure that SSL is not required on the Exchange Virtual Directory.
Avatar of wedelenbos
wedelenbos

ASKER

We are almost there....

When i go to the internal url (https://servername/exchange) i got the certificate warning and click yes to accept it and then i get the login screen. But when i log in, i'll get a very crappy window with parts of my mailbox in it.  When i click on it (inbox or something, i get an errer that the server isn't available.

When i go to the external url (webmail.companyname.nl) i got the certificate warning and click yes to accept it and then i still get Error Code: 500 Internal Server Error. The target principal name is incorrect. (-2146893022).
I published the mailserver with ISA 2004 and imported the certificate from my own CA. (My ISA server isn't on the domain. It is an stand alone)
I'm not sure about the cert error - I think that might come from ISA.  Is the FE server at the same or higher service pack level as the BEs?  It can't be lower.  If it was ever at a lower SP level when you tried to access OWA in it, then even if you updated it since, you will need to empty your browser's cache.
It was on a lower level, but i brought it to Exchange 2003 SP2.
But still crappy window....Maybe i have to reset all web folder of exchange and do it all again....?
I've solved the problem with internal error 500.
I have changed the To (from the publish rule in ISA 2004) in webmail.comanyname.nl and made an entry in the hosts file. I also said by the authentication it should use the form.. And every user has to authenticate.
Now i got the loginscreen when i go to webmail.companyname.nl, but when i want to log in (i use domain\username and my password) i get an error:  
You could not be logged on to Outlook Web Access. Make sure your domain\user name and password are correct, and then try again.
I'm for sure it is correct. Maybe some more little problems in ISA 2004 configuration of the publishing rule?
ASKER CERTIFIED SOLUTION
Avatar of LeeDerbyshire
LeeDerbyshire
Flag of United Kingdom of Great Britain and Northern Ireland image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
LeeDerbyshire, you are right. I updated the front-end server and internal everything works fine...
Now i have to get it working for the internet...I disabled form based login on the FE server. Delete the old rules and created a new one... and now everything works very fine.....
Your the best LeeDerbyshire....!!!!!