Benutzer mit den meisten Antworten
GPO Replikation Netzwerkname konnte nicht gefunden werden. Sysvol nicht freigegeben.

Frage
-
Hallo zusammen,
Ich habe zwei DCs, einen Windows Server 2012 (zakservernew) und einen Windows Server 2019 (zakdc).
Den letzteren habe ich vor ca. 2 Monaten der Domäne gejoint und zum PDC etc. gemacht, das hat an sich auch ganz gut funktioniert. Und es hat auch alles ordnungsgemäß repliziert. Aber jetzt wollte ich eine neue Gruppenrichtlinie erstellen, dabei gibt mir der neue Server den Fehler aus: Der Netzwerkname konnte nicht gefunden werden. Daraufhin wollte ich mir den SYSVOL Ordner anschauen, der war jedoch auf dem neuen Server leer, auf dem alten Server waren die Policies etc. noch da. Dabei ist mir auch noch aufgefallen, dass auf dem neuen Server gar keine Sysvol Freigabe existiert. Deswegen habe ich dann den Sysvol Ordner einfach freigegeben (macht man das so?)
Über Sites and Services wollte ich danach dann eine Replikation erzwingen, hat aber nicht geklappt. Der Fehler im GPM des neuen DCs hat sich nur geändert zu: The System cannot find the path specified. Und unter Sysvol ist immer noch nichts zu finden.
Danach habe ich noch auf beiden Servern repadmin etc. ausprobiert, die aufgetreten Fehler aber nicht beheben können. Deswegen stelle ich mal die Outputs der zwei Server hier rein, ich hoffe ihr könnt mir weiterhelfen.
ZAKDC:
dcdiag /fix
Testing server: Default-First-Site-Name\ZAKDC
Starting test: Connectivity
......................... ZAKDC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\ZAKDC
Starting test: Advertising
Warning: DsGetDcName returned information for \\ZAKSERVERNEW.zaknew.forest, when we were trying to reach
ZAKDC.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... ZAKDC failed test Advertising
Starting test: FrsEvent
......................... ZAKDC passed test FrsEvent
Starting test: DFSREvent
There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing
SYSVOL replication problems may cause Group Policy problems.
......................... ZAKDC failed test DFSREvent
Starting test: SysVolCheck
......................... ZAKDC passed test SysVolCheck
Starting test: KccEvent
......................... ZAKDC passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... ZAKDC passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... ZAKDC passed test MachineAccount
Starting test: NCSecDesc
......................... ZAKDC passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\ZAKDC\netlogon)
[ZAKDC] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
......................... ZAKDC failed test NetLogons
Starting test: ObjectsReplicated
......................... ZAKDC passed test ObjectsReplicated
Starting test: Replications
......................... ZAKDC passed test Replications
Starting test: RidManager
......................... ZAKDC passed test RidManager
Starting test: Services
......................... ZAKDC passed test Services
Starting test: SystemLog
......................... ZAKDC passed test SystemLog
Starting test: VerifyReferences
......................... ZAKDC passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : zaknew
Starting test: CheckSDRefDom
......................... zaknew passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... zaknew passed test CrossRefValidation
Running enterprise tests on : zaknew.forest
Starting test: LocatorCheck
......................... zaknew.forest passed test LocatorCheck
Starting test: Intersite
......................... zaknew.forest passed test Intersiterepadmin /showrepl
Default-First-Site-Name\ZAKDC
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: a8a46986-e6dd-4163-b739-3f0f59197c44
DSA invocationID: c1b31cf0-6c2a-47dc-9f56-094a777f72e4
==== INBOUND NEIGHBORS ======================================
DC=zaknew,DC=forest
Default-First-Site-Name\ZAKSERVERNEW via RPC
DSA object GUID: 5fd2278b-ed50-4661-9210-22a1d4d50809
Last attempt @ 2020-02-21 17:32:04 was successful.
CN=Configuration,DC=zaknew,DC=forest
Default-First-Site-Name\ZAKSERVERNEW via RPC
DSA object GUID: 5fd2278b-ed50-4661-9210-22a1d4d50809
Last attempt @ 2020-02-21 17:32:04 was successful.
CN=Schema,CN=Configuration,DC=zaknew,DC=forest
Default-First-Site-Name\ZAKSERVERNEW via RPC
DSA object GUID: 5fd2278b-ed50-4661-9210-22a1d4d50809
Last attempt @ 2020-02-21 17:32:04 was successful.
DC=DomainDnsZones,DC=zaknew,DC=forest
Default-First-Site-Name\ZAKSERVERNEW via RPC
DSA object GUID: 5fd2278b-ed50-4661-9210-22a1d4d50809
Last attempt @ 2020-02-21 17:32:04 was successful.
DC=ForestDnsZones,DC=zaknew,DC=forest
Default-First-Site-Name\ZAKSERVERNEW via RPC
DSA object GUID: 5fd2278b-ed50-4661-9210-22a1d4d50809
Last attempt @ 2020-02-21 17:32:04 was successful.netdom /query fsmo
Schema master ZAKDC.zaknew.forest
Domain naming master ZAKDC.zaknew.forest
PDC ZAKDC.zaknew.forest
RID pool manager ZAKDC.zaknew.forest
Infrastructure master ZAKDC.zaknew.forest
The command completed successfully.ZAKSERVERNEW:
dcdiag /fix
Home Server = ZAKSERVERNEW
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\ZAKSERVERNEW
Starting test: Connectivity
......................... ZAKSERVERNEW passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\ZAKSERVERNEW
Starting test: Advertising
......................... ZAKSERVERNEW passed test Advertising
Starting test: FrsEvent
......................... ZAKSERVERNEW passed test FrsEvent
Starting test: DFSREvent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... ZAKSERVERNEW passed test DFSREvent
Starting test: SysVolCheck
......................... ZAKSERVERNEW passed test SysVolCheck
Starting test: KccEvent
......................... ZAKSERVERNEW passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... ZAKSERVERNEW passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... ZAKSERVERNEW passed test MachineAccount
Starting test: NCSecDesc
......................... ZAKSERVERNEW passed test NCSecDesc
Starting test: NetLogons
......................... ZAKSERVERNEW passed test NetLogons
Starting test: ObjectsReplicated
......................... ZAKSERVERNEW passed test ObjectsReplicated
Starting test: Replications
......................... ZAKSERVERNEW passed test Replications
Starting test: RidManager
......................... ZAKSERVERNEW passed test RidManager
Starting test: Services
......................... ZAKSERVERNEW passed test Services
Starting test: SystemLog
......................... ZAKSERVERNEW passed test SystemLog
Starting test: VerifyReferences
......................... ZAKSERVERNEW passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : zaknew
Starting test: CheckSDRefDom
......................... zaknew passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... zaknew passed test CrossRefValidation
Running enterprise tests on : zaknew.forest
Starting test: LocatorCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
......................... zaknew.forest failed test LocatorCheck
Starting test: Intersite
......................... zaknew.forest passed test Intersitereapdmin /showrepl
Default-First-Site-Name\ZAKSERVERNEW
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 5fd2278b-ed50-4661-9210-22a1d4d50809
DSA invocationID: 5fd2278b-ed50-4661-9210-22a1d4d50809
====INBOUND NEIGHBORS ======================================
DC=zaknew,DC=forest
Default-First-Site-Name\ZAKDC via RPC
DSA object GUID: a8a46986-e6dd-4163-b739-3f0f59197c44
Last attempt @ 2020-02-21 17:31:48 was successful.
CN=Configuration,DC=zaknew,DC=forest
Default-First-Site-Name\ZAKDC via RPC
DSA object GUID: a8a46986-e6dd-4163-b739-3f0f59197c44
Last attempt @ 2020-02-21 17:31:48 was successful.
CN=Schema,CN=Configuration,DC=zaknew,DC=forest
Default-First-Site-Name\ZAKDC via RPC
DSA object GUID: a8a46986-e6dd-4163-b739-3f0f59197c44
Last attempt @ 2020-02-21 17:31:48 was successful.
DC=DomainDnsZones,DC=zaknew,DC=forest
Default-First-Site-Name\ZAKDC via RPC
DSA object GUID: a8a46986-e6dd-4163-b739-3f0f59197c44
Last attempt @ 2020-02-21 17:44:10 was successful.
DC=ForestDnsZones,DC=zaknew,DC=forest
Default-First-Site-Name\ZAKDC via RPC
DSA object GUID: a8a46986-e6dd-4163-b739-3f0f59197c44
Last attempt @ 2020-02-21 17:44:07 was successful.
netdom /query fsmo
Schema master ZAKDC.zaknew.forest
Domain naming master ZAKDC.zaknew.forest
PDC ZAKDC.zaknew.forest
RID pool manager ZAKDC.zaknew.forest
Infrastructure master ZAKDC.zaknew.forest
The command completed successfully.
Vielen Dank im Voraus!
Antworten
-
Hallo Leuchtekulli,
kann es sein das dsa SysVol noch aus der Vergangenheit mit File Replication Service und nicht mit DFS-R betrieben wird? Schau dir mal diesen KB Artikel an: https://support.microsoft.com/de-de/help/2958414/dfs-replication-how-to-troubleshoot-missing-sysvol-and-netlogon-shares
Viele Grüße / Kind regards
Fabian Niesen
---
Infrastrukturhelden.de (German) - Infrastructureheroes.org (English)
LinkedIn - Xing - Twitter
#Iwork4Dell - Opinions and Posts are my own
My post are provided as they are. Usage is on your own risk.- Als Antwort vorgeschlagen Martin Schroedl Mittwoch, 26. Februar 2020 07:12
- Als Antwort markiert Yavor TanevMicrosoft contingent staff Montag, 2. März 2020 10:57
Alle Antworten
-
Hallo Leuchtekulli,
kann es sein das dsa SysVol noch aus der Vergangenheit mit File Replication Service und nicht mit DFS-R betrieben wird? Schau dir mal diesen KB Artikel an: https://support.microsoft.com/de-de/help/2958414/dfs-replication-how-to-troubleshoot-missing-sysvol-and-netlogon-shares
Viele Grüße / Kind regards
Fabian Niesen
---
Infrastrukturhelden.de (German) - Infrastructureheroes.org (English)
LinkedIn - Xing - Twitter
#Iwork4Dell - Opinions and Posts are my own
My post are provided as they are. Usage is on your own risk.- Als Antwort vorgeschlagen Martin Schroedl Mittwoch, 26. Februar 2020 07:12
- Als Antwort markiert Yavor TanevMicrosoft contingent staff Montag, 2. März 2020 10:57
-
Hallo Fabian,
das Problem war zwar nicht FSR, aber der Artikel hat mir trotzdem weitergeholfen.
Als ich nämlich in den Event Viewer geschaut habe, war da das Event 2213, die DFSR Datenbank ist nicht richtig heruntergefahren worden, danach habe ich einfach die Schritte des entsprechenden Artikels befolgt und jetzt klappt alles wieder.
Vielen Dank für die schnelle Hilfe!
-
Hallo Leuchtekulli,
wenn der Hinweis geholfen hat, markiere meine Antwort bitte als Lösung, dann finden andere Suchende das auch schneller.
Vielen Dank
Viele Grüße / Kind regards
Fabian Niesen
---
Infrastrukturhelden.de (German) - Infrastructureheroes.org (English)
LinkedIn - Xing - Twitter
#Iwork4Dell - Opinions and Posts are my own
My post are provided as they are. Usage is on your own risk.