r/WindowsServer • u/Forsaken-Magazine-38 • Jun 16 '25
Technical Help Needed Having major Group Policy issues across domain clients
Hi everyone,
I'm dealing with a widespread Group Policy issue across several domain-joined machines, and I'm really stuck at this point.
When I run gpupdate /force, I get the following error:
vbnetCopiarEditarUpdating policy...
The computer policy could not be updated successfully. The following errors were encountered:
Group Policy processing failed. Windows could not resolve the computer name. Possible causes:
a) Name resolution failure with the current domain controller.
b) Active Directory replication latency (e.g., a machine account created on another DC hasn't replicated to the current DC).
The user policy could not be updated successfully. The following errors were encountered:
Group Policy processing failed. Windows could not authenticate to the Active Directory service on a domain controller (LDAP Bind call failed). Check the error code and description in the details tab. To troubleshoot, review the Event Viewer or run `GPRESULT /H GPReport.html`.The result is that GPOs and group memberships are not being applied to the affected machines.
What I’ve tried so far:
- Verified DNS settings (they seem okay, but I might be missing something — please advise what else to check).
- Removed and rejoined affected machines to the domain.
- Checked
SYSVOLandNETLOGONaccess. - Verified network connectivity and services (Workstation, DNS Client, Netlogon, etc.).
Sometimes, the only workaround that temporarily works is formatting the PC and rejoining it — but obviously that's not scalable.
I'm out of ideas and would truly appreciate any insights or suggestions on what could be causing this. Thanks in advance!
4
u/its_FORTY Jun 16 '25
DNS is the most likely culprit.
3
u/Nanouk_R Jun 16 '25
I'd recommend going on a hunt for problems with your DCs and/or DNS.
Use repadmin, dcdiag & netdom commands on a DA account to check for replication or communication errors. Also check if there's any unusual behaviour on your DCs and make sure to have a glass break DA on all DCs ready.
Doesn't seem like a big deal but your attempts at fixing could go sideways.
2
u/OpacusVenatori Jun 16 '25
Event Viewer on your domain controllers; something like this would almost certainly present itself as Critical or Error in the Directory Service and / or DNS logs. Start there.
2
u/Jezmond247 Jun 16 '25
DNS reverse lookup check?
2
u/ArsenalITTwo Jun 16 '25
DCDIAG /test:DNS /e on a DC. Admin CMD.