Quantcast
Channel: Chilkat Forum - latest questions
Viewing all articles
Browse latest Browse all 1061

Error on SSL client handshake

$
0
0

I have a working code which runs on 3.5 framework 32 bit and Chilkat version 9.0.8.0.It works on upload a file internall for sftp server

I am trying the download a file from external SFTP site and place the file in one of our server. I am getting the error message as: Please help!!!

Error Log created
Could not establish connection to C:\File\\ message:ChilkatLog:
  NumFilesAndDirs:
    DllDate: Feb 15 2010
    UnlockPrefix: FTP
    Username: rkuruvilla
    Component: .NET 2.0
    ListDir:
      (SendSecure) Cannot send data, not connected.
      SetModeBinary: Elapsed time: 0 millisec
    N: -1
    Failed.

Error Log created
Could not establish connection to C:\\ message:ChilkatLog:
  Connect:
    DllDate: Feb 15 2010
    UnlockPrefix: FTP
    Username: rkuruvilla
    Component: .NET 2.0
    Using Implicit SSL
    ImplicitSsl: 1
    AuthTls: 0
    AuthSsl: 0
    Hostname: coserv-storage-test.ifactornotifi.com
    Port: 22
    Connecting via SSL
    Protocol: default
    IdleTimeoutMs: 60000
    ConnectTimeout: 60
    HeartbeatMs: 0
    ConnectTimeoutMs: 60000
    protocol: default
    Invalid token.
    ReceivedDataQP: SSH-2.0-OpenSSH_5.3

SEC_E_INVALID_TOKEN
    Aborting SSL client handshake because of fatal error
    Possible solution: Check to see if your server requires a client-side certificate.  If so, it can be provided by calling SetSslClientCert prior to connecting.
    Possible solution: Try explicitly setting the SslProtocol property = "SSL 3.0".
    Error performing handshake
    ConnectFailReason: 103
    Failed to connect to FTP server.

Error Log created
Could not establish connection to C:\\ message:ChilkatLog:
  Connect:
    DllDate: Feb 15 2010
    UnlockPrefix: FTP
    Username: rkuruvilla
    Component: .NET 2.0
    Using Implicit SSL
    ImplicitSsl: 1
    AuthTls: 0
    AuthSsl: 0
    Hostname: coserv-storage-test.ifactornotifi.com
    Port: 22
    Connecting via SSL
    Protocol: default
    IdleTimeoutMs: 60000
    ConnectTimeout: 60
    HeartbeatMs: 0
    ConnectTimeoutMs: 60000
    protocol: default
    Invalid token.
    ReceivedDataQP: SSH-2.0-OpenSSH_5.3

SEC_E_INVALID_TOKEN
    Aborting SSL client handshake because of fatal error
    Possible solution: Check to see if your server requires a client-side certificate.  If so, it can be provided by calling SetSslClientCert prior to connecting.
    Possible solution: Try explicitly setting the SslProtocol property = "SSL 3.0".
    Error performing handshake
    ConnectFailReason: 103
    Failed to connect to FTP server.
    

Viewing all articles
Browse latest Browse all 1061

Trending Articles