Hi All. I upgraded by FTP Voyager/Scheduler from v13 to v16. The interface I like along with the stability but I am having issues galore. So I'll post some and see what I get back. The questions below assume it worked fine in v13 and isn't or is doing something different in v16.

1) My downloads from Unix to Windows used ASCII and was fine. Now the CR (carriage returns) are being stripped and I can't figure out why or how to fix it. In global and profile options I have tried all 3 transfer modes. The file is still stripped.

2) My scheduler actions I have just the file to download and the local path I could use the variables for dates and also rename it from there. Now, if I use a variable or rename in that local path line, it creates a folder with the dates variables and put the file in side unchanged. <- driving me crazy.

3) Many jobs were failing saying "path not found" which I learned has to be the absolute path now. Is this true?

Any help with these would be great. I have had to write a bunch of batch files for temporary use until I can figure out how to make Voyager do it [again] like it has been.

Thanks all

Hi All,

I'm trying to rename a file that has a date in the filename, but the 2 methods I'm trying are both failing.

Using date variables followed by a wildcard                                             Using date variables WITHOUT a wildcard

Since today is September 30 2014, I KNOW %m = 09, %d = 30, and %Y = 2014. Yet, somehow the date variables are not being interpreted. Any idea why not?

Hi All,

   I have a file on a remote site, File1.txt and I need to download it twice. Each time however, I need to rename the file to a different name:

File1.txt   --->   abc.txt

File1.txt   --->   def.txt

I'm not sure how to accomplish this, since file rename rules are PROFILE specific rather than Scheduled Job Specific. Any ideas?

Thanks.

Al

I am using the FTP Voyager Scheduler (16.2.0.328) on a Windows server to transfer files to a Red Hat Linux server.  The vsftpd daemon is running on the Linux server and is configured with a create mask of 000.  All files sent to this server should have rw-rw-rw- permissions. From the Windows server, files transferred with ftp.exe or FileZilla have the expected permissions. Files transferred with FTP Voyager, using the same Linux account, have rw-r--r--- permissions.  I can only assume that this is a feature of FTP Voyager.  Although the documentation shows how to manually change file permissions, I could not find where or how to set the default permissions.  Is there any way to get FTP Voyager to assign specific file permissions or not to set them at all?

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.

Hello

I’m trying to run FTP Voyager from the command line like so:call "C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe" profile=ZFTP autosync=1 syncoptions=0 local=C:\zsm2web\ remote=/ZSMDOC/ autoquit=1

This works if the remote folder is empty.

I want  to overwrite the existing files based on the timestamp of the files in the local folder or delete the files if they dont exist in de local folder.

Can anyone give me a working example using :

syncoptions List

•         SyncRemote = 0x0000

•         SyncLocal = 0x0001

• IgnoreCase = 0x0002

• CompareSize = 0x0004

• CompareTime = 0x0008

• IncludeDirs = 0x0010

• DontDelete = 0x0020

• OverwriteConfirmations = 0x0040

• DeleteConfirmations = 0x0080

• RemoteIgnoreNewer = 0x0100

• RemoteIgnoreOlder = 0x0200

• LocalIgnoreNewer = 0x0400

• LocalIgnoreOlder = 0x0800

• MinimizeStatusDialogs = 0x1000

• QueueErrorMessages = 0x2000

• IgnoreSymbolicLinks = 0x4000

  Not sure how i should add this to the command line so a complete working example woulde be appreciated

I have my FTP Voyager Scheduler setup to automatically connect to a server and download a backup file (about 17GB).

The process starts at 3:00am and ends at about 7:45am.  However, if I do it manually, it will only take about 45 minutes.  Any ideas on how to speed up the scheduled process or settings I have selected that might slow it down?

I know it's not bandwidth or network congestion because I can do the manual transfer during the day with everybody on the network.  At 3:00am, nobody is on the network.

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!

So the Move Down functionality in FTP Voyager Scheduler is not consistent with what one would typically call a file move operation.  Previously, in version 15 of FTP Voyager, a Move Down operation behaved like this:

1. Get list of all files at destination.
2. Copy remote file to local destination.
3. Delete remote file.
4. Go to next file on list.
5. Continue until list is empty.

