none
lync client is stucked in Contacting Server and Signing In

    Question

  • im having a issue with client loging, It get stucked in 'Contacting Server and Signing In' it didnt time out or show any error messages..plz help
    Friday, October 19, 2012 9:49 AM

Answers

  • Hi,

    If other machine not a member of Domain , you have to import Internal CA root Certificate to these machines.

    Regards,

    Ahmed

    Friday, October 19, 2012 10:38 AM
  • Open Web http://CAserver/Certsrv then click on Download the Certificate and save it.

    Then on any other machine open Run>mmc>add remove snap in > certificate > Computer > Local Computer and under trusted root certificate authorities click import and import exported certificate .

    Regards,

    Ahmed

    • Proposed as answer by danielategan Friday, October 19, 2012 12:42 PM
    • Marked as answer by Kent-Huang Monday, October 29, 2012 2:56 AM
    Friday, October 19, 2012 10:41 AM
  • Hi,

    Are the DNS and CA server also placed on this AD machine? Please try to import the Internal CA root certificate to test as Ahmed suggested.

    If the issue persists, please refer to the following tips to troubleshot:

    1. Since lync client on AD machine can connect to lync front end server properly, it indicated the DNS records are correct. Please try to clear your DNS cache in your client computer.

    2. Try to type the FQDN of Lync front end pool to manual sign in.

    3. If the issue persists, please try to ping DNS server, front end pool on client computer. And try to telnet front end pool on port 5061.


    Regards,

    Kent Huang

    TechNet Community Support ************************************************************************************************************************ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.



    • Edited by Kent-Huang Monday, October 22, 2012 2:49 AM
    • Marked as answer by Kent-Huang Monday, October 29, 2012 2:56 AM
    Monday, October 22, 2012 2:49 AM

All replies

  • HI,

    Did you create SRV record for Automatic Sign in

    On the DNS server, click Start, click Administrative Tools, and then click DNS.

    • In the console tree for your SIP domain, expand Forward Lookup Zones, and then right-click the SIP domain in which Lync Server 2010 will be installed.

    • Click Other New Records.

    • In Select a resource record type, click Service Location (SRV), and then click Create Record.

    • Click Service, and then type _sipinternaltls.

    • Click Protocol, and then type _tcp.

    • Click Port Number, and then type 5061.

    • Click Host offering this service, and then type the FQDN of the pool or Standard Edition server.

    • Click OK, and then click Done.

    • Regards,

    • Ahmed

    • Please Mark as answer if this post solve your issue.

    Friday, October 19, 2012 10:13 AM
  • thanks for the reply ahmed :) Yes i did create the SRV record just like you mentioned above.i think my issue might be something else :/

    Friday, October 19, 2012 10:33 AM
  • i installed lync client in AD machine and it works fine..but in the other machines i get this error
    Friday, October 19, 2012 10:34 AM
  • Hi,

    If other machine not a member of Domain , you have to import Internal CA root Certificate to these machines.

    Regards,

    Ahmed

    Friday, October 19, 2012 10:38 AM
  • Open Web http://CAserver/Certsrv then click on Download the Certificate and save it.

    Then on any other machine open Run>mmc>add remove snap in > certificate > Computer > Local Computer and under trusted root certificate authorities click import and import exported certificate .

    Regards,

    Ahmed

    • Proposed as answer by danielategan Friday, October 19, 2012 12:42 PM
    • Marked as answer by Kent-Huang Monday, October 29, 2012 2:56 AM
    Friday, October 19, 2012 10:41 AM
  • Hi,

    Are the DNS and CA server also placed on this AD machine? Please try to import the Internal CA root certificate to test as Ahmed suggested.

    If the issue persists, please refer to the following tips to troubleshot:

    1. Since lync client on AD machine can connect to lync front end server properly, it indicated the DNS records are correct. Please try to clear your DNS cache in your client computer.

    2. Try to type the FQDN of Lync front end pool to manual sign in.

    3. If the issue persists, please try to ping DNS server, front end pool on client computer. And try to telnet front end pool on port 5061.


    Regards,

    Kent Huang

    TechNet Community Support ************************************************************************************************************************ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.



    • Edited by Kent-Huang Monday, October 22, 2012 2:49 AM
    • Marked as answer by Kent-Huang Monday, October 29, 2012 2:56 AM
    Monday, October 22, 2012 2:49 AM