Re: can't connect to SSL site
From: Jerry III (jerryiii_at_hotmail.com)
Date: 02/27/04
- Next message: Fast Eddie: "Re: Schannel error on W2K server -- HELP --"
- Previous message: Mike: "OWA\IIS - User Must Change Password"
- In reply to: Jeff Cochran: "Re: can't connect to SSL site"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 27 Feb 2004 13:33:19 -0800
Not true. Two SSL sites can share the same IP, as long as they are on
different ports. The problem here is that John needs to setup the second's
web site port to something else than the default 443. HTTP and HTTPS cannot
listen on the same port, so don't expect HTTPS to work on 81 if you setup
regular HTTP listener on port 81.
Jerry
"Jeff Cochran" <jcochran.nospam@naplesgov.com> wrote in message
news:4042ad59.1383164695@msnews.microsoft.com...
> On Fri, 27 Feb 2004 11:58:00 -0800, "John Smith"
> <anonymous@discussions.microsoft.com> wrote:
>
> >I have a web server with a default web site that works
> >fine. I added a new site, same IP and different port (81).
> >The second site works fine (http://domainname:81/directory)
> >until I try to install SSL on the second site. I set up a
> >certificate server, requested a server certificate on the
> >second web site, installed it and when I "view
> >certificate" everything's ok.
> >
> >As soon as I check "Require secure channel (SSL)", clients
> >can't access the site from their browser.
> >Am I missing something?
>
> SSL needs a separate IP and not a different port.
>
> Jeff
- Next message: Fast Eddie: "Re: Schannel error on W2K server -- HELP --"
- Previous message: Mike: "OWA\IIS - User Must Change Password"
- In reply to: Jeff Cochran: "Re: can't connect to SSL site"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|