Protocol ftp protocol error



FileZilla Forums

Welcome to the official discussion forums for FileZilla

protocol error invalid data could not import account setting

protocol error invalid data could not import account setting

#1 Post by beach2011 » 2011-09-04 17:24

Hello, I lose my FTP passwords every week and i have to re-set it gain and this is what i get:
«protocol error invalid data could not import account settings. could not change account settings «

Thank you for your help,

Re: protocol error invalid data could not import account set

#2 Post by boco » 2011-09-04 17:54

Re: protocol error invalid data could not import account set

#3 Post by beach2011 » 2011-09-04 20:27

Re: protocol error invalid data could not import account set

#4 Post by botg » 2011-09-04 21:42

Re: protocol error invalid data could not import account set

#5 Post by beach2011 » 2011-09-05 01:57

Re: protocol error invalid data could not import account set

#6 Post by boco » 2011-09-05 05:46

You seem to be seriously confused, you are definitely using the server.

You must make sure that both FileZilla Server.exe and FileZilla Server Interface.exe can fully access its own program directory, especially the configuration XML files. Furthermore, loss of settings occurs because of corruption of the FileZilla Server.xml. In turn, the most probable cause of configuration files corruption could be by either flaky hardware (memory or disk come to my mind) or an unstable/corrupted file system. Since you have a virtual or dedicated server, do you have any means to check the file system?

Re: protocol error invalid data could not import account set

#7 Post by beach2011 » 2011-09-05 18:49

Источник

FileZilla Forums

Welcome to the official discussion forums for FileZilla

Protocol error: Unknown protocol identifier (0x50 0x50 0x48) Most likely conected to the wrong port

Protocol error: Unknown protocol identifier (0x50 0x50 0x48) Most likely conected to the wrong port

#1 Post by acabiya » 2015-10-09 23:13

I exhausted all my alternatives. Have been trying to fix for many hours.
I see on the Internet that it is a relatively common problem.

I have windows 10 Home 64
Installed FileZillaServer. I have been using it for years on XP and 7, never had problems.

I installed it and it does not connects giving this message:

Protocol error: Unknown protocol identifier (0x50 0x50 0x48) Most likely conected to the wrong port 5 seconds to reconnect.

It goes on and on and never stops so I can NOT configure settings. I have uninstalled and reinstalled it already 5 times.
I URGENTLY NEED TO SOLVE THIS, since I receive important data though my FTP
ANY QUICK FIX.

Re: Protocol error: Unknown protocol identifier (0x50 0x50 0x48) Most likely conected to the wrong port

#2 Post by boco » 2015-10-09 23:24

Re: Protocol error: Unknown protocol identifier (0x50 0x50 0x48) Most likely conected to the wrong port

#3 Post by acabiya » 2015-10-09 23:55

Читайте также:  There an error pro tools

Ok. I followed your instructions.

The problem I’m having is that the POPUP requesting the port and the password is NOT prompting after the FIRST installation. WHAT DO I HAVE TO DO FOR IT TO PROMPT. Is there a registry key or something I have to get read of for it to prompt.

It goes directly to open FileZillaServer.

THANKS FOR YOUR FAST RESPONSE

Re: Protocol error: Unknown protocol identifier (0x50 0x50 0x48) Most likely conected to the wrong port

#4 Post by acabiya » 2015-10-10 01:24

Re: Protocol error: Unknown protocol identifier (0x50 0x50 0x48) Most likely conected to the wrong port

#5 Post by acabiya » 2015-10-10 20:35

My First POST
I exhausted all my alternatives. Have been trying to fix for many hours.
I see on the Internet that it is a relatively common problem.

I have windows 10 Home 64
Installed FileZillaServer. I have been using it for years on XP and 7, never had problems.

I installed it and it does not connects giving this message:

Protocol error: Unknown protocol identifier (0x50 0x50 0x48) Most likely connected to the wrong port 5 seconds to reconnect.

It goes on and on and never stops so I can NOT configure settings. I have uninstalled and reinstalled it already 5 times.
I URGENTLY NEED TO SOLVE THIS, since I receive important data though my FTP
ANY QUICK FIX.
************************************************
Received answer and I tried it.*******
Ok. I followed your instructions.

The problem I’m having is that the POPUP requesting the port and the password is NOT prompting after the FIRST installation. WHAT DO I HAVE TO DO FOR IT TO PROMPT? Is there a registry key or something I have to get UNDONE of for it to prompt.

It goes directly to open FileZillaServer.
****************
I think it is a FZS BUG and no one has a answers.

Why in the world, on the first installation the final popup appears, you comply with requirements, the installation does NOT works, gives me the error message that I published, and 5 additional installations the FINAL screen POPUP does NOT shows again.

The worst part is that NO ONE can tell me what I have to erase or delete from FZS for it to not recognizes the previous installation and shows the POPUP requesting the Port and password. Isn’t that popup PART OF THE INSTALLATION.
IS THERE SOMEONE THAT CAN TELL ME.

Источник

Protocol ftp protocol error

This forum is closed. Thank you for your contributions.

Asked by:

Question

Does anyone knows how to correctly allow FTP Access from Internal to External for FTP-Clients through TMG 2010?

I created the rule that Allow FTP and FTP over HTTP Protocols from Internal to External for specific AD Group, but it works very strange.

FTP Read-only flag is turned off for all Rules where it’s possible.