Now, however, version 16 behaves like this:

1. Get list of all files at destination.
2. Copy remote file to local destination.
3. Go to next file.
4. Continue until list generated at step 1 is complete.
5. Delete all remote files at destination, regardless of what was contained in list generated at step 1.

Effectively it is just the Download and Delete Remote Path commands chained together.  This is a big problem for my automation, as I cannot guarantee that the folder won't have new files created in it during download operations #2-4, which will then ultimately get deleted by step #5.

So long story short, can the behavior be reverted to the v15 style of move?

I've been a long-time user of FTP Voyager, well before SW bought up RhinoSoft.  I even paid for it too, back in those days.  However, lately I upgraded to the new version, and found out that hey!  It's free now!  Cool!

However, all was not sunshine and roses.  I too have run into the FTP Voyager Scheduler empty folder bug, wherein you perform a "Move Down" command against an empty folder and it simply sits there.  In my case, it performs KEEP ALIVE tasks to hold the connection open.  Critically, because this task is still executing, it will not execute any of the other scheduled tasks.  See below for a log output.

[03] Fri 05Dec14 14:15:49 - Getting "real path" name to keep connection alive (KEEP ALIVE)

[07] Fri 05Dec14 14:15:49 - SSH_FXP_REALPATH: translating path: .

[08] Fri 05Dec14 14:15:49 - SSH_FXP_NAME: translated path: /

[03] Fri 05Dec14 14:18:49 - Getting "real path" name to keep connection alive (KEEP ALIVE)

[07] Fri 05Dec14 14:18:49 - SSH_FXP_REALPATH: translating path: .

[08] Fri 05Dec14 14:18:49 - SSH_FXP_NAME: translated path: /

I see that this is a known issue here on the forums, and that there are supposidly "bug fix requests" or something to handle it.  However, I have a problem with this NOW.

I believe I found a simple work around.  I chained a file upload to the destination folder first, uploading a single 1-byte file to the destination, and THEN performing the full folder move down.

This will always cause the remote folder to have something in it, and for then the task to complete successfully.  I then set up my local-side automation to ignore that file, and things were working.

Not exactly elegant, but it's working for now. :-/

I succesfully logged into a server and saw the content available.

I selected what I wanted to download and chose Download.

Now the log shows

STATUS>    Connecting to "64.27.7.34" on port 21.

STATUS>    Connected to 64.27.7.34:21 from 192.168.1.78:60507.

ERROR>    The server has unexpectedly closed the connection.

and cycles this 8 more times.

I cannot now see the content on the server and if I close FT Voyager and restart it just goes thru'

STATUS>    Connecting to "64.27.7.34" on port 21.

STATUS>    Connected to 64.27.7.34:21 from 192.168.1.78:60507.

ERROR>    The server has unexpectedly closed the connection.

9 times again!

Any thoughts would be helpful.

Nigel

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

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

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

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

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

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, I am a new user and am confused about something probably very simple.

I'd like to transfer music files from my PC to my Android phone.

