September 14, 2017 at 7:24 am
I just installed a new SSRS 2016 on a windows server 2012 r2 vm. I can connect to both the engine and report server on the vm using ssms 2016. but I cannot connect to the report server outside the vm using ssms 2016. I had similar issue with the engine but was able to resolve it through the firewall. I have read and try a lot from here and on the web with no help.
what am i doing wrong here.
September 14, 2017 at 8:00 am
From memory
1. Can you connect to the windows 2012 vm remotely? The vm might use an internal network.
2. SQL Configuration Manager: is TCP protocol enabled?
3. The SQL Server instance is set for fixed network ports (dynamic ports may mess up the firewall)
4. SPN's are set ? (especially when authenticating with windows/Kerberos).
5. Double check firewalls at both sides (client & server)
6. SSRS has its own access-configuration (at start it is restricted to buildin administrators)
There must be a connectivity guide for SSRS on the web somewhere
September 14, 2017 at 8:09 am
gissah - Thursday, September 14, 2017 7:24 AMI just installed a new SSRS 2016 on a windows server 2012 r2 vm. I can connect to both the engine and report server on the vm using ssms 2016. but I cannot connect to the report server outside the vm using ssms 2016. I had similar issue with the engine but was able to resolve it through the firewall. I have read and try a lot from here and on the web with no help.
what am i doing wrong here.
Did you go through this article?
Configure a Firewall for Report Server Access
If you have all of those open, what else did you try and what errors do you get trying to connect?
Sue
September 14, 2017 at 9:02 am
Hi SSC-Insane Yes that is the guide I used to set up my port I only limit it to Domain/Private is that why for safety?
Hi SCCChampion, Thanks for your response please
Can you connect to the windows 2012 vm remotely? The vm might use an internal network. Yes I can connect to the vm
2. SQL Configuration Manager: is TCP protocol enabled? Yes TCP is enabled
3. The SQL Server instance is set for fixed network ports (dynamic ports may mess up the firewall) My Dynamic port is empty, cause I am using TCP Port 1433
4. SPN's are set ? (especially when authenticating with windows/Kerberos). looking into it. I run a couple of script to set the spn
5. Double check firewalls at both sides (client & server) the report is working across the network
6. SSRS has its own access-configuration (at start it is restricted to buildin administrators) I think this is where my issue is even please advice
Thanks
September 14, 2017 at 9:08 am
Take it your trying to get to SSMS to connect to the SSRS instance. IIFC that uses RPC so you need to allow the full RPC port numbers which is pretty much every port which is a security risk as you expose a lot about the server in doing so. I've not found a way to limit the RPC port for SSRS yet. So if your security/network teams say OK you can do it otherwise, the solution is to remote into the machine and run SSMS from there.
September 14, 2017 at 2:22 pm
@SSC-dedicated Oh ok thanks, tried that and it didn't work as well. system adm has taken over. Thanks all
September 15, 2017 at 1:31 am
gissah - Thursday, September 14, 2017 2:22 PM@SSC-dedicated Oh ok thanks, tried that and it didn't work as well. system adm has taken over. Thanks all
Try going to the URL instead of the machine, eg http://reports.mydomain.com/reportserver or http://servername/reportserver does that work for you?
Ant
September 15, 2017 at 11:47 am
My issue was on this line <RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel> . I changed it to Allow. when I revised it to OFF is started working. I don't know why
September 15, 2017 at 12:01 pm
gissah - Friday, September 15, 2017 11:47 AMMy issue was on this line <RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel> . I changed it to Allow. when I revised it to OFF is started working. I don't know why
Thanks for posting back. The convoluted mess of combinations of what is and isn't supported with the extended protection levels is in this document - you could try to figure out which pieces come into play in your environment. Seems that your connection needed to support extended protection levels and using the allow setting supports it but doesn't require it :
Extended Protection for Authentication with Reporting Services
Sue
March 6, 2024 at 11:04 am
I got the same with a new SSRS 2022 edition setup.
The solution was actually pretty simple,
I created the "required" SPN's, but noticed a bas syntaxis when doublecheckin.
Correct SPNS should be set as:
setspn -s http/servername serviceaccountforSSRS
setspn -s http/servername.domain serviceaccountforSSRS
Maybe handy info for somebody else having this issue.
Wkr,
Eddy
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply