Is there a way to run FTP Voyager using scheduled events from a server while not logged in?

Hello together,

is it possible that FTP-Voyager has a problem with a 4096bit ssh-rsa host key?

I am using FTP Voyager Version 16.2.0.328. I am not able to connect to an SFTP-Server with an ssh host key with 4096 bit. Are there any settings or options I have to change?

It's working with an other ftp client.

Thank you for your Help.

Kind Regards

visitor

Hello everyone,

I need to recovery password for any users in FTP Voyager client Version 16.2.

I don't remember their passwords .

Is there any way decipher them ?

Many thanks

Fedel

Hi,

We have a schedule running every minute to move files from one location to another

It seems to run fine the 99% of the time however occasionally the task hangs and is stuck at executing (which therefore makes our other tasks wait in the queue)

It is so sporadic but looks as though it only occurs when a file is created in the outbound folder at the same time as the task is executing

The error message I get in the log is as per below:

[04] Wed 21Oct15 13:53:22 - SSL Accept failed on FTP data channel. The connection will be aborted.

Thanks,

Mike

Hi,

We have a scheduled task that should upload a file to a remote location via FTP over SSL or TLS. This was working fine with version 15 but not now with version 16. The upload works sometimes but most of the time it doesn't.

We really need this to work or else a downgrade must be done. So any ideas or questions will be appreciated.

Kind regards,

Peter Nilsson

STATUS> Resolving host "ftps.xxxxx.xx"...

STATUS> Connecting to "nnn.nnn.nnn.nnn" on port 21.

STATUS> Connected to nnn.nnn.nnn.nnn:21 from nnn.nn.n.nnn:64626.

220-FTP 10:12:22 on 2016-03-15.

220 Connection will close if idle for more than 5 minutes.

COMMAND> AUTH TLS

234 Security environment established - ready for negotiation

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

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

STATUS> Connected. Logging in to the server.

COMMAND> USER xyz

331 Send password please.

COMMAND> PASS ***

230 xyz is logged on.  Working directory is "/remotefolder1/remotefolder2/out".

STATUS> Login successful.

COMMAND> SYST

215 UNIX is the operating system of this server. FTP Server is running on z/OS.

COMMAND> FEAT

211- Extensions supported

SIZE

MDTM

AUTH TLS

PBSZ

PROT

211 End

COMMAND> REST 100

504 Restart requires Block or Compressed transfer mode.

STATUS> Server supports resume.

COMMAND> PBSZ 0

200 Protection buffer size accepted

COMMAND> PROT P

200 Data connection protection set to private

COMMAND> PWD

257 "/remotefolder1/remotefolder2/out" is the HFS working directory.

COMMAND> CWD /remotefolder1/remotefolder2/in

250 HFS directory /remotefolder1/remotefolder2/in is the current working directory

COMMAND> PASV

227 Entering Passive Mode (nnn,nnn,nnn,nnn,nnn,nn)

STATUS> Opening passive mode data connection to nnn.nnn.nnn.nnn, port 60734.

STATUS> Negotiating SSL connection with server...

COMMAND> LIST /remotefolder1/remotefolder2/in/File123.txt

550 LIST cmd failed : ls: FSUM6785 File or directory "/remotefolder1/remotefolder2/in/File123.txt" is not found

STATUS> Sending: \\localserver\localfolder1\localfolder2\out\File123.txt -> /remotefolder1/remotefolder2/in/File123.txt

COMMAND> TYPE A

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

STATUS> Resolving host "ftps.xxxxx.xx"...

STATUS> Connecting to "nnn.nnn.nnn.nnn" on port 21.

STATUS> Connected to nnn.nnn.nnn.nnn:21 from nnn.nn.n.nnn:64630.

220-FTP 10:12:25 on 2016-03-15.

220 Connection will close if idle for more than 5 minutes.

COMMAND> AUTH TLS

234 Security environment established - ready for negotiation

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

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

STATUS> Connected. Logging in to the server.

COMMAND> USER xyz

331 Send password please.

COMMAND> PASS ***

230 xyz is logged on.  Working directory is "/remotefolder1/remotefolder2/out".

STATUS> Login successful.

COMMAND> SYST

215 UNIX is the operating system of this server. FTP Server is running on z/OS.

COMMAND> FEAT

211- Extensions supported

SIZE

MDTM

AUTH TLS

PBSZ

PROT

211 End

COMMAND> REST 100

504 Restart requires Block or Compressed transfer mode.

STATUS> Server supports resume.

COMMAND> PBSZ 0

