• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 152
  • Last Modified:

dcdiag errors

New server on line to replace existing 2003 SBS. New server is a DC, GC, and all FSMO roles transferred, DNS and DHCP on new server. Windows Firewall off for testing. System Log has errors to do with Group Policy error.

The processing of Group Policy failed. Windows attempted to read the file \\xxx.local\sysvol\xxx.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful.
 
DCDIAG run on new server results;
C:\Users\administrator.xxx>dcdiag /q
         Warning: DsGetDcName returned information for \\old server.xxx.local,
         when we were trying to reach new server.
         SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
         ......................... new server failed test Advertising
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
            Replicating Directory Changes In Filtered Set
         access rights for the naming context:
         DC=ForestDnsZones,DC=xxx,DC=local
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
            Replicating Directory Changes In Filtered Set
         access rights for the naming context:
         DC=DomainDnsZones,DC=xxx,DC=local
         ......................... new server failed test NCSecDesc
         Unable to connect to the NETLOGON share! (\\new server\netlogon)
         [new server] An net use or LsaPolicy operation failed with error 67,
         The network name cannot be found..
         ......................... new server failed test NetLogons

repadmin /replsum no errors

Old 2003 SBS Server hasn't been demoted yet.
0
rettif9
Asked:
rettif9
  • 2
1 Solution
 
DeadmanCommented:
Set the “Enable Journal Wrap Automatic Restore” registry parameter to 1

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters and HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup\BurFlags
change value as "D2" (Non-Authrotive Restore)

http://support.microsoft.com/kb/556025
Restart ntfrs service and File replication services
After that try running gpupdate /force
0
 
rettif9ManagerAuthor Commented:
The registry keys listed above didn't exist. I had to get the server running so I created a Microsoft support ticket. It ended up being rather involved. It took the Microsoft service engineer a couple of hours.
0
 
rettif9ManagerAuthor Commented:
I needed to get the problem resolved quickly.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now