| Paul Chan[MSFT] 2004-08-19, 5:53 pm |
| To add on that, I think Nishi's issue is actually a Server Configuration
Application (SCA) issue rather than Site Manager.
The SCA problem is that Nishi is trying to access SCA via the URL
http://ServerName/NRConfig
By default, the SCA site will use the localhost reference instead of
<ServerName>. Once the SCA "sees" that the HTTP request is not localhost
(i.e. not opening SCA from the local server), it will switch to a page
saying that it requires SSL.
If it is true that Nishi is accessing SCA from a remote machine, then SSL
is required. However, if accessing SCA from the local server, the access
can be made a bit simple by using the localhost reference than a
<ServerName>. One other thing I'm not sure if it is correct or not; that
is, there's no TCP port in the SCA URL from Nishi's original message. I
wonder if SCA is installed on the default website.
Just try to make the /NRConfig accessible from using a localhost reference
on the server machine, it should not ask for SSL. Unless it is needed to
access SCA from a remote machine, SSL is not required. However, if it is
really necessary to access SCA from a remote machine, then Nishi should
definitely follow Stefan's suggestion to locate IIS support resources to
make sure SSL is working properly first.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.
|