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 want to use FTP Voyager to upload data on a regular schedule from remote sites to my FTP server.  The application checks all of the boxes for what I need it to do: Upload all files in a folder, do some XCRC/XMD5/XSHA1, and then delete the local files after successful upload.  My problem is that the scheduled task seems to never complete sometimes and we stop receiving files.

The Internet connections for most of our locations frequently drop.  It seems this might have something to do with the problem.  My oldest installation has been running reliably since July and has a solid connection.  The scheduler hangs most frequently on sites with the worst connectivity issues.

I have implemented a klugey work-around by scheduling a task that restarts the Voyager scheduler service.  This keeps the problem from manifesting and we receive our files.

I set the following scheduler options:

• connection timeout = 90
• connection retries = 9
• connection delay = 3
• transfer send timeout = 90
• transfer idle timeout = 5
• file transfer upload file tries = 10

Scheduled task creation:

1. I create a scheduled task that runs every 15 minutes.
2. Add an action to run an external program.  This executes a batch file that moves files into a staging folder for the FTP transfer.
3. Add a second action to synchronize remote folders.  This moves the files up to our FTP server.
   1. I add an event to this action that runs a batch file after upload.  The batch file is there to delete the uploaded file and is passed, "$LocalPath", as an argument.

This setup works perfectly well in my lab and at the site with the consistent Internet connection.  Other locations have been seen to work for days and even weeks, but eventually the scheduled task hangs until the scheduler service is restarted.  Any help would be greatly appreciated.

Hello,

I have setup a FTP Voyager Scheduled Task that will not executing.  The task is setup to reach out to a FTP to move down any available files and also move up any new files that have been created locally.

When the task is scheduled, it will not stop executing and no available files are pulled down from the FTP or moved up to the FTP site.

Any help is appreciated.

Thanks

If I create a new site profile in Voyager I can not see it in Scheduler when I go to set up a new task. How do I get Scheduler to see the profiles created in Voyager? I seem to recall at one time (maybe an earlier version) that there was a way to "send" the profiles to Scheduler....

In scheduler I can see 2 folders - Sites, Personal Sites. But both are empty - even though there are lots of sites defined under these folders in Voyager.

Moreover, when I change site profile details e.g. IP address in Voyager, this is not being picked up by Scheduler which continues to try to connect to the old address.

There seems to be a total breakdown in connection between Voyager and Scheduler.

HELP!

I have a scheduled task to download a txt from SFTP site with FTP Voyager.

However, the task met with error message ' The server has unexpectedly closed the connection.' when the download comes to one hour.

Tried the download with other tool like FileZilla. It's all OK.

Our FTP Voyager version is 16.2.0.328.

Does anyone have idea on such case?

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 everyone,

   I am new to FTP Voyager, and I am using FTP Scheduler feature to sync the data on remtoe ftps site. It

Client OS: Windows 7 /10 Professional

Server: Windows 2012 R2 with FileZilla Server installed.

Issue details:  I want to sync the data on ftps server to my local network share driver. It happens that when the transfor over the internet, If I set up the ftps in the intranet, there is no problem.

But I am SURE that all the ports that FileZilla using is opened on the firewall. I can use FTP Voyager client to download the files manually

Based on the documentation on the offical website, I disable the UAC and use UNC instead of mapped letter. When I sync the data, a few minutes later, I found the following errors:

I also use Wireshark to troubleshot the problem and found that there is no responsing from client after FTP server send the ACK packet:

Any ideas on the issue?

Regards,

Bruce

Users transfer date to serv-U server with FTP Voyager.

User do also transfer data to some linux SFTP servers.

We used to have FTP Voyager 15.2.0.15 - everything worked fine.

Since updating to FTP Voyager 16.0.2.0 authentication
with linux SFTP servers fail (connection to Serv-U is still working) It seames that the password is not transferred to the server.

