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.

I'm new to Voyager FTP.  How can I edit the permissions in existing jobs

yaI'm currently exploring using Voyager for a large multi-user deployment where files will be uploaded on an hourly or daily basis to a common ftp location via Scheduler.   The requirement is that the files that were recently transferred should be moved into a post-processing folder for safe keeping in case there is a reason to need to re-process them or retrieve the files that were uploaded.

Other than doing a generic batch file and moving '*' from the local source to the local archive destination, I do not see a way to accomplish what I need to do.   The batch solution would work, but I am looking for something more elgant, and preferably with file  by file copies so that error checking and logging can be handled better than a generic "copy * c:\newlocation"

Please let me know if Im missing an obvious feature, or if this is indeed not possible.

Hi,

Recently got a new computer, and I don't ftp very often, here's the errors I'm receiving, sorry for the length:

FTP Voyager - Version 15.2.0.0

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:18. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> HOST ftp.j-a-associates.com

          530 You aren't logged in

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

COMMAND:> FEAT

          211-Extensions supported:

           EPRT

           IDLE

           MDTM

           SIZE

           REST STREAM

           MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;

           MLSD

           AUTH TLS

           PBSZ

           PROT

           ESTA

           PASV

           EPSV

           SPSV

           ESTP

          211 End.

STATUS:>  Server supports resume

COMMAND:> PWD

          257 "/" is your current location

COMMAND:> CWD /

          250 OK. Current directory is /

COMMAND:> OPTS MLST Type;Size;Modify;UNIX.mode;UNIX.owner;UNIX.group;

          200  MLST OPTS type;size;sizd;modify;UNIX.mode;UNIX.uid;UNIX.gid;unique;

COMMAND:> PORT 192,168,1,103,220,112

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 2)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:19. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,115

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 3)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 4 of 50 allowed.

          220-Local time is now 16:20. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,118

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 4)...

COMMAND:> NOOP

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:22. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,149

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 5)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:23. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,153

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 6)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 4 of 50 allowed.

          220-Local time is now 16:25. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,158

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 7)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 4 of 50 allowed.

          220-Local time is now 16:26. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

COMMAND:> NOOP

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,160

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 8)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:28. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,165

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 9)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:29. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,169

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 10)...

COMMAND:> NOOP

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 2 of 50 allowed.

          220-Local time is now 16:31. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,213

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 11)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 2 of 50 allowed.

          220-Local time is now 16:32. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

COMMAND:> NOOP

          200 Zzz...

I am helping a local accounting firm migrate their infrastructure to a virtual cloud environment where they have multiple virtual desktops and one virtual server with their data on it. Prior to moving their data, one of their daily duties was to scan documents into PDF's and drop them on a network share in a particular folder for their customer(s) for data retention. Now that they are using a cloud, this process becomes more challenging. My thought was to use the Voyager FTP solution along with Voyager FTP Scheduler to take files scanned on a desktop and saved locally on a folder and sync it with their virtual server via an FTP connection. If I create a folder on the virtual server called "tempscans" and kick off the task on Voyager Scheduler, it will save this file to the correct folder. Now I am wondering if this utility can merge files in existing folders when it does it's scheduled sync? My thought was to create a local folder on each local desktop with just the folder structure that has the names of their customers only minus any files. That way, when they scan a document into PDF, they can perform a "Save As" option to the respected folder and hopefully, when the scheduled sync kicks off, it will just merge that new file in with the existing and in the existing folder.

Is this possible with this client?

Just wondering if there is documentation or syntax for initiating an FXP transfer in FTP Voyager from the command line? I know how to do it in the GUI, but it would be useful to be able to script it.

Im just testing the free voyager 16 on default settings. With large files over several GB the speed either drops down to almost zero, or the transfer just restarts.

Tried transfering one image backup, at one point it had 15 minutes left, the next time it had started the transfer all over again.

Any ideas if this is a bug or some setting that could be adjusted?

Is FTP Voyager (v 16.2.0.328) TLS 1.1 and/or 1.2 compatible?

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?

Hey Guys -

I do a lot of downloading over the internet via FTP - most of which are files 1gb - 8gb.  For a couple of years now, I've used SmartFTP due to it's feature of being able to set "Multi-Part Transfers.  Using this makes downloading much faster per file!  For example, when downloading a large file (1gb+) with default settings, it downloads at ~250kb/s  when above is set to 32, I go my max speed of 2.0mb/s.  If not familer, here's how the setting works:

