Windows Server 2003. Cluster IP Reachability Recovery on Resource Move?

Question

Clusters

There is a cluster on Windows Server 2003. After transferring the "Cluster IP address" resource from one server to another, the cluster's IP reachability is restored in 5-10 minutes. This is due to a feature of the TCP / IP protocol, a third-party network device does not immediately understand that the cluster IP address has moved to another server (to another network card) and continues to break into a no longer active one, in my case it is a clustered Virtual Server 2005 virtual machine on which costs Windows Server 2003. If on a third-party device in the network adapter status window you click the "fix" button, then IP reachability is restored.

As an option, I am considering a crutch that will ping the cluster once per minute and restart the network adapter. Is there a standard solution to this problem, without crutches, that would reduce the overall transition time of resources?

Answer 1

www.microsoft.com/download/en/details.aspx?id=8005

Answer 2

Strange, how is the cluster configured?
standard NLB in multicast mode in the most excellent way instantly switches calls to another machine.