no ssl connection possible

Hi,

I have a SBS 2003 Standard SP2. In the default website we have exchange
(exchange, exchweb and public). I used selfssl from IIS-Resourcekit for a
ssl certificate. Everything worked fine (https://servername/exchange). Now,
for unknown reason, I am only able to communicate via port 80. From the
server itself I am not able to reach any ssl-pages anymore. "Page cannot be
displayed", thats all. Telnet "servername 443" accepts the connection.

Any idea?

Thanks in advance,

Nico Brandt

Re: no ssl connection possible

Interesting. have you try wfetch to test it?
what changed before it is not working?

--
Regards,
Bernard Cheah
http://www.iis.net/
http://www.iis-resources.com/
http://msmvps.com/blogs/bernard/


"Nico Brandt" wrote in message
news:OmCZSE%23tHHA.4612@TK2MSFTNGP04.phx.gbl...
> Hi,
>
> I have a SBS 2003 Standard SP2. In the default website we have exchange
> (exchange, exchweb and public). I used selfssl from IIS-Resourcekit for a
> ssl certificate. Everything worked fine (https://servername/exchange).
> Now, for unknown reason, I am only able to communicate via port 80. From
> the server itself I am not able to reach any ssl-pages anymore. "Page
> cannot be displayed", thats all. Telnet "servername 443" accepts the
> connection.
>
> Any idea?
>
> Thanks in advance,
>
> Nico Brandt
>

Re: no ssl connection possible

On Jun 26, 4:59 am, "Nico Brandt" wrote:
> Hi,
>
> I have a SBS 2003 Standard SP2. In the default website we have exchange
> (exchange, exchweb and public). I used selfssl from IIS-Resourcekit for asslcertificate. Everything worked fine (https://servername/exchange). Now,
> for unknown reason, I am only able to communicate via port 80. From the
> server itself I am not able to reach anyssl-pages anymore. "Page cannot be
> displayed", thats all. Telnet "servername 443" accepts the connection.
>
> Any idea?
>
> Thanks in advance,
>
> Nico Brandt

Make sure that there is a private key associated with the certificate
(it will say so at the bottom when you view the certificate details).
Also make sure that IIS is set up to use port 443 for SSL on that
website and that you have restarted the server.

--
Robert
http://www.sslshopper.com