200 Protection buffer size accepted

COMMAND> PROT P

200 Data connection protection set to private

COMMAND> PWD

257 "/remotefolder1/remotefolder2/out" is the HFS working directory.

COMMAND> QUIT

221 Quit command received. Goodbye.

Hello,

when i try connect to ftp i get error:

SSL accept failed on FTP data channel.

The connection will be aborted

but i can connect with FileZilla or other ftp clients.

FTP Voyager 16.2.0.328

log:

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

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

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

STATUS> Negotiating SSL connection with server...

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

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

220 (vsFTPd 3.0.2)

COMMAND> HOST ftp.xxxxxx.xx

530 Please login with USER and PASS.

STATUS> Connected. Logging in to the server.

COMMAND> USER ftp-baku

331 Please specify the password.

COMMAND> PASS ***

230 Login successful.

STATUS> Login successful.

COMMAND> SYST

215 UNIX Type: L8

COMMAND> FEAT

211-Features:

AUTH TLS

EPRT

EPSV

MDTM

PASV

PBSZ

PROT

REST STREAM

SIZE

TVFS

UTF8

211 End

STATUS> Server supports resume.

COMMAND> OPTS UTF8 ON

200 Always in UTF8 mode.

COMMAND> PBSZ 0

550 Permission denied.

COMMAND> PROT P

550 Permission denied.

COMMAND> PROT C

550 Permission denied.

COMMAND> PWD

257 "/"

COMMAND> PASV

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

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

STATUS> Negotiating SSL connection with server...

COMMAND> LIST

150 Here comes the directory listing.

226 Directory send OK.

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

Please help me with solving a problem.

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?

Welcome to the FTP Voyager space on thwack!  If this is your first time here, you’ll find a wealth of information available to you on FTP Voyager as well as other SolarWinds products.  thwack is an active community where SolarWinds customers can share ideas and tips, ask questions, discuss feature requests, and find out what’s in the latest release and what’s coming next.  SolarWinds Product Management, Development, and Support staff all regularly monitor and post to thwack.  We look forward to hearing your feedback and ideas!

-Craig

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

We have had some complaints about connecting to our Serv-U server with FTP Voyager, because of these complaints I have decided to test it myself.

FTP Voyager version: 16.2.0.328

Serv-U version: 15.1.6.25

I don't have many SSL/TLS options for the FTP/FTPS protocols in FTP Voyager but it fails when it tries to read the SSL certificate. We use this solution:

Deploy Serv-U MFT in a cluster - SolarWinds Worldwide, LLC. Help and Support

This is the error:

FileZilla and FTP Voyager with the exact same settings, from the exact same computer, with the same user and at the same time. FileZilla works, FTP Voyager does not.

The log the Serv-U server shows when FTP Voyager wants to connect.

I have asked the Solarwinds support for help because we make use of their Serv-U solution but they do not support their FTP Voyager application, so they cannot help me.

Do you guys have any problems with FTP Voyager in combination with these solutions FTP explict FTP over TLS or FTP implicit FTP over TLS?

If yes, do you have any solution?

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.

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

I'm not sure if these issues are related or not. Just upgraded from version 10 to version 16 and am having an issue with one of my sites. Nightly I send a large zip file via FTP voyager scheduler and since upgrading, if the file is over 1Gig, it will timeout around 1Gig and say remote host disconnected. I've been falsely assuming it was on our remote end and discovered this morning that with filezilla it sends the file no issues every time. The second thing I noticed is filezilla uses my full pipe (sending 9MB/s) so the file goes in a couple minutes. With FTP voyager on the same machine at the same time of day I get transfer speeds of around 650Kb/s and after about 20~ minutes it times out.

Any help would be appreciated. I worry if I Can't solve this soon I'll be force to switch all my sites over to filezilla.

Hello

I am trying to connect to a site using FTP over TLS (explicit) with port 21.

I am able to connect with no problems using other FTP clients but I cannot with FTP Voyager.

I am able to connect using standard FTP.

I am also able to connect with SSH which I didnt know I could.

My password is correct.  Again, I can connect with many other clients using the same settings.

Could it have anything with FTP Voyager thinking the server certificate is insecure?

ANy setting to allow insecure certificates to try that?

ANy help is apprecoated.

Thanks

This is the log:

STATUS> Resolving host "ftp.mysite.net"...

STATUS> Connecting to "111.111.111.58" on port 21.

STATUS> Connected to 111.111.111.58:21 from 192.168.1.127:51112.

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

220-You are user number 1 of 50 allowed.

