Network location server Certificate binding fails.

the certificate binding network location server has been modified. without correct certificate, connectivity directaccess clients located in internal network not work expected.

1. certificate binding has been changed process or application.
2. certificate not bound 1 or more ip addresses on internal interface.

1. ensure certificate binding has not been modified network location server.
2. if bind port 62000 certificate use different application,  ensure network location server configured use same certificate binding application.
3. ensure certificate bound ip addresses on internal interface.

i have couple weeks old single server da deployment encountered error.  problem began during nighttime, when no changes had been made server @ least week, perplexed.  certificates issued fine, because valid until 2020.  external clients connecting through da fine, when connected myself lan had issues: couldn't network drives or resolve server name rdp or ping, yet nslookup resolve server names.  event viewer had many errors related not being able reach dc, etc.

what found issue simpler suggest answer:

the directaccess-nls.mydomain dns entry had disappeared dns servers.  assume got scavenged, explains why happened @ odd hour.  da server must not update record automatically (my da server has static ip)?

i went in , set directaccess-nls.mydomain static entries in dns myself (both ipv4 , ipv6), , after reboot begain work me.

as additional precaution myself in case happens again, changed da policy relax dns name resolution "use local name resolution kind of dns resolution (least restrictive)", have read it, might have allowed computer function bit more on lan when directaccess-nls became unavailable.

(i glad rolled out da 2 pcs spend 90%+ of time outside network, plus own until totally sure solution rock solid!  have been disruptive issue if had clients @ our offices not being able corporate resources unless left office.)

Windows Server  >  Network Infrastructure Servers