Endpoint Protection

 View Only
Expand all | Collapse all

Port communication

Migration User

Migration UserDec 01, 2011 05:39 AM

  • 1.  Port communication

    Posted Dec 01, 2011 05:22 AM

    Hi,

       My 2 of the clients servers are not getting update from long time, I have checked the pinging is working on the both client ever server also.

    But I have checked telnet port with 8014, it's not working, pls confirm is it require ya another port require to communicate.



  • 2.  RE: Port communication

    Broadcom Employee
    Posted Dec 01, 2011 05:32 AM

    client will talk to SEPM on the configured port, if it is 8014 it should be open. Check the IIS manager to see the port that has been configured.



  • 3.  RE: Port communication

    Posted Dec 01, 2011 05:37 AM

    It's working for last 2 year and i confirmed from Security Engg. This port has been blocked from last 2 year. so any other port to communicate the same.??



  • 4.  RE: Port communication

    Posted Dec 01, 2011 05:39 AM

    Same is also a Server(But not the Symantec)



  • 5.  RE: Port communication

    Posted Dec 01, 2011 05:44 AM

    Hi,

    You mean to say that the clients are not communicating on port 8014 now or they never communicated on that port no.

    Check the below article for the ports used by Symantec for communication :

    http://www.symantec.com/docs/TECH102416



  • 6.  RE: Port communication

    Broadcom Employee
    Posted Dec 01, 2011 05:44 AM

    DO you mean the SEPM is installed on 8014?

    It could be telnet might be blocked, can you run sylink on client and pass on the result.



  • 7.  RE: Port communication

    Posted Dec 01, 2011 05:47 AM

    Yes client system is not communicate with server on this port 8014



  • 8.  RE: Port communication

    Posted Dec 01, 2011 05:49 AM

    Same is also one of our Server but not communicate threw this port 8014, but it's communicate on port 80

    Version is 11.0.6005



  • 9.  RE: Port communication

    Broadcom Employee
    Posted Dec 01, 2011 05:55 AM

    check this article for troubleshooting, if telnet is blocked collect the sylink logs from the clients

    http://www.symantec.com/docs/TECH95789



  • 10.  RE: Port communication

    Broadcom Employee
    Posted Dec 01, 2011 05:56 AM

    so it might be that the server may have configured on port 80 instead of 8014



  • 11.  RE: Port communication

    Posted Dec 01, 2011 06:45 AM

    It seems that the client communication is customized on a different port.

     

    As per Version is 11.0.6005 browse to following location :- C:\Program Files\Symantec\Symantec Endpoint Protection and look for sylink.xml.

     

    This file is used for communication between SEPM and clients. When you open the file which would open is a web page (IE) by default, that would give us more info about which port client communication is configured on.

    If possible could you upload sylink.xml file to confirm the same

    Cheers!!



  • 12.  RE: Port communication

    Posted Dec 01, 2011 09:48 AM

    Pls find the snapshot, I think all detail mention here



  • 13.  RE: Port communication
    Best Answer

    Posted Dec 01, 2011 10:03 AM

    its trying to communicate with server on port 8014.

    on a command prompt  try this 

    c:\>telnet SEPMservername 8014

    does it connect?

    it not u it might be somefirewall in between which is blocking the connection

    alternatively you can try the secars test as in this document

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



  • 14.  RE: Port communication

    Posted Dec 02, 2011 06:51 AM

    I have tried to run the command

    Telnet Server IP 8014

    But it's not working

     

    Also I have running the path of WEB Browser threw IE

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

    It's also not working.

    Secuirty Engg also check the firewall log from last month but not of any changing found here.

    so any other way to check out.



  • 15.  RE: Port communication

    Broadcom Employee
    Posted Dec 02, 2011 07:15 AM

    what was the error after testing the below infor you provided.

    Also I have running the path of WEB Browser threw IE

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



  • 16.  RE: Port communication

    Broadcom Employee
    Posted Dec 02, 2011 07:20 AM

    can you copy the sylink.xml from SEPM and copy onto machines not connecting?



  • 17.  RE: Port communication

    Posted Dec 02, 2011 08:55 AM

    Boss- we have open the port from Firewal 8014, now it's connection, but one other problem occur, i have stop the smc on one of the system, but in the services staus is in stopping mode and startup box disable here and also smc -start service not getting starup the same



  • 18.  RE: Port communication

    Posted Dec 02, 2011 10:44 AM

    Pls confirm what can I do on same???

    Error Snapshot attached below.

     



  • 19.  RE: Port communication

    Posted Dec 02, 2011 04:53 PM

    Pls revert, if any solution on same without restarting the system



  • 20.  RE: Port communication

    Broadcom Employee
    Posted Dec 02, 2011 11:13 PM

    sumitgupta786, I believe only restart will refresh the srevices.



  • 21.  RE: Port communication

    Posted Dec 03, 2011 12:35 AM

    That is Critical Server Machine, I can't able to restart the same, any of the process need to kill to stop/start this service?



  • 22.  RE: Port communication

    Broadcom Employee
    Posted Dec 03, 2011 01:10 AM

    there are some application out ( google it) which needs to be installed, however its not a good idea to install such application on the critical server.