Verify Connectivity for External Users

Test Connectivity of External Users and External access

Manual verification tests for external user access should include each type of external user that your organization supports, including any or all of the following:

• Users from at least one federated domain, and test IM, presence, A/V and desktop sharing.

• Users of each public IM service provider that your organization supports (and for which provisioning has been completed).

• Anonymous users.

• Users within your organization who are logged into Lync remotely, but not using VPN.

These tests determine whether your Edge Server is:

• Listening on the necessary ports by using a telnet client from outside your network.

  • Example: telnet ae.contoso.com 443

  • Perform the preceding test on ports you are using on the Edge Server or Edge Server pool depending on your deployment.

• Performing accurate external DNS resolution.

  • From outside your network ping each of the external FQDN’s of your Edge or Edge pool. Even if the ping fails you will see the IP addresses, which you can compare to the ones you have assigned.

Using the Remote Connectivity Analyzer

The Remote Connectivity Analyzer is a Web-based tool that can perform connectivity tests against your Office Communications Server 2007 R2 or Lync Server 2010 deployment and return the test results. The results can be used to confirm that your Edge Servers and reverse proxies are properly configured and that communication was successful, or reveal connectivity problems that need to be addressed. The Remote Connectivity Analyzer is located at https://www.testocsconnectivity.com/

The tests provided include:

1. Microsoft Lync Server Remote Connectivity Test with AutoDiscover

2. Microsoft Lync Server Remote Connectivity Test

3. Microsoft Office Communications Server Remote Connectivity Test

4. Microsoft Lync Mobile Auto-Discover Web Service Remote Connectivity Test

5. Microsoft Office Communications Server Remote Connectivity Test with AutoDiscover