Home > IT Answers > Microsoft Windows > Windows 2008 in Win 2003 SBS Domain - AD Issu...
Avonbeg
5 pts.
0
Q:
Windows 2008 in Win 2003 SBS Domain - AD Issues.
Windows Server 2008, SBS 2003, Event ID 1006, Active Directory, Group Policy, Domain management
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!
ASKED: Jul 1 2009  11:07 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Avonbeg
5 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
Last Answered: Jul 1 2009  11:07 AM GMT by Avonbeg   5 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Windows 2008 in Win 2003 SBS Domain – AD Issues. | WEBMASTERLIB.COM   0 pts.  |   Jul 1 2009  5:38PM GMT

[...] at HERE Related PostseHowToGuru ยป Best Place To Buy Multiple Domain Names?Godaddy Domain Coupons : .com [...]

 

PCJunkie   870 pts.  |   Jul 3 2009  12:41AM GMT

See if any of the scenarios match up to that of yours at Event ID 1006

 

Vijaykiran   15 pts.  |   Jul 22 2009  2:41PM GMT

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.

 
0