Cannot sign in to Lync
-
martes, 22 de mayo de 2012 14:30
Hi all,
I've installed and configured Lync and publish the topology but when I try to log in from the client I receive the folloqing error:
"Cannot sign in because the server is temporary unavailable. If the problem continues, please contact your support team."
I've already created the SRV record in the DNS _sipinternaltls._tcp.domain.local and also _sipinternal._tcp.domain.local. and I'm able to find the record with a nslookup from the client and also ping the Lync front-end server
If I use the manual configuration with the IP address or the FQDN I'm able to log in
Any suggestions?
Todas las respuestas
-
martes, 22 de mayo de 2012 16:45
Are you sure that you SRV is pointing to the right place? And that your SRV is configured with the right port?
To test SRV:
- Open cmd
- Type: nslookup
- Type: set type=all
- Type the SRV record to list its content
- Internal
- _sipinternaltls._tcp.domain.com
- Usually points to Poo or Lync standardl name with correct sip domain on port 5061
- _sipinternaltls._tcp.domain.com
Regards
JP
If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks.
Jean-Philippe Breton | Senior Microsoft Consultant | MCTS, MCITP, MCT, Lync MVP -
miércoles, 23 de mayo de 2012 1:50
Enable Event Log logging in the client and the replicate the issue. What do the errors/warnings say in the Application log?
You can also use the following tool to help troubleshoot issues:
http://www.insideocs.com/Tools/RUCT/RUCT.htmTim Harrington | MVP: Lync | MCITP: EMA 2007/2010, Lync 2010, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington
-
miércoles, 23 de mayo de 2012 2:58Moderador
Hi,
Since you are able to log in through manual configuration with the IP address or the FQDN, the issue may be caused by SRV record. Please refer to the following information to check your SRV record:
http://technet.microsoft.com/en-us/library/gg398680.aspx
http://msunified.net/2010/08/09/how-to-check-srv-records-for-ocs-and-exchange/
Regards,
Kent
-
miércoles, 23 de mayo de 2012 9:08
Hi all,
For sure the record were alòready created in DNS and were available.
I solve my problem after installing this patch on the client
http://www.microsoft.com/en-us/download/details.aspx?id=14490
Thanks to all for your answers
- Marcado como respuesta Pif2011 miércoles, 23 de mayo de 2012 9:09
.png)