220-Local time is now 10: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.

COMMAND> AUTH TLS

234 AUTH TLS OK.

ERROR> Connection attempt failed.  Retrying in 3 seconds...

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,

Got FTP-Voyager to work great in command mode using a batch file to initiate file sync to my server from industrial robots to back them up.  Was working great as far as doing the job closing out starting another instance and going to the next robot.

New problem.....

It no longer closes out at the end of the sync.  What option did I change that keeps FTP-Voyager from closing ?  I am using "autoquit=1" in the command line.

Thanks

Stan

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

Hi

I am trying to run Execute an ftp voyager scheduled sync manually,

This scheduled event syncs files from Pershing to a network location on our server

It looks like it works and ftp voyager scheduler does not spit out an error neither do I receive an email notification that sync has failed which I set up yesterday in the Event section of Task properties.

but when I go to the network share the files look like they have not been synced.

Passwords for the connections were changed on Saturday the 10th of November but since then I have entered the new passwords in FTP Voyager.

so I checked the logs below.

03] Wed 14Nov18 09:34:55 - Resolving host "clientftp.bnymellon.com"...

[03] Wed 14Nov18 09:34:55 - Connecting to "170.61.238.34" on port 22.

@

[03] Wed 14Nov18 09:34:55 - Connected to 170.61.238.34:22 from 10.0.3.7:51906.

[03] Wed 14Nov18 09:34:55 - Negotiating SSH2 session with server...

[03] Wed 14Nov18 09:34:55 - Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

[03] Wed 14Nov18 09:34:55 - Server Identification: SSH-2.0-Serv-U_15.0.0.0

[03] Wed 14Nov18 09:34:55 - Initializing key exchange process...

[03] Wed 14Nov18 09:34:55 - Selected key exchange algorithm: diffie-hellman-group1-sha1

[03] Wed 14Nov18 09:34:55 - Host Key Fingerprint: 7A:D3:AB:F6:04:85:42:2A:04:60:4E:7B:CA:48:EA:C3

[03] Wed 14Nov18 09:34:55 - Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

[03] Wed 14Nov18 09:34:55 - Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

[03] Wed 14Nov18 09:34:55 - Selected public key protocol: ssh-dss

[03] Wed 14Nov18 09:34:55 - Key exchange process successfully completed.

[07] Wed 14Nov18 09:34:55 - SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

[08] Wed 14Nov18 09:34:55 - SSH_MSG_SERVICE_ACCEPT: service accepted

[03] Wed 14Nov18 09:34:55 - Querying server for supported authentication methods

[07] Wed 14Nov18 09:34:55 - SSH_MSG_USERAUTH_REQUEST: user: qg5n8a1; service: ssh-connection; type: none

[08] Wed 14Nov18 09:34:55 - SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

[03] Wed 14Nov18 09:34:55 - Supported authentication methods: password, publickey

[07] Wed 14Nov18 09:34:55 - SSH_MSG_USERAUTH_REQUEST: user: qg5n8a1; service: ssh-connection; type: password

[04] Wed 14Nov18 09:34:55 - Password not accepted.

[04] Wed 14Nov18 09:34:55 - Unable to login.

[04] Wed 14Nov18 09:34:55 - Connection attempt failed. Retrying in 3 seconds...

[07] Wed 14Nov18 09:34:55 - SSH_MSG_DISCONNECT: reason code 11; description: Password not accepted.

[04] Wed 14Nov18 09:34:55 - The server has unexpectedly closed the connection.

[04] Wed 14Nov18 09:34:55 - Connection attempt failed. Retrying in 3 seconds...

Please help.

We have had some complaints about connecting to our Serv-U server with FTP Voyager, because of these complaints I have decided to test it myself.

FTP Voyager version: 16.2.0.328

Serv-U version: 15.1.6.25

I don't have many SSL/TLS options for the FTP/FTPS protocols in FTP Voyager but it fails when it tries to read the SSL certificate. We use this solution:

Deploy Serv-U MFT in a cluster - SolarWinds Worldwide, LLC. Help and Support

This is the error:

FileZilla and FTP Voyager with the exact same settings, from the exact same computer, with the same user and at the same time. FileZilla works, FTP Voyager does not.

The log the Serv-U server shows when FTP Voyager wants to connect.

I have asked the Solarwinds support for help because we make use of their Serv-U solution but they do not support their FTP Voyager application, so they cannot help me.

Do you guys have any problems with FTP Voyager in combination with these solutions FTP explict FTP over TLS or FTP implicit FTP over TLS?

If yes, do you have any solution?