With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case.
New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.

Comments:EventID.Net
As per Microsoft: "Check the system event log for errors. Check the network adapter configuration and operation. Check the TCP/IP configuration and name resolution methods. Check the WINS servers for possible database problems or static mappings that are not valid". See the link to "Windows Cluster Service Troubleshooting and Maintenance" to download the original white paper.
x
1

EventID.Net
See the link to "EventID 1052 from source Cluster Service Clussvc" for details on this event.
x
1

Anonymous
I received this event, 1052, along with an event id 1069, with the exact symptoms as published in Microsoft Knowledge Base Article - ME257903. However, although the symptoms were identical, the resolve had nothing to do with WINS or Kerberos changes.

I was running Win2k Advanced Server, SP2 in a 2 node active/active configuration. This cluster was also running SQL 2000. When I attempted fail over, it did not occur and took my Cluster Name Resource offline, never to return. As a result, neither node in the cluster could assume the resource and as such other services such as SQL Server could not be brought online.

The fix, you must create a DNS Reverse Name Lookup Zone on the DNS Server, for the network the servers use. We run private address VLAN's based on application, and we make the third octet of the IP address the same as the VLAN. We simply created a reverse lookup zone for this VLAN, flushed and refreshed DNS on the servers, and immediately we were able to bring the failed resource(s) back online. We were told by Microsoft that this was the result of a timing issue, and that SP3 corrected this problem.
x
1