Windows Server 2003. Restore the IP reachability of the cluster when the resource is moved

There is a cluster on Windows Server 2003. After migration of the resource "IP address cluster" from one server to another, IP reachability cluster is recovering for 5-10 minutes. This is due to the feature of TCP/IP, third-party network device did not immediately understand what cluster IP address went to another server (on another network card) and continues to break on is not active, in my case it clusterseven virtual machine Virtual Server 2005 which is Windows Server 2003. If a third-party device in the status window of the network adapter, click "fix", that IP reachability is restored.

As a variant I consider a crutch that will ping your cluster, let's say once a minute and restarted the network adapter. Is there a standard solution to this problem, without crutches, which would reduce the total transfer time of resources?
October 8th 19 at 02:17
2 answers
October 8th 19 at 02:19
October 8th 19 at 02:21
Strangely, the cluster as configured?
standard NLB in multicast mode is a great way to instantly switch treatment to another machine.

Find more questions by tags Windows ServerNetwork administrationIPclusters