(The -a switch returns open listening ports as well as any ports with established connections.
To verify that the proper ports are listening and the Edge services are functional the following validation checks can be performed. Example Configurationįor the remainder of this article the following Lync Server Topology is used throughout all example text and screenshots. For example, traffic sent to the internal IP of the Edge server over port 443 would be for relaying media, but traffic sent to the Access Edge external IP over port 443 would actually be external client SIP signaling requests. Thus it is important to always note the IP address of the interface as well as the port. Simply looking at the port number alone is not enough to know what type of traffic might be associated with it as different services will use the same port number for different purposes, albeit on different IP addresses as no two services can occupy the same listening port on the same IP address. The Reverse Proxy server was removed as well as the outbound connections for DNS and HTTP, leaving only the inbound listening ports required on the Edge Server depicted.Īs shown above there are multiple ports utilized by the Edge server with some of the same port numbers (e.g. The following diagram is a slight modification from the Port Summary for Single Consolidated Edge documentation in TechNet. When troubleshooting it is helpful to know the basic Service Name and well as the core application for each of the Edge services.
This article takes a look at the services and network traffic which travels to, and through, the Edge Server in an effort to simplify deployment and troubleshooting by gaining a basic understanding of the Edge Server’s purpose. But without knowing some of the basic functionality provided it can be confusing at times to understand what traffic is going where in the topology. The Lync Edge Server is an often misunderstood server role that in theory is not all that complicated.