- From the JetPatch server, try to telnet to endpoint server over 22 (Linux/Unix) or 445 (Windows)
- Check that the firewall configuration is configured properly on both the endpoint and JetPatch server
- Make sure IPV6 is disabled on the endpoint
- For Linux servers
- Check SElinux configuration (it may limit the connection)
- For insufficient permission issues on Linux servers, see this article
- Do you have other endpoints which are connected successfully to JetPatch? If so, try to understand what are the differences and change accordingly.
- Deploy the connector from the endpoint itself
For invalid credentials issues, please read the article 'Invalid Credential Errors'
For Unable to determine cause of failure - please contact Intigua support, if this occurs when you try to add or remove the connector, make sure you have the necessary protocols enabled.
For Windows endpoints behind a NAT, if it fails with "No IP Found", then verify the WSUS endpoint configuration is pointing to the private IP of the WSUS server.
If none of the above came up successful please download the connector logs. After downloading the logs, search for ERROR messages or any exceptions which may help understand the root cause.
For any other issue, please contact the JetPatch support team with the logs attached.