Re: Switching from http to https
- From: Kansas <Kansas@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 19 Oct 2006 05:16:02 -0700
Our original site linked to a program's html file. You would connect as
http:<ip address>/program. The instructions had us install certificates on
the default website with SSL not enabled (using port 443) in the IIS. SSL
would be enabled in IIS on the program's web site changing the program's
address to https://program.smith.com/program. We were then instructed to add
a certificate to the program. These errors we received when trying to
troubleshoot:
connecting to http://<ip address>/program resulted in having to add an 's'
after the http. When attempting to access the site with https://<ip
address>/program we got a message that the address does not match the
certificate. When attempting to access the site by
https://program.smith.com/program we got the "cannot find server or DNS
error" It turns out port 444 was closed and subsequently opened but still no
success in getting to the site. The instructions had us obtain a certificate
for IIS using the new address (program.smith.com). The certificate for the
program was for the actual server domain name. Could it be that the
certificate names have to match? The instructions also had us check the
Require SSL and Ignore Client Certifictes under the program in IIS. When I
tried changing it in IIS to Ignore, I would get a message that this would
prevent everyone from accessing.
"Bernard Cheah [MVP]" wrote:
No. should be similiar for IIS 5 and 6..
I still don't get what's the error statement, you cert can't bind to port
444 ?
have you change the binding port ? restart https service?
do a netstat -an to check the status ? why not use 443 ? or ?
--
Regards,
Bernard Cheah
http://www.iis.net/
http://www.iis-resources.com/
http://msmvps.com/blogs/bernard/
"Kansas" <Kansas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EC984F85-4178-498D-85A6-980B2101D7CC@xxxxxxxxxxxxxxxx
Just an update. I'm new to this and the certicicates and IIS were set up
with version 5 instructions. It turns out port 444 was not open, so they
opened it up. I reinstalled the RSA certificate, restarted the server and
still was not able to connect. Same error message as before. We ended up
removing the certicates and went back to the original website. Is there
much
of a difference installing certificates between IIS 5 and 6? Thanks
"Kansas" wrote:
We just upgraded to Server 2003 and we run a program that now requires
https.
The certificate was installed to change the site along with the
certificate
to access the server. When trying to connect to the https site, I get a
page
cannot be displayed, cannot connect to server or DNS error. If I try the
old
way, I get the certificate does not match the web address. When the
program
starts that runs the program, it shows it's listening on the secure port
(444) and when I run the netstat -an command I didn't see any problems.
Port
443 is being used by IIS. I can also connect to other SSL sites from the
server. Any idea what could be causing this? I've checked some of the
other
postings and noticed that it might be a certificate problem which we're
in
the process of doing. Thanks
- Follow-Ups:
- Re: Switching from http to https
- From: Funkadyleik Spynwhanker
- Re: Switching from http to https
- References:
- Re: Switching from http to https
- From: Bernard Cheah [MVP]
- Re: Switching from http to https
- Prev by Date: Re: Using a Domain ID for Anonymous User Account
- Next by Date: Webservice to an Out of process server
- Previous by thread: Re: Switching from http to https
- Next by thread: Re: Switching from http to https
- Index(es):
Relevant Pages
|
