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.

Just recently our server that is running FTP Voyager, started experiencing some odd things with the scheduler.  The tray icon will show up and seem like it is running.  Btw, we're running 16.2.0.328.  However, when I click on the system tray and try to start the management console, it never comes up.  I can kill the processes and try again, but it doesn't change anything.  I can see the tray and scheduler processes running in the task manager.  Is there any other way to get the management console for the scheduler to come up?  Any help would be greatly appreciated.

Our server is Windows Server 2012 R2 Standard.

Thanks

Greg

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

I noticed that voyager has the option to save the logs locally but per scheduler .

Is it possible to have all the schedulers logs saved in one? or send them to a log target?

Thank you!

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????

Hi,

We are using FTP Voyager 16.1.0.0 & sometimes schedule task stuck. There are 5 actions (Local Folders Synchronize) used. Task log are showing below messages.

Kindly suggest what could be the problem & how to resolve it.

[03] Thu 27Nov14 11:08:09 - Transferred 80,058 bytes. 625.45 KB/sec.

[05] Thu 27Nov14 11:08:09 - XCRC "/DATA/Data_11272014_1_00_02_AM.CSV"

[06] Thu 27Nov14 11:08:09 - 500 'XCRC "/Data/Data_11272014_1_00_02_AM.CSV"': command not understood.

[04] Thu 27Nov14 11:08:09 - XCRC command failed. The command may not be supported by this server.

[03] Thu 27Nov14 11:08:09 - XCRC command checking has been disabled for future transfers using this session.

Regards,

Dhiraj

I'm setting up the FTP Voyager Scheduler to download backup files from our F5's. It works on some, with this log message:

[12] Tue 13Oct15 12:05:04 - (Task: f5-internal-01_backup) - Execution successfully completed.

[07] Tue 13Oct15 12:05:07 - SSH_MSG_DISCONNECT: reason code 11; description: Disconnection initiated by user.

But fails on 4 out of 6 with this log message:

The last message is from having to cancel the task, as it just sits at "Executing". The only difference is the F5 OS version, the ones that work are 11.2.0 and the ones that fail are 11.6.0, anyone see this before?

Help!  I had been using FTP Voyager 15.2.0.11 to access an ancient VAX computer.   My old computer crashed & had to be replaced.   Now, it seems I have no choice but upgrade to FTP Voyager 16.2.   I have a copy of the 15.2 FTP Voyager, but I have lost the Registration ID in the computer crash.  The new 16.2 version is much, much different from 15.2;  when I try to use my settings notes from 15.2 on 16.2, the old settings don't seem to apply.   This Voyager is lost at sea!  SOS

Hi support team,

If we have multiple tasks that are executing at same time, seems like they will be queued up and executing one after another (in another work NOT at same time). is this the case? or can we set this dfferently?

Please advise.

Thanks

Best Regards

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.

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

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

Hello -

I'm a new user of FTP Voyager.

I'm uploading a large file, and I've been pausing and resuming the transfer in an effort to troubleshoot some connectivity issues.  I'm uploading to a web server over explicit FTP over SSL.

In doing so, I noticed that the count of "Transferred" data is being counted in correctly.

When I resume a transfer, the amount of data transferred should start from the size of the file currently on the target server.  Instead, it is adding the amount that was previously transferred to the size of the file on the target server.  Each time I pause and resume, the amount transferred jumps even higher.

The file I'm currently experimenting with is 429,386KB

The server currently has 327,839 KB of that file uploaded to it.

After several stops and restarts, the transfer queue says I now have transferred "937 MB of 419 MB" on that 1 file.

Another quick resume and pause, and now it says I have transferred "1,249 MB of 419 MB"

So that should be a pretty simple bug to fix.

----------------------

Separate but related issue:

I will also note that when I have the transfer paused and I refresh the target directory, I see the current file size of the target file -- the amount that has been transferred so far.

I resume the transfer, I see the transfer taking place in the transfer queue.  The file size in the target directory stays the same.  (Not a problem.)

When I pause the transfer, the target directory updates, and suddenly shows the file size as being very small -- I believe it's just the amount that was transferred in the most recent block between "resume" and "pause"

If I right click the target directory and choose "refresh", then the directory updates and once again shows the correct file size for the partially uploaded file.

So those are two bugs that should be investigated.

Thanks

James Grove

We need to send a document via FTP over TLS (Explicit) using TLS 1.1.  Does FTP Voyager 16.1 support that?  If so, how do I get my site profile to use that?

Thanks

Hi,

I have a question about FTP Voyager and SFTP (SSH).

Why doesn't the FTP client support SFTP via SSH3 and only SSH2?
Product: FTP Voyager (Free Windows Client) Version: 16.2.0.328

