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

[FN-GM]

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

[EduTech]

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.

[FN-GM]

I will send a copy of my cert for you to look at.

 

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

[EduTech]

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.