+ Post New Thread
Results 1 to 4 of 4
Enterprise Software Thread, lync cannot verify the server is trusted for your sign in address in Technical; I am getting this problem here - "Lync cannot verify that the server is trusted for your sign-in address" message ...
  1. #1

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,108
    Thank Post
    892
    Thanked 1,754 Times in 1,512 Posts
    Blog Entries
    12
    Rep Power
    458

    lync cannot verify the server is trusted for your sign in address

    I am getting this problem here - "Lync cannot verify that the server is trusted for your sign-in address" message when a user tries to sign in to Lync 2013

    I would rather my certificate get fixed. But i can't see anything wrong with it? It has all the SAN names in there.

    Has anyone had this please? Maybe @EduTech can help

    Thanks

  2. #2

    EduTech's Avatar
    Join Date
    Aug 2007
    Location
    Reading
    Posts
    5,071
    Thank Post
    160
    Thanked 935 Times in 730 Posts
    Blog Entries
    3
    Rep Power
    275
    Hi,

    Can you send me a list of the names that you have in your Internal FE SAN Certificate? Ensure that the Pool FQDN Matches the one found in your SAN Cert.

    Is your Lync SIP Domain the same as the domain used in your Internal FE SAN Certificate?

    Regards,
    James.

  3. #3

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,108
    Thank Post
    892
    Thanked 1,754 Times in 1,512 Posts
    Blog Entries
    12
    Rep Power
    458
    I will send a copy of my cert for you to look at.

    The SIP domain is not the same as the FE server.

  4. #4

    EduTech's Avatar
    Join Date
    Aug 2007
    Location
    Reading
    Posts
    5,071
    Thank Post
    160
    Thanked 935 Times in 730 Posts
    Blog Entries
    3
    Rep Power
    275
    For future reference in case anyone else has the same problem,

    If you use the LyncDiscoverInternal A Record then Lync 2013 will use this over the SRV Record and as the FQDN of your STD Edition Pool will differ from your SIP Domain you will get the error explained in the KB Article. If you use a different internal FQDN from the Primary SIP Domain then you need to ensure you have the SRV Record in place and not the LyncDiscoverInternal A Record for this error message to go away.

    The reason why it happens is because when using the A Record it won't know of the Primary SIP Address and therefore throw up the error in regards to the Trust, If you use the SRV Record it will show the sip.primarySIP.tld domain and it will be aware and therefore trust it.

    I hope that makes sense, this issue is now resolved.

    James.

  5. Thanks to EduTech from:

    FN-GM (7th May 2013)

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 7
    Last Post: 16th November 2013, 01:47 PM
  2. Replies: 6
    Last Post: 15th May 2012, 09:46 PM
  3. The EU is looking for ICT Specialists
    By AndyEUCareers in forum Educational IT Jobs
    Replies: 3
    Last Post: 28th September 2011, 11:33 AM
  4. [Joke] An Update Is Available For Your Computer...
    By DaveP in forum Jokes/Interweb Things
    Replies: 2
    Last Post: 23rd February 2011, 01:03 PM
  5. Windows cannot access the file gpt.ini for GPO ID 1058
    By mullet_man in forum Windows Server 2000/2003
    Replies: 3
    Last Post: 6th March 2009, 12:21 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •