5 our of 50 servers in server farm are chronic with the below issue.Environment: Sub-Domain in 9 domain forest.Issue: Servers hangs and only recovers by a force cold reboot.Symptoms: SPS links are no longer available, Shares are no longer available and RDP sessions just hang frozen.Platforms: 3-HPDL360 (ILO working), 1-Dell 2650 and1-VMO.S: 1-W2K, 4-W2K3System Error Message(s): Throughout 5 servers:~TermServDevices ID:1111~Service Control Manager ID:7000~W32Time ID:29~DCOM ID10016~Service Control Manager: ID 7026There are many system warnings that reflect the Errors that happen there after.There are manysystem information messages that reflect the warning that happen there after.However, there are also vary manysystem information alerts about Print devices failing.These are servers in a production server farm, so they do not require printing.I believe these print drivers are pulled down from the clients when they attatch in a variety of ways. (SPS, shares or RDP)Full systemanti-virus scans have been performed to rule outmassive virus infections.This domain controller has a few messages in Event Log that I am unaware if it is related.Application Log: Error: WINSCTRS ID:4314 (Parent Domain has WINS server, we do not.Directory Services Log: Error: NTDS General ID:1419Directory Services Log: Warning: NTDS KCC ID:1865Directory Services Log:: Error: NTDS KCC ID:1311Directory Services Log: Warning: NTDS KCC ID:1566DNS Server: Warning: DNS ID: 3000 (more are being suppressed due to high volume)File Replication Service: Warning: NtFrs ID: 13508 and 13509System Log: Error: MrxSmb: ID: 8003TermServDevices ID:1111and again many print alerts from all categories: info, warning and error...I have to force cold reboot multiple times a day on each server.Are the print errors just symptoms or causes?What are the possibilities here and how can I troubleshoot further.Any and all help would be greatly appreciated.~Witt Send.

Hi Martin, For the server hang issue, you can boot the problematic system with clean boot to check if the issue still exists. Steps to clean boot: 1. Click Start->Run...-> type msconfig and press Enter 2. Click Services tab and select Hide All Microsoft Services and Disable All third party Services. 3. Click Startup tab and Disable All startup items 4. Click OK and choose Restart 5. After reboot, check whether the problem still occurs If the server hang issue still continues in clean boot mode, for the further troubleshooting, you may check in the Task Manager to see which process takes the memory resources. Meanwhile, you can also use Reliability and Performance Monitor to track down what cause the performance issue. Windows Reliability and Performance Monitor http://technet.microsoft.com/en-us/library/cc755081(WS.10).aspx Windows Performance Monitor http://technet.microsoft.com/en-us/library/cc749249.aspx If you want to know the root cause of the issue, we need to analyze the performance log file. Since the forum is not the best channel to troubleshoot this issue, I would suggest that you contact Microsoft Customer Support service to troubleshoot this issue efficiently. They are the best resource for this kind of issues. You may obtain the phone numbers for specific technology request please take a look at the web site listed below: https://support.microsoft.com/common/international.aspx?iid=174859&iguid=56907522-6886-4238-a70f-a1d06a4473c7_2_2&rdpath=1 Hope the issue will be resolved soon.This posting is provided "AS IS" with no warranties, and confers no rights.