Very strange issue here, we run a Lync 2010 environment but to ease issues we were having migrating users to Office 365 (Exchange) we upgraded everyone to Office 2013 which now includes the Lync 2013 client. Internally there are no issues with signing in, nor if a user is connected to the VPN from outside but now almost all laptop users now use Direct Access instead of VPN. If they're on DA then the automatic configuration settings will not work on the Lync 2013 client to sign-in, instead I have enter the manual internal and external server settings. This isn't optimal because those settings will probably change when we upgrade to 2013 front-ends, director, & edge.

I've verified everything in the NRPT table is correct so Lync is bypassing DA for sign-in and the automatic settings work externally from a non-domain joined computer, it's only DA that causing the issue.

Any ideas would be much appreciated!

Cheers

Eric

Hi Diocletian,

Microsoft DirectAccess is purely based on IPV6 and Lync 2013 is fully supporting IPV6, but Lync Server 2010 does not support IPV6.

Check out this article,

IPv6 Support in Microsoft Products and Services

Also have a look at this article,

http://social.technet.microsoft.com/wiki/contents/articles/19407.running-lync-2013-client-on-directaccess-computer.aspx

Best regards,

Eric

That's why the NRPT table entries are made, that way Lync bypasses DA and uses external DNS resolution. Our Lync 2010 clients on DA work fine, it's just the Lync 2013 clients on DA that are homed on 2010 front-ends.

Hi Diocletian,

Please try adding these FDQN to the Direct Access Exclusion:

Sip.contoso.com
_sip._tls.contoso.com
Web.contoso.com
Av.contoso.com
poolname.consoto.com
Web-external.contoso.com
Meet.contoso.com
Dialin.contoso.com
autodiscover.contoso.com
owa.contoso.com
lyncdiscover.contoso.com
lyncdiscoverinternal.contoso.com

Please let me know whether or not it works.

Best regards,

Eric

So you have confirmed that the srv record and the resulting returned FQDN lookup is occurring via external DNS?

Have you also confirmed that once you enter manual settings that the client is connecting to the external edge rather than internal? Hold shift and right click the Lync task tray icon and select "Config Info" to get the details.