We hebben een server verhuisd naar een andere locatie en vanaf het eerste moment kunnen we de shares niet meer benaderen. Ook op de server zelf kun je de shares niet in (Windows cannot access \\server\sysvol.... The network path was not found).
In de log heb ik de volgende error:
The processing of Group Policy failed. Windows attempted to read the file \\domain.local\sysvol\domain.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\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.
Dcdiag staat ook vol met fouten.
De clients hebben allemaal een juiste verbinding en als ik een niewe client wil koppelen aan het domain, dan kan ik wel de credentials invoeren maar vervolgens krijg ik de melding dat de computer niet aangemeld kan worden omdat die het netwerkpad niet kan vinden (omdat de shares niet benaderd kunnen worden).
klein stuk uit de dcdiag:
Starting test: Services
Could not open Remote ipc to [srv-dc.domain.local]: error 0x35
"The network path was not found."
......................... SRV-DC failed test Services
Starting test: SystemLog
A warning event occurred. EventID: 0x0000009D
Time Generated: 11/15/2018 21:24:13
Event String:
The hypervisor did not enable mitigations for CVE-2018-3646 for virtual machines because HyperThreading is enabled and the hypervisor core scheduler is not enabled. To enable mitigations for CVE-2018-3646 for virtual machines, enable the core scheduler by running "bcdedit /set hypervisorschedulertype core" from an elevated command prompt and reboot.
A warning event occurred. EventID: 0x000003F6
Time Generated: 11/15/2018 21:24:32
Event String:
Name resolution for the name _ldap._tcp.dc._msdcs.domain.local. timed out after none of the configured DNS servers responded.
A warning event occurred. EventID: 0x000003F6
Time Generated: 11/15/2018 21:24:33
Event String:
Name resolution for the name wpad timed out after none of the configured DNS servers responded.
A warning event occurred. EventID: 0x00001796
Time Generated: 11/15/2018 21:24:37
Event String:
Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.
A warning event occurred. EventID: 0x000727AA
Time Generated: 11/15/2018 21:24:40
Event String:
The WinRM service failed to create the following SPNs: WSMAN/srv-dc.domain.local; WSMAN/srv-dc.
A warning event occurred. EventID: 0x00000081
Time Generated: 11/15/2018 21:24:40
In de log heb ik de volgende error:
The processing of Group Policy failed. Windows attempted to read the file \\domain.local\sysvol\domain.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\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.
Dcdiag staat ook vol met fouten.
De clients hebben allemaal een juiste verbinding en als ik een niewe client wil koppelen aan het domain, dan kan ik wel de credentials invoeren maar vervolgens krijg ik de melding dat de computer niet aangemeld kan worden omdat die het netwerkpad niet kan vinden (omdat de shares niet benaderd kunnen worden).
klein stuk uit de dcdiag:
Starting test: Services
Could not open Remote ipc to [srv-dc.domain.local]: error 0x35
"The network path was not found."
......................... SRV-DC failed test Services
Starting test: SystemLog
A warning event occurred. EventID: 0x0000009D
Time Generated: 11/15/2018 21:24:13
Event String:
The hypervisor did not enable mitigations for CVE-2018-3646 for virtual machines because HyperThreading is enabled and the hypervisor core scheduler is not enabled. To enable mitigations for CVE-2018-3646 for virtual machines, enable the core scheduler by running "bcdedit /set hypervisorschedulertype core" from an elevated command prompt and reboot.
A warning event occurred. EventID: 0x000003F6
Time Generated: 11/15/2018 21:24:32
Event String:
Name resolution for the name _ldap._tcp.dc._msdcs.domain.local. timed out after none of the configured DNS servers responded.
A warning event occurred. EventID: 0x000003F6
Time Generated: 11/15/2018 21:24:33
Event String:
Name resolution for the name wpad timed out after none of the configured DNS servers responded.
A warning event occurred. EventID: 0x00001796
Time Generated: 11/15/2018 21:24:37
Event String:
Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.
A warning event occurred. EventID: 0x000727AA
Time Generated: 11/15/2018 21:24:40
Event String:
The WinRM service failed to create the following SPNs: WSMAN/srv-dc.domain.local; WSMAN/srv-dc.
A warning event occurred. EventID: 0x00000081
Time Generated: 11/15/2018 21:24:40