Configure a Firewall for Report Server Access
Report server applications and published reports are accessed through URLs that specify an IP address, port, and virtual directory. If Windows Firewall is turned on, the port that the report server is configured to use is most likely closed. Indications that a port might be closed are the appearance of a blank Web page after requesting a report, or a blank page when you attempt to open Report Manager from a remote client computer.
To open a port, you must use the Windows Firewall utility on the report server computer. Reporting Services will not open ports for you; you must perform this step manually.
By default, the report server listens for HTTP requests on port 80. As such, the following instructions include steps that specify that port. If you configured the report server URLs to use a different port, you must specify that port number when following the instructions below.
If you are accessing SQL Server relational databases on external computers, or if the report server database is on an external SQL Server instance, you must open port 1433 and 1434 on the external computer. For more information, see Configure a Windows Firewall for Database Engine Access in SQL Server Books Online. For more information about the default Windows firewall settings, and a description of the TCP ports that affect the Database Engine, Analysis Services, Reporting Services, and Integration Services, see Configure the Windows Firewall to Allow SQL Server Access in SQL Server Books Online.
These instructions assume that you already configured the service account, created the report server database, and configured URLs for the Report Server Web service and Report Manager. For more information, see Manage a Reporting Services Native Mode Report Server.
You should also have verified that the report server is accessible over a local Web browser connection to the local report server instance. This step establishes that you have a working installation. You should verify that the installation is configured correctly before you begin opening ports. To complete this step on Windows Server, you must have also added the report server site to Trusted Sites. For more information, see Configure a Report Server for Local Administration on Windows Vista and Windows Server 2008.
Opening Ports in Windows Firewall
There are separate instructions for different versions of Windows Firewall.
To open port 80 on Windows 7, Windows Server 2008 R2, Windows Server
From the Start menu, click Control Panel, click System and Security, and then click Windows Firewall. Control Panel is not configured for 'Category' view, you only need to select Windows Firewall.
Click Advanced Settings.
Click Inbound Rules.
Click New Rule in the Actions window**.**
Click Rule Type of Port.
On the Protocol and Ports page click TCP.
Select Specific Local Ports and type a value of 80.
On the Action page click Allow the connection.
On the Profile page click the appropriate options for your environment.
On the Name page enter a name of ReportServer (TCP on port 80)
Restart the computer.
To open port 80 on Windows Vista or Windows Server 2008
From the Start menu, click Control Panel, click Security, and then click Windows Firewall.
Click Allow a program through Windows Firewall.
On the Exceptions tab, click Add Port.
In Name, type ReportServer (TCP on port 80).
In Port number, type 80.
Verify that TCP is selected.
Click Change Scope.
Click My network (subnet) only, and then click OK.
Click OK to close the dialog box.
Restart the computer.
After you open the port and before you confirm whether remote users can access the report server on the port that you open, you must grant user access to the report server through role assignments on Home and at the site level. You can open a port correctly and still have report server connections fail if users do not have sufficient permissions. For more information, see Grant User Access to a Report Server (Report Manager) in SQL Server Books Online.
You can also verify that the port is opened correctly by starting Report Manager on a different computer. For more information, see Report Manager (SSRS) in SQL Server Books Online.