I've used FileZilla easily for this, but it doesn't have the sync features of FTP Voyager. In FTP Voyager when I put in the FTP info. (Eg. ftp://10.0.0.55::8317) it requires a 'user name/Password. When I do this into FileZilla it does not and I am able to transfer files.

Can somebody please help?

Thanks

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

Looking on some help with this connection issue. I've tried passive mode, turned most options off and then one at a time...to troubleshoot and still no luck.

Trying to connect to and IBM MVS through FTP Voyager and getting directory listing error.

FTP Voyager - Version 16.2.0.328

[14:15:05] STATUS> Connecting to "*.*.*.*" on port **.
[14:15:05] STATUS> Connected to *.*.*.*:* from *.*.*.*:******.
[14:15:05]  220-FTPD1 IBM FTP CS V1R13 at ****.********.******.*******, *:*:* on 2016-02-24.
[14:15:05]  220 Connection will close if idle for more than 10 minutes.
[14:15:05] COMMAND> AUTH SSL
[14:15:06]  234 Security environment established - ready for negotiation
[14:15:06] STATUS> SSL connection established. All transactions are now secure.
[14:15:06] STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.
[14:15:06] STATUS> Connected. Logging in to the server.
[14:15:06] COMMAND> USER ********
[14:15:06]  331 Send password please.
[14:15:06] COMMAND> PASS ***
[14:15:06]  230 ****** is logged on.  Working directory is "******.".
[14:15:06] STATUS> Login successful.
[14:15:06] COMMAND> SYST
[14:15:06]  215 MVS is the operating system of this server. FTP Server is running on z/OS.
[14:15:06] STATUS> Server supports resume.
[14:15:06] COMMAND> PBSZ 0
[14:15:06]  200 Protection buffer size accepted
[14:15:06] COMMAND> PROT P
[14:15:06]  200 Data connection protection set to private
[14:15:06] COMMAND> PWD
[14:15:06]  257 "******.'" is working directory.
[14:15:06] COMMAND> CWD '******.'
[14:15:06]  250 "******." is the working directory name prefix.
[14:15:06] COMMAND> PORT *,*,*,*,*,*
[14:15:06]  200 Port request OK.
[14:15:06] COMMAND> LIST
[14:15:06]  550 No data sets found.
[14:15:06] ERROR> The default directory specified for this site profile is not accessible.  Please double-check your site profile settings.  Trying to access home directory instead...

I am getting this error only when connecting to a server with a profile under "scheduler site profile" (under tools), when using and identical profile under the regular "site profiles" (under browser) I don't get the error. It's very consistent when I try the scheduler site profile first and many times. Once I try the site in the regular profile and it connects I can then go back to the scheduler profile and it connects just fine. If I stop and start the scheduler service the error returns.

Any ideas? I've made sure both profiles are identical. I've also removed and re-created the scheduler profile. I don't get it. It's like a bug.

I've tried the re-connection and timeout values but they don't seem to help as it actually does connect but then immediately get's disconnected.

Some log below:

12] Thu 13Feb14 18:30:01 - (Task: CTABS Daily Upload) - Performing scheduled execution of task for Thursday, February 13, 2014 18:30:00.

[03] Thu 13Feb14 18:30:02 - Resolving host "eippftp.com"...

[03] Thu 13Feb14 18:30:02 - Connecting to "67.228.3.18" on port 22.

[03] Thu 13Feb14 18:30:02 - Connected to 67.228.3.18:22 from 10.4.60.160:17567.

[03] Thu 13Feb14 18:30:02 - Negotiating SSH2 session with server...

[03] Thu 13Feb14 18:30:02 - Client Identification: SSH-2.0-FTP Voyager_16.1.0.0

[04] Thu 13Feb14 18:30:02 - The server has unexpectedly closed the connection.

[12] Thu 13Feb14 18:30:02 - (Task: CTABS Daily Upload) - Execution failed (Last Error Message: ).

[12] Thu 13Feb14 18:30:02 - (Task: CTABS Daily Upload) - Next scheduled execution on Friday, February 14, 2014 18:30:00

Thanks all :-)

I have almost 100 scheduled task and I would like to know if we can add more. I tried creating new task but I think the limit is set to 100. Is there any way to change this?

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 realize that the company has little incentive to worry about how their free FTP client inter-operates with a rival server product, but I wondered if anyone had any clues about my problems connecting to IIS FTP server.  (Long ago I purchased Serv-U for my now geriatric server, and once owned an actual purchased copy of FTP voyager back when it was a paid product.  But by the time moved to a new server, Serv-U went upscale and is way too expensive for my humble purposes.)

I get two types of error, which might or might not be related:

1) When uploading multiple files at once to the server, the connection always hangs on the second file after successfully uploading one file.  IIS log looks like this:

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 990 PASV - 227 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 59159 DataChannelOpened - - 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 59159 DataChannelClosed - - 2 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 990 LIST /transfer/cart-proc.png 550 2 0 1566c127-f9c4-423d-a1b3-baaa0225faea /transfer/cart-proc.png -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 990 TYPE I 200 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 990 PASV - 227 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 59160 DataChannelOpened - - 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 59160 DataChannelClosed - - 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 990 STOR cart-proc.png 226 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea /transfer/cart-proc.png -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 990 XCRC "/transfer/cart-proc.png" 500 87 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 990 MDTM 20151217045612+/transfer/cart-proc.png 213 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea /transfer/cart-proc.png -

