500 syntax error command unrecognized filezilla

Hello Forum!

Being very new into FileZilla I’m hoping that someone here might be able to assist me getting my setup work smoothly.

A short background overview of my setup:

A dedicated Windows 2012R2 server located in our DMZ zone, our IT department has demanded that it’s being configured to use FTPS (tcp-990), and they’ve configured the firewall configuration to support this.

Ok, so far so good…

On the server I’ve installed and configured FileZilla Server 0.9.60 beta, in the “FTP over TLS settings, I’ve selected “Enable FTP over TLS support (FTPS), & “Disallow plain unencrypted FTP”, I’ve generated a certificate, and selected “Allow explicit FTP over TLS” – entered port 990 in the “Listen for FTP over TLS connections” and finally selected “Force PORT P to encrypt file transfers when using FTP over TLS” and “Require TLS session resumption on data connection when using PORT P”

Ok then… — and now explaining my problem… :

When using the Filezilla FTP client on a computer, I try to connect to my server – in the server log I can see that the client connect (= the firewall rules are working as the should I guess) but… — I can see in the log the “connected on port 990, sending welcome message” -> 220 “Welcome to my FTP server” -> 500 syntax error, command unrecognized

When using the build in FTP client in Ghisler “Total commander” I can connect with the exact same username and password as I’m using in Filezilla FTP client, however I do at the beginning see a “The certificate was not signed by a trusted party, continue anyway?” – if I select “Yes” the client connects, and everything is working (I can upload, download, edit, delete files on the FTP server)

The error I see in the Filezilla FTP client are the following :

Status: Connecting to xxx.xxx.xxx.xxx:990…
Status: Connection established, initializing TLS…
Error: GnuTLS error -15: An unexpected TLS packet was received.
Error: Could not connect to server

So… – I’m under the impression that the firewall properly is configured as it should be, and that the problem properly is located somewhere in my setup of the server client.

I’ve tried to follow all the “best practice” guides I could come across, however, no luck so far.

I would therefore be very thankful if anyone here have any suggestions!

Thanks in advance!

Kind regards

Lars

I installed the FileZilla Server on my Windows Server. and when I use the FileZilla Client to connect it there gets bellow error:

https://filezilla-project.org/
Connecting to server...
Connected, waiting for authentication
Logged on
(000018)2018/10/24 10:56:18 - (not logged in) (50.184.220.141)> Connected, sending welcome message...
(000018)2018/10/24 10:56:18 - (not logged in) (50.184.220.141)> 220-FileZilla Server version 0.9.43 beta
(000018)2018/10/24 10:56:18 - (not logged in) (50.184.220.141)> 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
(000018)2018/10/24 10:56:18 - (not logged in) (50.184.220.141)> 220 Please visit http://sourceforge.net/projects/filezilla/
(000018)2018/10/24 10:56:18 - (not logged in) (50.184.220.141)> SSH-2.0-FileZilla_3.32.0
(000018)2018/10/24 10:56:18 - (not logged in) (50.184.220.141)> 500 Syntax error, command unrecognized.

The FileZilla Server listen on the port 21.

In my Client I use sftp://102.33.56.81, port 21 to connect the Server, but get failed, the Server log is upper.

FileZilla Forums

Welcome to the official discussion forums for FileZilla

***Solved*** 500 Syntax error displayed right after sendeing the welcome message ?!

***Solved*** 500 Syntax error displayed right after sendeing the welcome message ?!

#1 Post by Lars_Simonsen » 2017-11-06 14:55

Being very new into FileZilla I’m hoping that someone here might be able to assist me getting my setup work smoothly.

A short background overview of my setup:

A dedicated Windows 2012R2 server located in our DMZ zone, our IT department has demanded that it’s being configured to use FTPS (tcp-990), and they’ve configured the firewall configuration to support this.

Ok, so far so good…

On the server I’ve installed and configured FileZilla Server 0.9.60 beta, in the “FTP over TLS settings, I’ve selected “Enable FTP over TLS support (FTPS), & “Disallow plain unencrypted FTP”, I’ve generated a certificate, and selected “Allow explicit FTP over TLS” – entered port 990 in the “Listen for FTP over TLS connections” and finally selected “Force PORT P to encrypt file transfers when using FTP over TLS” and “Require TLS session resumption on data connection when using PORT P”

Ok then… — and now explaining my problem… :

When using the Filezilla FTP client on a computer, I try to connect to my server – in the server log I can see that the client connect (= the firewall rules are working as the should I guess) but… — I can see in the log the “connected on port 990, sending welcome message” -> 220 “Welcome to my FTP server” -> 500 syntax error, command unrecognized

