Symantec AntiVirus quick communications check

Article:TECH101284  |  Created: 2005-01-11  |  Updated: 2010-08-13  |  Article URL http://www.symantec.com/docs/TECH101284
Article Type
Technical Solution


Environment

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

  1. On the parent server, open a command prompt and ping the client by computer name.
    For example, type ping <computer name>
    where <computer name> is the computer name of the client.
    The command should return the client's correct IP address.
  2. 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.
  3. On the client, open a command prompt and ping the parent server by computer name.
    For example, type ping <computer name>
    where <computer name> is the computer name of the parent server.
    The command should return the parent server's correct IP address.
  4. 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

  1. At a command prompt, type the following command:

    netstat -a

  2. 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
  3. If the correct ports are not open, restart the Symantec AntiVirus service.
  4. 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.

 

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

    telnet localhost 2967


    If successful, you briefly see the text "Connected to " and then a blank screen with a flashing cursor.
    If unsuccesful, make sure that a firewall is not configured to block the communication.
     
  2. To exit, press CTRL + ] and then type quit.
  3. 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 " and then a blank screen with a flashing cursor.
    If unsuccesful, make sure that a firewall is not configured to block the communication.
     
  4. 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:






 



Legacy ID



2005051106541348


Article URL http://www.symantec.com/docs/TECH101284


Terms of use for this information are found in Legal Notices