Quantcast
Channel: Symantec Connect - Endpoint Protection - Discussions
Viewing all articles
Browse latest Browse all 10484

SEP installed on same server as SEPM communications failure

$
0
0
I need a solution

I recently upgraded from 14.0.1 to 14.2.   Everything worked fine,  except I don't get the green dot in the SEP client installed on the same server as the SEPM manager. Running the troubleshooter in the SEP client comes back with "Communication Failure".

 I had previously installed a CA certificate and it worked before the upgrade.   If I do the secar test using the FQDN, it comes back OK.   So I looked in the apache access log,  and it seems all the clients use the FDQN of the server except the local one,  which is failing.   All other client's entrys come back with IPAddrAccessingIT "GET /secars/secars.dll?h=96... HTTP/1.1" 200 2462 and the local one comes back with 127.0.0.1 "GET /secars/secars.dll?action=36 HTTP/1.1" 200 723 "Java/1.8.0_151" .

If I do the secars test using the IP address instead of the FQDN,   my browser says Net::ERR_CERT_COMMON_NAME_INVALID.   Is there any way I can switch the SEP client to use the FQDN instead of localhost?

0

Viewing all articles
Browse latest Browse all 10484

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>