When syncing the RSA with the K2000 appliance cannot connect or I get error 12 or 255.
The first thing to check is any firewalls or network intrusion devices. In many situations, disabling these will resolve the issue.
If you cannot connect at all between the K2000 appliance and the RSA, there are two factors causing this. The first is name resolution as outlined below. The other is that in the Mange Linked Appliance page there is a check box for SSL. This is used in the event the K1000 appliance is using an SSL certificate. If you are not using SSL, then checking this box anywhere long the linking process will case the link to fail. Best practices suggest getting every thing working first without SSL, then enable SSL and troubleshoot. You know that the issue is SSL if, in fact it was working before the setting and now it is not.
Even though it is possible to navigate from the K2000 appliance webpage to the RSA webpage using single sign on it does not mean that you can sync files between the two.
The difference is the linking process (single sign on) uses port 80 while the syncing of files uses Secure Shell (SSH port 22). SSH is picky about the name of the computers the files are coming from and going to. Matching the name is part of the security. If the name of the appliance does not match the name in the Managed Linked Appliance page or visa versa, the sync will fail.
There are several errors that one might get if the names are not setup correctly. The best place to see what is going on is to look at the logs. In the console the log in question is Server Processor Task error log. "Host Key verification failed" generally means the a naming mismatch. In the case of the example, error 255 is given. Error 12 may also be exhibited.
Host key verification failed.
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(462) [sender=2.6.9]
Host key verification failed.
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(462) [sender=2.6.9]
shutdown: [pid 16878]
KServerTaskProcessor[766] @ Mon, Nov 24 2008 08:58:10 EST: shutting down
KServerTaskProcessor[764] @ Mon, Nov 24 2008 08:57:32 EST: starting up
Host key verification failed.
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(462) [sender=2.6.9]
When you are linking you need to make sure of the following:
- When naming the KACE 1000 and 2000 series appliances, be careful not to use the same prefix in the name. For example "KBOX2000" and "KBOX1000". Sticking with the default names kbox, ikbox, ekbox. This is a K1000 appliance specific issue and will not affect syncing but will cause issues with single sign on when connecting to the K2000 appliance. This was resolved in version 4.3 of the K1000 appliance.
- The name given to either appliance must be resolvable. For instance if you call your K2000 appliance ikbox but when you run reverse look up it resolves to ikbox.companyname.com then you need to change the name in Network Settings page to match. Of course renaming does force a reboot of the K2000 appliance.
- When working with the Managed Linked Appliances page, the name given to the K2000 appliance has to match the the value in hostname field (ikbox.companyname.com).
For more related information try these FAQs:
ERROR 12:
http://www.kace.com/support/resources/kb/article/Error-Code-12-occurred-while-syncing-the-K2000
ERROR 401:
http://www.kace.com/support/resources/kb/article/connection-response-401-associated-key