![]() See Figures 4 and 5 below. (click the gear symbol ( Figure 4) ->tools -> options-> general on the Lync client). ![]() If all checks out to this point, turn on Lync client logging on the Lync client itself. Start a new nslookup session and type to verify the fully qualified domain name can be reached. another connection point that must be reachable is the Lync server fully qualified domain name. If the lookup fails, either the service locator record (SRV) is missing from the server DNS, or there is a blockage in the connection to the server. Verify the SRV record for automatic client login. Along a similar path of troubleshooting, port failure. See TechNet documentation for more information. Place this http address into a browser on the affected client.įailure indicates a connection problem with IIS on the Lync server. If the configuration is already automatic and fails, try putting in the connection IP address ( Figure 3).Īnother step to isolate the failure to IIS or http is to verify the /abs/handler URL. Verify the configuration mode is automatic (tools ->options-> advanced on the Lync client) The steps to set manual configuration are: If you find connection problems from the Lync information, compare the results with using a manual configuration. The RUCT tool may be able to help explain why some of the failures in figure 2 may be occurring. See the remote unified communications troubleshooting tool (RUCT tool) at the end of this article. While this may not be a root cause, this would point to to failure between Exchange and Lync. For Example the EWS failure line may indicate there is an Exchange communication failure. Review and research failure lines from Figure 2 below. choose this option as seen below in Figure 1. You will see a choice called configure information. Using the keyboard, hold the control key and right click the Lync icon, at the bottom right corner of the windows task bar. Provided the questions were answered with the actual setting of the Lync deployment, this will generate an accurate network topology diagram that can be used to proof the Lync environment for best practices.Īn important Lync client troubleshooting step utilizes the client information property. Answering questions on the Lync Server Planning Tool will generate a network diagram. Another tool that can be helpful is the Lync Planning Tool. ![]() Microsoft has formalized the process into a checklist: The Microsoft Lync Check List. What is the name of the Sip domain? Is it the same as the mail domain or domain name? How many firewalls, routers, and switches are part of the Lync network?Īre VLANS used? How many and are they well connected? What is the source subnet and target subnet? Issue 1: Collect Deployment Specific Detailsīefore beginning to troubleshoot issues on Lync deployments, take a moment to find the characteristics of the deployment. This article provides information on how to troubleshoot a Lync Client.
0 Comments
Leave a Reply. |