ErrorCode: 0x12910000įor situations where the certificate is only valid for the FQDN, you will need to do the following:ġ. You need to use a valid hostname or IP address that matches your server certificate to log on Symantec Endpoint Protection Manager.Learn more. : No subject alternative DNS name matching sepm found.Īt java.base/.createSSLException(Alert.java:131)Īt java.base/.fatal(TransportContext.java:360)Īt java.base/.fatal(TransportContext.java:303)Īt java.base/.fatal(TransportContext.java:298)Īt java.base/$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:654)Īt java.base/$T12CertificateConsumer.onCertificate(CertificateMessage.java:473)Īt java.base/$nsume(CertificateMessage.java:369)Ĭom.CommunicationException: Your server certificate is not valid because the computer hostname or IP address changed. In addition, the following error may be seen in the scm-server-0.log: 14:38:05.177 THREAD 72 SEVERE: in: .task.SecurityAlertNotifyTask You need to use a valid hostname or IP address that matches your server certificate to log on Symantec Endpoint Protection Manager." "Your server certificate is not valid because the computer hostname or IP address changed. After upgrading the Endpoint Protection Manager (SEPM) to 14.3 RU8, logins fail with the following error:
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |