why is inetinfo.exe listening on port 443 when I have no https site?

[b***@peacefire.org]

I have IIS running and listening on port 80. I want to run another Web
server at the same time that listens for http requests on port 8080 and
https requests on port 443. The trouble is that the inetinfo.exe
process is also listening on port 443 (preventing the other Web server
from starting), and I don't know why because I don't have any HTTPS
sites set up in IIS.

My nodes in "Internet Information Services" are:
BENNETTS_3_2002
-Web Sites
-Default Web Site
-Default SMTP Virtual Server

The properties of "Default Web Site" shows that it's listening on port
80, and the properties of "Default SMTP Virtual Server" show that it's
listening on port 25. That explains why "netstat -a -n -o" shows the
inetinfo.exe process listening on ports 80 and 25, but why would it be
listening on port 443 as well?

If I try browsing it as an actual site, https://127.0.0.1/, I just get
"page cannot be displayed", although if I telnet from another box to
port 443 on my local box, it does accept the connection -- so
apparently IIS is hogging the port but not using it for any actual Web
site.

-Bennett

[Kristofer Gafvert]

Hello,

Right click the Website(s) in IIS Manager, and click Properties. Make sure
that the "SSL Port" field is empty.

You might also want to look at this KB Article:

"Page Cannot Be Displayed When You Connect Through SSL"
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q260096
--
Regards,
Kristofer Gafvert
http://www.ilopia.com

Post by b***@peacefire.org
I have IIS running and listening on port 80. I want to run another Web
server at the same time that listens for http requests on port 8080 and
https requests on port 443. The trouble is that the inetinfo.exe
process is also listening on port 443 (preventing the other Web server
from starting), and I don't know why because I don't have any HTTPS
sites set up in IIS.
BENNETTS_3_2002
-Web Sites
-Default Web Site
-Default SMTP Virtual Server
The properties of "Default Web Site" shows that it's listening on port
80, and the properties of "Default SMTP Virtual Server" show that it's
listening on port 25. That explains why "netstat -a -n -o" shows the
inetinfo.exe process listening on ports 80 and 25, but why would it be
listening on port 443 as well?
If I try browsing it as an actual site, https://127.0.0.1/, I just get
"page cannot be displayed", although if I telnet from another box to
port 443 on my local box, it does accept the connection -- so
apparently IIS is hogging the port but not using it for any actual Web
site.
-Bennett

[b***@peacefire.org]

I tried following the advice at
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q260096

However when following these steps:

1. Open the Security properties for the default Web site, and then
select Server Certificate.
2. In the wizard, click Assign an existing certificate, and then select
a certificate from the list.

I got stuck on the second step, because when I pick "Assign an existing
certificate", there are no certificates in the list to choose from.

What's the easiest way to get a certificate to show up in that list?
(I only need it very briefly, for the purpose of adding it and then
removing it again, to make IIS stop listening on port 443.)