Reportmanager (SSL): Unable to Connect to the remote server

Who can help me with SSL and Reporting Services (Reportmanager)?
Reportmanager (SSL): >> Unable to Connect to the remote server
System information:
Server 2003 Std Edition, SQL Server Enterprise, both 64-bit, latest service
packs
Microsoft SQL Server Reporting Services Version 9.00.3042.00
ASP.NET version 2.0.50727
Both Reportmanager (/Reports) and Reportserver (/Reportserver) are working
correctly on http (without SSL) using 'Basic authentication'.
I successfully installed a certificate 'extranet.website.nl' in IIS on the
'Default Web Site'.
With the Reporting Services Configuration Manager, I turned on SSL for
Reporting Services:
- Require Secure Socket Layer (SSL) connections: Yes
- Require for: 3 - All SOAP APIs (also tried other selections)
- Certificate Name: extranet.website.nl
After restarting everything the following happens:
- Reportserver (https://extranet.website.nl/reportserver) is working
correctly.
- Reportmanager (https://extranet.website.nl/reports) gives the following
error:
>> Unable to Connect to the remote server
Extra information:
The certificate is installed on the 'Default Web Site' and displayed on both
'Reports' and 'ReportServer'. Both using the DefaultAppPool.
-- rsreportserver.config --
<Add Key="SecureConnectionLevel" Value="3"/>
...
<UrlRoot>https://extranet.website.nl/reportserver</UrlRoot>
...
<WebServiceAccount>NT Authority\NetworkService</WebS...
...
-- RSWebApplication.config --
<ReportServerUrl>https://extranet.website.nl/ReportServer</Report...
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
I have changed to all possibilities 'Require secure channel (SSL)' and
'Require 128-bit encryption' in IIS on the 'Default Web Site', 'Reports' and
'ReportServer'. Afterwards restarting Reporting Services and IIS.
Who can help me with the solution for the Reportmanager (/Reports)?
>> Unable to Connect to the remote server
Thanks a lot for the working solution...Yes, it's working...
The working solution seemed to be more simple then expected:
(after a lot of trying)
In .../etc/hosts
add:
<local-ip-adres> <servername>
for example:
192.168.1.100 server001|||Directory: C:\WINDOWS\system32\drivers\etc
File: hosts
"Lonny" wrote:
> Can you explain your solution in a bit more detail?
> I am having the same issue with https.
> Where exactly is .../ect/hosts ?
> EggHeadCafe - .NET Developer Portal of Choice
> http://www.eggheadcafe.com
>