Linked Appliance Connection Error (4319481)

These instructions will refer to the target linked appliance as the Remote Site Appliance (RSA), but the same steps can apply when linking to a K1000 or another K2000.

Connection error. CURL Error 6: CURLE_COULDNT_RESOLVE_HOST

This error  indicates that the K2000 could not resolve the host name of the linked appliance. [http://curl.haxx.se/libcurl/c/libcurl-errors.html]
Some things to check for would be:

1. Make sure the entry for DNS is correct in Settings & Maintenance | Network Settings
2. Make sure that you can ping the system via hostname, FQDN, and IP address in Help | Troubleshooting
3. Go into Settings and Maintenance > Manage Linked Appliances, click on the entry for the linked appliance, and change the Host Name field to the linked appliance's FQDN, save, and test connection.
4. Go into Settings and Maintenance > Manage Linked Appliances, click on the entry for the linked appliance, and change the Host Name field to the linked appliance's IP address, save, and test connection.

 

Connection error. CURL Error 28: CURLE_OPERATION_TIMEOUTED

This error usually indicates that a connection to the linked appliance can not be made and the specified time-out period was reached. [http://curl.haxx.se/libcurl/c/libcurl-errors.html]
Some things to check for would be:

1. Make sure the machine that hosts the linked appliance can be contacted by pinging it.
2. Make sure that you can ping the remote site virtual appliance.  If not, make sure it was not shut down.
3. Make sure the virtual NIC is set to Bridged and the network information is correct. (not required for VMWare ESXi servers)
4. Make sure port 22 is open between the linked appliances.

 

Connection response: '401 Associated key fingerprint not found '.

This error indicates that the linked appliance does not have the linking key entered for the K2000.
Some things to check for would be:

1. Make sure that there is an entry on the RSA (Settings & Maintenance | Managed Linked Appliance) for the K2000 and vice versa.
2. Copy the linking key from the K2000 (Settings & Maintenance | KACE Linking) and paste it into the RSA in the Linking Key field (Settings & Maintenance | Managed Linked Appliance | click on the entry for the K2000), overwriting the previous data.
3. Test the connection. If it is still not working, copy the linking key from the RSA (Settings & Maintenance | KACE Linking). Then go to the K2000 (Settings & Maintenance | Managed Linked Appliance | click on the entry for the RSA in question) and paste the key into the Linking Key field, overwriting the previous data.

Connection response: '403 Forbidden'.

This error generally stems from a connection issue or a name resolution problem.
Some things to check for would be:

1. Try using IP addresses for linking the appliances:
   • On the K2000, go to Settings & Maintenance | Managed Linked Appliance | click on the entry for the RSA in question and change the 'Host Name:' field to the RSA IP address.
   • On the RSA, go to Settings & Maintenance | KACE Linking and change the 'K2000 Remote Site Friendly Name (this server): ' field to the RSA IP address.
   • On the RSA, go to Settings & Maintenance | Network Settings and change the 'Host Name:' field to the RSA IP address.
   • Test the link.
2. Recreate the connections:
   • Log into the K2000 and delete the RSA from Settings & Maintenance | Managed Linked Appliance.
   • Then, log into the RSA and delete the K2000 from Settings & Maintenance | Managed Linked Appliance.
   • Recreate the linked appliance connections on the K2000 and RSA.

Linking Error 302'.

This error generally occurs when SSL is enabled on the KACE SDA (K2000).
Some things to check for would be:

1. Try to enable the SSL option:
   • On the K2000, go to Settings & Maintenance | Managed Linked Appliance | click on the entry for the RSA in question.
   • Tick the Connect using SSL option.
   • Test the link.