IIS and SSL. Can someone help me?

[wannaBmsce]

Perhaps someone can help me with this.&nbsp;&nbsp;I am using IIS 4.0.&nbsp;&nbsp;I used Key Manager to request a demo (15-day, 40-bit) key from VeriSoft.&nbsp;&nbsp;My IIS server computer name is WEB (NetBIOS name) in the DOMAIN domain.&nbsp;&nbsp;I don't have a DNS server.&nbsp;&nbsp;I am using an LMHOSTS file with<br>192.168.0.4 <A HREF="

http://www.domain.com"

TARGET="_new">

http://www.domain.com</A>.<br><br>My

problem is that I just don't understand (duuuuh!)&nbsp;&nbsp;Before I required SSL authentication on the <A HREF="

http://www.domain.com"

TARGET="_new">

http://www.domain.com</A>

site, I was able to call up the site with no problems from Internet Explorer with the URL:&nbsp;&nbsp;<A HREF="

HTTP://www.domain.com.&nbsp"

TARGET="_new">

HTTP://www.domain.com.&nbsp</A>;&nbsp;After

I bind the certificate to the site (192.168.0.4 port 80), and I require SSL authentication to the site, pages can't be displayed due to an error &quot;Cannot Find Server or DNS Error.&quot;<br><br>If I try to access the site with <A HREF="

HTTP://www.domain.com.&nbsp"

TARGET="_new">

HTTP://www.domain.com.&nbsp</A>;&nbsp;I

get the error telling me I need to use a secure channel.&nbsp;&nbsp;This is correct.&nbsp;&nbsp;So I use <A HREF="

HTTPS://www.domain.com.&nbsp"

TARGET="_new">

HTTPS://www.domain.com.&nbsp</A>;&nbsp;It

is here that I get the officious error regarding DNS.<br><br>I am not using HOST HEADERS.&nbsp;&nbsp;Verisign says they are incompatible with SSL Certificates.&nbsp;&nbsp;Does SSL require a DNS Server?&nbsp;&nbsp;I thought I could get away with a HOSTS file for this simple experiment.&nbsp;&nbsp;In my Key Request to Verisign, I used WEB as my Common Name and a BIT length of 1024.&nbsp;&nbsp;I'm not sure how this relates to anything, but it seems pertinent to this problem.<br><br>Would appreciate any advice you could give me.&nbsp;&nbsp;I don't know what to do next.<br><br>Thanks

 

[jpriory]

SSL uses port 443. Is this enabled?

 

[wannaBmsce]

JPRIORY, thanks!<br><br>You know how it is when you try to make it through a complex computer-configuring process for the first time.&nbsp;&nbsp;If you forget to dot an i, it doesn't work.&nbsp;&nbsp;And because you've never gotten it to work before, you don't have a clue where the busted link is located in the long chain of instructions.&nbsp;&nbsp;Usually, it is something as stupid as an incorrect HOSTS file entry.&nbsp;&nbsp;I got confused about how DNS names work, and I got it wrong.&nbsp;&nbsp;Well, I got that solved.&nbsp;&nbsp;Additionally, I had to turn on SSL by specifying port 443.&nbsp;&nbsp;I thought this would be automatic.<br><br>So now, I have Internet Explorer accepting the public certificate from the web server. Yay! The problem now is that it won't trust the certificate no matter what I do.&nbsp;&nbsp;I got a demo 40-bit demo key from Verisign.&nbsp;&nbsp;I though it would work like a normal certificate for 15-days.&nbsp;&nbsp;I just don't know.&nbsp;&nbsp;I have to write them to look into it.<br><br>Thanks for taking the time!&nbsp;&nbsp;You really helped me.<br><br>Sincerely,<br>Dennis