Whithout configuring user and password in server profile: I've been asked for a username - not for the password.

     Log: SSH_MSG_USERAUTH_FAILURE

     /var/log/messages:

Jul  5 07:59:21 chwiitsv042 sshd[29597]: Connection from 10.142.40.230 port 2087

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: Client protocol version 2.0; client software version FTP Voyager_16.0.2.0

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: no match: FTP Voyager_16.0.2.0

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: Enabling compatibility mode for protocol 2.0

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: Local version string SSH-2.0-OpenSSH_5.1

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: user zfs-sftp matched group list sftponly at line 143

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: initializing for "zfs-sftp"

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: setting PAM_RHOST to "10.142.40.230"

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: setting PAM_TTY to "ssh"

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: do_cleanup

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: cleanup

Anyone an idea what's wrong ?

Thank you very much

Christof

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

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 there a way i can have a schedule setup to send a file and move the file once sent to a SENT folder. ive used other Clients before where this is possible but im struggling to find an option to do this,

we have a folder full of files that need to be sent out over FTP, once the files have been sent the files will need to be moved to the SENT folder as a backup.

many thanks in advanced and hope there is something that can be done

Hello,

when i try connect to ftp i get error:

SSL accept failed on FTP data channel.

The connection will be aborted

but i can connect with FileZilla or other ftp clients.

FTP Voyager 16.2.0.328

log:

STATUS> Resolving host "ftp.xxxxxx.xx"...

STATUS> Connecting to "xxx.xxx.xxx.xxx" on port 990.

STATUS> Connected to xxx.xxx.xxx.xxx:990 from 10.10.10.10:56773.

STATUS> Negotiating SSL connection with server...

STATUS> SSL connection established. All transactions are now secure.

STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.

220 (vsFTPd 3.0.2)

COMMAND> HOST ftp.xxxxxx.xx

530 Please login with USER and PASS.

STATUS> Connected. Logging in to the server.

COMMAND> USER ftp-baku

331 Please specify the password.

COMMAND> PASS ***

230 Login successful.

STATUS> Login successful.

COMMAND> SYST

215 UNIX Type: L8

COMMAND> FEAT

211-Features:

AUTH TLS

EPRT

EPSV

MDTM

PASV

PBSZ

PROT

REST STREAM

SIZE

TVFS

UTF8

211 End

STATUS> Server supports resume.

COMMAND> OPTS UTF8 ON

200 Always in UTF8 mode.

COMMAND> PBSZ 0

550 Permission denied.

COMMAND> PROT P

550 Permission denied.

COMMAND> PROT C

550 Permission denied.

COMMAND> PWD

257 "/"

COMMAND> PASV

227 Entering Passive Mode (82,138,52,71,34,222).

STATUS> Opening passive mode data connection to xxx.xxx.xxx.xxx, port 8926.

STATUS> Negotiating SSL connection with server...

COMMAND> LIST

150 Here comes the directory listing.

226 Directory send OK.

ERROR> SSL Accept failed on FTP data channel. The connection will be aborted.

Please help me with solving a problem.

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

I'm running this script on my PC1 with FTP Voyager version 16.2 but it does just open FTP voyager and DOES NOTHING.  No file transfer at all.

I checked and I do see 2 zip files inside d:\temp\ folder.  However if I take this same script and execute on another PC and it work fine.  This PC has same FTP voyager version and same configuration as PC1.

Can someone help? thanks.

FOR %%G in (d:\temp\*.zip) do (

echo.found %%G

"C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe" profile="Art_Test_FTPserver" put=%%G remote="/" logfile=NAR_upload.log -nostartupwizard -nosplash autoquit=1

Echo uploaded %%G successfully

Echo.

)

Echo.

Echo completed ...

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

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

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.

We are evaluating FTP Voyager for automating file transfers between sites with SSL. There are two worrisome issues:

1. Email reporting is failing. I am receiving an error in the Scheduler log stating the following:
   1. [04] Wed 31Dec14 13:43:30 - EVENT ERROR: Unable to send message to 'Test_email_Address': Unable to connect to SMTP server  on port 25.
   2. Our SMTP server is functioning with other services from this same server.
   3. I have input the SMTP information into both the FTP Voyager Options and the Scheduler Options.
   4. I have also checked the configuration files called out in another thread here and see our SMTP information correctly.
2. I cannot create Scheduler Site Profiles directly.
   1. I have to create them in the FTP Voyager Site Profile First and then right click and select 'Copy to Scheduler'
   2. If I create them in the Scheduler Site Profile directly, none of the advanced features apply correctly and the profile will not connect to the SSL site.

I believe the two issues may be related.  Issue number 2 is an annoyance but not a show stopper. Issue number 1 on the other hand is preventing me from completing my proof of concept and integration into monitoring.

The scheduler service is running as a domain user with full rights to the server it's running on.

Any assistance would be greatly appreciated. I can provide log files, screen shots, etc. if required.

Thanks,

-Mike

Hello,

I have been going crazy attempting to upload files to another (Linux) server and I am getting errors.

once I figured out how to get the sites to show up when using the scheduler, i used the export and import rather then re-create accounts.

a users guide with examples would be really great!  i can find any such thing.

so the issue i am see is this...   I can connect using the browser and upload files with no issues.  when i use the scheduler, I have to specfiy the local and remote directories.  this is where things get interesting.  I am placed in a home directory on the remote side, so for the remote side I just use / and for the local side i click on the folder icon and navigate to the folder E:\folder\folder1  and I would assume that everything in folder1 would be uploaded.  Wrong! it tries to create the remotefolder2 and dose not have permissions and so it fails.  why is it trying to create folders?  in the help man, it says that the directory listed in the local and remote will grab everything in that folder and says nothging about trying to create that folder.  I just want to move files in that local folder1 to the remotefolder2.

the Actions I have tried so far is as follows:

Upload: "E:\localfolder\localfolder1" to "/"

Upload: "E:\localfolder\localfolder1" to "/remotefolder/remotefolder1/remotefolder2"

Upload: "E:\localfolder\localfolder1\*.*" to "/"

any trailing "/" or "\" are removed when you hit save.

when I add the /remotefolder/remotefolder1/remotefolder2 to the remote folder location, the error logs show it attempts to create remote directories remotefolder/remotefolder1/remotefolder2

I have changed the site profile advanced options \ file transfer \ transfer mode to Binary.

here is the thing i don't understand.  I can connect using the browser and see the remote site, and i can transfer files to and delete on the remote end with no issues at all and the logs are much smaller.  only when trying to use the scheduler is where things go goofy.

[07] Sat 27Feb16 12:18:15 - SSH_MSG_USERAUTH_REQUEST: user: XXXXXX; service: ssh-connection; type: publickey

[08] Sat 27Feb16 12:18:15 - SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

[07] Sat 27Feb16 12:18:15 - SSH_MSG_USERAUTH_REQUEST: user: XXXXXX; service: ssh-connection; type: publickey

[08] Sat 27Feb16 12:18:16 - SSH_MSG_USERAUTH_SUCCESS: authentication successful

[03] Sat 27Feb16 12:18:16 - Login successful.

[07] Sat 27Feb16 12:18:16 - SSH_MSG_CHANNEL_OPEN: type: session; local channel: 0

[08] Sat 27Feb16 12:18:16 - SSH_MSG_CHANNEL_OPEN_CONFIRMATION: local channel: 0; remote channel: 0

[07] Sat 27Feb16 12:18:16 - SSH_MSG_CHANNEL_REQUEST: remote channel: 0; request type: subsystem; subsytem: sftp

[08] Sat 27Feb16 12:18:16 - SSH_MSG_CHANNEL_SUCCESS: channel request succeeded; local channel: 0

