Преимущество Microsoft Cluster по Microsoft Network Load Balancer
Вы видите ошибки при записи HD в журнале ядра? Удостоверьтесь, что проверили статистику S.M.A.R.T. диска, например: http://www.captain.at/howto-linux-smartmontools-smartctl.php
Кроме того, поврежденная память могла вызвать поврежденные файлы. У Вас есть удаленный доступ KVM к машине? В этом случае необходимо выполнить memtest или подобный (http://www.memtest.org/)
That's not how NLB works. The NLB port rule determines what port/ports are load balanced amongst the NLB hosts. Traffic not "bound" to a NLB port rule is not load balanced amongst the NLB hosts. NLB does not monitor the port/ports associated with a port rule and disable NLB cluster traffic to that host upon a close of that/those port/ports or the crash of an application providing services on that/those port/ports on a particular host. NLB uses a Layer 2 "heartbeat" to determine the availability of a host in the cluster. If a host fails the heartbeat mechanism then all of the other hosts will "converge" (or re-converge) removing the non-responding host from the cluster so that no cluster traffic (based on the port rule) is directed to the non-responding host. NLB is strictly a layer 3 (network layer) load balancing mechanism. It is not a layer 7 (application layer) load balancing mechanism.
It's perfectly normal to have a hung application on an NLB host (such as HTTP or RDP) defined in an NLB port rule still receiving NLB traffic even though the application isn't capable of accepting that traffic. This is because NLB isn't aware of anything above layer 3.