Applies To: Windows Server 2008
Group Policy processing requires network connectivity to one or more domain controllers. The Group Policy service reads information from Active Directory and the sysvol share located on a domain controller. The absence of network connectivity prevents Group
Policy from applying to the user or computer.
The Group Policy service logs the name of the domain controller and the error code. This information appears on the
Details tab of the error message in Event Viewer. The error code (displayed as a decimal) and error description fields further identify the reason for the failure. Evaluate the error code with the list below:
This error code usually indicates that the client computer cannot find the path specified in the event.
This failure may be caused by the DFS Client not running. Refer to the Microsoft Knowledge Base article about how to resolve this failure (http://support.microsoft.com/kb/314494).
To test client connectivity to the domain controller's sysvol:
This error code usually indicates that the user or computer does not have the appropriate permissions to access the path specified in the event.
On the domain controller: Ensure the the user and computer have appropriate permission to read the path specified in the event.
To test computer and user credentials:
This error code usually indicates that the computer cannot resolve the name in the provided network path.
To test network path name resolution:
Group Policy applies during computer startup and user logon. Afterwards, Group Policy applies every 90 to 120 minutes. Events appearing in the event log may not reflect the most current state of Group Policy. Therefore, you should always refresh Group Policy
to determine if Group Policy is working correctly.
To refresh Group Policy on a specific computer:
Group Policy is working correctly if the last Group Policy event to appear in the System event log has one of the following event IDs:
Group Policy Preprocessing (Networking)
Group Policy Infrastructure
The link at end of Error Code 3 is bringing me to a very generic page, therefore the linked article is probably now gone. Can you please provide more info on troubleshooting error code 3?
go.microsoft.com/fwlink this link doesn't work
I'm getting ErrorCode 31: "A device attached to the system is not functioning" - So not one of those listed...