I am attempting to setup my Exchange Server's Default
Website with HTTPS instead of HTTP.  I have installed
certificate services, created and installed the
certificate in this format:

servername.publicdomainname.com

I have turned on the "require ssl" in IIS

But, when I try to open the site either internally using
the server's IP address or externally using the public
domain name (i.e. www.publicdomainname.com) I get a page
cannot be displayed error message.

If it type in the old http: then it tells me to try using
https:  so I know that it sees the option is turned on.

Running Server 2003 Standard with Exchange Server 2003.
I am trying to get this setup so that I can have RPC or
http and also activesync directly work with the server.

Any help is appreciated,

Thanks,

Steve

[ Post a follow-up to this message ]

Hi Steve,

if you check Default Site properties is SSL port defined? It should be 443?

Can you telnet to servername.publicdomainname.com on port 443?

telnet servername.publicdomainname.com 443

I hope this helps,

Mike

"Steve" <trmfp@nospam.yahoo.com> wrote in message
news:c32a01c47a31$51ea9210$a401280a@phx.gbl...
> I am attempting to setup my Exchange Server's Default
> Website with HTTPS instead of HTTP.  I have installed
> certificate services, created and installed the
> certificate in this format:
>
> servername.publicdomainname.com
>
> I have turned on the "require ssl" in IIS
>
> But, when I try to open the site either internally using
> the server's IP address or externally using the public
> domain name (i.e. www.publicdomainname.com) I get a page
> cannot be displayed error message.
>
> If it type in the old http: then it tells me to try using
> https:  so I know that it sees the option is turned on.
>
> Running Server 2003 Standard with Exchange Server 2003.
> I am trying to get this setup so that I can have RPC or
> http and also activesync directly work with the server.
>
> Any help is appreciated,
>
> Thanks,
>
> Steve

[ Post a follow-up to this message ]

Thanks for the quick reply, Mike.  I do have the port
defined as 443 in IIS.  When I try to telnet, it just
sits there and says connecting to servername.......

Maybe I have done something wrong in the certificate
creation.  As I stated before it is
servername.publicdomainname.com

Should it be hostname.publicdomainname.com?  By hostname
I mean the header such as email or www or etc.

I do have Port 443 Open to this server in my firewall,
but I also tried telnet to the IP address of the server
and the port number and it still just said connecting.
Or is that normal.

Steve


>-----Original Message-----
>Hi Steve,
>
>if you check Default Site properties is SSL port
defined? It should be 443?
>
>Can you telnet to servername.publicdomainname.com on
port 443?
>
>telnet servername.publicdomainname.com 443
>
>I hope this helps,
>
>Mike
>
>"Steve" <trmfp@nospam.yahoo.com> wrote in message
>news:c32a01c47a31$51ea9210$a401280a@phx.gbl... 
using[vbcol=seagreen] 
page[vbcol=seagreen] 
using[vbcol=seagreen] 
>
>
>.
>

[ Post a follow-up to this message ]

Hi Steve,

no this is not normal -- either web service is not running or access to this
TCP port if filtered (e.g. on firewall). Try to connect from the server
itself e.g.

telnet localhost 443

and

telnet 10.10.10.10 443

(replace 10.10.10.10 with real server's IP). Does this work? If it does,
check firewall configuration again. If it doesn't check IIS configuration
and restart IIS service...

Mike

"Steve" <trmfp@nospam.yahoo.com> wrote in message
news:c2d601c47a38$8362e430$a301280a@phx.gbl...[vbcol=seagreen]
> Thanks for the quick reply, Mike.  I do have the port
> defined as 443 in IIS.  When I try to telnet, it just
> sits there and says connecting to servername.......
>
> Maybe I have done something wrong in the certificate
> creation.  As I stated before it is
> servername.publicdomainname.com
>
> Should it be hostname.publicdomainname.com?  By hostname
> I mean the header such as email or www or etc.
>
> I do have Port 443 Open to this server in my firewall,
> but I also tried telnet to the IP address of the server
> and the port number and it still just said connecting.
> Or is that normal.
>
> Steve
>
> 
> defined? It should be 443? 
> port 443? 
> using 
> page 
> using 

[ Post a follow-up to this message ]

OK, here is what I get when trying to telnet:

I type in either telnet servername 443 or telnet x.x.x.x
443 and press enter, I get a blank black screen.

If I press Ctrl + ] then it gives me a microsoft telnet
prompt

I am assuming that I am connected at that point?

Don't know what this extra step is about.

Anyway, it looks like I can see it now, but I still can't
access my web pages via https://

Should I use the host name or servername in my
certificate?

Steve
>-----Original Message-----
>Hi Steve,
>
>no this is not normal -- either web service is not
running or access to this
>TCP port if filtered (e.g. on firewall). Try to connect
from the server
>itself e.g.
>
>telnet localhost 443
>
>and
>
>telnet 10.10.10.10 443
>
>(replace 10.10.10.10 with real server's IP). Does this
work? If it does,
>check firewall configuration again. If it doesn't check
IIS configuration
>and restart IIS service...
>
>Mike
>
>"Steve" <trmfp@nospam.yahoo.com> wrote in message
>news:c2d601c47a38$8362e430$a301280a@phx.gbl... 
hostname[vbcol=seagreen] 
Default[vbcol=seagreen] 
installed[vbcol=seagreen] 
public[vbcol=seagreen] 
on.[vbcol=seagreen] 
2003.[vbcol=seagreen] 
RPC or[vbcol=seagreen] 
server.[vbcol=seagreen] 
>
>
>.
>

[ Post a follow-up to this message ]

Hi,

can you check your certificate and see if it has these two properties set.
Compare it to example that I posted here...
http://freeweb.siol.net/mpihler/cert.jpg

You can view your certificate if you open your Default Web Site ->
Properties -> Directory Security -> View Certificate.

Mike

"Steve" <trmfp@yahoo.com> wrote in message
news:c33301c47a3b$21a028e0$a301280a@phx.gbl...[vbcol=seagreen]
> OK, here is what I get when trying to telnet:
>
> I type in either telnet servername 443 or telnet x.x.x.x
> 443 and press enter, I get a blank black screen.
>
> If I press Ctrl + ] then it gives me a microsoft telnet
> prompt
>
> I am assuming that I am connected at that point?
>
> Don't know what this extra step is about.
>
> Anyway, it looks like I can see it now, but I still can't
> access my web pages via https://
>
> Should I use the host name or servername in my
> certificate?
>
> Steve 
> running or access to this 
> from the server 
> work? If it does, 
> IIS configuration 
> hostname 
> Default 
> installed 
> public 
> on. 
> 2003. 
> RPC or 
> server. 

