Accessing Reporting Services Using a Fully Qualified Domain Name

Accessing Reporting Services Using a Fully Qualified Domain Name

Accessing Reporting Services Using a Fully Qualified Domain Name

If you installed SQL Server Reporting Services (SSRS) on a server in a domain and you use a domain user to start the service and did not perform any further configuration, then you most probably can only access the Report Manager using an IP and not the Fully Qualified Domain Name (FQDN) of the server (if an SPN is not set).

If you try to use the Fully Qualified Domain Name to access reporting services then you will most probably be prompted for username password several times ending with an empty page.


How to Enable Accessing Reporting Services Using a Fully Qualified Domain Name

In order to be able to access Reporting Services using FQDN you will need to perform the following actions:

1. Register a Service Principal Name (SPN) for the Domain User Account that Runs SSRS

Consider the following example:

sample computer name: reportsrv01
sample domain:
sample domain account: examplessrsuser

Then on the Domain Controller Server in a Command Prompt with Elevated Rights, you can Run as Administrator:

example 1: If SSRS are on port 80 (no need to specify 80 as it is the default http port):
Setspn -s http/ examplessrsuser

example 2: If SSRS are on any other port (i.e. 2430):
Setspn -s http/ examplessrsuser


2. Edit the RsReportServer.config File

On the Reporting Services server, in the virtual directory of SSRS, edit the “RsReportServer.config” file and locate the authenticationtypes section.

Then add </rswindowsnegotiate> as the first entry in the authenticationtypes section.

The above step will actually enable NTLM.

For more information please visit this MSDN article.


Read Also


Featured Database Security and Administration Tool: DBA Security Advisor

DBA Security Advisor: Secure your SQL Server instances by scanning multiple instances against a rich set of security checks, and by getting recommendations and remediation steps.

DBA Security Advisor - SQL Server Security and Administration Tool

Learn more


Did you find this article useful and interesting? Feel free to leave your comment!

If you enjoy my SQL Server administration tips and articles, I have something special just for you. It is one of my eBooks and it is called “Administering SQL Server“. Check it out!

Subscribe to our newsletter and stay up to date with our latest articles on SQL Server and related technologies!

Check out our latest software releases! All our software tools have 30-day Trial Versions which are free to download.


Rate this article: 1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)


Reference: (

© SQLNetHub


Artemakis Artemiou
Artemakis Artemiou is a Senior SQL Server Architect, Author, and a 9 Times Microsoft Data Platform MVP (2009-2018). He has over 15 years of experience in the IT industry in various roles. Artemakis is the founder of SQLNetHub and Artemakis is the creator of the well-known software tools Snippets Generator and DBA Security Advisor. Also, he is the author of many eBooks on SQL Server. Artemakis currently serves as the President of the Cyprus .NET User Group (CDNUG) and the International .NET Association Country Leader for Cyprus (INETA). Artemakis's official website can be found at