When using the build in FTP client in Ghisler “Total commander” I can connect with the exact same username and password as I’m using in Filezilla FTP client, however I do at the beginning see a “The certificate was not signed by a trusted party, continue anyway?” – if I select “Yes” the client connects, and everything is working (I can upload, download, edit, delete files on the FTP server)

The error I see in the Filezilla FTP client are the following :

Status: Connecting to xxx.xxx.xxx.xxx:990.
Status: Connection established, initializing TLS.
Error: GnuTLS error -15: An unexpected TLS packet was received.
Error: Could not connect to server

So. – I’m under the impression that the firewall properly is configured as it should be, and that the problem properly is located somewhere in my setup of the server client.

I’ve tried to follow all the “best practice” guides I could come across, however, no luck so far.

I would therefore be very thankful if anyone here have any suggestions!

Thanks in advance!

Re: 500 Syntax error displayed right after sendeing the welcome message ?!

#2 Post by botg » 2017-11-06 16:29

Re: 500 Syntax error displayed right after sendeing the welcome message ?!

#3 Post by Lars_Simonsen » 2017-11-06 16:46

This is from the server :

(000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)> Connected on port 990, sending welcome message.
(000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)> 220 Welcome to the FTP Server
(000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)>
(000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)> 500 Syntax error, command unrecognized.
(000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)> Ý
(000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)> 500 Syntax error, command unrecognized.
(000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)> ÙZ
(000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)> 500 Syntax error, command unrecognized.
(000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)> ½2_ (000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)> 500 Syntax error, command unrecognized.
(000016)06/11/2017 17:38:23 — (not logged in) (10.8.4.108)> could not send reply, disconnected.
(000017)06/11/2017 17:38:28 — (not logged in) (10.8.4.108)> Connected on port 990, sending welcome message.
(000017)06/11/2017 17:38:28 — (not logged in) (10.8.4.108)> 220 Welcome to the FTP Server
(000017)06/11/2017 17:38:28 — (not logged in) (10.8.4.108)>
(000017)06/11/2017 17:38:28 — (not logged in) (10.8.4.108)> 500 Syntax error, command unrecognized.
(000017)06/11/2017 17:38:28 — (not logged in) (10.8.4.108)> Ý
(000017)06/11/2017 17:38:28 — (not logged in) (10.8.4.108)> 500 Syntax error, command unrecognized.
(000017)06/11/2017 17:38:28 — (not logged in) (10.8.4.108)> ÙZ
(000017)06/11/2017 17:38:28 — (not logged in) (10.8.4.108)> 500 Syntax error, command unrecognized.
(000017)06/11/2017 17:38:28 — (not logged in) (10.8.4.108)> could not send reply, disconnected.

This is from the FileZilla FTP client :

Status: Connecting to xxx.xxx.xxx.x:990.
Status: Connection established, initializing TLS.
Error: GnuTLS error -15: An unexpected TLS packet was received.
Error: Could not connect to server
Status: Waiting to retry.
Status: Connecting to xxx.xxx.xxx.xxx:990.
Status: Connection established, initializing TLS.
Error: GnuTLS error -15: An unexpected TLS packet was received.
Error: Could not connect to server

Re: 500 Syntax error displayed right after sendeing the welcome message ?!

#4 Post by boco » 2017-11-06 17:20

You’re doing it wrong. The TCP port 990 is ONLY for Implicit FTPS. Implicit is encrypted from the start and thus needs a separate port. You cannot connect using Explicit or plain FTP to that port.

Explicit FTP over TLS uses the same port as plain FTP, 21 by default.

If you want to keep using port 990, you need to switch to Implicit, completely. The Implicit TLS port is set on the «FTP over TLS settings» tab in FileZilla Server, so you need to clear the Listen port on the «General» tab if you want to disallow plain FTP and Explicit FTP over TLS.

***SOLVED*** 500 Syntax error displayed right after sendeing the welcome message ?!

#5 Post by Lars_Simonsen » 2017-11-07 07:01

@boco — You are my hero! — clearing the Listen port on the «General» tab solved the problem!

Источник

FileZilla Forums

Welcome to the official discussion forums for FileZilla

500 Syntax error

500 Syntax error

#1 Post by chrisn8cuh » 2008-08-29 00:46

I keep getting this error when I try to log onto to my FTP Server using FTPS. I have tried searching the forums but no luck. I generated a certification and placed in the same folder as FileZilla. Port 990 is open on firewall. I cannot connect to it locally or off the Internet.