Читайте также:  Что такое runtime error 205

Some distant FTP-servers works perfect without any Errors. But some have errors when FTP-clients (TotalCommander, FAR, FileZilla) try to get folder lists.

MLSD
425 Unable to build data connection: Software caused connection abort

If I try to reconnect several times, or refresh page (TotalCommander), then sometimes it shows folder lists.

If I try to connect to this servers through my old ISA 2004 server, all is perfect.

Additional, I found some strange messages from my DMZ-TMG servers:

Closed Connection
Log type: Firewall service
Status: You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name.
Rule: Allow all from Internal to External
Source: Internal (172.16.0.101:46508)
Destination: External (62.113.86.19:31021)
Protocol: FTP

Maybe anyone knows how to solve this error? It’s the error on my side or on External FTP-server side? Why some Servers are works fine and some with errors?

All replies

Seems like you are trying to establish an Active FTP connection when Active FTP is not allowed.

In the TMG MMC, go to System / Application Filters / Properties of FTP Access filter / FTP properties tab

Enable Active FTP (check the box).

Hth, Anders Janson Enfo Zipper

No, I set manualy Passive mode. And in FTP-session all is about Passive:

Status: Connecting with 62.113.86.19:21.
Status: Connecting established
Reply: 220 FTP Server (Zenon Hosting, (access to

user)) [62.113.86.19]
Command: USER XXXXXX
Reply: 331 Password required for XXXXXX
Command: PASS **********
Reply: 230 User XXXXXX logged in
Status: Server is not supporting ASCII.
Status: Connecting established
Status: Reading folders list.
Command: PWD
Reply: 257 «/» is the current directory
Command: TYPE I
Reply: 200 Type set to I
Command: PASV
Reply: 227 Entering Passive Mode (62,113,86,19,207,210).
Command: MLSD
Reply: 425 Unable to build data connection: Software caused connection abort

I try to enable Active Mode, but with same result.

How does your access rule for this look like?

Are you using the default protocol definition («FTP») in the access rule? Is the FTP filter still attached to the protocol?

Hth, Anders Janson Enfo Zipper

Well, I create rule with that parameters:

Protocols: All Outbound (I tried to use only FTP, but with same error)

To: FTP External Servers (Computer set with list of allowed FTP Servers)

Condition: FTP Users (Group with AD Users Group)

Yes, I tried to use onlu «default» FTP-protocol, but with same errors. FTP filter still attached to the protocol.

Connections to some destination FTP-servers are works perfectly.

What does the logs on the TMG say? Does it allow the data connection? If yes, then your issue is elsewhere and not on the TMG. To start working on where the issue is, install your favorite network sniffer on TMG and on the client and start a trace on TMG (both external and internal interface) and on the client. Review the resulting traces and work fromt there.

Читайте также:  Error enoent no such file or directory open etc ksc web console setup json

Hth, Anders Janson Enfo Zipper

Yes, TMG allow connection, but here is the order of DMZ TMG actions:

1. Initiation of FTP connection — success:

Protocol: FTP

2. Initiated secondary connection — success:

Initiated Connection DMZ-TMG-02 28.05.2014 13:59:24
Log type: Firewall service
Status: The operation completed successfully.
Rule: Allow all from Internal to External
Source: Internal (172.16.0.101:50478)
Destination: External (62.113.86.19:29725)
Protocol: FTP

Источник

Fix: Cannot establish FTP connection to an SFTP server in FileZilla

If you try to connect to a SFTP server using FileZilla, you may see a Critical error: Could not connect to server. Here’s why you see this error and how to fix it.

The other day I had to connect to my web server. I use FileZilla for connecting to FTP servers. FileZilla is a free and open source GUI software that allows you to connect to a FTP server in Linux.

When I entered the hostname and password and tried to connect to the FTP server, it gave me the following error:

Error: Cannot establish FTP connection to an SFTP server. Please select proper protocol.
Error: Critical error: Could not connect to server

Fixing ‘Critical error: Could not connect to server’ in Linux

By reading the error message itself made me realize my mistake. I was trying to establish an FTP connection with an SFTP server. You see, I had SFTP setup on the Linux server. Clearly, I was not using the correct protocol which should have been SFTP and not FTP.

As you can see in the picture above, FileZilla defaults to FTP protocol.

Solution for “Cannot establish FTP connection to an SFTP server”

Solution is simple. Use SFTP protocol instead of FTP. The one problem you might face is to know how to change the protocol to SFTP. This is where I am going to help you.

In FileZilla menu, go to File->Site Manager.

In the Site Manager, go in General tab and select SFTP in Protocol. Also fill in the host server, port number, user password etc.

I hope you can handle things from here onward.

I hope this quick tutorial helped you to fix “Cannot establish FTP connection to an SFTP server. Please select proper protocol.” problem. If you have questions or suggestion, do let me know. If this article helped you fix the problem, I won’t mind a simple ‘thanks’ comment 🙂

In related articles, you can read this post to know how to set up FTP server in Linux.

Источник

Оцените статью
toolgir.ru
Adblock
detector
Initiated Connection DMZ-TMG-02 28.05.2014 13:59:24
Log type: Firewall service
Status: The operation completed successfully.
Rule: Allow all from Internal to External
Source: Internal (172.16.0.101:50476)
Destination: External (62.113.86.19:21)