2016-03-02 19:20:56 11.22.33.44 servername\username 44.33.22.11 990 PASV - 227 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:57 - servername\username 44.33.22.11 59161 DataChannelClosed - - 2 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:57 11.22.33.44 servername\username 44.33.22.11 990 LIST /transfer/core-strat.png 550 2 0 1566c127-f9c4-423d-a1b3-baaa0225faea /transfer/core-strat.png -

2016-03-02 19:20:57 11.22.33.44 servername\username 44.33.22.11 990 PASV - 227 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:57 - servername\username 44.33.22.11 59162 DataChannelClosed - - 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

2016-03-02 19:20:57 11.22.33.44 servername\username 44.33.22.11 990 ControlChannelClosed - - 0 0 1566c127-f9c4-423d-a1b3-baaa0225faea - -

This is just uploading a bunch of random images to a folder called "transfer".  After the LIST command for the second filename (to see if it's already there), and another PASV command, everything poops out.

2) I get a lot of "SSL Accept Failed on FTP Data Channel" errors.  These pop up any time I try to upload a file when a file of the same name already exists in the destination folder; and also at random other times.  To get anything done, I need to delete or rename any file of the same name from the server first before uploading; and when the "SSL Accept ..." error pops up at other random times, I need to refresh the destination folder and try again, sometimes repeating this cycle several times.  Eventually it always works, but it's a pain.  The IIS log file for an attempt to upload a file which already exists, generating the "SSL Accept ..." error, looks like this:

2016-03-02 20:56:26 11.22.33.44 - 44.33.22.11 990 ControlChannelOpened - - 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:26 11.22.33.44 - 44.33.22.11 990 USER username 331 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:26 11.22.33.44 servername\username 44.33.22.11 990 PASS *** 230 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 / -

2016-03-02 20:56:26 11.22.33.44 servername\username 44.33.22.11 990 SYST - 215 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:26 11.22.33.44 servername\username 44.33.22.11 990 FEAT - 211 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:26 11.22.33.44 servername\username 44.33.22.11 990 OPTS UTF8+ON 200 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:26 11.22.33.44 servername\username 44.33.22.11 990 PBSZ 0 200 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:26 11.22.33.44 servername\username 44.33.22.11 990 PROT P 200 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:26 11.22.33.44 servername\username 44.33.22.11 990 PWD - 257 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:26 11.22.33.44 servername\username 44.33.22.11 990 CWD /transfer 250 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 /transfer -

2016-03-02 20:56:26 11.22.33.44 servername\username 44.33.22.11 990 PASV - 227 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:27 11.22.33.44 servername\username 44.33.22.11 64021 DataChannelOpened - - 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:27 11.22.33.44 servername\username 44.33.22.11 64021 DataChannelClosed - - 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:27 11.22.33.44 servername\username 44.33.22.11 990 LIST /transfer/pxspoe.png 226 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 /transfer/pxspoe.png -

2016-03-02 20:56:27 11.22.33.44 servername\username 44.33.22.11 990 PASV - 227 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:27 11.22.33.44 servername\username 44.33.22.11 64022 DataChannelOpened - - 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:27 11.22.33.44 servername\username 44.33.22.11 64022 DataChannelClosed - - 2 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:27 11.22.33.44 servername\username 44.33.22.11 990 LIST /transfer/pxspoe+(2).png 550 2 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 /transfer/pxspoe+(2).png -

2016-03-02 20:56:27 11.22.33.44 servername\username 44.33.22.11 990 TYPE I 200 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

2016-03-02 20:56:30 11.22.33.44 servername\username 44.33.22.11 990 ControlChannelClosed - - 0 0 cca4903e-ca7c-4a25-87ba-dd2af0e98a04 - -

It's not very informative.  It gets as far as verifying that the alternative filename is available, and then poops out.  IIS FTP server seems to have no more logging detail available.  It's not just a dumb-nuts firewall problem, since I can upload individual files one at a time in passive mode using the tricks mentioned above.

Any insight is appreciated.