I just got it working. Had to take the host name off the setting where it says site to publish.
We aren't using outlook anywhere or RPC over HTTP. Thanks anyway and now I can go home and have a good weekend. Glen. From: Jeremy Phillips [mailto:jeremy.phill...@azaleos.com] Sent: Friday, March 20, 2009 4:20 PM To: MS-Exchange Admin Issues Subject: RE: OWA and ISA I vaguely remember something about wildcard certs not working properly with Outlook Anywhere/RPC over HTTP. Thanks, Jeremy Phillips From: Glen Johnson [mailto:gjohn...@vhcc.edu] Sent: Friday, March 20, 2009 1:12 PM To: MS-Exchange Admin Issues Subject: OWA and ISA Any suggestions greatly appreciated. We have ISA 2006 in front of Exchange 2003 OWA. Split DNS but same internal and external names. On the exchange box, our free StartCom certificate expired today. We have purchased a DigiCert wildcard cert last year for some other stuff and as the StartCom is not trusted by many browsers. I've had the DigiCert cert on the ISA server for a long time and outside users were working fine. Internal users hitting the OWA directly worked but they got the certificate not trusted warning. Today, I've tried using the new wildcard certificate on the Exchange server. Now internal users are working normally, no prompt about the certificate not being trusted. Life is good, except. Outside users can't log in. The get an error about target principle name incorrect. OWA works fine on the isa server, doesn't complain about the cert and it is using the exchange cert. I've googled and played with the host header settings but nothing seems to make a difference. Thanks. Glen. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
