Endpoint Protection

Hi,

Got an issue after upgrade SEP from 14.0 to 14.2, i have 10 windows client upgraded and all of them unable to communicate with the SEP Server. At all clients, i found error message that said: "SSL peer certificate or SSH remote key was not OK" in the Troubleshooting - Server Connection Status window.

Another information you guys might to know:

OS: Windows Server 2012 (SEP Server & clients)
Database: SQL Server

Note: Got the installer from official site Symantec and manually installed on server and each client.

Thanks in advance.

As a test, what is the result if you push out a new sylink.xml file to an affected client?

Hi Brian,

Even we have the same issue. after upgrading to 14.2, client will never communicate to port 443. Creating MSL to port 8014 and it connects.

Can you let us know if there is any way to get rid of this. We want it connect to port 443.

Brian I am also seeing the same error. All my clients connect except the client that runs locally on the server that hosts the SEPM manager server. I am using port 50000. I've created firewall rules for both inbound and outbound connections. The client still can't connect locally. 

So I typed in https://192.168.0.6:50000 and I am seeing an SSL certificate for my old server (has a different hostname). We did a migration and used the restore functionality. Do I need to renew this? If so, why can all the other clients connect but just this one client cant?

Thanks Brian for ur response,

Yes, i have tried to push sylink.xml to every clients but same error still happened. 

For further information, i'm not using any certificate. Not sure whether it is possibly the culprit of the issue.

What worked for me was issuing a new certificate under the server settings in the admin panel and then deploying a new communications package reinstall to each client.

Known issue. KB article posted here:

https://www.symantec.com/docs/TECH251024

Solution from Daniel Diaz works like a charm on this issue. Thanks guys for all ur response.