Comments on: Publish OWA on ISA server 2006 enterprise edition problem

By: Troy Tate

Troy Tate — Thu, 05 Nov 2009 12:38:20 +0000

Thanks for sharing the fix.

By: eliyevelxan

eliyevelxan — Thu, 05 Nov 2009 09:48:20 +0000

I resolved this problem. i added mail.mydomain.com to DNS server as my exchange server. Then i change rule on isaserver domain.mydomain.com (My web server name ) to mail.embawood.com. After this the problem resolved

By: Troy Tate

Troy Tate — Wed, 04 Nov 2009 17:48:05 +0000

Please review the blog posting about certificates above. You will need a subject alternative name (SAN) certificate that can hold multiple host names in the subject. That type of certificate will have the external name as well as the internal server name.

By: eliyevelxan

eliyevelxan — Wed, 04 Nov 2009 12:54:09 +0000

on Isa server it gives me error

Description: ISA Server could not establish an SSL connection with the published server domain.embawood.dm on port 443 because the name on the SSL server certificate used by the published server does not match the internal name of the Web server mail.embawood.com, as specified in the publishing rule.
Verify that the internal name specified in the publishing rule is correct. If the problem persists contact the Web server administrator

By: eliyevelxan

eliyevelxan — Wed, 04 Nov 2009 12:42:41 +0000

The page cannot be displayed
Explanation: There is a problem with the page you are trying to reach and it cannot be displayed.

——————————————————————————–

Try the following:

Refresh page: Search for the page again by clicking the Refresh button. The timeout may have occurred due to Internet congestion.
Check spelling: Check that you typed the Web page address correctly. The address may have been mistyped.
Access from a link: If there is a link to the page you are looking for, try accessing the page from that link.

——————————————————————————–

Technical Information (for support personnel)

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

By: eliyevelxan

eliyevelxan — Wed, 04 Nov 2009 12:36:20 +0000

I resolved certficate name problem. But

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

error problem not resolved. Please help me.

By: eliyevelxan

eliyevelxan — Wed, 04 Nov 2009 08:43:58 +0000

I published OWA on ISAserver 2006. I tried open mail.mydomain.com/exchange i get office OWA outlook web access. Then i wrote mydomainusername and parol. When i entered site i get this error:

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

What may be problem?

My certficate name is “domain”. It is not the same name of my web server (OWA server).
Is it necessary the same being of the site name and certficate name?
Please help me

By: Troy Tate

Troy Tate — Mon, 02 Nov 2009 15:45:54 +0000

It is not necessary to install the certificate on the client. You can use the same certificate on the ISA server that you use on the OWA server. An issue though will arise if/when users access the ISA/OWA server through a client that does not "trust" the certificate if it is a self-signed certificate. Check out this blog article for more details on OWA certificates.

By: eliyevelxan

eliyevelxan — Tue, 27 Oct 2009 08:01:29 +0000

Is certficate necessary for publishing OWA server on ISAserver? If necessary If i install certficate on OWA server when clients opens OWA from Web will it request certficate to install on client computer?