Windows 2008 in Win 2003 SBS Domain – AD Issues.

5 pts.
Tags:
Active Directory
Domain management
Event ID
Group Policy
SBS 2003
Windows Server 2008
Hi, I'm trying to help sort out some teething issues with a Win2008 Std Svr incorporated into an existing Win2k3 SBS Domain. The 2008 Svr was preped to join the existing SBS Domain as a seconday member server. But they have recently being having access issues & the Sys Log is displaying Event ID 1006 (Processing of Group Policy Failed). Any suggestions or advice? Thanks in advance!

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Avonbeg
    [...] at HERE Related PostseHowToGuru » Best Place To Buy Multiple Domain Names?Godaddy Domain Coupons : .com [...]
    0 pointsBadges:
    report
  • PCJunkie
    See if any of the scenarios match up to that of yours at Event ID 1006
    870 pointsBadges:
    report
  • Vijaykiran
    There are different flavours for this event depending on the actual description of the reason why the computer was unable to bind to the domain controller: - Invalid Credentials - This indicates that the computer was able to find and attempt to connect to the domain controller but the credentials used to authenticate itself were incorrect. In most cases this is a sign of incorrect DNS configuration. - Local Error - This shows that the computer didn't get that far as to connect to a domain controller (there was a problem locally). For example, having TCP/IP Filtering enabled on the network card may stop the local computer from connecting to the domain controller using the TCP/389 (LDAP) protocol. - Timeout - When this is recorded, it appears that the computer did find the domain controller but when it tried to connect to it the connection request timed out.
    15 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following