	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

6.7

Windows 2003 SP2 Domain Controllers become unresponsive until reboot

Asked by MGio4 in Domain Name Service (DNS), Windows 2003 Server, Active Directory

Tags: Microsoft, Windows Server, 2003 SP2, Event Type: Error Event ID: 4016 The DNS server timed out attempting an Active Directory service operation on ---. Check Active Directory to see that it is functioning properly., Event Type: Error Event ID:

Background:
While installing a new DC, because the SA I was replacing was on the wrong path, we discovered that DNS zones were not Active Directory Integrated. We changed zones to ADI and after discovering other issues, DEMOTED the new DC and unpublished the DC root cert for it.

Our network consists of the following:
DC1 - Windows 2003 Server Enterprise w/SP2
DC2 / Exchange Server - Windows 2003 Server Enterprise w/SP2 / Exchange - Exchange 2003 w/SP3 (please stop laughing... it's not MY choice).
Both DC's have DNS installed.
Bluecoat Proxy
Users authenticate by CAC using Valicert Desktop Validator. All certs are downloaded and cached at 24 hour intervals.

Problem:
Network will run fine for several hours (24 - 36) with no errors being reported. Out of nowhere, one or both DC's will become completely unresponsive. Upon reboot, everything begins to run fine again for another 24-36 hours. In the course of troubleshooting, I've increased the size of my security logs and have them backed up and cleared well before they fill up in accordance with Microsoft kb316685. The issue was initially occurring every 24 hours or so. After increasing event log size, the uptime seemed to increase by 12 hours or so (this may be coincidental).

DC1 appears to become unable to find itself, at which point DC2 is usually the first to become unresponsive.

I've attached events (in chron. order) from when the issues seem to start (prior to lockup). We are a military network, so for security reasons, I have replaced the actual FQDN with <FQDN> and altered actual usernames and IP info.

Any and all help is greatly appreciated.

View the Solution FREE for 30 Days

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:

           
           
             Event Type:	Error
Event Source:	Userenv
Event Category:	None
Event ID:	1006
Date:		10/8/2008
Time:		9:09:15 AM
User:		NT AUTHORITY\SYSTEM
Computer:	TACMDC1
Description:
Windows cannot bind to <FQDN> domain. (Timeout). Group Policy processing aborted. 
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------------------------
Event Type:	Error
Event Source:	Userenv
Event Category:	None
Event ID:	1030
Date:		10/8/2008
Time:		9:09:15 AM
User:		NT AUTHORITY\SYSTEM
Computer:	TACMDC1
Description:
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------
Event Type:	Error
Event Source:	BCAAA
Event Category:	(1)
Event ID:	2200
Date:		10/8/2008
Time:		9:10:29 AM
User:		N/A
Computer:	TACMDC1
Description:
[1692:1992] Cannot query domain controller 137.12.5.1; status=64:0x40:The specified network name is no longer available.
-----------------------------------------------------------------------
Event Type:	Error
Event Source:	DNS
Event Category:	None
Event ID:	4016
Date:		10/8/2008
Time:		9:12:08 AM
User:		N/A
Computer:	TACMDC1
Description:
The DNS server timed out attempting an Active Directory service operation on DC=103,DC=5.12.137.in-addr.arpa,cn=MicrosoftDNS,cn=System,DC=DOMAIN,DC=IRAQ,DC=PARENTDOMAIN1,DC=PARENTDOMAIN2,DC=MIL.  Check Active Directory to see that it is functioning properly. The event data contains the error.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 55 00 00 00               U...    
-----------------------------------------------------------------------
Event Type:	Error
Event Source:	DNS
Event Category:	None
Event ID:	4016
Date:		10/8/2008
Time:		9:12:47 AM
User:		N/A
Computer:	TACMDC1
Description:
The DNS server timed out attempting an Active Directory service operation on ---.  Check Active Directory to see that it is functioning properly. The event data contains the error.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 55 00 00 00               U...    
-----------------------------------------------------------------------
Event Type:	Error
Event Source:	Userenv
Event Category:	None
Event ID:	1006
Date:		10/8/2008
Time:		9:14:15 AM
User:		NT AUTHORITY\SYSTEM
Computer:	TACMDC1
Description:
Windows cannot bind to FQDN domain. (Server Down). Group Policy processing aborted. 
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
----------------------------------------------------------------------
Event Type:	Error
Event Source:	Userenv
Event Category:	None
Event ID:	1030
Date:		10/8/2008
Time:		9:14:15 AM
User:		NT AUTHORITY\SYSTEM
Computer:	TACMDC1
Description:
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
---------------------------------------------------------------------
Event Type:	Error
Event Source:	BCAAA
Event Category:	(1)
Event ID:	2200
Date:		10/8/2008
Time:		9:14:28 AM
User:		N/A
Computer:	TACMDC1
Description:
[1692:1992] Cannot query domain controller 137.12.5.1; status=64:0x40:The specified network name is no longer available.
--------------------------------------------------------------------
 
Event Type:	Warning
Event Source:	KDC
Event Category:	None
Event ID:	21
Date:		10/8/2008
Time:		9:14:39 AM
User:		N/A
Computer:	TACMDC1
Description:
The client certificate for the user DOMAIN\DOEJ is not valid, and resulted in a failed smartcard logon.  Please contact the user for more information about the certificate they're attempting to use for smartcard logon. The chain status was : The revocation function was unable to check revocation because the revocation server was offline.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 14 00 00 00 13 20 09 80   ..... .€
0008: 00 00 00 00 00 00 00 00   ........
---------------------------------------------------------------------
Event Type:	Error
Event Source:	Valicert Desktop Validator
Event Category:	None
Event ID:	1
Date:		10/8/2008
Time:		9:14:36 AM
User:		N/A
Computer:	TACMDC1
Description:
Certificate Revocation Status
Calling Application: lsass.exe
Certificate Name: /C=US/O=U.S. Government/OU=DoD/OU=PKI/OU=USA/CN=DOE.JOHN.David.123456789
Certificate Issuer: /C=US/O=U.S. Government/OU=DoD/OU=PKI/CN=DOD EMAIL CA-16
Certificate Serial Number: 1B8CC0
Revocation Status: Unable to verify
Validation Url: file://\\tacmdc1\crls$\emailca16.crl
Error: Memory allocation failure

           
         

20100308-EE-VQP-140 - Hierarchy / EE_QW_2_20070628

Your technology problems solved.

Close See Plans and Pricing. Try it FREE for 30 days.

Hall of Fame

1. Chris-Dent195,409
2. demazter54,057
3. wdurrett45,205
4. dariusg39,953
5. shauncro...33,570
6. henjoh0922,864
7. mkline7120,450
8. Akhater18,400
9. alanhardisty16,500
10. Springy55515,322
11. farazhkhan15,100
12. DrDave24214,950
13. ChiefIT14,284
14. Awinish13,828
15. NJComput...13,600
16. Firebar12,700
17. Mestha12,500
18. RobWill12,254
19. giltjr12,100
20. hades66610,400
21. PaciB10,001
22. PsychoFelix9,775
23. bluntTony8,753
24. jar38178,539
25. Dustin_L...8,500

1. Chris-Dent2,327,579
2. KCTS272,808
3. dariusg272,100
4. RobWill271,760
5. lrmoore209,996
6. tigermatt190,650
7. demazter159,073
8. Sembee157,702
9. jar3817155,930
10. ChiefIT150,078
11. henjoh09147,487
12. oBdA138,684
13. giltjr130,286
14. keith_ala...128,889
15. Mestha117,559
16. DrDave242117,080
17. bluntTony114,487
18. omarfarid111,898
19. hypercat110,146
20. toniur108,180
21. Bamit9993,320
22. leew88,540
23. wdurrett84,905
24. LauraEHu...81,407
25. TechSoEasy81,030

Windows 2003 SP2 Domain Controllers become unresponsive until reboot

Asked by MGio4 in Domain Name Service (DNS), Windows 2003 Server, Active Directory

Tags: Microsoft, Windows Server, 2003 SP2, Event Type: Error Event ID: 4016 The DNS server timed out attempting an Active Directory service operation on ---. Check Active Directory to see that it is functioning properly., Event Type: Error Event ID:

About this solution