Fri

08

Jul

2011

Can't connect (Error 3 or Error 102)

Some users have reported that they cannot connect to the SilverSHielD server after upgrading it to the latest version. The error reported is Error number 3 (SSH_DISCONNECT_KEY_EXCHANGE_FAILED) or number 102 (unknown error).

 

EASY FIX: Just upgrade to v2.2.3.88 or higher, it handles such issue automatically. Otherwise, please read on...

 

In such cases the log file shows something like (similar to) this:

2011-05-25 13:02:32 Client connection from [XX.XX.XXX.XX] established
2011-05-25 13:02:33 [0000059k] >>>>> Error 3
2011-05-25 13:02:33 [0000059k] SSH connection closed
2011-05-25 13:02:33 NTC (0)
2011-05-25 13:02:33 [0000059k] server thread terminated

 

Such error is related to Z-Compression. If that happens it means that the client you're using does not support Z-Compression or it does not support the same version of the compression algorithm used by SilverSHielD.

 

To fix the problem, just open the SilverSHielD Management Console, disable Z-Compression and save the configuration.

Or, if you're using a client that supports Z-Compression, like WinSCP for instance, jusr remember to enable compression on the client as well.

Latest news...

31-May-2013

SilverSHielD v5.5.5.185 released: improved overall stability of the event handling subsystem, fixed bug that prevented downloading open files. You can download it now.

 

24-Jan-2013

SilverSHielD v5.3.20.160 released: adds HTTP support to the scripting language. See the release notes.

 

15-Dec-2012

SilverSHielD v5.3.15.155 released: adds ExecApp and ExecAppAndWait functions to the event-handling scripting language. See the release notes.

Share our web site...