Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have Lync 2010 Standard deployed in my environment, along with an edge server. On my firewall I have NAT'd the public address(s) to the server. Right now I have all the ports opened for these addresses to work, but now I want to lock this down for security concerns. Is there a complete list of ports that Lync needs opened in order to work properly? I used the port numbers on the Lync Manual, but it was still blocking audio/video after I entered them into the FW. Any assistance from anyone who has set this up previously would be much appreciated.

share|improve this question
    
Are you using TMG or another kind of reverse proxy as well? –  SpacemanSpiff Jul 25 '12 at 16:30
    
Not using any kind of reverse proxy or TMG. I wish there was a simple list of what exact ports need to be configured. I'll do some more research to see if I'm missed this documentation from Microsoft. –  yum_tacos4u Jul 25 '12 at 16:50
add comment

2 Answers 2

up vote 5 down vote accepted

I have a similar setup to you, and here's what I'm doing and everything works:

External IP1, Port 80/TCP is NAT/PAT to Standard server port 8080/TCP External IP1, Port 443/TCP is NAT/PAT to Standard server port 4443/TCP

Since you're not using a TMG server, your firewall must do port translation so that external requests hit the correct site in IIS on your Standard (frontend) server.

External IP2, 443/TCP, 5061/TCP, 3478/UDP, TCP/UDP 50000-59999 Static NAT to Edge server, no port translation

Firewall rules permit the Edge server to talk to the standard edition frontend server.

I'd have to go back and look at my topology, but I believe I used separate URLs and IPs for each of the different services/media. Most of the Lync headaches are in the DNS misconfigurations, sometimes it won't accept CNAMES where you need A records, and vice versa.

If you're going to have a lot of clients (more than 100) than you probably should use a TMG or "insert reverse proxy here" to protect your frontend.

The image below may help you, as will the source that drew it:

http://ucken.blogspot.com/2011/07/configuring-lync-for-external-access.html

Lync Diagram

share|improve this answer
    
That is exactly what I was looking for. Thanks SpacemanSpiff! –  yum_tacos4u Jul 25 '12 at 16:54
    
No problem, went through this exact fun about 6 mnonths ago, good luck. –  SpacemanSpiff Jul 25 '12 at 16:54
    
I did go and look, and it appears I'm using two IP addressed on my edge server on the inside, with the inbound stuff hitting the primary, and the access, webconf, and av traffic from the inside hitting the second –  SpacemanSpiff Jul 25 '12 at 20:15
add comment

The Lync documentation from Microsoft is complete and accurate. If you're still experiencing an issue, chances are that you configured your firewall rules incorrectly. I'd give that another look before you conclude that the Microsoft-provided document is wrong.

share|improve this answer
    
Good point. Thanks for the advise. I'll review my setup and report back. Thanks! –  yum_tacos4u Jul 25 '12 at 16:21
    
The Lync documentation does not cover deploying without Forefront TMG all that well, it's terribly confusing. –  SpacemanSpiff Jul 25 '12 at 16:41
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.