Will there be a new version of FTP Voyager?

I have setup FTP Voyager with the SMTP settings for gmail to send an email after FTP Scheduler completes a task. I have added the event, send email after task complete, however I do not receive an email.

Any help would be appreciated

Regards

Nick

FTP-Voyager :

Using command line.

Want to upload (to my computer / plant network) files from a Fanuc robot.  The Fanuc robot stores teach pendent files and others files in directories on the robot's internal hard drive.

Using "get=*.*" will not work just as the help files indicate.  Alternate would be to use syncronization.

My question is how to use syncoption command.  The text in the help files are confusing as to which syncoption=1  or syncoption=0 writes to the local hard drive and does not write to the remote hard drive.

It is critical I get it right or I will wipe out the files on a robot and cause massive down time.  Once I figure it out then it's no problem, copy paste in batch file.  (not time to experiment on first time I try it !)

I will be reading all files from the robot and storing into an empty directory on the computer / network as a backup device.  The only time I will write to the robot(s) is when I need to restore a robot on an individual basis like after a power failure and a dead battery in the robot.  I will be writing a batch file with the task of backing up several hundred robots with several hundred files per robot.

(1) Is the syncronization method the best way ? ie: ftp-voyager can only do 100 timed tasks,  I need to have the batch file create and move to new directories under a folder for each robot, and capture all the files.

(2) How does the syncoption command work ie :

• syncoptions: The syncoptions flag specifies how a Synchronization will take place. To determine what value should be used, refer to the list at the bottom of this page. The value here must be a decimal representation of the sum of all applicable hex values. The simplest ones are syncoptions=0 (synchronize a remote folder to a local folder) and syncoptions=1 (synchronize a local folder to a remote folder)
• Synchronize a remote directory to a local directory: "C:\Program Files\RhinoSoft\FTP Voyager\FTPVoyager.exe" profile=YourProfileName autosync=1 syncoptions=1 local=C:\dat\ remote=/dat/ autoquit=1
• Synchronize a local directory to a remote directory: "C:\Program Files\RhinoSoft\FTP Voyager\FTPVoyager.exe" profile=YourProfileName autosync=1 syncoptions=0 local=C:\dat\ remote=/dat/ autoquit=1

The question is which one of these is right ?

Thanks

Stan

Well i am confused with the syncoptions switchs. The documentation is very odd and not very straight forward.

What i am needing to do is move all folders and their contents from a local folder to a remote folder that already has folders and files.   I need everything to remain on the remote and only add the new folder from the local, then clear the local folder.    A 'cut and paste into' type move.

What option would i use?

The 0  and 1 options seem to indicate it will delete everything on side A that is not on side B, and then copy side B files over to side A, thus being 'synced'.

I need more of a move from side A and add to everything on side B.

• syncoptions: The syncoptions flag specifies how a Synchronization will take place. To determine what value should be used, refer to the list at the bottom of this page. The value here must be a decimal representation of the sum of all applicable hex values. If no other options are specified, the synchronization process will upload or download missing files from the master, and delete files from the target that are missing from the master. The simplest syncoptions are the following:
  • syncoptions=0 - synchronize a remote folder to a local folder. The master is the local folder, and the remote folder is getting synchronized to match it.
  • syncoptions=1 - synchronize a local folder to a remote folder. The master is the remote folder, and the local folder is getting synchronized to match it.
• SyncRemote = 0x0000
• SyncLocal = 0x0001
• IgnoreCase = 0x0002
• CompareSize = 0x0004
• CompareTime = 0x0008
• IncludeDirs = 0x0010
• DontDelete = 0x0020
• OverwriteConfirmations = 0x0040
• DeleteConfirmations = 0x0080
• RemoteIgnoreNewer = 0x0100
• RemoteIgnoreOlder = 0x0200
• LocalIgnoreNewer = 0x0400
• LocalIgnoreOlder = 0x0800
• MinimizeStatusDialogs = 0x1000
• QueueErrorMessages = 0x2000
• IgnoreSymbolicLinks = 0x4000

I have a connection set up to a server, all that is fine...

I can send smaller files just fine...

Larger files? It seems that the Command channel times out...

In the header of the Welcome message is a warning of a timeout at 3 minutes of inactivity...

So I dutifully setup a 150 second Keep Alive...

What I see in the log is...

The file (11GB+) sends fine...(Although there seems to be many reconnections during the transfer)

I will see an OPTS MLST command send

followed by a PWD and then a reconnection attempt...

Finally I will see a "Transfered <many> bytes STATUS message... Followed by an XCRC - which seems to receive no response after maybe 30 seconds...

Then another PWD...

Then an ERROR> Server has unexpectedly closed the connection...

And we start again....

Ideas?