|
To troubleshoot this problem, try one or all of the following:
- Review the event description to obtain additional details regarding why the machine has an account problem.
- In Event Viewer, click System, and then look for any networking-related messages, such as Netlogon messages, that indicate a network connectivity issue.
- At the command prompt, type netdiag, and look for any errors. Typically, these errors have to be resolved before Group Policy processing can continue.For more information about using NetDiag, see article Q265706, “DCDiag and NetDiag Facilitate Join and DC Creation,“ in the Microsoft Knowledge Base.
- At the command prompt, type gpupdate, and then check the Event Viewer to see if the Userenv events are logged again.
- To verify that the domain controller can be contacted through Domain Name System (DNS), try to access \\mydomain.com\sysvol\mydomain.com, where mydomain.com represents the fully qualified DNS name of your domain.
- Verify that you can access the domain controller by using tools such as Active Directory Users and Computers.
- Check whether other computers on your network are having the same problem.
- If this is a forest trust scenario, ensure that the forest for the user account is currently available and can be contacted from the computer where policy processing failed.
- Use verbose logging to debug this error. The log file explains the specific error.For more information about enabling userenv logging, see article 221833 , “How to Enable User Environment Debug Logging in Retail Builds of Windows” at the Microsoft Knowledge Base.
If none of the previous user actions identified the problem, follow the steps in “Troubleshooting Group Policy in Windows Server 2003” at the Microsoft Web site.
|