Limagito Filemover Software Blog and News

  • 04 Jun

    SSH Error Codes

    Copyright Value Description
    ERROR_SSH_INVALID_IDENTIFICATION_STRING 1 (0x0001) Invalid identification string of SSH-protocol
    ERROR_SSH_INVALID_VERSION 2 (0x0002) Invalid or unsupported version
    ERROR_SSH_INVALID_MESSAGE_CODE 3 (0x0003) Unsupported message code
    ERROR_SSH_INVALID_CRC 4 (0x0004) Message CRC is invalid
    ERROR_SSH_INVALID_PACKET_TYPE 5 (0x0005) Invalid (unknown) packet type
    ERROR_SSH_INVALID_PACKET 6 (0x0006) Packet composed incorrectly
    ERROR_SSH_UNSUPPORTED_CIPHER 7 (0x0007) There is no cipher supported by both: client and server
    ERROR_SSH_UNSUPPORTED_AUTH_TYPE 8 (0x0008) Authentication type is unsupported
    ERROR_SSH_INVALID_RSA_CHALLENGE 9 (0x0009) The wrong signature during public key-authentication
    ERROR_SSH_AUTHENTICATION_FAILED 10 (0x000A) Authentication failed. There could be wrong password or something else
    ERROR_SSH_INVALID_PACKET_SIZE 11 (0x000B) The packet is too large
    ERROR_SSH_HOST_NOT_ALLOWED_TO_CONNECT 101 (0x0065) Connection was rejected by remote host
    ERROR_SSH_PROTOCOL_ERROR 102 (0x0066) Another protocol error
    ERROR_SSH_KEY_EXCHANGE_FAILED 103 (0x0067) Key exchange failed
    ERROR_SSH_INVALID_MAC 105 (0x0069) Received packet has invalid MAC
    ERROR_SSH_COMPRESSION_ERROR 106 (0x006A) Compression or decompression error
    ERROR_SSH_SERVICE_NOT_AVAILABLE 107 (0x006B) Service (sftp, shell, etc.) is not available
    ERROR_SSH_PROTOCOL_VERSION_NOT_SUPPORTED 108 (0x006C) Version is not supported
    ERROR_SSH_HOST_KEY_NOT_VERIFIABLE 109 (0x006D) Server key can not be verified
    ERROR_SSH_CONNECTION_LOST 110 (0x006E) Connection was lost by some reason
    ERROR_SSH_APPLICATION_CLOSED 111 (0x006F) User on the other side of connection closed application that led to disconnection
    ERROR_SSH_TOO_MANY_CONNECTIONS 112 (0x0070) The server is overladen
    ERROR_SSH_AUTH_CANCELLED_BY_USER 113 (0x0071) User tired of invalid password entering
    ERROR_SSH_NO_MORE_AUTH_METHODS_AVAILABLE 114 (0x0072) There are no more methods for user authentication
    ERROR_SSH_ILLEGAL_USERNAME 115 (0x0073) There is no user with specified username on the server
    ERROR_SSH_INTERNAL_ERROR 200 (0x00C8) Internal error of implementation
    ERROR_SSH_NOT_CONNECTED 222 (0x00DE) There is no connection but user tries to send data
    ERROR_SSH_CONNECTION_CANCELLED_BY_USER 501 (0x01F5) The connection was cancelled by user
    ERROR_SSH_FORWARD_DISALLOWED 502 (0x01F6) SSH forward disallowed
    ERROR_SSH_ONKEYVALIDATE_NOT_ASSIGNED 503 (0x01F7) The event handler for OnKeyValidate event, has not been specified by the application
    ERROR_SSH_GSSKEX_SERVER_ERROR_MESSAGE 601 (0x0259) GSS KEX server error.
    ERROR_SSH_TCP_CONNECTION_FAILED 24577 (0x6001) TCP connection failed. This error code defined in SBSSHForwarding unit.
    ERROR_SSH_TCP_BIND_FAILED 24578 (0x6002) TCP bind failed. This error code defined in SBSSHForwarding unit.
    By Limagito Error , ,
  • 04 Jun

    Socket error codes

    Copyright Value Description
    SB_SOCKET_ERROR_WINSOCK_INIT_FAILED 96257 (0x17801) Winsock initialization failed
    SB_SOCKET_ERROR_WRONG_SOCKET_STATE 96258 (0x17802) Wrong socket state
    SB_SOCKET_ERROR_NOT_A_SOCKET 96259 (0x17803) Not a socket (socket initialization failed)
    SB_SOCKET_ERROR_INVALID_ADDRESS 96260 (0x17804) Invalid address
    SB_SOCKET_ERROR_ACCEPT_FAILED 96261 (0x17805) Accept failed
    SB_SOCKET_ERROR_ADDRESS_FAMILY_MISMATCH 96262 (0x17806) Socket handle is IPv6 and could not be used with IPv4 address
    SB_SOCKET_ERROR_INVALID_SOCKET_TYPE 96263 (0x17807) Invalid socket type
    SB_SOCKET_ERROR_SOCKS_NEGOTIATION_FAILED 96264 (0x17808) SOCKS negotiation failed
    SB_SOCKET_ERROR_SOCKS_AUTH_FAILED 96265 (0x17809) SOCKS authentication failed
    SB_SOCKET_ERROR_SOCKS_FAILED_TO_RESOLVE_DESTINATION_ADDRESS 96266 (0x1780A) SOCKS failed to resolve destination address
    SB_SOCKET_ERROR_DNS_SECURITY_FAILURE 96267 (0x1780B) DNS security failure
    SB_SOCKET_ERROR_DNS_TIMEOUT 96268 (0x1780C) DNS timeout exceeded
    SB_SOCKET_ERROR_WEBTUNNEL_NEGOTIATION_FAILED 96269 (0x1780D) Web tunnel negotiation failed
    SB_SOCKET_ERROR_TIMEOUT 96270 (0x1780E) Timeout occured while trying to use the socket connection
    By Limagito Error
  • 27 May

    Web Remote Client SSL option

    Dear Users,

    We’ve added SSL (HTTPS) to our Web Remote Server.  To enable SSL you need to provide 3 certificate files:

    • (Public) Certificate File: This file contains the certificate public key part.
      So everything between and including these two statements:
    • (Private) Key File: This file contains the private key part.
      So everything between and including these two statements:
    • (Public) Root Certificate File: The final file that SSL requires is the Certificate Authority certificate file.
      You can obtain this from the Internet Explorer in Trusted Root Certificate Authority dialog.
      Select the Authority that issued your certificate and export it in Base64 (cer) format.
      This format is also the same as PEM format so after export simply rename the file to root.pem

    The type of certificates we need are .pem files.  The PEM extension is used for Base-64 encoded X.509 certificates. They contain ASCII armored data between “—– BEGIN …”  and “—–END …” lines. Sometimes the certificates come in a single pem file. In this case, you need to open it with a text editor and save the individual certificates in separate pem files.

    Certificates can be obtained from a trusted certificate authority. You can also generate your own but the browser will not trust this and will display a warning.

    If you have a certificate in .pfx format, you’ll have to convert it first. In this case we need a utility called openssl.exe.  First, download and install the OpenSSL Windows binaries from here (at you own risk). The lite version of the binaries is sufficient.

    • Start a command prompt with administrative privileges
    • At command prompt issue the following command:
      • openssl.exe pkcs12 –in <your file>.pfx –out <your file>.pem

    Openssl.exe will ask you for the password of the pfx file. Leave it blank if you did not specify one. It will also ask you for a new password for the .pem file (= optional). The certificates are converted to single pem file. You need to open the converted pem file with a text editor and save the individual certificates in separate pem files.

    Also online certificate conversions are available:

    Web Remote Setup is available in our LimagitoX Config Tool.


    Limagito Team

1 2 3 4 5 6 29