Hi, We have about 30+ 2003 domain controllers in the domain, we have noticed this issue from past few months on all the domain controllers at least once. Symptoms - They provide all the services like authentication, DHCP lease, DNS etc. - We cannot connect to the domain controller in anyway, no RDP, no locally on console, even monitoring tool cannot collect resource info from the DCs when they are unresponsive. - Only resolution is to reboot the server and everything is normal. - We don’t see anything particular on logs - Lsass.exe takes up lot of memory. - We have seen this only on domain controllers and sometimes multiple DCs at one time. As we cannot connect to the server not sure what to capture. We suspect there is some memory leak. Please advise. Thanks

Hello please see that: http://support.microsoft.com/kb/308356 This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

http://support.microsoft.com/kb/810585Darshana Jayathilake

In addition to Mr X. Check this blog. Also check the performance tuning guide. Thanks

Thanks for input but This article applies to Windows server 2000 Domin controller. As I mentioned above we have all 2003 domain controllers

Hi, Microsoft KB article 810585 does not apply to Windows Server 2003, others apply to Windows Server 2003. Regards, Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

We were able to resolve this, Typically this started happening only once we went through round of driver updates. this cased to enable some SNMP feature which caused an issue. This articale helped us http://support.microsoft.com/kb/948496