August 24, 2011 at 6:04 am
I thought I had posted this a couple of days ago but I can't find it. If this is the same issue posted twice I apologize. I'm new here.
I had the following network setup:
server1 - IIS, email and SSRS
server2 - Terminal and domain
server3 - domain and virus protection
server4 - SQL and file server
I am using Kerberos authentication. Everything was running fine except I was running into issues with the terminal server and domain server on the same box. I moved the domain to server one which created an issue with SSRS so I move SSRS to server4.
If SSRS is configured for just HTTP I can access reports from server4 but not from anywhere else. If i configure SSRS for SSL I cannot access reports from anywhere. Remote access to server4 SQL service was and is working fine. Is there something in one of the SSRS web.config files that I am missing?
Thanks
Chuck
August 24, 2011 at 11:07 am
where did you get the SSL certificate for the site, is it self generated?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 24, 2011 at 12:01 pm
Hi Perry,
It's a self certificate and it resides on the IIS server [servier1]. The SSRS server [server4] does not have IIS and no certificate reside on that box but it does see the certificate from server1.
Chuck
August 24, 2011 at 12:35 pm
ok the certificate is or at least should be bound to the fully qualified computername which you have changed. Self certs do also seem to be an issue i have had problems with them in the past. I take it you're not using a host header for the SSRS url
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply