KACE SMA is Public Facing but remote clients don't connect


We'd made our KACE SMA public facing a while ago, and we as administrators have never had a problem accessing the SMA remotely, both by external IP address or DNS name.   However, now that everyone is working from home, we've noticed that none of the clients are showing connected or receiving commands while off of our network.  All the clients have been configured using the DNS name, so they shouldn't see a difference internal or external.  Just to test, I reconfigured my test laptop to point directly to the external IP as outlined here https://support.quest.com/kace-systems-management-appliance/kb/118540/how-to-make-your-system-management-appliance-sma-publicly-facing-sma-integrity-test and it still wouldn't show as online in KACE.  

What am I missing that would prevent the clients from connecting to our SMA remotely?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: KevinG 9 months ago
8th Degree Black Belt

You will want to check the \ProgramData\Quest\KACE\konea.log and the \ProgramData\Quest\KACE\user\KAgent.log for error messages while trying to connect to the SMA.

The KAT (Kace Agent Toolkit ) can also be used to collect Agent log files for review.

If you should decide to open a support ticket, please submit the logs collected by the KAT program.

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