How can I manually verify autodiscovery configuration for on premise environment from Lync 2013 desktop client?

Question

I have very limited access to an environment (basically just user access). I am documenting the Lync 2013 cilent for this environment. I was provisioned a limited SIP enabled account for testing. Autodiscovery from the Lync 2010 client works, but not from
the 2013 client. I can connect (with some issues) from either 2010 client (autodiscovery) and 2013 client (manually configuring the server). So I want to verify if the Autodiscover is configured correctly to work with the 2013 client or not and if the reason
it fails for me is due to something wrong with my account or if this will happen with other users?
I have checked the lyncdiscoverinternal.domain.com and it resolves and is reachable. I can navigate to https :// lyncdiscoverinternal.domain.com/Autodiscover/AutodiscoverService.svc/root/domain and it returns the information I would think it should
including hrefs to Internal/Autodiscover, Internal/AuthBroker, External/Autodiscover, External/AuthBroker, Internal/Mcx & External/Mcx as well as fqdns for SipClientExternalAccess, SipClientInternalAccess, SipServerExternalAccess & SipServerInternalAccess.
The AuthBrokers urls return what I believe is the expected RemoteService Service pages. The Mcx urls return what I believe is the expected McxService2 Service pages. The SipClientInternalAccess & SipServerInternalAccess fqdns are both resolvable and
reachable. The Autodiscover urls return hrefs for Domain and User. Those Domain urls return the same information as the initial root/domain url and the user url (which I believe is the one that is actually opened by lync during the autodiscover process) returns
what I believe is an expected 401 - Unauthorized: Access is denied due to invalid credentials page.
If I explicitly configure the Lync 2013 client to use the fqdn listed for SipClientInternalAccess, the client will log me in. However on Automatic configuration, it fails to log me in.
One other note is that when I watch with Wireshark, I observed that it is getting another internal server fqdn from somewhere. We'll just say that the SipClientInternalAccess fqdn is lyncABC.domain.internal. When looking at Wireshark and the DNS requests,
I'm also seeing a lync2013ABC.domain.internal that does resolve and is reachable and can also be used as the explicitly listed server in the Lync 2013 client and it will log in. However, that fqdn is not listed in any of the root or domain url replies. So
I'm not sure where it is coming from or how to check that.
Is there any additional information anywhere that can tell me exactly what the behavior of the 2013 client is when trying to find the server to authenticate to and how I can reproduce any missing steps manually to determine what it is identifying as the
login server (if any) since it is obviously not the trying the one listed as SipClientInternalAccess?
Thanks,
Richard

Answer 1

Hi Richard,
To narrow down the issue, you could refer to the following steps first.
1. Delete the Lync client 2013 user profile and registry key.
User profile:
%userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]
Registry Key:
HKCU\Software\Microsoft\Office\15.0\Lync\[email protected]
Certificate:
a. Open Windows Certificate Manager. To do this, press Windows + R, type certmgr.msc, and then click OK.
b. Expand Personal, and then expand Certificates.
c. Look for a certificate that's issued by Communications Server and delete it.
2. Upgrade Lync client to the latest update.
3. Check the DNS records(A records and SRV records) again.
Best regards,
Eric