Lync 2013 Firewall Ports – Internal Clients

Updated April 22,2014 following the contribution from Mark Poulton.

Every time I need to list the Lync 2013 firewall ports required in a corporate network I find myself jumping from the TechNet article Port Requirements to the Lync 2013 Protocol Workloads poster (for example to check the requirements for the different scenarios)

They are both really good resources  but what I need is usually a dumb list of origin – destination – protocol – ports for the different roles and features. So I tried to write down a series of docs easy to use and to supply to the firewall / security persons.

Hope you will like them, I will start with the port requirements of the Lync 2013 internal clients.

If you want to download the PDF version, you will find it Lync 2013 internal client Ports

As usual, if I missed something, please let me know.


Note: the scenario I used is the easiest one, with no hardware load balancer or pools.


  1. Just curious why you don’t have the TCP ports listed for application sharing and video conf? The range is there, but only the UDP protocol.

    1. Mark, congratulation for the keen eye 🙂
      Your comments where both correct and I have fixed the table accordingly.
      I forgot the TCP range because I used a lot the Lync 2013 workload poster and there you have a single arrow for both TCP and UDP ports used for application sharing.
      Usually the two protocols are shown separately.
      Thank you for your contribution.

  2. What about the situation, when 2 users in different pools are trying to connect to each other?
    Ports 1024-65535 are blocked by firewalls between Sites, what will be Lync Client Behavior? Will the signaling and media flow thought Edge Servers, if they exist in both sites?

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.