Hi I am not able to connect to SFTP server from windows 20089 server with proxy server
getting error message The serverhasunexpectedlyclosed the connection
from the same server i am able to connect to SFTP via wiscp
i believe the issue is with encryption because Winscp had Diffi Helman Exchange group that is not available in FTP voyager
Please help
Regards
Kamran Shams
Hi,
We have a scheduled task that should upload a file to a remote location via FTP over SSL or TLS. This was working fine with version 15 but not now with version 16. The upload works sometimes but most of the time it doesn't.
We really need this to work or else a downgrade must be done. So any ideas or questions will be appreciated.
Kind regards,
Peter Nilsson
STATUS> Resolving host "ftps.xxxxx.xx"...
STATUS> Connecting to "nnn.nnn.nnn.nnn" on port 21.
STATUS> Connected to nnn.nnn.nnn.nnn:21 from nnn.nn.n.nnn:64626.
220-FTP 10:12:22 on 2016-03-15.
220 Connection will close if idle for more than 5 minutes.
COMMAND> AUTH TLS
234 Security environment established - ready for negotiation
STATUS> SSL connection established. All transactions are now secure.
STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.
STATUS> Connected. Logging in to the server.
COMMAND> USER xyz
331 Send password please.
COMMAND> PASS ***
230 xyz is logged on. Working directory is "/remotefolder1/remotefolder2/out".
STATUS> Login successful.
COMMAND> SYST
215 UNIX is the operating system of this server. FTP Server is running on z/OS.
COMMAND> FEAT
211- Extensions supported
SIZE
MDTM
AUTH TLS
PBSZ
PROT
211 End
COMMAND> REST 100
504 Restart requires Block or Compressed transfer mode.
STATUS> Server supports resume.
COMMAND> PBSZ 0
200 Protection buffer size accepted
COMMAND> PROT P
200 Data connection protection set to private
COMMAND> PWD
257 "/remotefolder1/remotefolder2/out" is the HFS working directory.
COMMAND> CWD /remotefolder1/remotefolder2/in
250 HFS directory /remotefolder1/remotefolder2/in is the current working directory
COMMAND> PASV
227 Entering Passive Mode (nnn,nnn,nnn,nnn,nnn,nn)
STATUS> Opening passive mode data connection to nnn.nnn.nnn.nnn, port 60734.
STATUS> Negotiating SSL connection with server...
COMMAND> LIST /remotefolder1/remotefolder2/in/File123.txt
550 LIST cmd failed : ls: FSUM6785 File or directory "/remotefolder1/remotefolder2/in/File123.txt" is not found
STATUS> Sending: \\localserver\localfolder1\localfolder2\out\File123.txt -> /remotefolder1/remotefolder2/in/File123.txt
COMMAND> TYPE A
ERROR> SSL Accept failed on FTP data channel. The connection will be aborted.
STATUS> Resolving host "ftps.xxxxx.xx"...
STATUS> Connecting to "nnn.nnn.nnn.nnn" on port 21.
STATUS> Connected to nnn.nnn.nnn.nnn:21 from nnn.nn.n.nnn:64630.
220-FTP 10:12:25 on 2016-03-15.
220 Connection will close if idle for more than 5 minutes.
COMMAND> AUTH TLS
234 Security environment established - ready for negotiation
STATUS> SSL connection established. All transactions are now secure.
STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.
STATUS> Connected. Logging in to the server.
COMMAND> USER xyz
331 Send password please.
COMMAND> PASS ***
230 xyz is logged on. Working directory is "/remotefolder1/remotefolder2/out".
STATUS> Login successful.
COMMAND> SYST
215 UNIX is the operating system of this server. FTP Server is running on z/OS.
COMMAND> FEAT
211- Extensions supported
SIZE
MDTM
AUTH TLS
PBSZ
PROT
211 End
COMMAND> REST 100
504 Restart requires Block or Compressed transfer mode.
STATUS> Server supports resume.
COMMAND> PBSZ 0
200 Protection buffer size accepted
COMMAND> PROT P
200 Data connection protection set to private
COMMAND> PWD
257 "/remotefolder1/remotefolder2/out" is the HFS working directory.
COMMAND> QUIT
221 Quit command received. Goodbye.
Hello,
when i try connect to ftp i get error:
SSL accept failed on FTP data channel.
The connection will be aborted
but i can connect with FileZilla or other ftp clients.
FTP Voyager 16.2.0.328
log:
STATUS> Resolving host "ftp.xxxxxx.xx"...
STATUS> Connecting to "xxx.xxx.xxx.xxx" on port 990.
STATUS> Connected to xxx.xxx.xxx.xxx:990 from 10.10.10.10:56773.
STATUS> Negotiating SSL connection with server...
STATUS> SSL connection established. All transactions are now secure.
STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.
220 (vsFTPd 3.0.2)
COMMAND> HOST ftp.xxxxxx.xx
530 Please login with USER and PASS.
STATUS> Connected. Logging in to the server.
COMMAND> USER ftp-baku
331 Please specify the password.
COMMAND> PASS ***
230 Login successful.
STATUS> Login successful.
COMMAND> SYST
215 UNIX Type: L8
COMMAND> FEAT
211-Features:
AUTH TLS
EPRT
EPSV
MDTM
PASV
PBSZ
PROT
REST STREAM
SIZE
TVFS
UTF8
211 End
STATUS> Server supports resume.
COMMAND> OPTS UTF8 ON
200 Always in UTF8 mode.
COMMAND> PBSZ 0
550 Permission denied.
COMMAND> PROT P
550 Permission denied.
COMMAND> PROT C
550 Permission denied.
COMMAND> PWD
257 "/"
COMMAND> PASV
227 Entering Passive Mode (82,138,52,71,34,222).
STATUS> Opening passive mode data connection to xxx.xxx.xxx.xxx, port 8926.
STATUS> Negotiating SSL connection with server...
COMMAND> LIST
150 Here comes the directory listing.
226 Directory send OK.
ERROR> SSL Accept failed on FTP data channel. The connection will be aborted.
Please help me with solving a problem.
I have several tasks setup to run at different time intervals on a daily basis.
After the time change for Daylight Savings Time on Sunday morning the tasks run as scheduled and then stop and re-start continuously.
I have tried re-starting the service, updating the task scheduler time and re-booting the server all to no avail.
Has anyone else seen this or does anyone have any ideas on how to correct it.
I am on FTP Voyager version 16.0.2.0.
Never had this issue on any previous versions.
Is there a place to download version 15 again????
scheduler run task continuously after upgrade to v16.1.0.0 - I've tried restarting the server and the scheduler service but nothing seems to work. how do i stop this task?
In FTP Voyager I create a site profile under “Tool – Scheduler Site Profiles”. I’m able to connect to this profile and manually upload and manage documents. I created a Task in Scheduler to sync the remote folder using the profile I create. When executed I get the following error “Execution failed (Last Error Message: )”.
Why am I getting the error in Scheduler when I don’t making a direct connection?
Snippet from log:
[03] Wed 21May14 12:02:57 - Server supports resume.
[05] Wed 21May14 12:02:57 - OPTS UTF8 ON
[06] Wed 21May14 12:02:57 - 200 OPTS UTF8 command successful - UTF8 encoding now ON.
[05] Wed 21May14 12:02:57 - PWD
[06] Wed 21May14 12:02:57 - 257 "/" is current directory.
[13] Wed 21May14 12:02:57 - (Action: "C:\pdcloud01 hold\Trade Show\CSV File\Idatix" to "/") - Synchronizing remote folder "/" with local folder "C:\pdcloud01 hold\Trade Show\CSV File\Idatix"
[05] Wed 21May14 12:02:57 - CWD /
[06] Wed 21May14 12:02:57 - 250 CWD command successful.
[05] Wed 21May14 12:02:57 - PORT 47,23,21,53,245,30
[06] Wed 21May14 12:02:57 - 200 PORT command successful.
[05] Wed 21May14 12:02:57 - LIST
[06] Wed 21May14 12:02:57 - 150 Opening ASCII mode data connection.
[06] Wed 21May14 12:03:19 - 550
[13] Wed 21May14 12:03:19 - (Action: "C:\pdcloud01 hold\Trade Show\CSV File\Idatix" to "/") - Action failed (Last Error Message: ).
[12] Wed 21May14 12:03:19 - (Task: fd test) - Execution failed (Last Error Message: ).
[12] Wed 21May14 12:03:19 - (Task: fd test) - Next scheduled execution on Wednesday, May 21, 2014 12:12:56
[05] Wed 21May14 12:03:19 - QUIT
[06] Wed 21May14 12:03:19 - 221 Goodbye
I am getting this error and I don't know what the problem is.
SSH Disconnect Error: no more authentication methods available.
We are using Serv-U on the back-end and FTP Voyager on the front end.
Regular password based connections work fine.
As soon as I create a private / public key and bind it to the user (on both sides), then the authentication will not work.
Here is the log.
Perhaps I have to disable password authentication before public key authenication will work?
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58052.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 2)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58054.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 3)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58056.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 4)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58058.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 5)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58060.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 6)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58061.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 7)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58064.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
ERROR> The server has unexpectedly closed the connection.
ERROR> Could not establish a connection to MFT-AIM.
Hi,
Got FTP-Voyager to work great in command mode using a batch file to initiate file sync to my server from industrial robots to back them up. Was working great as far as doing the job closing out starting another instance and going to the next robot.
New problem.....
It no longer closes out at the end of the sync. What option did I change that keeps FTP-Voyager from closing ? I am using "autoquit=1" in the command line.
Thanks
Stan
Hello,
I have been going crazy attempting to upload files to another (Linux) server and I am getting errors.
once I figured out how to get the sites to show up when using the scheduler, i used the export and import rather then re-create accounts.
a users guide with examples would be really great! i can find any such thing.
so the issue i am see is this... I can connect using the browser and upload files with no issues. when i use the scheduler, I have to specfiy the local and remote directories. this is where things get interesting. I am placed in a home directory on the remote side, so for the remote side I just use / and for the local side i click on the folder icon and navigate to the folder E:\folder\folder1 and I would assume that everything in folder1 would be uploaded. Wrong! it tries to create the remotefolder2 and dose not have permissions and so it fails. why is it trying to create folders? in the help man, it says that the directory listed in the local and remote will grab everything in that folder and says nothging about trying to create that folder. I just want to move files in that local folder1 to the remotefolder2.
the Actions I have tried so far is as follows:
Upload: "E:\localfolder\localfolder1" to "/"
Upload: "E:\localfolder\localfolder1" to "/remotefolder/remotefolder1/remotefolder2"
Upload: "E:\localfolder\localfolder1\*.*" to "/"
any trailing "/" or "\" are removed when you hit save.
when I add the /remotefolder/remotefolder1/remotefolder2 to the remote folder location, the error logs show it attempts to create remote directories remotefolder/remotefolder1/remotefolder2
I have changed the site profile advanced options \ file transfer \ transfer mode to Binary.
here is the thing i don't understand. I can connect using the browser and see the remote site, and i can transfer files to and delete on the remote end with no issues at all and the logs are much smaller. only when trying to use the scheduler is where things go goofy.
[07] Sat 27Feb16 12:18:15 - SSH_MSG_USERAUTH_REQUEST: user: XXXXXX; service: ssh-connection; type: publickey
[08] Sat 27Feb16 12:18:15 - SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
[07] Sat 27Feb16 12:18:15 - SSH_MSG_USERAUTH_REQUEST: user: XXXXXX; service: ssh-connection; type: publickey
[08] Sat 27Feb16 12:18:16 - SSH_MSG_USERAUTH_SUCCESS: authentication successful
[03] Sat 27Feb16 12:18:16 - Login successful.
[07] Sat 27Feb16 12:18:16 - SSH_MSG_CHANNEL_OPEN: type: session; local channel: 0
[08] Sat 27Feb16 12:18:16 - SSH_MSG_CHANNEL_OPEN_CONFIRMATION: local channel: 0; remote channel: 0
[07] Sat 27Feb16 12:18:16 - SSH_MSG_CHANNEL_REQUEST: remote channel: 0; request type: subsystem; subsytem: sftp
[08] Sat 27Feb16 12:18:16 - SSH_MSG_CHANNEL_SUCCESS: channel request succeeded; local channel: 0
[07] Sat 27Feb16 12:18:16 - SSH_FXP_INIT: client version: 6
[08] Sat 27Feb16 12:18:16 - SSH_FXP_VERSION: server version: 3
[03] Sat 27Feb16 12:18:16 - Negotiated SFTP version 3
[07] Sat 27Feb16 12:18:16 - SSH_FXP_REALPATH: translating path: .
[08] Sat 27Feb16 12:18:16 - SSH_FXP_NAME: translated path: /remotefolder/remotefolder1/remotefolder2
[13] Sat 27Feb16 12:18:16 - (Action: "E:\localfolder\localfolder1" to "/") - Uploading from "E:\localfolder\localfolder" to "/"
[07] Sat 27Feb16 12:18:16 - SSH_FXP_STAT: path: /localfolder1/Test Doc.txt
[08] Sat 27Feb16 12:18:16 - SSH_FXP_STATUS: status: SSH_FX_NO_SUCH_FILE; description: No such file
[03] Sat 27Feb16 12:18:16 - Sending: E:\localfolder\localfolder1\Test Doc.txt -> /remotefolder2/Test Doc.txt
[07] Sat 27Feb16 12:18:16 - SSH_FXP_STAT: path: /remotefolder2
[03] Sat 27Feb16 12:18:16 - Connecting to "XXX.XXX.XXX.XXX" on port 22.
[03] Sat 27Feb16 12:18:16 - Connected to XXX.XXX.XXX.XXX:22 from XXX.XXX.XXX.XXX:57917.
[03] Sat 27Feb16 12:18:16 - Negotiating SSH2 session with server...
[03] Sat 27Feb16 12:18:16 - Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
[03] Sat 27Feb16 12:18:16 - Server Identification: SSH-2.0-OpenSSH_5.3
[03] Sat 27Feb16 12:18:16 - Initializing key exchange process...
[03] Sat 27Feb16 12:18:16 - Selected key exchange algorithm: diffie-hellman-group1-sha1
[08] Sat 27Feb16 12:18:16 - SSH_FXP_STATUS: status: SSH_FX_NO_SUCH_FILE; description: No such file
[07] Sat 27Feb16 12:18:16 - SSH_FXP_MKDIR: path: /remotefolder2
[08] Sat 27Feb16 12:18:16 - SSH_FXP_STATUS: status: SSH_FX_PERMISSION_DENIED; description: Permission denied
[04] Sat 27Feb16 12:18:16 - Unable to create parent folder for upload: /remotefolder2
[04] Sat 27Feb16 12:18:16 - Upload failed: Could not create target path for "/remotefolder2/Test Doc.txt"
[04] Sat 27Feb16 12:18:16 - Retrying failed transfer (attempt 2 out of 3)...
any help would be great.
thanks,
Hi
I am trying to run Execute an ftp voyager scheduled sync manually,
This scheduled event syncs files from Pershing to a network location on our server
It looks like it works and ftp voyager scheduler does not spit out an error neither do I receive an email notification that sync has failed which I set up yesterday in the Event section of Task properties.
but when I go to the network share the files look like they have not been synced.
Passwords for the connections were changed on Saturday the 10th of November but since then I have entered the new passwords in FTP Voyager.
so I checked the logs below.
03] Wed 14Nov18 09:34:55 - Resolving host "clientftp.bnymellon.com"...
[03] Wed 14Nov18 09:34:55 - Connecting to "170.61.238.34" on port 22.
@
[03] Wed 14Nov18 09:34:55 - Connected to 170.61.238.34:22 from 10.0.3.7:51906.
[03] Wed 14Nov18 09:34:55 - Negotiating SSH2 session with server...
[03] Wed 14Nov18 09:34:55 - Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
[03] Wed 14Nov18 09:34:55 - Server Identification: SSH-2.0-Serv-U_15.0.0.0
[03] Wed 14Nov18 09:34:55 - Initializing key exchange process...
[03] Wed 14Nov18 09:34:55 - Selected key exchange algorithm: diffie-hellman-group1-sha1
[03] Wed 14Nov18 09:34:55 - Host Key Fingerprint: 7A:D3:AB:F6:04:85:42:2A:04:60:4E:7B:CA:48:EA:C3
[03] Wed 14Nov18 09:34:55 - Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
[03] Wed 14Nov18 09:34:55 - Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
[03] Wed 14Nov18 09:34:55 - Selected public key protocol: ssh-dss
[03] Wed 14Nov18 09:34:55 - Key exchange process successfully completed.
[07] Wed 14Nov18 09:34:55 - SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
[08] Wed 14Nov18 09:34:55 - SSH_MSG_SERVICE_ACCEPT: service accepted
[03] Wed 14Nov18 09:34:55 - Querying server for supported authentication methods
[07] Wed 14Nov18 09:34:55 - SSH_MSG_USERAUTH_REQUEST: user: qg5n8a1; service: ssh-connection; type: none
[08] Wed 14Nov18 09:34:55 - SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
[03] Wed 14Nov18 09:34:55 - Supported authentication methods: password, publickey
[07] Wed 14Nov18 09:34:55 - SSH_MSG_USERAUTH_REQUEST: user: qg5n8a1; service: ssh-connection; type: password
[04] Wed 14Nov18 09:34:55 - Password not accepted.
[04] Wed 14Nov18 09:34:55 - Unable to login.
[04] Wed 14Nov18 09:34:55 - Connection attempt failed. Retrying in 3 seconds...
[07] Wed 14Nov18 09:34:55 - SSH_MSG_DISCONNECT: reason code 11; description: Password not accepted.
[04] Wed 14Nov18 09:34:55 - The server has unexpectedly closed the connection.
[04] Wed 14Nov18 09:34:55 - Connection attempt failed. Retrying in 3 seconds...
Please help.
I want to use FTP Voyager to upload data on a regular schedule from remote sites to my FTP server. The application checks all of the boxes for what I need it to do: Upload all files in a folder, do some XCRC/XMD5/XSHA1, and then delete the local files after successful upload. My problem is that the scheduled task seems to never complete sometimes and we stop receiving files.
The Internet connections for most of our locations frequently drop. It seems this might have something to do with the problem. My oldest installation has been running reliably since July and has a solid connection. The scheduler hangs most frequently on sites with the worst connectivity issues.
I have implemented a klugey work-around by scheduling a task that restarts the Voyager scheduler service. This keeps the problem from manifesting and we receive our files.
I set the following scheduler options:
Scheduled task creation:
This setup works perfectly well in my lab and at the site with the consistent Internet connection. Other locations have been seen to work for days and even weeks, but eventually the scheduled task hangs until the scheduler service is restarted. Any help would be greatly appreciated.
I'm trying to used the command line interface of FTP Voyager and the 'profile' switch is working to connect me to the correct site, but the 'put' is not. The site opens and I don't see any attempt to upload the file.
Below is the generated command line:
D:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe profile=NOR1 put=T:\Cognos\Exports\NOR1\AFFSHB20140417.tab
Hi,
I installed the FTP Voyager software on a server on a 2nd site. Everything has been configured on site 1 and is working as intended. I configured everything the same way on site 2nd site and the task never ends. I tried a backup and a sync with and without other tasks (emails on success/failure), nothing works. It does the job as insrtucted but the task never ends meaning the next day, the backup will never run.
How can I fix this?
Hi
I am able to upload files to a remote destimation but there is
a problem downloading.
For example, when I donwload a csv, it downloads the
file name and extension of .csv but the contents is blank and is 0KB in
size.
Do you know what would be causing this please?
Best regards
Dan
Hi
I have set up the SMTP for the scheduler to use the smtp details for Office 365 which uses port 587. When the event attempts to run, I get an error saying
Unable to send message to xxxxxxxxxxx Unable to connect to SMTP server on port 25
1) Why is this failing?
2) Why is it saying it is using port 25 when I have told it to use port 587?
Thanks
We recently replaced our server and had to move FTP Voyager. We took a backup copy of the files as outlined in the article http://www.serv-u.com/kb/1189/how-to-back-up-and-restore-ftp-voyager . We did a new install of FTPVoyager v 16.1.0 and reinstalled the backup files onto the new server.
We have now discovered after much head scratching and lost hours, that the email settings relating to SMTP server, and the sending address (From) are not being correctly maintained. We tried to update the SMTP setttings in the GUI (both in Scheduler and in Voyager) but they are not used when Scheduler runs an Event that requires email. Instead, it appears to use the ones in the FTPVoyagerSettings.Archive file.
In order to change the SMTP server name and the "From" entry we now have to do this by hacking the FTPVoyagerSettings.Archive file rather than via the GUI.
Is this a known bug? Is there anything we can do to get the parameters set in the GUI of Voyager and Scheduler to be retained and used?
Also, whilst asking questions in this area, why are there 2 interfaces for email settings under Tools - one in Options and one in Scheduler options. These seem to be independent as we can put different values in each which are retained between sessions- both of which are ignored(!) in favour of those in FTPVoyagerSettings.Archive file. I have been unable to track down where the GUI values are actually stored.
A right dog's breakfast.
Barry Sutton.
Hello,
when i try connect to ftp i get error:
SSL accept failed on FTP data channel.
The connection will be aborted
but i can connect with FileZilla or other ftp clients.
FTP Voyager 16.2.0.328
log:
STATUS> Resolving host "ftp.xxxxxx.xx"...
STATUS> Connecting to "xxx.xxx.xxx.xxx" on port 990.
STATUS> Connected to xxx.xxx.xxx.xxx:990 from 10.10.10.10:56773.
STATUS> Negotiating SSL connection with server...
STATUS> SSL connection established. All transactions are now secure.
STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.
220 (vsFTPd 3.0.2)
COMMAND> HOST ftp.xxxxxx.xx
530 Please login with USER and PASS.
STATUS> Connected. Logging in to the server.
COMMAND> USER ftp-baku
331 Please specify the password.
COMMAND> PASS ***
230 Login successful.
STATUS> Login successful.
COMMAND> SYST
215 UNIX Type: L8
COMMAND> FEAT
211-Features:
AUTH TLS
EPRT
EPSV
MDTM
PASV
PBSZ
PROT
REST STREAM
SIZE
TVFS
UTF8
211 End
STATUS> Server supports resume.
COMMAND> OPTS UTF8 ON
200 Always in UTF8 mode.
COMMAND> PBSZ 0
550 Permission denied.
COMMAND> PROT P
550 Permission denied.
COMMAND> PROT C
550 Permission denied.
COMMAND> PWD
257 "/"
COMMAND> PASV
227 Entering Passive Mode (82,138,52,71,34,222).
STATUS> Opening passive mode data connection to xxx.xxx.xxx.xxx, port 8926.
STATUS> Negotiating SSL connection with server...
COMMAND> LIST
150 Here comes the directory listing.
226 Directory send OK.
ERROR> SSL Accept failed on FTP data channel. The connection will be aborted.
Please help me with solving a problem.
We are evaluating FTP Voyager for automating file transfers between sites with SSL. There are two worrisome issues:
I believe the two issues may be related. Issue number 2 is an annoyance but not a show stopper. Issue number 1 on the other hand is preventing me from completing my proof of concept and integration into monitoring.
The scheduler service is running as a domain user with full rights to the server it's running on.
Any assistance would be greatly appreciated. I can provide log files, screen shots, etc. if required.
Thanks,
-Mike
Hello,
We are trying to set up FTP Voyager for use with Serv-U. The scenario is this: we want to have a user set up in Serv-U so that when they log in and upload a file FTP Voyager is invoked via command line to move a file to another system (lileky the file that was uploaded). The problem is that we cannot seem to get FTP Voyager to actually work as intended even removing Serv-U from the equation.
According to KB article #1140 this is the command line to invoke FTP Voyager:
"C:\Program Files\RhinoSoft\FTP Voyager\FTPVoyager.exe" profile="Personal Site.My Site" put=C:\file.txt
I get Voyager to come up and it does log into the profile just fine because we see the user's remote folder structure however the "put" command does not work, regardless of how it is invoked. We have tried a number of command line structures including how it is actually invocked in Serv-U which looked like this in the logs:
Event: FILE_UPLOAD (mtintdev file upload); Type: EXECUTE; Path "C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe"; Parameters "profile="TESTDEVORA" put="Q:\DEV\files\testuser\testfile.txt"
(In the user event we actually use these parameters: profile="TESTDEVORA" put=$LocalPathName so that it goes to the file that was just uploaded but that's beside the point right now.)
If this is put in the command window:
"C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe" profile=TESTDEVORA put=Q:\DEV\files\testuser\testfile.txt
Voyager loads, we get the remote folder but nothign else happens. It's as if the "put" command is not recognized. Anyone else have this issue? Suggestions?
I am getting this error and I don't know what the problem is.
SSH Disconnect Error: no more authentication methods available.
We are using Serv-U on the back-end and FTP Voyager on the front end.
Regular password based connections work fine.
As soon as I create a private / public key and bind it to the user (on both sides), then the authentication will not work.
Here is the log.
Perhaps I have to disable password authentication before public key authenication will work?
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58052.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 2)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58054.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 3)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58056.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 4)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58058.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 5)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58060.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 6)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58061.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 7)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58064.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
ERROR> The server has unexpectedly closed the connection.
ERROR> Could not establish a connection to MFT-AIM.