[ Post a follow-up to this message ]

Steve,

It's funny because I am having the exact same problem as
you and have been following along with Mike's great
advice, but to no avail as well.

My certificate says the same as yours, so I await a
response as well.

Thanks,

Mark
>-----Original Message-----
>The bottom part is correct, however the top reads as
>follows:
>
>This certificate is inteded for te following purpose
>All Issuance Policies
>All Application Polices
>
>Thanks,
>
>Steve 
>two properties set. 
>Web Site -> 
>x.x.x.x 
telnet[vbcol=seagreen] 
>can't 
>connect 
this[vbcol=seagreen] 
>check 
>port 
>just 
certificate[vbcol=seagreen] 
>firewall, 
>server 
>connecting. 
>on 
>internally 
>get a 
>try 
>turned 
Server[vbcol=seagreen] 
>.
>

[ Post a follow-up to this message ]

Steve and Mark,

what CA did you use to issue this certificates? Your internal -- Microsoft
CA services that comes with Windows or ... ?

How do you have IP setup? Any unassigned or? Is this only web site on this
server? If not, can you stop any other site and restart IIS. Make sure that
only Default Web Site is running.

Can you go over this Microsoft article?

HOW TO: Install Imported Certificates on a Web Server in Windows Server 2003
http://support.microsoft.com/defaul...4&Product=iis60

Mike

"Steve" <trmfp@nospam.yahoo.com> wrote in message
news:006e01c47a42$19339e60$a401280a@phx.gbl...[vbcol=seagreen]
> The bottom part is correct, however the top reads as
> follows:
>
> This certificate is inteded for te following purpose
> All Issuance Policies
> All Application Polices
>
> Thanks,
>
> Steve 
> two properties set. 
> Web Site -> 
> x.x.x.x 
> can't 
> connect 
> check 
> port 
> just 
> firewall, 
> server 
> connecting. 
> on 
> internally 
> get a 
> try 
> turned 

[ Post a follow-up to this message ]

Mike,

I used the the Microsoft 2003 one. My IP is assigned port
80 as well as 443 in IIS.  It the onlt web server I have.

When I try to access it internally, the certificate box
does not pop up, only the message "You are leaving a non
secure....".

Thanks,

Mark
>-----Original Message-----
>Steve and Mark,
>
>what CA did you use to issue this certificates? Your
internal -- Microsoft
>CA services that comes with Windows or ... ?
>
>How do you have IP setup? Any unassigned or? Is this
only web site on this
>server? If not, can you stop any other site and restart
IIS. Make sure that
>only Default Web Site is running.
>
>Can you go over this Microsoft article?
>
>HOW TO: Install Imported Certificates on a Web Server in
Windows Server 2003
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;816794&Product=iis60
>
>Mike
>
>"Steve" <trmfp@nospam.yahoo.com> wrote in message
>news:006e01c47a42$19339e60$a401280a@phx.gbl... 
telnet[vbcol=seagreen] 
this[vbcol=seagreen] 
servername.......[vbcol=seagreen] 
certificate[vbcol=seagreen] 
servername.publicdomainname.com[vbcol=seagreen] 
message[vbcol=seagreen] 
the[vbcol=seagreen] 
the[vbcol=seagreen] 
to[vbcol=seagreen] 
Server[vbcol=seagreen] 
have[vbcol=seagreen] 
the[vbcol=seagreen] 
>
>
>.
>

[ Post a follow-up to this message ]

I used the Microsoft Certificate Services.

I have only one website on this server.

I will look at the article provided.

Thanks,

Steve
>-----Original Message-----
>Steve and Mark,
>
>what CA did you use to issue this certificates? Your
internal -- Microsoft
>CA services that comes with Windows or ... ?
>
>How do you have IP setup? Any unassigned or? Is this
only web site on this
>server? If not, can you stop any other site and restart
IIS. Make sure that
>only Default Web Site is running.
>
>Can you go over this Microsoft article?
>
>HOW TO: Install Imported Certificates on a Web Server in
Windows Server 2003
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;816794&Product=iis60
>
>Mike
>
>"Steve" <trmfp@nospam.yahoo.com> wrote in message
>news:006e01c47a42$19339e60$a401280a@phx.gbl... 
telnet[vbcol=seagreen] 
this[vbcol=seagreen] 
servername.......[vbcol=seagreen] 
certificate[vbcol=seagreen] 
servername.publicdomainname.com[vbcol=seagreen] 
message[vbcol=seagreen] 
the[vbcol=seagreen] 
the[vbcol=seagreen] 
to[vbcol=seagreen] 
Server[vbcol=seagreen] 
have[vbcol=seagreen] 
the[vbcol=seagreen] 
>
>
>.
>

[ Post a follow-up to this message ]