- It applies to each download worker

- You may set the file size threshold for it to be used (I set mine to 1mb)

- You configure how many "Parts" (connections) you wish for it to use (between 1 - 32)

- It may be enabled or disabled globally or per favorite

I'm trying to find an alternative FTP client as SmartFTP has had issues recently, but cannot find one which offers this setting.  Does FTP Voyager?

I downloaded and installed FTP Voyager and started a download from the same site with default settings and 1 worker.  The download speed capped at about 270kb/s.

If you could tell me how to set this if available, I'd appreciate it very much!

Thank You!

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.

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

I'm running FTP Voyager 16.1.0.0 on Windows 7 on a Dell laptop.  It opens and functions properly, but after a minute or so, it abruptly closes with a Window error message "FTP Voyager has stopped working". Needless to say, the necessity to keep opening the program because it consistently closes itself is frustrating.  Any thoughts?

I'm using ftp Voyager at a daily basis to check remote sites and move down all files.

The task works almost every day. Exception are when the remote ftp site is empty. Here the task will run continuously.

I've tried to turn off keep alive, but it continues to run forever.

I'd like the task to fail, if no files.

Anyone knows what i'm doing wrong?

Thanks.

Hi,

I'm trying to use FTP Voyager Scheduler to upload files on the FTP. But if the connection was disconnected during the files transfer, the scheduler was hang (still showing executing, but from the log, you can see that nothing is running).

Is it possible to solve this problem? Please kindly advice. Thank you.

We've been trying to track down an issue with some scheduled transfers and it turned out that logging to files wasn't enabled on this particular task. I've enabled it and allowed it to run overnight however the log file I expected to see wasn't created. Is there anything that needs to be done after modifying a task to get the changes to take effect?

Also, I opened the Scheduler Log tab in this task about an hour ago and it's still "thinking". What would cause something like this?

I've had FTP Voyager and FTP Scheduler installed for many years.

On 11/2/2012 the scheduler stopped running nightly backups and now only generates errors when manually executing the jobs.

"Could not retrieve additional information about the local path. Please make sure the path exists and the local user has permissions".

This system has been setup for years and has not changed. The FTP Voyager can manually connect to the profile and I can download files from the server manually without problems.

The only major change to the system were recent FTP software upgrades and patches.

I've double checked the FTP Scheduler Profiles (which never changed passwords in the first place).

I've added a brand new FTP folder with new login password to the server which connects in FTP Voyager, but generates the same errors when manually executing a synch job in FTPV Scheduler.

And I've tried restarting the FTP Voyager Scheduler service and rebooting.

Also nothing has changed on the server and all the files and folders have full read/write access (and can be copied down manually from the FTP Voyager).

Its only when executing the job from within FTP Scheduler that it now fails with these messages and it started around 11/2/12.  But I can't recall on what dates I applied the FTP software patches and upgrades.

We are using the scheduler to move files to a customer ftp server. The process just moves files, nothing else. Currently the task will run but hang, when we check the customer ftp server we can see files are transferred. But there is always zero length files. I assume these are the placeholder of the file to be transferred. Process will just hang after 5 or 6 files and the files that are transferred are not deleting from home directory. The files are only 2kb each so I can't imagine file size being the problem.

Is there a queue size limit on number of files that can be transferred? We have sometimes up to a thousand files that will need to be moved. Also does the process only delete after it has completed? We have seen it complete once or twice with about 40 files, but that is so random we can't call it an actual successful test.

Thanks

Jim

Hello SolarWinds and FTP Voyager developers. I got a feature request. I am testing some FTP programs and like FTP Voyager sofar. But I am missing support for SCP (Secure Copy Protocol). I got some servers and a router. They support SSH login via putty. If I try to connect via SSH with FTP Voyager (or any other FTP client) I get disconnected. I also tried WinSCP with SSH. It disconnects also. If I switch from SSH to SCP in WinSCP, I can connect fine and transfer files without problems. But I do not want to have 2 or more programs installed and WinSCP has less features than FTP Voyager. Therefore it would be nice if you could add support for SCP.

ftp Voyager Scheduler 16.1.0.0 is set to run many scheduled uploads, but on many of these uploads it appears to hang after completion, the log records the task as completed with the last lines reading:

Sent xxxxx bytes

Transfer time: 00:00:02.587

QUIT

221

but in the Scheduler task tab the task appears to be still running, this blocks all other tasks from starting and a user must manually abort the running task.

Anyone any ideas what might be happening here?