Ports used for communication in SAV 10.doc

Ports used for communication in Symantec AntiVirus 10.x and Symantec Client Security 3.x Question/Issue: This document discusses the ports that Symantec AntiVirus 10.x and Symantec Client Security 3.x use for communication between servers and clients.Solution:Installation portsThe following table describes the network protocols and ports that must to be available to perform network installations of the product: Function Location Protocol Port range Client deployment Symantec System Center TCP local ports 1024–4999 Client deployment Target clients TCP local ports 1024–5000 Client deployment Management server and target clients TCP 139 Server deployment Target servers TCP local ports 1024–5000 Server deployment Management server and target servers TCP 139, 38293 Remote installationRemote installation tools such as ClientRemote Install and AV Server Rollout use TCP port 139 on the targeted computers. If you plan to install Symantec Client Security or Symantec AntiVirus onto a computer running Windows 2003/XP, then read Windows XP Service Pack 2 or Windows Server 2003 firewall prevents remote installation.Client/server communication portsThe following table describes the network protocols and ports that must be available to perform the standard functions of the product. Configurable ports are marked with an asterisk (*). Function Location Protocol Port range General communication Symantec System Center, servers TCP local ports 1024–4999 General communication Symantec System Center, servers, clients TCP 2967* General communication NetWare servers TCP 2968* General communication Clients TCP local ports 1024–5000 RtvscanRtvscan makes a request to Winsock for TCP port 2967 on IP-based networks. This is the only port needed for default client-to-server communication. On NetWare servers, Rtvscan.nlm listens on TCP port 2968. Note: Some versions of the Administrators Guide erroneously state that Symantec AntiVirus uses port 2043. It actually us