Link to home
Start Free TrialLog in
Avatar of Sawyer
SawyerFlag for Saudi Arabia

asked on

domain error/windows server 2003

windowsn server 2003
Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1006
Date:            17/09/2011
Time:            12:18:48 AM
User:            NT AUTHORITY\SYSTEM
Computer:      TATWEERSRV
Description:
Windows cannot bind to Tatweer.Local domain. (Local Error). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Avatar of Ryan Weaver
Ryan Weaver
Flag of United States of America image

If rebooting the server does not solve the issue, you may need to remove the server from the domain, reboot and re-add the server to the domain.
Avatar of Sawyer

ASKER

but how?? it's the domain controller
Assuming that it is the only LAN domain controller, make sure that your DNS settings points to itsef, and the DNS FSMO services points to itself.
You didn't indicate it was a domain controller.

Like ReneGe suggested, check the DNS settings.

You can also try some of the suggestions here: Event ID 1006 Source Userenv
I actually assumed it was in a domain, because I found in his original question "Tatweer.Local domain"

Cheers
I saw that too, but that message can be on any member server. Sometimes the member can't authenticate properly to the domain, caused by any number of things from firewall on and get this type of message.
ASKER CERTIFIED SOLUTION
Avatar of ReneGe
ReneGe
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial