Verifying Connectivity Issues Between Saner Agent and Server

Modified on Sun, 11 May at 1:41 PM

Purpose

This guide provides essential steps to help troubleshoot and verify connectivity issues between the Saner Agent and the SanerNow server. These checks are particularly helpful if you're facing problems during scan execution, content downloads (e.g., GetCRE), or remediation status uploads.

When to Use This Guide

Agent fails to fetch or upload content
Scan or remediation job appears stuck or failing to upload the results
Issues related to GetCRE download
403 reject or forbidden request
General network communication failures between agent and server

Connectivity Verification Steps

1. Check Basic Reachability

Run the following curl command to ensure the server is reachable and responding:

curl -v -k https://saner.secpod.com/AncorWebService

2. Test Server Trace with Verbose Output

This helps you trace the connection and identify any SSL issues or connection drops:


curl -v -k https://saner.secpod.com --trace –

3.Check Content Download using MAC Address

Use this command to simulate the agent's attempt to fetch content. Replace the MAC address with the one from the target device:


curl -H "Content-type: application/x-www-form-urlencoded" -H "Authorization: SAML <assertion.key content>" "https://saner.secpod.com/AncorWebService/sanergetcontent?macaddress=A4-BB-6D-D7-45-FB" -o abc.zip

Ensure you place the correct SAML token and device MAC address.

screenshot below for reference

Verify Route to the Server

This helps determine if there are network hops causing delays or drops:


tracert saner.secpod.com

Conclusion

These commands are effective in identifying whether network issues are blocking agent-server communication. Running them during troubleshooting can help isolate the root cause quickly — whether it’s a connectivity issue, content block, or endpoint restriction.