To troubleshoot this problem, try one or all of the following:
- In Event Viewer, review the event description. Look for additional details regarding why the computer has an account problem.
- In Event Viewer, in the System folder, check for any networking-related messages, such as Netlogon messages, that indicate a network connectivity issue.
- At the command prompt, type netdiag, and review any errors. Typically, you must resolve these errors before Group Policy processing can continue. (Netdiag is available as part of the Windows 2000 Support tools. To download the Netdiag tool, see “Windows 2000 Support Tools: Netdiag.exe Update” at the Microsoft Download Center Web site.)
- At the command prompt, type gpupdate, and then check Event Viewer to see whether the Userenv events are logged again.
- Verify that the domain controller can be contacted through Domain Name System (DNS), by trying 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 the Active Directory Users and Computers.
- Check to see 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 information about enabling userenv logging, see article 221833, How to Enable User Environment Debug Logging in Retail Builds of Windows, in the Microsoft Knowledge Base.)
If none of the above actions identified the problem, see Troubleshooting Group Policy in Windows Server 2003, at the Microsoft Website.