How can I easily migrate from version 15.2.0.19 to 16.1.0.0?  I've managed to import my site profiles into ftp voyager, however how do I import my scheduled tasks into scheduler?

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

Continually getting the following message after a connection is created from FTP Voyager:

SSL accept failed on FTP data channel - The connection will be aborted

Using FTP over TLS - explicit

Works from FileZilla for example to the same host with the same credentials.

Do FTP voyager keep a history for the status log?

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

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

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

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

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

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

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

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

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

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

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 scheduled FTP Voyager job that runs weeknights and sends me an email at the end of the job.

Last night, I started getting an email every second from the job.

I was fortunate enough to find a solution, here:  https://thwack.solarwinds.com/message/338097

I'm running version 16.2.0.328.

A coworker has an installation of 15.2.0.17 that seems unaffected by this bug.

How can I download a safe copy of an older version of FTP Voyager to test if my job would be unaffected if run under that version?

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

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

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

Our server is Windows Server 2012 R2 Standard.

Thanks

Greg

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

Hi,

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

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

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

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

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

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

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

Regards,

Dhiraj

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

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

Thanks

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

We are using FTP voyager for our ftp services and I am very new to this client.

I am planning to migrate our ftp sites to new AWS environment and when I tried to connect using Site Profiles Manager for an SFTP client, I am getting an error like this

The server has unexpectedly closed the connection.

Would you please help me to find a solution for it?

This is the log file info

Thanks

Suj

I am attempting to connect to a Ubuntu server running Open SSH via SFTP using FTP Voyager, but I cannot get the private/public keys to be accepted.  The same keys work fine for Putty (SSH).  Any thoughts?

Hi,

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

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

Will there be a new version of FTP Voyager?

I'm trying to used the command line interface of FTP Voyager and the 'profile' switch is working to connect me to the correct site, but the 'put' is not.  The site opens and I don't see any attempt to upload the file.

Below is the generated command line:

D:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe profile=NOR1 put=T:\Cognos\Exports\NOR1\AFFSHB20140417.tab

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