Reporting Services 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: receiving a blank page when you attempt to open the web portal from a remote client computer, or a blank Web page after requesting a report.
To open a port, you must use the Windows Firewall utility on the report server computer. Reporting Services doesn't 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 in this article.
You must open port 1433 and 1434 on the external computer if one of the following statements is true:
If you're accessing SQL Server relational databases on external computers
If the report server database is on an external SQL Server instance
These instructions assume that you already configured the service account. They also assume you created the report server database and configured URLs for the Report Server Web service and the web portal. For more information, see Manage a Reporting Services native mode report server.
You should also verify 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 also add the report server site to Trusted Sites. For more information, see Configure a native mode report server for local administration (SSRS).
Open ports in Windows Firewall
To open port 80:
From the Start menu, select Control Panel, select System and Security, and then choose Windows Firewall. Control Panel isn't configured for Category view, you only need to select Windows Firewall.
Select Specific Local Ports and enter a value of 80.
Select Next.
On the Action page, select Allow the connection.
Select Next.
On the Profile page, select the appropriate options for your environment.
Select Next.
On the Name page, enter the name of ReportServer (TCP on port 80).
Select Finish.
Restart the computer.
Next steps
After you open the port, you must grant user access to the report server through role assignments on Home and at the site level. This action is done before confirming whether remote users can access the report server on the opened port. You can open a port correctly and still have report server connections fail if users don't have sufficient permissions. For more information, see Grant user access to a report server.
Open a port in the Windows Firewall for TCP access
In the Rule Type dialog box, select Port, and then select Next. In the Protocol and Ports dialog box, select TCP. Select Specific local ports, and then type the port number of the instance of the Database Engine, such as 1433 for the default instance. Select Next.
As we have already mentioned, the SQL Server Database Engine listens on port 1433 for the TCP/IP connections, and port 1434 is used for the UDP connections by default. However, if you are working with more than one SQL Server instance at the same time, you will have the default port numbers.
Click the Start button on the local machine and type “CMD” into the search programs and files field.Enter “Telnet IP-address 1433” in the Command Prompt. If port 1433 is not open, it will immediately return an error. We will be able to connect to the MS-SQL server if port 1433 is open.
TCP port 1433 is the default port for communication between Microsoft SQL Server and its applications. SQL Server powers many of the world's top data-driven solutions, and port 1433 is widely used to connect to the database.
For example, if your server name is "MyServer" and the port number is "1234", you would use the following connection string: server=MyServer,1234;database=myDatabase;integrated security=true; When connecting with Microsoft SQL Server Management studio, enter port number with comma.
You can use a network security group to control access to the SQL Managed Instance data endpoint by filtering traffic on port 1433 and ports 11000-11999 when SQL Managed Instance is configured for redirect connections.
In order for two SQL Server instances to exchange Service Broker messages, each instance must be able to send TCP/IP traffic to the port that the other instance uses for Service Broker communications. By convention, Service Broker often uses port 4022 for broker-to-broker communication.
Address: 359 Kelvin Stream, Lake Eldonview, MT 33517-1242
Phone: +577037762465
Job: Product Hospitality Supervisor
Hobby: Gardening, Web surfing, Video gaming, Amateur radio, Flag Football, Reading, Table tennis
Introduction: My name is Manual Maggio, I am a thankful, tender, adventurous, delightful, fantastic, proud, graceful person who loves writing and wants to share my knowledge and understanding with you.
We notice you're using an ad blocker
Without advertising income, we can't keep making this site awesome for you.