(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)>
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> O
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> KH·E–¶ÅÆ`–‰¥$Æë”ÑF¹6:¥ÚåÞí(„ðOg
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> $
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 3
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> E
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 9
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> ˆ
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)>
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 2
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> D
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 8
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> ‡
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)>
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> f
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> /
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> A
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 5
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> „
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)>
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)>
(000098) 8/28/2008 20:40:18 PM — (not logged in) (71.115.168.44)> 500 Syntax error, command unrecognized.

Re: 500 Syntax error

#2 Post by da chicken » 2008-08-29 07:07

Источник

FileZilla Forums

Welcome to the official discussion forums for FileZilla

500 Syntax error, command unrecognized. when tring to connect with SFTP

500 Syntax error, command unrecognized. when tring to connect with SFTP

#1 Post by AB3217 » 2017-11-15 10:43

I am new to FileZilla ,What I am trying is to connect 2 windows 7 PC in same LAN network .
In one machine I have Installed Filezilla Server and in other I have Installed the Client ,when I am trying to Connect the Client with server by Using FTP (Port 21) I am able to connect and transfer the file.
But when I am trying to connect with SFTP (Port 22) I am unable to connect and getting the below error.

SSH-2.0-FileZilla_3.29.0
(000042)15-11-2017 15:35:08 — (not logged in) (10.63.145.136)> 500 Syntax error, command unrecognized.

Please let me know how can I connect with SFTP ,Do I need to do any specific configuration for SFTP?

(Also pls let me know am I going the right way by trying to connect filezilla client with Filezilla server via SFTP . if not how can we setup a SFTP connection with filezilla server.)

Re: 500 Syntax error, command unrecognized. when tring to connect with SFTP

#2 Post by boco » 2017-11-15 15:13

FileZilla Server does not support SFTP, you can stop trying to get connected to port 22.

FileZilla Server supports FTP and Explicit FTPS (AUTH TLS) on the normal listening port (21 by default). It also supports Implicit FTPS on a dedicated port (990 by default). For SFTP, you’d need a different server altogether.

Re: 500 Syntax error, command unrecognized. when tring to connect with SFTP

#3 Post by AB3217 » 2017-11-15 16:15

Thanks for your prompt reply. Can you please suggest some of the free SFTP Servers from which filezilla clients can be connected to provide sftp transfer.

Thanks a lot in advance.

Re: 500 Syntax error, command unrecognized. when tring to connect with SFTP

#4 Post by boco » 2017-11-15 17:09

Re: 500 Syntax error, command unrecognized. when tring to connect with SFTP

#5 Post by AB3217 » 2017-11-15 17:19

Thanks . Could you pls guide me how can we setup SFTP with an open SSH..Do we have any link or document for reference.

Источник

500, 501, 502, 503, 504 FTP Response Codes

This article explains 500 series response code:

500 FTP Response code

A 500 response code may be sent in response to any command that the server is unable to recognize. It is a permanent negative response, which means the client is discouraged from sending the command again since the server will respond with the same reply code. It usually means that the client has sent a command to the server that the server does not recognize. This may be due to an error in the spelling or formatting of the command itself or that the command is newer than the FTP implementation in place on the server or is a proprietary command of another server implementation.

Example response

500 Syntax error, command unrecognized.

501 FTP Response code

A 501 response code may be sent in response to any command that requires or supports the optional use of a parameter or argument. It is a permanent negative response, which means the client is discouraged from sending the exact command and parameter(s) again since the server will respond with the same response code. It differs from the 500 response code in that the server recognizes the command present but is unable to take the requested action due to a syntax error in the parameter(s) present with the command. Sending the same command to the server with a corrected parameter may result in a different response code.

Example response

501 Syntax error in parameters or argument.

502 FTP Response code

A 502 code may be sent in response to any FTP command that the server does not support. It is a permanent negative reply, which means the client is discouraged from sending the command again since the server will respond with the same reply code. The original FTP specification dictates a minimum implementation for all FTP servers with a list of required commands. Because of this, a 502 reply code should not be sent in response to a required command.

Example response

502 Command not implemented.

503 FTP Response code

A 503 response code may be sent in response to any command that requires the successful processing of previous commands first. It is a permanent negative reply, which means the client is discouraged from immediately sending the command again since the server will respond with the same reply code. For example, a file rename requires a successful RNFR command before the RNTO command can be sent. Sending the RNTO command first will result in a 503 response code.

Example response

503 Bad sequence of commands.

Possible commands:

504 FTP Response code

A 504 response code can be sent in response to any command using a parameter that is not supported by the server. It is a permanent negative response, which means the client is discouraged from sending the command again since the server will respond with the same response code. Issuing the same command with a different parameter may result in a different response code.

Example response

504 Command not implemented for that parameter.

Источник

I have created a ftp server using Filezilla. I am trying to upload a single file using c# code. My cide is very simple a functino called upload:

static void UploadFile(string filepath)
    {
     string m_FtpHost = "http://ip:port/";
     string m_FtpUsername = "userID";
     string m_FtpPassword = "pass";
     // Get an instance of WebClient
     WebClient client = new System.Net.WebClient();
     // parse the ftp host and file into a uri path for the upload
     Uri uri = new Uri(m_FtpHost + new FileInfo(filepath).Name);
     // set the username and password for the FTP server
     client.Credentials = new System.Net.NetworkCredential(m_FtpUsername, m_FtpPassword);
     // upload the file asynchronously, non-blocking.

     client.UploadFileAsync(uri, "STOR", filepath);
    }

    static void Main(string[] args)
    {
      UploadFile("file.pdf"); 
      Console.ReadKey();
    }

In the Filezilla server gui I am getting the following messages:

(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> STOR  /file.pdf HTTP/1.1
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> 530 Please log in with USER and PASS first.
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> Content-Type: application/octet-stream
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> 500 Syntax error, command unrecognized.
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> Host: ip:port
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> 500 Syntax error, command unrecognized.
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> Content-Length: 481868
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> 500 Syntax error, command unrecognized.
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> Expect: 100-continue
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> 500 Syntax error, command unrecognized.
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> Connection: Keep-Alive
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> 500 Syntax error, command unrecognized.
(000017)11/23/2015 10:47:19 AM - (not logged in) (ip)> disconnected.

Any idea what might be wrong here?
EDIT: I tried to change http with ftp in the UploadFile. Now I am receiving the following:

(000019)11/23/2015 10:59:53 AM - chrathan user (ip)> 257 "/" is current directory.
(000019)11/23/2015 10:59:53 AM - user (ip)> TYPE I
(000019)11/23/2015 10:59:53 AM - user (ip)> 200 Type set to I
(000019)11/23/2015 10:59:53 AM - user (ip)> PASV
(000019)11/23/2015 10:59:53 AM - user (ip)> 227 Entering Passive Mode (ip with comma)
(000019)11/23/2015 10:59:53 AM - user (ip)> STOR file.pdf
(000019)11/23/2015 10:59:53 AM - user (ip)> 150 Opening data channel for file upload to server of "/file.pdf"
(000019)11/23/2015 10:59:53 AM - user (ip)> 550 can't access file.
(000019)11/23/2015 10:59:53 AM - user (ip)> disconnected.

EDIT2: Basically the folder I try to have access is a network share disk. When I changed to a local folder in my pc everything works. My issue finally is how can I have access to a network share disk?

If you have problems connecting to your FTP account using FileZilla, check out the information below to help you solve the problem.

Response: 530 Login authentication failed

Response: 530 Login authentication failed

Error: Critical error

Error:  Could not connect to server

If you see this error message when trying to connect it means that you entered an incorrect username/password or host. If you don�t remember your login details, please follow the steps in this tutorial to reset it.

Your domain name must point to your hosting account. This happens by pointing your domain name�s DNS A record to your hosting account�s IP address.

Response: 421 Sorry, cleartext sessions are not accepted on this server

Response:    421 Sorry, cleartext sessions are not accepted on this server.

Error:    Could not connect to server

If you see this message, please check and make sure that FileZilla is set to use the following details:

Protocol: FTP protocol

Encryption: Require FTP over explicit TLS/SSL

LogonType : Normal

Filezilla timeout after 20 seconds of inactivity

1. Open Site manager
2. Click on �New site� button
3. You need to change the Encryption to �Only use plain FTP (insecure)� and Logon type to Normal
4. Enter host address, user name, and password and click �Connect�

Response: 500 unrecognized command

Response: 500 unrecognized command

Error:  Could not connect to server

This error can be caused by an incorrect port setting, please make sure you are using the correct port 21.

Response: 331 User savsuq2b1 OK. Password required

Error: Connetion timed out

Error: Could not connect to server

If you see this error you�ll first need to make sure that you�re using the correct login information. If they are all correct, you�ll need to check for Firewalls or Antivirus installed on your computer, try disabling them and test the connection again.

Response: Connection timed out (Failed to retrieve directory listing)

Error: Connection timed out after 10 seconds of inactivity

Error: Failed to retrieve directory listing

There could be a Firewalls or Antivirus problem, which might be blocking the transfer, try disabling them and test the connection again.

By default, FileZilla is defined to close the transfer of files if the file transfer takes more than a fixed amount of time, so if the disabling the Firewall doesn�t fix the problem you should try disabling the timeout settings.To disable the timeout select Edit -> Settings -> Connections -> Change Timeout to a higher value.

Connection attempt failed with �EAI_NONAME

Full error: Connection attempt failed with �EAI_NONAME � Neither nodename nor servname provided, or not known�.

If you see this error, this means that the issue is related to Name resolution error. The �Host� you are using is not correct, or your domain may not be pointed to our DNS. Check for spelling mistakes or try using the server�s IP address.

Was this article helpful?

Thanks for your opinion!