Firewalls can be placed between reporting-related applications and the databases that support them. If a firewall is placed between an application and a database that it relies on, both the database and the firewall must be configured to allow traffic between the ports used for this communication.
About This Task
Although it is possible to query the SQL Server and set the firewall to allow the ports it is currently using, restarting the SQL Server instance can result in it using different (dynamic) ports, and therefore lost communication. Therefore, we recommend setting static ports.
- Set static listener ports on the named SQL Server instances.
For instructions, see Microsoft's TechNet article, Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager).
- Configure the firewall to pass traffic between the Web Console and the SQL Server through the static ports you configured, or add application exceptions for the affected applications:
- If it is a Windows Firewall, see Microsoft's TechNet article entitled Configure the Windows Firewall to Allow SQL Server Access.
- If it is a hardware-based firewall device, consult its manufacturer's documentation.
- Third-Party Port Mapping (TPPM) can be used to route traffic in this scenario. See Configuring Third-Party Connections Using the Firewall Configuration File.
- In addition to configuring your firewall to allow traffic for the static ports you configured on each SQL Server named instance, allow ports 1433 and 1434 also.