• RE: Office 365 connecting with EWS

    Asking the same, especially since Basic Authentication is being disabled very soon.
  • RE: SFTP connection Errors 105 and 96258

    Replying to my own post here in case anyone comes across a similar case. It turned out that I had to manually try several combinations of protocols and ciphers until I found a working one. Apparently leaving things to AUTO does not always work. Information found in the logs was also not too helpful unfortunately. 
  • SFTP connection Errors 105 and 96258

    Due to a change on one of our partners side, I need to reconfigure the SFTP connection on a file transfer task. When testing with the new connection info, I get FTP failed errors as follows:

    In FTP Browser: "Error: Connection lost due to error 96258"
    In log file: Error 105

    Partner site operator gave the following info:

    ------ QUOTE  -----

    •    hmac-sha256    
    •    hmac-sha512
    •    hmac-sha256@ssh.com
    •    hmac-sha2-512
    •    hmac-sha2-256    
    •    hmac-sha2-512-etm@openssh.com
    •    hmac-sha2-256-etm@openssh.com
    •    hmac-sha2-512-96
    •    hmac-sha2-256-96    
    •    hmac-ripemd160

    •    aes128-cbc    
    •    aes128-ctr
    •    aes192-cbc    
    •    aes192-ctr
    •    aes256-cbc    
    •    aes256-ctr
    •    blowfish-cbc    

    •    diffie-hellman-group-exchange-sha256    
    •    ecdh-sha2-nistp256
    •    diffie-hellman-group14-sha256    
    •    ecdh-sha2-nistp384
    •    diffie-hellman-group16-sha512    
    •    ecdh-sha2-nistp521
    •    diffie-hellman-group18-sha512    

    •    x509v3-rsa2048-sha256    
    •    ecdsa-sha2-nistp384
    •    x509v3-ecdsa-sha2-nistp256    
    •    ecdsa-sha2-nistp521
    •    x509v3-ecdsa-sha2-nistp384    
    •    ecdsa-sha2-nistp256-cert-v01@openssh.com
    •    x509v3-ecdsa-sha2-nistp521    
    •    ecdsa-sha2-nistp384-cert-v01@openssh.com
    •    x509v3-ssh-rsa    
    ---  END QUOTE ---

    When testing with WinSCP on the same machine, the connection works and I can see the following connection details:

    ---- QUOTE ----
    File transfer protocol = SFTP-4
    Cryptographic protocol = SSH-2
    SSH implementation = SSHD
    Encryption algorithm = AES-256 SDCTR (AES-NI accelerated)
    Compression = No
    Server host key fingerprints
    SHA-256 = ssh-rsa 2048 uddH1t8Q-REDACTED-5DKGsQnLWGZu6R1Y=
    MD5 = ssh-rsa 2048 b3:6f:13:55:-REDACTED-9:52:2c:52:e2:1b
    Can change permissions = Yes
    Can change owner/group = Yes
    Can execute arbitrary command = No
    Can create symbolic/hard link = Yes/No
    Can lookup user groups = No
    Can duplicate remote files = No
    Can check available space = No
    Can calculate file checksum = No
    Native text (ASCII) mode transfers = Yes
    Additional information
    The server supports these SFTP extensions:
    ---- END QUOTE ----

    I tried these settings in Automate, without success. Besides that,  I believe by keeping everything on AUTO it should just work.

    There's one thing however. The password I was given contains special characters, namely a bracket "(", and a hashtag "#*. Could these cause any issue?

    Using Automate