Lync 2013 login Troubleshoot methods
Lync 2013 troubleshooting :
In this article we going to see How To troubleshoot the lync 2013 various issues. If any errors happen it affect you business communication.
Collect some basic Details :
When you going to Lync 2013 troubleshooting you need collect some basic Details about the environment. Collect some details about your network ,firewalls, routers, switches. Make sure you deployed a edge server or not. Collect details about certificate. Make sure the sip address. Some mail and sip address may be different. So concerned in sip address.
Test the Lync Client Connectivity :
In this step press and hold the control button and click lync icon in the bottom bar. Then new window will open, here you will see configure information. Here you can check the details.
If you find ews error, then it may cause of exchange and lync error. There is a error between lynch and exchange. You can solve this using unified communications tool.
If you find any connection problem then you need to do manual configuration.
Verify configuration mode
Tools » options » advanced on lync client.
Verify the srv record for automatic client login. .type the following
If nslookup fails, the service locator record (srv) missing in your dns or there is any blockage in connection. Another connection point must be rechargeable in your lync server fully qualified domain name.
Start new nslookup session and type fq.domain.com can be reached.
Lync 2013 Client login :
Turn on lync client automatic login lync client in self,
Click the gear symbol» tools» option» General lync client you can see events and login error.
Reset the lync client :
If there is any problem during login ,then it must be authentication problems. Then this error may caused the certificate out date.
Cached credentials and certification problems may solve by clearing the history.
To solve this problem try to login new user in this lync client the new user is able to sign in ,then we do some work to solve this issue for other users.
1. Verify the naming of sip domain.
2. Clear the cache in credentials history, from the credential lockers.
Go to control panel » all control panel » credentials manager or type cred in start menu
3. Clear user registry.
*.Go to the registry and remove the user specific registry keys
*.Remove the problem user principle name folder from HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient
*.Remove the problem user principle name folder from HKEY_CURRENT_USER\Software\Microsoft\Communicator\ConfAddin\
*.Remove the user folder from \Users\username\AppData\Local\Microsoft\Communicator
*.Run ipconfig /flushdns && ipconfig/registerdns on the client
*.On windows XP, Open Windows Explorer and go to C:\Documents and Settings\User\Application Data\Microsoft\Crypto\RSA\ folder and Delete the RSA key subfolder.
Fixing lync 2013:
1. The lync client will able to resolve the full qualified domain name of front end server.
2. After finding the fqdn then client looking for the auto configuration .
3. The client check the domain ,any front end server with the name of using srv record.
4. If the server find the domain, The client looking for the certificate.
5. The server and client certificate need trustworthy.
6. If all ok, then authentication will happen with ntlm or Kerberos.
If you meet this issue Then you can follow these steps to troubleshoot your lync 2013 lync client.