LYNC 2010 for internal nat clients

Helo!

Please approve that Lync Server 2010 can interoperate with INTERNAL isolated NAT- clients with LYNC 2010 EDGE role ONLY and optionaly WITHOUT Reverse-proxy (no security for https). Have got somebody have such a topology in production environment?

Thanks.
atom_73Asked:
Who is Participating?
 
Jeff_SchertzConnect With a Mentor Commented:
The Reverse Proxy server is only used for external clients and should not be needed for an internal clients.  A proper deployment would be to make sure that ll clients across any internal subnets can connect to the internal web services (80 & 443 TCP) running on any internal Lync Front End and Director servers.

Also make sure that the same clients can reach the internal interface of the Edge server over at least 443 TCP and 3478 UDP and then the Edge Server can be used to relay media sessions between any internal clients which cannot do so directly.

Ideally though you should not be using your Edge server primarily for internal media relay, the best practices are to instead define a range of 40 contiguous ports (e.g. 55501-55540) for Lync client media relay and then open these ports between all internal firewalled subnets so that Lync clients can utilize peer-to-peer media sessions.
0
 
atom_73Author Commented:
Please take into account that ALL "internal" clients behind NAT, no direct routing....
0
All Courses

From novice to tech pro — start learning today.