Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Windows 10 cannot join domain or access shares - The specified network name is no longer available (System error 64)

$
0
0

Hi All,

I got a peculiar problem that I cannot seem to understand. I suspect there must be something wrong with our domain configuration, as no Windows 10 machines (upgarded or clean install) is able to join (or re-join) the domain, or access any file shares on any servers. The error message is always the same:

System error 64 has occured.
The specified network name is no longer available

Checks that I've completed:

  • Windows 7 on the same machine/network OK
  • Windows 10 upgrade is not okay, Windows 10 clean install also unable to join the domain
  • ip, DNS config, DNS suffix OK
  • nslookup domain.local OK
  • nslookup domain controllers OK
  • ping domain OK
  • ping domain controllers OK
  • net use \\DC\Netlogon returns the same error
  • gpupdate returns the same error (see below)
  • No suspcious errors in the event log
  • Raised domain functionality level to Windows Server 2008 R2 
  • IPv6 enabled everywhere
  • DFS is enabled on the DCs
  • UNC hardening turned on/off (RequireMutualAuthentication=0, RequireIntegrity=0), didn't help

We have Windows SBS 2011 and a Windows 2008 R2 domain controllers. The servers are hosted with only IPv4 VPN communication enabled with site-to-site tunneling between the offices. However nothing changed in the network infrastructure since we tried upgrading Windows 7 computers.

The full GPUPDATE error message:

Computer policy could not be updated successfully. The following errors were encountered:
The processing of Group Policy failed. Windows attempted to read the file \\domain.local\SysVol\domain.local\Policies\{UID}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.

I found this thread to be quite useful and seemingly people are having the same problem, however it didn't resolve my issue:
https://community.spiceworks.com/topic/1119601-windows-10-group-policy-issue

Some people even hinted that it is a Win10 bug that wasn't yet solved in the Threshold 2 update.

Is there anyone out there who could help me? :)


Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>