Can Lync/SfB "Internal" clients be NAT'd RRS feed

  • Question

  • Scenario:

    Central Data Centre hosting all SfB Servers (Front-Ends/Edge etc).

    Multiple Client Networks where IP Address Ranges Overlap (therefore the Clients are NAT'd).


    1. Is NAT'ing of clients networks supported?

    2. If not supported, does it still work - and if so, what the potential issues/considerations?

    3. Can you describe the traffic flow for peer-to-peer connectivity between clients residing on separate subnets that have overlapping IP Ranges (i.e. similar IP ranges used in each subnet)?

    4. Do all client communications for these peer to peer communications rely on the internal Edge service to relay media?



    Wednesday, March 29, 2017 8:44 PM

All replies

  • Hi Steve,

    Issue1: did you meant you have configured NAT between SFB server and SFB client? If that, just make sure SFB client could communicate with SFB server without any problems(include Ping and DNS resolution).

    Issue2: refer to issue1’s answer.

    Issue3: SFB/Lync server traffic flow could be referred by the following link: https://www.microsoft.com/en-us/download/details.aspx?id=39968 , in your organization, just add NAT’s address then to SFB server, and vice versa.

    Issue4: internal communication don’t reply on the internal Edge service, Edge service just be used when internal user communicate with external user.

    If I misunderstand your NAT topology, you could post your NAT topology snapshot to us for troubleshooting.

    Best Regards,
    Jim Xu
    TechNet Community Support

    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by jim-xu Wednesday, April 5, 2017 9:35 AM
    Thursday, March 30, 2017 8:06 AM