Symantec AntiVirus quick communications check

Symantec.com > Enterprise > Support > Knowledge Base

Symantec AntiVirus quick communications check

Question/Issue:
You experience communication problems between computers that run Symantec AntiVirus server, Symantec AntiVirus client, or the Symantec System Center. You need a quick way to confirm basic communication.

Solution:
Use the ping, netstat, and telnet commands to confirm basic communication between managed clients and servers.

Confirm network communication
Make sure that the clients and the parent server can communicate.

To confirm network communication

On the parent server, open a command prompt and ping the client by computer name.
For example, type ping <client1>
where <client1> is the computer name of the client.
The command should return the client's correct IP address.
On the parent server, open a command prompt and use the ping -a command with the client's IP address.
For example, type ping -a 192.168.0.1
where 192.168.0.1 is the client's IP address.
The command should return the client's correct fully qualified domain name.
On the client, open a command prompt and ping the parent server by computer name.
For example, type ping <server1>
where <server1> is the computer name of the parent server.
The command should return the parent server's correct IP address.
On the client , open a command prompt and use the ping -a command with the parent server's IP address.
For example, type ping -a 192.168.0.2
where 192.168.0.2 is the parent server's IP address.
The command should return the parent server's correct fully qualified domain name.

If network communication fails, fix any problems on your network that are related to DNS or name resolution.

Confirm that Symantec AntiVirus works correctly on the parent server
On the parent server, confirm that the Symantec AntiVirus service is started and that the correct ports are open. The default port is 2967. If you configured a custom port, then look for that port number when you follow these directions.

To confirm that the correct ports are open on the parent server

At a command prompt, type the following command:netstat -a
Do one of the following:
- On a Symantec AntiVirus 10.x server, confirm that TCP port 2967 appears and that the port's status is LISTENING
- On a Symantec AntiVirus 10.x server that manages legacy clients, confirm that UDP port 2967 also appears and that the port's status is LISTENING
- On a Symantec AntiVirus 9.x or earlier server, confirm that UDP port 2967 appears and that the port's status is LISTENING
If the correct ports are not open, restart the Symantec AntiVirus service.
If the correct ports are not open after you restart the Symantec AntiVirus service, look at the Windows Event Viewer - Application log for error messages.

Confirm that you can connect with the Symantec AntiVirus service
The default port is 2967. If you configured a custom port, then use that port number when you follow these directions.

To confirm communication with the telnet command

NOTE: This is only valid for the 10.x product as 8.x and 9.x use udp and should be tested with a udp port tester.

On the parent server, at a command prompt, type the following command:

telnet localhost 2967

If successful, you briefly see the text "Connected to <computer>" and then a blank screen with a flashing cursor.
If unsuccesful, make sure that a firewall is not configured to block the communication.
To exit, press CTRL + ] and then type quit.
From a remote computer, such as a secondary server, managed client, or a computer that runs Symantec System Center, telnet to port 2967 by using the parent server's IP address.
For example, type telnet 192.168.0.2 2967
where 192.168.0.2 is the parent server's IP address.

If successful, you briefly see the text "Connected to <computer>" and then a blank screen with a flashing cursor.
If unsuccesful, make sure that a firewall is not configured to block the communication.
To exit, press CTRL + ] and then type quit.

If you can confirm communication by using the ping, netstat, and telnet commands but still experience communication problems, read the document for your program version:

Document ID: 2005051106541348
Last Modified: 02/25/2009
Date Created: 05/11/2005
Operating System(s): Windows 2000, Windows XP Home, Windows XP Professional Edition, Windows XP Tablet PC, NetWare 5.1, NetWare 6.0, NetWare 6.5, Windows XP 64-Bit Edition 2003, Windows Server 2003 32-bit Edition, Windows Server 2003 64-bit Edition, Windows XP Media Center Edition 2005, Windows 98, Windows Me, Windows NT 4.0 SP6a, Windows 2000 Professional, NetWare 5.0
Product(s): Symantec AntiVirus 10.1, Symantec AntiVirus Corporate Edition 10.0, Symantec AntiVirus Corporate Edition 8.0, Symantec AntiVirus Corporate Edition 9.0, Symantec Client Security 3.0, Symantec Client Security 3.1
Release(s): SAV 10.0 [All Releases], SAV 8.0 [All Releases], SAV 9.0 [All Releases], Symantec AntiVirus 10.1 [All Releases], Symantec Client Security 3.1 [All Releases], Symantec Client Security 3.x [All versions]