Hi Guys,

I have a little issue with lync 2013 mobile client. We have a lync 2013 environment. For testing purposes we use private CA for the issued certificates before we buy the publics. The CA certificate is  installed on the mobile phones. Now we have the following behavior:

The Lync 2010 client works fine on Android and Ipad.

The lync 2013 client can sign in on Andriod and Ipad, can send and receive message but: After sending or receiving a message it disconnects saying: failed to process the server response. If I do not send message it stays connected.

On windows phone , neither client can sign in.

Lync connectivity analyzer comes green, saying the environment meets the minimum requirements for mobile apps.

Can anyone help what is wrong with the 2013 mobile client and why does this behavior?

Thanks,

Gabor

Hi,

Please make sure that you have add HTTP URLs in the CRL.

For WP8 root certificates need to have HTTP URLs in the CRL (Certificate Revocation List). If root certs doesnt contain these CRL attributes than the certificate wont be accepted by WP8 and sign in would fail.

Best Regards,

Eason Huang

Ok, I will check the CA cert. And what about the failed to process response from server message? Any idea?

So , how do I have the CRL attributes in the root cert? The CRL paths are set at the extension tab of the certificate authority properties. Issued certificates contain these urls, but no such attribute in the root certificate.

Hi,

You can create a CRL distribution point for internal certificate authority with the help of the link below:

http://blogs.technet.com/b/nexthop/archive/2012/12/17/creating-a-certificate-revocation-list-distribution-point-for-your-internal-certification-authority.aspx

Best Regards,

Eason Huang

Seems strange this issue is marked as resolved (by the person answered :) )

How could an internal CRL setting resolve issues with a mobile client?  Mobile client only hits reverse proxy and an edge server, shall CRL for public certs be checked? If so then fixing internal CA CRL is not an answer (I have a similar issue, and CRL is configured by default via LDAP, which is ok as the edge is domain member)

The issue with the clients have gone after upgrading the frontend with the latest CU.

• Proposed as answer by Emin Huseynov Monday, March 02, 2015 3:06 PM

The issue with the clients have gone after upgrading the frontend with the latest CU.

• Proposed as answer by Emin Huseynov Monday, March 02, 2015 3:06 PM

The issue with the clients have gone after upgrading the frontend with the latest CU.

• Proposed as answer by Emin Huseynov Monday, March 02, 2015 3:06 PM

Thanks, solved my issue with installing CU on edge and frontend (CU Feb 2015)

Proposing your solution as an answer (instead of completely unrelated CRL thing)