Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

symantec updation problem in clients

Migration User

Migration UserMar 22, 2012 12:00 AM

port no is 5900
Migration User

Migration UserMar 27, 2012 05:27 AM

Please telnet the port 8014 Regards
Migration User

Migration UserMar 27, 2012 08:01 AM

it not showing any error in sylink.log file

  • 1.  symantec updation problem in clients

    Posted Mar 20, 2012 03:16 AM

    i am using sym 11.x version and installing the symantec in my clients system and installation is successful(checked the 32 or 64bit os system) and after installation is completed (right click on sepm and update policy is clicked one or more times and restarted the system.)

    but, the problem is updation is not taking place in the vista(os) client and xp(os) there is no problem(and i have checked the net connectivity and everything)

    and i checked help& support -->troubleshooting

    where server shows offline.

    then using download support tool, i downloaded http download and checked the connection , it shows 3 errors

    1.secars communication is failed.

    it shows error message.

    2.proactive threat protection definition are out of date.proactive threat protection is currently not running

    3.

    please, provide me a solution................



  • 2.  RE: symantec updation problem in clients

    Broadcom Employee
    Posted Mar 20, 2012 03:41 AM

    can you post the sylink log?also can you try copying working sylink.xml on to these machines and check if the updates are successful?



  • 3.  RE: symantec updation problem in clients

    Posted Mar 20, 2012 04:29 AM

     

    i also copied sylink.xml file from server and copied it in client.but, still server is in offline.

    but ping is taking place between client and server system.

     

    i cant post sylink log due to company privacy.



  • 4.  RE: symantec updation problem in clients

    Broadcom Employee
    Posted Mar 20, 2012 04:40 AM

    in that case, can you review the sylink log and look for errors like sms 403, 503 etc? 



  • 5.  RE: symantec updation problem in clients

    Broadcom Employee
    Posted Mar 20, 2012 06:18 AM

    Hi,

    What's the SEP version ?

    Could you attach Sylink log text file ?

    You are using windows firewall or Symantec firewall on Vista ?

     



  • 6.  RE: symantec updation problem in clients

    Posted Mar 20, 2012 07:19 AM

    sep version-11.0.6200.754

    sylink file i cant able to attach due to company privacy.

    firewall is off.



  • 7.  RE: symantec updation problem in clients

    Posted Mar 20, 2012 10:20 AM

    To test connectivity from a client to the Symantec Endpoint Protection Manager (SEPM), type the following URL In a web browser:

    http://<SEPM_Server_IP_or_Machine_Name:Port>/secars?hello,secars

    Example: http://10.0.2.2:8014/secars?hello,secars

    A successful connection returns a web page that displays "OK."

     

    Try the below article

    http://www.symantec.com/business/support/index?page=content&id=TECH105894&locale=en_US



  • 8.  RE: symantec updation problem in clients

    Posted Mar 20, 2012 10:21 AM

    If the secars test failed, check if the port 8014 is open.

    Start > Run > cmd > telnet <SEPM IP> 8014



  • 9.  RE: symantec updation problem in clients

    Posted Mar 21, 2012 01:18 AM

    it shows message like

     

    "could not open connection to the host,on port 8014: connect failed



  • 10.  RE: symantec updation problem in clients

    Broadcom Employee
    Posted Mar 21, 2012 01:43 AM

    is the SEPM hosted on 8014 ? if not, you should be using configured port to test secar



  • 11.  RE: symantec updation problem in clients

    Posted Mar 21, 2012 06:14 AM

    IF 8014 is the port SEPM is configured with (by default it is), kindly check the firewalls to open this port.



  • 12.  RE: symantec updation problem in clients

    Posted Mar 21, 2012 06:23 AM

    try to do a telnet to the SEPM server on the port which it is configured to use.... and on the SEPM do you see this client with green dot?

     

    If yes delete the client and see if it comes back again with a green dot.



  • 13.  RE: symantec updation problem in clients

    Posted Mar 21, 2012 06:29 AM

    telnet communication is failed & client does not shows any green dot



  • 14.  RE: symantec updation problem in clients

    Posted Mar 21, 2012 06:49 AM

    As mentioned, kindly get in touch with the network team (if it is a different team) to open the ports. Without that the machine will not communicate with SEPM.



  • 15.  RE: symantec updation problem in clients

    Posted Mar 21, 2012 07:41 AM

    In which port the SEPM connectivity has configured..?



  • 16.  RE: symantec updation problem in clients

    Posted Mar 22, 2012 12:00 AM

    port no is 5900



  • 17.  RE: symantec updation problem in clients

    Broadcom Employee
    Posted Mar 22, 2012 12:13 AM

    does the sylink.xml on client have this value 5900 as a port for communication?



  • 18.  RE: symantec updation problem in clients

    Posted Mar 27, 2012 05:27 AM

    Please telnet the port 8014

    Regards



  • 19.  RE: symantec updation problem in clients

    Posted Mar 27, 2012 07:40 AM

    hi,

    Just perform the follownig steps:

    1. Copy Sylink.xml file from working client/server and paste it into problematic system at respective location (IF not worked then)

    2. Try to check the connectivity with the following :

    http://<SEPM_Server_IP_or_Machine_Name:Port>/secars?hello,secars

    Example: http://10.0.2.2:8014/secars?hello,secars

    (if not works then)

    3. Try telnet to SEPM IP on port no. 8014,

    if telnet is not working successfully then you need to check that Port 8014 is opened or not from your Firewall

    Then share the complete observation..



  • 20.  RE: symantec updation problem in clients

    Posted Mar 27, 2012 08:01 AM

    it not showing any error in sylink.log file