Re: HTTP Virtual Server Loses Settings

Well that was easy... I didn't think Exchange System Manager would allow me
to bind SSL ports to IP addresses (it was grayed out) since I already has SSL
on another IP addreess. Apparently, all I had to do was clear the "TCP 80"
out and sure enough the SSL port box was then available.

Thanks!
--
CSS


"Ed Crowley [MVP]" wrote:

Make the changes to the HTTP virtual server in Exchange System Manager.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Chris Smith" <inraindreams@xxxxxxxxxxx> wrote in message
news:1760EE22-2BD7-4AD3-9594-462CA819875A@xxxxxxxxxxxxxxxx
Sorry, I didn't make myself very clear. Below is an exampe config... and
it
works fine with ActiveSync (both virtual servers) and via a web browser
with
the SSL certificates for quite a while before the settings disappear. I've
replaced the domain names for obvious reasons.


Default Web Site:

PublicIPAddress1 Port 80 exchange.originaldomain.com
InternalIPAddress Port 80 exchange.originaldomain.com

PublicIPAddress1 SSL Port 443


Second Virtual Server:

PublicIPAddress2 Port 80 exchange.newdomain.com
InternalIPAddress Port 80 exchange.newdomain.com

PublicIPAddress2 SSL Port 443
InternalIPAddress SSL Port 443



Basically, it all works until all the settings in Second Virtual Server
just
disappear/reset back to the default.


Thanks.













--
CSS


"Lee Derbyshire [MVP]" wrote:

"Chris Smith" <inraindreams@xxxxxxxxxxx> wrote in message
news:2B7BE476-26F0-4BA5-953D-BB8620B2DEC9@xxxxxxxxxxxxxxxx
I have a second virtual server setup via System Manager. I then
went in
through IIS Admin tool and did more advanced configuration such as
adding SSL
to a specific IP address, host header for a different IP address,
etc. so
that I can have two "http virtual servers" that use two different
SSL
certificates (we are in the process of migrating domains and we use
Treo
700wx's).

It works great for several hours... but then, for some reason, all
the SSL,
host header configuration, etc. for the second HTTP virtual server
disappear
and it stops listening on 443 at the specified IP address. It almost
seems
like it is being reset back to the default at random intervals by
Exchange
management.

Any ideas?

Thanks,

Chris


--
CSS

You mentioned host headers, but host headers don't work with SSL
(because the request is still encrypted at the stage that IIS is
trying to work out which site to send it to). Your Default Web Site
and the extra site must have different IP addresses and/or different
port numbers. It sounds like you are using port 443 for both, so your
Default Web Site can no longer use the 'All Unassigned' IP selection.
Pick one IP address for the DWS and another for the extra site.

Lee.

--
_______________________________________

Outlook Web Access For PDA , OWA For WAP
www.owapda.com
email a@t leederbyshire d.0.t c.0.m
_______________________________________






.

Relevant Pages

  • Re: OWA logon screen
    ... did you produce a SSL Request from Default Web Site / Exchange Web Site (in ... I just have to get SSL working now. ... Exchange admin. ... I have a certificate enabled within the server and i can click ...
    (microsoft.public.exchange.admin)
  • OWA - SSL exchange 2003
    ... I am trying to Setup OWA to use SSL, I am using the following from 2003 ... Exchange Server deployment guide chapter 8. ... identities for this Web site, verify that the Web site IP address is ... After you obtain an SSL certificate to use either with your Exchange ...
    (microsoft.public.exchange.setup)
  • Re: Exch 2K3 OWA port 80 conflict with SUS
    ... MVP - Exchange ... How do I examine the IIS metabase and validate that port 80 is used by ... FE - Default Web Site ... FE - Default Web Site - Anonomouse Auth and Integrated - Require SSL ...
    (microsoft.public.exchange.setup)
  • Re: OWA will not work with SSL
    ... Bob Walker posted their thoughts, ... The entire default web site is set to use port 442 ... > this includes Exchange. ... port 442 and not 443 for SSL, unless that was just a typo? ...
    (microsoft.public.exchange2000.general)
  • Re: OWA will not work with SSL
    ... Bob Walker posted their thoughts, ... The entire default web site is set to use port 442 ... > this includes Exchange. ... port 442 and not 443 for SSL, unless that was just a typo? ...
    (microsoft.public.exchange2000.admin)