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.

   I'm a professional musician and use FTP Voyager  to upload updated pages to my website. I've used the product probably since around 1999-2000, when I did a couple years of very basic web work as a developer, but I am totally away from the world of development for over a decade now. I had an auto-saved password on the Connect log-in box of FTP Voyager, and over the years, something happened that I no longer have that password. I know the User ID, but since there is no official support for Voyager because it is a free product now, I'm uncertain what to do. Meanwhile, I am able to use the Quick Connect, and I do have the User ID and Password for my domain, so I've been able to upload the files that way.

   I recently had someone hack my password and they uploaded over a hundred folders onto my website. I've since changed my server password to something very strong. I sought out phone support only to find that I cannot get any. I wanted to get all my password ducks in a row, so to speak -- I have no idea how to reset the basic Connect password.

{ So my question }: Is it a big deal that I can only log into my FTP Voyager via the Quick Connect? (and not the basic Connect)

Thanks!

~ Rebecca

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 :-)

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

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

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

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?

I've got a number of jobs that I want to schedule to run every 5 minutes.

E.g. I've set-up the job with 'Execute task every 5 minutes'

However, what seems to happen is that the jobs runs, then adds 65 minutes before the next execution!

Any ideas?

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

The FTP voyager doesn't delete the file after a move up.

When I perform a move task and the a delete task, the server moves and deletes perfectly the file. But I want that both actions can be handled with the move up.

I use the FTP voyager version 16.1.0.0

03] Wed 12Apr17 13:44:16 - Server supports resume.

[05] Wed 12Apr17 13:44:16 - CLNT FTP Voyager 16.1.0.0

[05] Wed 12Apr17 13:44:16 - STOR 20170412112901_20170412112858_af_5_4.pdf

[06] Wed 12Apr17 13:44:16 - 200 Don't care

[05] Wed 12Apr17 13:44:16 - OPTS UTF8 ON

[06] Wed 12Apr17 13:44:16 - 150 Opening data channel for file upload to server of "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412112901_20170412112858_af_5_4.pdf"

[06] Wed 12Apr17 13:44:17 - 202 UTF8 mode is always enabled. No need to send this command.

[05] Wed 12Apr17 13:44:17 - PWD

[06] Wed 12Apr17 13:44:17 - 257 "/" is current directory.

[05] Wed 12Apr17 13:44:17 - CWD /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste

[06] Wed 12Apr17 13:44:17 - 250 CWD successful. "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste" is current directory.

[05] Wed 12Apr17 13:44:17 - MLST /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf

[06] Wed 12Apr17 13:44:17 - 250-Listing /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf

[06] Wed 12Apr17 13:44:17 -  type=file;size=174798;modify=20170412114416; /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf

[06] Wed 12Apr17 13:44:17 - 250 End

[05] Wed 12Apr17 13:44:17 - MLST /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0 (2).pdf

[06] Wed 12Apr17 13:44:17 - 550 File or directory not found.

[03] Wed 12Apr17 13:44:17 - Sending: C:\ADM\Test2\BE0659837055_AF_Aankoopfacturen_BrasserieJuste\20170412113759_20170412113758_ENI_0.pdf -> /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf

[05] Wed 12Apr17 13:44:17 - TYPE I

[06] Wed 12Apr17 13:44:17 - 200 Type set to I

[05] Wed 12Apr17 13:44:17 - PASV

[06] Wed 12Apr17 13:44:17 - 227 Entering Passive Mode (136,144,129,18,195,72)

[03] Wed 12Apr17 13:44:17 - Opening passive mode data connection to 136.144.129.18, port 49992.

[05] Wed 12Apr17 13:44:17 - STOR 20170412113759_20170412113758_ENI_0.pdf

[06] Wed 12Apr17 13:44:17 - 150 Opening data channel for file upload to server of "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf"

[06] Wed 12Apr17 13:44:17 - 226 Successfully transferred "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf"

[03] Wed 12Apr17 13:44:17 - Transferred 174 798 bytes. 641,73 KB/sec.

[05] Wed 12Apr17 13:44:17 - XCRC "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf"

[04] Wed 12Apr17 13:44:17 - The server has unexpectedly closed the connection.

[06] Wed 12Apr17 13:44:17 - 226 Successfully transferred "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412112901_20170412112858_af_5_4.pdf"

[03] Wed 12Apr17 13:44:17 - Transferred 1 207 004 bytes. 1 796,82 KB/sec.

[05] Wed 12Apr17 13:44:17 - XCRC "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412112901_20170412112858_af_5_4.pdf"

[04] Wed 12Apr17 13:44:17 - The server has unexpectedly closed the connection.

[03] Wed 12Apr17 13:44:17 - Connecting to "136.144.129.18" on port 21.

[03] Wed 12Apr17 13:44:17 - Connected to 136.144.129.18:21 from 192.168.149.242:53539.

[06] Wed 12Apr17 13:44:17 - 220-FileZilla Server 0.9.60 beta

[06] Wed 12Apr17 13:44:17 - 220-written by Tim Kosse (tim.kosse@filezilla-project.org)

[06] Wed 12Apr17 13:44:17 - 220 Please visit https://filezilla-project.org/

[03] Wed 12Apr17 13:44:17 - Connected. Logging in to the server.

[05] Wed 12Apr17 13:44:17 - USER certifisc2

[06] Wed 12Apr17 13:44:17 - 331 Password required for certifisc2

[05] Wed 12Apr17 13:44:17 - PASS ***

[06] Wed 12Apr17 13:44:17 - 230 Logged on

[03] Wed 12Apr17 13:44:17 - Login successful.

[05] Wed 12Apr17 13:44:17 - SYST

[06] Wed 12Apr17 13:44:17 - 215 UNIX emulated by FileZilla

[05] Wed 12Apr17 13:44:17 - FEAT

[06] Wed 12Apr17 13:44:17 - 211-Features:

[06] Wed 12Apr17 13:44:17 -  MDTM

[06] Wed 12Apr17 13:44:17 -  REST STREAM

[06] Wed 12Apr17 13:44:17 -  SIZE

[06] Wed 12Apr17 13:44:17 -  MLST type*;size*;modify*;

[06] Wed 12Apr17 13:44:17 -  MLSD

[06] Wed 12Apr17 13:44:17 -  UTF8

[06] Wed 12Apr17 13:44:17 -  CLNT

[06] Wed 12Apr17 13:44:17 -  MFMT

[06] Wed 12Apr17 13:44:17 -  EPSV

[06] Wed 12Apr17 13:44:17 -  EPRT

[06] Wed 12Apr17 13:44:17 - 211 End

[03] Wed 12Apr17 13:44:17 - Server supports resume.

[05] Wed 12Apr17 13:44:17 - CLNT FTP Voyager 16.1.0.0

[06] Wed 12Apr17 13:44:17 - 200 Don't care

[05] Wed 12Apr17 13:44:17 - OPTS UTF8 ON

[06] Wed 12Apr17 13:44:17 - 202 UTF8 mode is always enabled. No need to send this command.

[05] Wed 12Apr17 13:44:17 - PWD

[06] Wed 12Apr17 13:44:17 - 257 "/" is current directory.

[13] Wed 12Apr17 13:44:17 - (Action: "C:\ADM\Test2\*" to "/Test") - Action successfully completed.

[12] Wed 12Apr17 13:44:17 - (Task: test) - Execution successfully completed.

[05] Wed 12Apr17 13:44:24 - QUIT

[06] Wed 12Apr17 13:44:24 - 221 Goodbye

Freeze Log

I have multiple users getting this crash in FTP Voyager:

Faulting application name: FTP Voyager.exe, version: 16.2.0.328, time stamp: 0x542c320b

Faulting module name: SHELL32.dll, version: 10.0.17134.1, time stamp: 0x75c40783

Exception code: 0xc0000005

Fault offset: 0x0000000000053dc4

Faulting process id: 0x1f04

Faulting application start time: 0x01d480400b074d8c

Faulting application path: C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe

Faulting module path: C:\windows\System32\SHELL32.dll

Report Id: 23c7bee2-035f-4439-aa16-24dd8572198b

Faulting package full name:

Faulting package-relative application ID:

The users are on Win 10x64 ver 1803 build 17134.

Voyager launches without an issue. Once in it, users can connect to different site profiles. As they are browsing folders, the application randomly crashes, usually while waiting for a  folder to load. It happens on multiple folders and does not always crash.

Does anyone have an idea what may be causing it?

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

I am getting this error and I don't know what the problem is. 

SSH Disconnect Error: no more authentication methods available.

We are using Serv-U on the back-end and FTP Voyager on the front end.

Regular password based connections work fine.

As soon as I create a private / public key and bind it to the user (on both sides), then the authentication will not work. 

Here is the log.

Perhaps I have to disable password authentication before public key authenication will work?

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58052.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

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

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

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

STATUS>    Retrying Connection (attempt 2)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58054.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

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

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

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

STATUS>    Retrying Connection (attempt 3)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58056.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

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

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

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

STATUS>    Retrying Connection (attempt 4)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58058.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

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

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

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

STATUS>    Retrying Connection (attempt 5)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58060.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

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

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

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

STATUS>    Retrying Connection (attempt 6)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58061.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

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

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

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

STATUS>    Retrying Connection (attempt 7)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58064.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

ERROR>    The server has unexpectedly closed the connection.

ERROR>    Could not establish a connection to MFT-AIM.

I have several tasks setup to run at different time intervals on a daily basis.

After the time change for Daylight Savings Time on Sunday morning the tasks run as scheduled and then stop and re-start continuously.

I have tried re-starting the service, updating the task scheduler time and re-booting the server all to no avail.

Has anyone else seen this or does anyone have any ideas on how to correct it.

I am on FTP Voyager version 16.0.2.0.

Never had this issue on any previous versions.

Is there a place to download version 15 again????

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