Microsoft Windows system with teamed NICs causes duplicate IP address
Symptom
Servers running Microsoft Windows 2003 or Windows 2000, that have teamed NICs using Broadcom Advanced Server Programs (BASP) in an active/active team, respond to other server's gratuitous ARP packet with an incorrect IP address. The Microsoft Windows server will respond to the other server sending the gratuitous ARP, with the Microsoft Windows server team MAC address, but with the other server's IP address in the sender field of the packet. This causes the other system to respond as if there is a duplicate IP on the network. This issue has been known to affect other servers running AIX, Linux, and Sun Solaris 10.
Solution
Upgrade to BASP driver version 6.2.32, or newer. This version of the BASP driver was first included with the Broadcom NetXtreme Gigabit Ethernet Software CD version 10.7b.3
Alternatively, BASP driver version 6.2.33 was included with the Broadcom NetXtreme II Gigabit Ethernet Software CD version T4.1.3
The BASP driver is independent of the NIC type (NetXtreme I or II); therefore, the BASP driver, in either of the above mentioned software CDs, will fix this issue.
Workaround
Disable the active/active NIC team and use an active/standby team instead. To fix the issue altogether, upgrade the BASP driver as described in the Fix section.
Source
To view the source of this information with additional details, please read the following IBM article.
IBM article - Microsoft Windows system with teamed NICs causes duplicate IP address