Network Connectivity Issues on Intel Teamed Network Interface Cards (NICs) when Symantec AntiVirus (SAV) or Symantec Endpoint Protection (SEP) Client is installed.
Last Updated September 28, 2011
Computers Running Windows 2003 Service Pack 2 (SP2) with teamed Intel NICs experience intermittent network connectivity issues when the Antivirus/Antispyware portion of Symantec AntiVirus or Symantec Endpoint Protection is installed.
Symptoms Network connectivity is limited in the following ways:
Other computers will no longer be able to ping the Internet Protocol (IP) address assigned to the Team reliably.
Connectivity to external servers (Active Directory Domain Server, Active Directory Global Catalog Server, Domain Name System (DNS), Dynamic Host Control Protocol (DHCP), Exchange etc) is limited or not possible.
Removing the Team from the Network Control Panel restores normal communications.
Removing the SAV/SEP client from the computer restores normal communications.
This issue may be caused by inconsistencies introduced into the network stack when using certain versions of Intel's Advanced Networking Services (iANDS) NDIS Intermediate Driver. This same behavior has been observed when using other third party network filter drivers, including WireShark - a popular packet capture software.
For assistance it is recommended by Symantec that you engage your network driver provider. Intel has announced a driver release (version 14.0) containing a fix for this issue.
Upgrading the NIC driver to the latest version available version should be the first troubleshooting step!
Technical Information This has been reproduced on Windows Server 2003 server (SP2) with teamed Intel Pro/1000 MT adapters. In testing, the issue was not observed until Microsoft Windows Server 2003 was updated to Service Pack 2.
Imported Document ID: TECH104849
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe