Welcome to the new home of the Cumulus Support forum.

Latest Cumulus release v1.9.4 (build 1099) - Nov 28 2014
Latest Cumulus MX release - v3.0.0 build 3043 Jan 20 2017. See the Wiki for download

Search found 54 matches

by Dinant
Fri Sep 14, 2018 7:33 am
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

Disable 'auto update' in the internet settings.
Yes, but then all files are not updated anymore. I want all files being updated but no ftp from within Cumulus.
The FTP upload of Cumulus is being rejected by my internet provider.
I have to upload the files with my own script (FTP with TLS 1.2).
by Dinant
Wed Sep 12, 2018 8:23 pm
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

I have disabled the FTP upload by disabling the following options: Enable realtime FTP Realtime.txt FTP Realtimegauges.txt FTP But I still get "Error connecting ftp - The handshake failed due to an unexpected packet format." in the MXDIAG file every 5 minutes. In the ftplog.txt is says: 2018-09-12 2...
by Dinant
Sun May 27, 2018 5:16 pm
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

My provider has disabled TLS 1.0 again. So I have added an external ftp script which uses WinSCP. First you have to install WinSCP. Then add 2 files ftp2web.bat and ftp2web.txt to the Cumulus directory. <cumulus-directory>\ftps2web.bat: "<winscp-install-directory>\WinSCP.com" /script=<cumulus-direct...
by Dinant
Wed Apr 11, 2018 9:12 am
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

OK, unless you are getting the exception I don't think it was picking up the new file. I had a quick look this morning, I don't think MX can be made to use an updated DLL without MX being recompiled - because the public key of the assembly will change (or be removed ;) )when I compile it. :( I thin...
by Dinant
Wed Apr 11, 2018 7:21 am
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

Replacing the 2 files produces also an exception during the start of cumulus. Current culture: Dutch (Netherlands) Unhandled Exception: System.IO.FileLoadException: Could not load file or assembl y 'System.Net.FtpClient, Version=1.0.5281.14359, Culture=neutral, PublicKeyToken =fa4be07daa57c2b7' or o...
by Dinant
Wed Apr 11, 2018 6:17 am
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

I have tested the new System.Net.FTClient DLL but it doesn't work. It produces the same error. I am using .NET Framework 4.7.1.
by Dinant
Tue Apr 10, 2018 5:36 pm
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

I have tested MX with the newer dll. TLS 1.0 is still not working. Same error.
by Dinant
Tue Apr 10, 2018 2:39 pm
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

The version of System.Net.FtpClient.dll MX is using is 1.0.5281.14359. On the https://www.nuget.org/packages/System.Net.FtpClient/1.0.5824.34026 it says there are two newer versions. The latest version is 1.0.5824.34026. On that page there exists a Manual download link. If you download that file and...
by Dinant
Tue Apr 10, 2018 2:24 pm
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

I'll found some info on https://archive.codeplex.com/?p=netftp under issues. Look for the item TLSv1.2 support.
Maybe TLS1.1 and TLS1.2 must be added to the SslProtocols?
by Dinant
Tue Apr 10, 2018 1:56 pm
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

What is the name of the FTP component you using?
by Dinant
Mon Apr 09, 2018 5:07 pm
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

My Windows 2012 R2 server is capable of using SSLv3, TLS 1.0, TLS 1.1 and TLS 1.2 only if it also enabled on the server side.
I have tested this with WinSCP.

So I think the existing version of MX (v3.0.0 build 3042) is capable of using SSLv3 and maybe TLS 1.0.
by Dinant
Mon Apr 09, 2018 2:33 pm
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

I have an answer from my provider. Indeed they have disabled SSLv2 and SSLv3 but also TLS v1.0. So they only support TLS 1.1 and TLS 1.2. My provider uses proFTPD with the following line in the proFTPD config file: TLSProtocol TLSv1.1 TLSv1.2 Tonight I'll do a test with WinSCP if TLS 1.1 and TLS 1.2...
by Dinant
Mon Apr 09, 2018 11:31 am
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

steve wrote:What version of Windows are you using - 2003 as in your profile?
I am using Windows 2012 R2.
First I'll wait for my provider to answer my questions about TLS 1.0 not working.
In the meantime I've changed my profile!
by Dinant
Mon Apr 09, 2018 9:10 am
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

This is what i have found on the Wiki page: https://en.wikipedia.org/wiki/FTPS Explicit In explicit mode (also known as FTPES), an FTPS client must "explicitly request" security from an FTPS server and then step up to a mutually agreed encryption method. If a client does not request security, the FT...
by Dinant
Sun Apr 08, 2018 10:04 am
Forum: Cumulus MX
Topic: The handshake failed due to un unexpected packet format
Replies: 38
Views: 9616

Re: The handshake failed due to un unexpected packet format

I did some tests with FTPS on 2 webservers of my provider. One with SSLv2 and SSL v3 disabled and one with the original settings (all enabled). On the servers with everything enabled there are no login problems detected. On the server with SSLv2 and SSLv3 disabled I see the following results: SSL 3....