Publish OWA

[mcbs25]

Hi

I am having some problems to publish OWA 2003 with ISA 2004. I created a certificate on Exchange 2003 and import to ISA server. I did all of this like Microsoft suggests on its page.

I published the mail server normally, the first page appears without any problems, but when i type the username and password it doesn´t appear the screen to ask for username and password again.

On the browser appears the following message:

https://public.ip/CookieAuth.dll?GetLogonWrapper?url=/exchange&reason=0

Technical Information (for support personnel)

Error Code: 500 Internal Server Error. The target principal name is incorrect. (-2146893022)


I need help!! Please!!

Thanks!!

 

[mcbs25]

On my internal network it works perfectly!!

 

[dput]

Are you entering the user name as either domain\username or username@domain? I found that we had to start doing that after going up on OWA 2003.

Dan

 

[mcbs25]

I am using domain\username but the error persists.

 

[coco10]

try using basic auth. for the OWA

and check this as a guide!

http://www.isaserver.org/articles/2004pubowartm.html

hope its helps
coco10

 

[mcbs25]

When i try to access the https page the following screen appears before show the first page:



the security certificate date is valid

the name on the security certificate is invalid or does not match the name of the site

Do you want to proceed?

I choose YES and appears the page when i logon.


OBS.: coco10 i tried to use your document but i didn´t work

 

[coco10]

check in the auth settings and put in basic only for test.


coco10

 

[NickFerrar]

When you imported the certifcate did you include the full certifcate chain option? Also did you use the fully qualified name when creating the certificate?

How many certs do you have? You need a 3rd party one on the FBA web listener and an internally-generated one for the SSL link between the ISA and FE exchange server (assuming you are using an SSL bridge).

 

[Knutern]

The target principal name is incorrect. (-2146893022)

I've seen this error with DNS. For example: you publish a internal OWA with the public name of mail.mydom.com and the rule passes the request onto you internal mail.mydom.com, for example.

There are at least two ways to solve this:
1. instead of using mail.mydom.com, use the servers internal ip
2. split your DNS: one for public and one for internal

Cheers
Knutern