[07] Sat 27Feb16 12:18:16 - SSH_FXP_INIT: client version: 6

[08] Sat 27Feb16 12:18:16 - SSH_FXP_VERSION: server version: 3

[03] Sat 27Feb16 12:18:16 - Negotiated SFTP version 3

[07] Sat 27Feb16 12:18:16 - SSH_FXP_REALPATH: translating path: .

[08] Sat 27Feb16 12:18:16 - SSH_FXP_NAME: translated path: /remotefolder/remotefolder1/remotefolder2

[13] Sat 27Feb16 12:18:16 - (Action: "E:\localfolder\localfolder1" to "/") - Uploading from "E:\localfolder\localfolder" to "/"

[07] Sat 27Feb16 12:18:16 - SSH_FXP_STAT: path: /localfolder1/Test Doc.txt

[08] Sat 27Feb16 12:18:16 - SSH_FXP_STATUS: status: SSH_FX_NO_SUCH_FILE; description: No such file

[03] Sat 27Feb16 12:18:16 - Sending: E:\localfolder\localfolder1\Test Doc.txt -> /remotefolder2/Test Doc.txt

[07] Sat 27Feb16 12:18:16 - SSH_FXP_STAT: path: /remotefolder2

[03] Sat 27Feb16 12:18:16 - Connecting to "XXX.XXX.XXX.XXX" on port 22.

[03] Sat 27Feb16 12:18:16 - Connected to XXX.XXX.XXX.XXX:22 from XXX.XXX.XXX.XXX:57917.

[03] Sat 27Feb16 12:18:16 - Negotiating SSH2 session with server...

[03] Sat 27Feb16 12:18:16 - Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

[03] Sat 27Feb16 12:18:16 - Server Identification: SSH-2.0-OpenSSH_5.3

[03] Sat 27Feb16 12:18:16 - Initializing key exchange process...

[03] Sat 27Feb16 12:18:16 - Selected key exchange algorithm: diffie-hellman-group1-sha1

[08] Sat 27Feb16 12:18:16 - SSH_FXP_STATUS: status: SSH_FX_NO_SUCH_FILE; description: No such file

[07] Sat 27Feb16 12:18:16 - SSH_FXP_MKDIR: path: /remotefolder2

[08] Sat 27Feb16 12:18:16 - SSH_FXP_STATUS: status: SSH_FX_PERMISSION_DENIED; description: Permission denied

[04] Sat 27Feb16 12:18:16 - Unable to create parent folder for upload: /remotefolder2

[04] Sat 27Feb16 12:18:16 - Upload failed: Could not create target path for "/remotefolder2/Test Doc.txt"

[04] Sat 27Feb16 12:18:16 - Retrying failed transfer (attempt 2 out of 3)...

any help would be great.

thanks,

Hi

I've referred to here by FTP Voyager support.

This is my first time I use FTP Voyager for scheduling file transfer, configuring task was very easy, but I still cannot make it work.

In the task action, I created a new action to download a specific folder (and all files and subfolders inside that folder to my local PC

In action information, I put the (Remote File or Folder) as: /FolderName

Nothing downloaded, and error in the log says:

Execution failed (Last Error Message: Unable to perform file action: Could not retrieve additional information about the source path.  Does the source path exist?).

I changed it to: FolderName (without slash).

Nothing downloaded, and same error in the log.

I then tried: FolderName/*.*

Log says: Execution successfully completed.

But in the local folder, I found it only downloaded files from main folder (No subfolders or files inside them), and some of them with ZERO size !!!!!

Again, I tried: /FolderName/*.*

Log says: Execution successfully completed.

I found that the ZERO size problem has been solved (files downloaded with correct size) but still cannot get the subfolders !

In the forum, I found a link to the older version (ver. 15.2.0.19)

I downloaded and tried it on another PC, It works like a charm, with no errors !

Can anyone here help me to figure out how to make the scheduler download the whole content of remote folder ??