Was this page helpful?
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Understanding firewall requirements for SQL Server with Lync Server 2013


Topic Last Modified: 2013-02-21

For a Standard Edition deployment, firewall exceptions are created automatically during Lync Server 2013 Setup. However, for Enterprise Edition deployments, you must configure the firewall exceptions manually on the SQL Server Back End Server. The TCP/IP protocol allows for a given port to be used once for a given IP address. This means that for the SQL Server-based server you can assign the default database instance the default TCP port 1433. For any other instances you will need to use the SQL Server Configuration Manager to assign unique and unused ports. This topic covers:

  • Requirements for a firewall exception when using the default instance

  • Requirements for a firewall exception for the SQL Server Browser service

  • Requirements for static listening ports when using named instances

If you are using the SQL Server default instance for any database when deploying Lync Server 2013, the following firewall rule requirements are used to help ensure communication from the Front End pool to the SQL Server default instance.


Protocol Port Direction



Inbound to SQL Server

The SQL Server Browser service will locate database instances and communicate the port that the instance (named or default) is configured to use.


Protocol Port Direction




When using named instances in the SQL Server configuration for databases supporting Lync Server 2013, you configure static ports by using SQL Server Configuration Manager. After the static ports have been assigned to each named instance, you create exceptions for each static port in the firewall.


Protocol Port Direction


Statically defined


Microsoft SQL Server 2012 documentation provides detailed guidance on how to configure firewall access for databases. For details about Microsoft SQL Server 2012, see “Configuring the Windows Firewall to Allow SQL Server Access” at http://go.microsoft.com/fwlink/p/?linkId=218031.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft