Publishing Multiple Web Sites:
When I get to adding the second site (www) I do not have the "Create a new certificate" selection. I would have to remove the current certifacte (owa) before I can create a new one. Is this correct or have I done something out of order.
The second site, which listens for "www.domain.com", is on a *different* Web server, not the same one as the OWA site. Check out the sample lab config to see that there are two Web servers in use. You can accomplish a similar thing with one Web server if you've created two virtual Web servers.
Hi Tom. I gues this would also work when you only have to publish the OWA-site?
For me it didn't. I followed all steps in your article except those for the second website. When I try to access my OWA-site I get the error mesage: 403 - Forbidden. The server denies the specified URL.
I've taken a closer look at what happens. I've monitored and logged my requests for my OWA-site and saw that every request I made was denied by the default firewall rule, wich denies all traffic. This means that the firewall policy skips the firewall rule created by the web publishing wizard.
When I took a closer look at the firewall rule for the OWA publishing, I saw that the protocols allowed are HTTP and HTTPS, not 'HTTPS Server'. Could this be the problem?
I have the following question about publishing the owa site on a different name than the internal domain name. I followed the totural with the different name than the domain. From the internet everyting is working oke. But from the inside (firewall clients) I get an error:
<TD width= The page cannot be displayed
I added the different name to my dns server as a lookup zone and added the exchange server to it. Now it only works when I turn of the firewall client.
Just a warning regarding Wildcard certificates... the successful validation (client-side) of SSL certificates is application dependant.
For example, using your PocketPC to browse a web site protected by a wildcard SSL certificate works fine..... however, if you publish Server ActiveSync using a wildcard SSL certificate, the client-side ActiveSync application will refuse to validate the server's certificate (unless certificate validation is disabled).
This has been confirmed as expected behaviour by Microsoft PSS.
So just beware, and double-check any non-browser apps before you shell out!
RE: Discussion of using a Wildcard Certificate in ISA20... - 23.Apr.2004 2:03:00 AM
I have having the same problem as gatorz posted. Any ideas?
>gatorz >posted February 28, 2004 03:20 AM >-------------------------------- > When i go to select the cert in the new Web listener, it tells me there are no certificates configured on this server i have verified that the certificate is installed per the article