Endpoint Protection

 View Only

  • 1.  SEP 14.1 client not connecting to SEPM

    Posted Jul 16, 2018 09:28 PM

    Hi all,

    SEP clients are cannot connecting to SEPM.

    Shows below error SEPM ersecreg.log

    07/17 08:43:10 [376:4180] 4 Bad format.

    07/17 08:43:10 [376:4180] IP address--FAILED.

     



  • 2.  RE: SEP 14.1 client not connecting to SEPM

    Posted Jul 16, 2018 10:00 PM

    SCAR test is OK,

    8014 is opened

    Telnet is OK

    Tried Pull and Push mode but still no luck.



  • 3.  RE: SEP 14.1 client not connecting to SEPM

    Posted Jul 17, 2018 10:53 AM

    Download and run SymDiag on an affected client - what are the results?

    Enable sylink logging and let it run through afew heartbeats - post the log here for further review if needed.



  • 4.  RE: SEP 14.1 client not connecting to SEPM

    Broadcom Employee
    Posted Jul 17, 2018 11:30 AM

    07/17 08:43:10 [376:4180] 4 Bad format.

    07/17 08:43:10 [376:4180] IP address--FAILED.

    This error means there is a KCS mismatch

     

    The clients are likely checking in with the wrong KCS.  You will need to push new Sylink.xml to the clients.

     



  • 5.  RE: SEP 14.1 client not connecting to SEPM
    Best Answer

    Posted Jul 17, 2018 09:25 PM

    When checked ersecreg.log initailizes different KCS than Sylink.

    Currently we had 1 primary SEPM and 5 replication partners. Recently we added new replication partner to primary SEPM.

    Then KCS is changed and clients disconnected.

    I'm repaired main SEPM from Program and Features and repaired,

    Then created sylink and replaced client sylink, clients are connecting to without error.