In Add Network Entities, expand Networks, click External, click Add, and then click Close.In the This rule applies to traffic from these sources list, click Anywhere, and then click Remove.On the Properties page, on the From tab, do the following:.On the TMG Server, open the Management Console and open the properties of the Lync Services rule that was created in the previous step.Now that the basic rule is created it can be changed to redirect to the Lync port, i.e.
To configure a Web Publishing Rule in TMG2010 use the following steps: This should also be configured in the TMG rule later on. As you can see in the picture above, the web service is listening on port 4443 and published on port 443. So, the FQDN will point to the TMG Server, while the will point to the Lync 2013 Edge Server. The FQDN for this server is defined in the External Web Services FQDN in the Topology Builder: The TMG Server is a different server with a different external IP address. This Edge Server is also used for federation services with other partners. In our environment, the external Lync clients connect directly to the Lync Edge Server.
Enabling remote users to download files from the Address Book service.Enabling external users to expand distribution groups.Enabling external users to download meeting content for your meetings.You also might want to implement publishing rules on your Threat Management Server (TMG) 2010 to implement the following additional services: This way you can use Lync 2013 internally and externally, including federation with other Lync 2010/2013 or OCS 2007 R2 organizations.
In an earlier blog post I explained how to setup a Lync 2013 environment with a Front-End server and an Edge Server.