Ftp syntax error command unrecognized - Исправление ошибок и поиск оптимальных решений проблем

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

Источник

Remove From My Forums

Question

I created FTP code to transfer files. This code works fine except that it sometimes causes an error 500. The exact error is —

Error: System.Reflection.TargetInvocationException: Exception has 
been thrown by the target of an invocation. 
---> System.Net.WebException: The remote server returned an error: 
(500) Syntax error, command unrecognized.
   at System.Net.FtpWebRequest.CheckError()
   at System.Net.FtpWebRequest.SyncRequestCallback(Object obj)
   at System.Net.CommandStream.Abort(Exception e)
   at System.Net.FtpWebRequest.FinishRequestStage(RequestStage stage)
   at System.Net.FtpWebRequest.GetRequestStream()
   at ST_772dn22cj49ndfddatee.csproj.ScriptMain.Main()
   --- End of inner exception stack trace ---

I noticed that the error occurs when the biggest file is loaded, ie about 290 KB. All other files are less than this and i get no exception for them. I don’t know why this happens. Can someone tell me why ?

As an aside, in case you notice some room for improvement in my code or logical error, then please mention that as well. I am not really looking for code reviews, but its welcome.

    public void Main()
    {

        Boolean conditions = true;

        if(conditions == true)
        {
        string fileLocation = "my windows directory";
        string fileName = "fileName.extension";

        string ftpFolder = @"/ftpFolder/";
        Boolean ftpMode = true; //passive or active. True = passive 
        string ftpPassword = "password";
        int ftpPort = 21;// the default
        string ftpServerName = "server name";
        string ftpUserName = "user name";

        //Create an object to communicate with the server.
        string ftpRequestString = "ftp://" + ftpServerName + ":" 
        + ftpPort + ftpFolder + fileName; 

        try{

        FtpWebRequest request = 
        (FtpWebRequest)WebRequest.Create(ftpRequestString);
        request.Method = WebRequestMethods.Ftp.UploadFile;

        request.Credentials = new NetworkCredential(ftpUserName, ftpPassword);

        //Set mode
        if(ftpMode == true){
            request.UsePassive = true;
        }

        //Copy the file to the request.

        string filePath = @fileLocation + "\" + fileName;
        StreamReader sourceStream = new StreamReader(filePath);
        byte[] fileContents = Encoding.UTF8.GetBytes(sourceStream.ReadToEnd());
        sourceStream.Close();
        request.ContentLength = fileContents.Length;

        Stream requestStream = request.GetRequestStream();
        requestStream.Write(fileContents, 0, fileContents.Length);
        requestStream.Close();

        FtpWebResponse response = (FtpWebResponse)request.GetResponse();

        response.Close();

        }
         catch (WebException ex)
         {
            MessageBox.Show(ex.Message);

         }//try-catch

        }

    }//main

Answers

            bool pass = true;
            FtpWebRequest request = null;
            Stream requestStream = null;
            FtpWebResponse response = null;
            try
            {
                request = (FtpWebRequest)WebRequest.Create(ftpRequestString);
                request.Method = WebRequestMethods.Ftp.UploadFile;
                request.Credentials = new NetworkCredential(ftpUserName, ftpPassword);

                //Set mode
                if (ftpMode == true)
                {
                    request.UsePassive = true;
                }
            }
            catch (Exception ex)
            {
                pass = false;
            }
            if (pass == true)
            {
                int count = 10;
                string filePath = @fileLocation + "\" + fileName;
                StreamReader sourceStream = null;
                do
                {
                    try
                    {
                        // enter code here

                        sourceStream = new StreamReader(filePath);
                        byte[] fileContents = Encoding.UTF8.GetBytes(sourceStream.ReadToEnd());
                        request.ContentLength = fileContents.Length;

                        requestStream = request.GetRequestStream();
                        requestStream.Write(fileContents, 0, fileContents.Length);

                        response = (FtpWebResponse)request.GetResponse();
                        pass = true;

                    }
                    catch (Exception ex)
                    {
                        pass = false;
                        count--;
                    }
                } while ((pass == false) && (count > 0));

                if (sourceStream != null)
                {
                    sourceStream.Close();
                }
                if (requestStream != null)
                {
                    requestStream.Close();
                }
                if (response != null)
                {
                    response.Close();
                }
            }

jdweng

Marked as answer by

Friday, January 24, 2014 8:42 AM

You may find an error message in Control Panel : Adminstrative Tools : Event Viewer. Also using a sniffer like wireshark or fiddler may help. The detail exception (StackTrace) also has more info.

jdweng
- Marked as answer by
  Herro wongMicrosoft contingent staff
  Friday, January 24, 2014 8:42 AM

Источник

Содержание

FileZilla Forums
***Solved*** 500 Syntax error displayed right after sendeing the welcome message ?!
***Solved*** 500 Syntax error displayed right after sendeing the welcome message ?!
Re: 500 Syntax error displayed right after sendeing the welcome message ?!
Re: 500 Syntax error displayed right after sendeing the welcome message ?!
Re: 500 Syntax error displayed right after sendeing the welcome message ?!
***SOLVED*** 500 Syntax error displayed right after sendeing the welcome message ?!
FileZilla Forums
500 Syntax error
500 Syntax error
Re: 500 Syntax error
FileZilla Forums
500 Syntax error, command unrecognized. when tring to connect with SFTP
500 Syntax error, command unrecognized. when tring to connect with SFTP
Re: 500 Syntax error, command unrecognized. when tring to connect with SFTP
Re: 500 Syntax error, command unrecognized. when tring to connect with SFTP
Re: 500 Syntax error, command unrecognized. when tring to connect with SFTP
Re: 500 Syntax error, command unrecognized. when tring to connect with SFTP
500, 501, 502, 503, 504 FTP Response Codes
This article explains 500 series response code:
500 FTP Response code
501 FTP Response code
502 FTP Response code
503 FTP Response code
504 FTP Response code

FileZilla Forums

Welcome to the official discussion forums for FileZilla

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:

Ok, so far so good…

Ok then… — and now explaining my problem… :

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

#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

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

Источник

FTP server return codes always have three digits, and each digit has a special meaning.^[1] The first digit denotes whether the response is good, bad or incomplete:

Range Purpose 1xx Positive Preliminary reply

The requested action is being initiated; expect another reply before proceeding with a new command. (The user-process sending another command before the completion reply would be in violation of protocol; but server-FTP processes should queue any commands that arrive while a preceding command is in progress.) This type of reply can be used to indicate that the command was accepted and the user-process may now pay attention to the data connections, for implementations where simultaneous monitoring is difficult. The server-FTP process may send at most, one 1xx reply per command.

2xx Positive Completion reply

The requested action has been successfully completed. A new request may be initiated.

3xx Positive Intermediate reply

The command has been accepted, but the requested action is being held in abeyance, pending receipt of further information. The user should send another command specifying this information. This reply is used in command sequence groups.

4xx Transient Negative Completion reply

The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. The user should return to the beginning of the command sequence, if any. It is difficult to assign a meaning to «transient», particularly when two distinct sites (Server- and User-processes) have to agree on the interpretation. Each reply in the 4xx category might have a slightly different time value, but the intent is that the user-process is encouraged to try again. A rule of thumb in determining if a reply fits into the 4xx or the 5xx (Permanent Negative) category is that replies are 4xx if the commands can be repeated without any change in command form or in properties of the User or Server (e.g., the command is spelled the same with the same arguments used; the user does not change his file access or user name; the server does not put up a new implementation.)

5xx Permanent Negative Completion reply

The command was not accepted and the requested action did not take place. The User-process is discouraged from repeating the exact request (in the same sequence). Even some «permanent» error conditions can be corrected, so the human user may want to direct his User-process to reinitiate the command sequence by direct action at some point in the future (e.g., after the spelling has been changed, or the user has altered his directory status.)

6xx Protected reply

The RFC 2228 introduced the concept of protected replies to increase security over the FTP communications. The 6xx replies are Base64 encoded protected messages that serves as responses to secure commands. When properly decoded, these replies fall into the above categories.

Below is a list of all known return codes that may be issued by an FTP server.

Code Explanation 100 Series The requested action is being initiated, expect another reply before proceeding with a new command. 110 Restart marker replay . In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm where yyyy is User-process data stream marker, and mmmm server’s equivalent marker (note the spaces between markers and «=»). 120 Service ready in nnn minutes. 125 Data connection already open; transfer starting. 150 File status okay; about to open data connection. 200 Series The requested action has been successfully completed. 202 Command not implemented, superfluous at this site. 211 System status, or system help reply. 212 Directory status. 213 File status. 214 Help message. Explains how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user. 215 NAME system type. Where NAME is an official system name from the registry kept by IANA. 220 Service ready for new user. 221 Service closing control connection. 225 Data connection open; no transfer in progress. 226 Closing data connection. Requested file action successful (for example, file transfer or file abort). 227 Entering Passive Mode (h1,h2,h3,h4,p1,p2). 228 Entering Long Passive Mode (long address, port). 229 Entering Extended Passive Mode (|||port|). 230 User logged in, proceed. Logged out if appropriate. 231 User logged out; service terminated. 232 Logout command noted, will complete when transfer done. Alternatively: User logged in, authorized by security data exchange. 234 Specifies that the server accepts the authentication mechanism specified by the client, and no security data needs to be exchanged. 235 Specifies that the server accepts the security data given by the client, and no further security data needs to be exchanged. 250 Requested file action okay, completed. 257 «PATHNAME» created. 300 Series The command has been accepted, but the requested action is on hold, pending receipt of further information. 331 User name okay, need password. 332 Need account for login. 334 Specifies that the server accepts the authentication mechanism specified by the client, but some security data needs to be exchanged. 335 Specifies that the server accepts the security data given by the client, but further security data needs to be exchanged. 350 Requested file action pending further information 400 Series The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. 421 Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down. 425 Can’t open data connection. 426 Connection closed; transfer aborted. 430 Invalid username or password 434 Requested host unavailable. 450 Requested file action not taken. 451 Requested action aborted. Local error in processing. 452 Requested action not taken. Insufficient storage space in system. File unavailable (e.g., file busy). 500 Series Syntax error, command unrecognized and the requested action did not take place. This may include errors such as command line too long. 501 Syntax error in parameters or arguments. 502 Command not implemented. 503 Bad sequence of commands. 504 Command not implemented for that parameter. 530 Not logged in. 532 Need account for storing files. 534 Request denied for policy reasons. 550 Requested action not taken. File unavailable (e.g., file not found, no access). 551 Requested action aborted. Page type unknown. 552 Requested file action aborted. Exceeded storage allocation (for current directory or dataset). 553 Requested action not taken. File name not allowed. 600 Series Replies regarding confidentiality and integrity 631 Integrity protected reply. 632 Confidentiality and integrity protected reply. 633 Confidentiality protected reply. 10000 Series Common Winsock Error Codes^[2] (These are not FTP return codes) 10054 Connection reset by peer. The connection was forcibly closed by the remote host. 10060 Cannot connect to remote server. 10061 Cannot connect to remote server. The connection is actively refused by the server. 10065 No route to host / DNS cannot be resolved. 10066 Directory not empty. 10068 Too many users, server is full.

Источник

Problem

During FTP secure communications — FTPS / SSL : 500 Syntax error, command unrecognized
Communication session is failing to add data to inbound queue

Symptom

500 Syntax error, command unrecognized

Cause

This has been identified as a product defect under APAR IT07637

Diagnosing The Problem

Review ftp log and look for 500 Syntax error, command unrecognized on inbound receive for FTP secure

Resolving The Problem

Fix is scheduled for 3.6.0.11 Point Release. At present time you will need to contact support for hot fix. After released, download fix from Fix Central
Production Date: 2015
APAR IT07637
Q/C #458542 Compile Date: 2015/03/11
EBDI069FTP Program — FTP CLIENT back-end processor
The secure FTP session was failing when a 500 message was being issued in the FTP log.

[{«Product»:{«code»:»SS6UY8″,»label»:»Sterling Gentran:Server for iSeries»},»Business Unit»:{«code»:»BU059″,»label»:»IBM Software w/o TPS»},»Component»:»—«,»Platform»:[{«code»:»PF012″,»label»:»IBM i»}],»Version»:»3.5;3.6″,»Edition»:»»,»Line of Business»:{«code»:»LOB59″,»label»:»Sustainability Software»}}]

Источник

dll: Командир экипажа; Сообщения: 76; Зарегистрирован: Чт июл 23, 2009 4:14 pm; Благодарил (а):
2 раза; Поблагодарили:
1 раз

«500 Syntax error, command unrecognized.» при работе с FTP

xStarter 1.9.4.9, 1.9.4.13, WinXp SP3
Задача скачать с одного FTP-сервера файлы и залить их на другой FTP-сервер. Скрипт скомпилирован в exe-файл. Все проходит нормально, за исключением того, что почта не отсылается по TLS-соединению (проблема уже описана в viewtopic.php?f=3&t=2048). Т.е. файлы скачиваются и закачиваются откуда надо и куда надо. Раньше я не пользовался возможностью при скачивании и закачивании по FTP выводить ход процесса в лог (опция «Лог файл» в Действиях FtpSyncDownload и FtpSyncUpload). Сейчас проведя успешное скачивание-заливку посмотрел получившиеся файлы и обнаружил там кучу ошибок вида:
500 Syntax error, command unrecognized.

Повторюсь, все скачалось и закачалсоь, как и должно было. Непонятно, что это за ошибки. Кто может внести ясность: ошибки это xStarter-а, который неверно считает ошибочный нормальное течение процесса или происходит какая-то, действительно, ошибочная ситуация, но тогда в чем она заключается?

Саму задачу и два архива получившихся лог-файлов прикладываю к данному посту. Пароли, естественно, стерты.

Вложения

FTP161146.xstk: (26.57 КБ) 564 скачивания

upload.7z: (11.15 КБ) 327 скачиваний

download.7z: (8.54 КБ) 347 скачиваний

LizardOfOzz: Гвардии пилот — Наставник; Сообщения: 1165; Зарегистрирован: Пт сен 08, 2006 8:59 pm; Благодарил (а):
8 раз; Поблагодарили:
38 раз; Контактная информация:

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Сообщение

LizardOfOzz » Вт окт 27, 2009 9:27 pm

А нет ли возможности получить логи со стороны фтп-серверов?

upd: Похоже, FileZilla не поддерживает xсrc. Просто снимите соответствующую галку в настройках. =(

За это сообщение автора LizardOfOzz поблагодарил:: dll (Вт окт 27, 2009 9:27 pm)

dll: Командир экипажа; Сообщения: 76; Зарегистрирован: Чт июл 23, 2009 4:14 pm; Благодарил (а):
2 раза; Поблагодарили:
1 раз

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Сообщение

dll » Чт окт 29, 2009 9:32 pm

LizardOfOzz писал(а):А нет ли возможности получить логи со стороны фтп-серверов?

Не совсем понял, какие именно логи требуются, но, в принципе, в этим FTP-серверам у меня полный доступ. Только я, честно сказать, ни в зуб ногой, куда FTP-сервер пишет «записки» о своей деятельности. Если подскажете, где искать, то нет вопросов.

upd: Похоже, FileZilla не поддерживает xсrc. Просто снимите соответствующую галку в настройках. =([/quote]
Workaround понятен, попробую. Но это, опять же, workaround, а не решение проблемы. Повторюсь, по-факту, все работает, как и должно, никаких нареканий, кроме этих немного смущающих записей в логе.

LizardOfOzz: Гвардии пилот — Наставник; Сообщения: 1165; Зарегистрирован: Пт сен 08, 2006 8:59 pm; Благодарил (а):
8 раз; Поблагодарили:
38 раз; Контактная информация:

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Сообщение

LizardOfOzz » Чт окт 29, 2009 10:37 pm

1. Логи с сервера оказались не нужны, т.к. у меня под рукой есть FileZilla Server.
2. Не понимаю, почему вы считаете, что это workaround. Если сервер чего-то не умеет, то причём тут стартер? Вот, например, mail.ru не поддерживает tls и в почтовом клиенте я эту галку не ставлю. Это тоже workaround?

dll: Командир экипажа; Сообщения: 76; Зарегистрирован: Чт июл 23, 2009 4:14 pm; Благодарил (а):
2 раза; Поблагодарили:
1 раз

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Сообщение

dll » Пн ноя 09, 2009 10:38 am

1) Ok
2) Понял вас. Согласен, workaround в данном случае неверное слово. Но в таком случае не совсем понятно зачем в интерфейсе xStarter-а есть такая галка, если она, в принципе, не будет работать. Как вы это можете объяснить?

LizardOfOzz: Гвардии пилот — Наставник; Сообщения: 1165; Зарегистрирован: Пт сен 08, 2006 8:59 pm; Благодарил (а):
8 раз; Поблагодарили:
38 раз; Контактная информация:

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Сообщение

LizardOfOzz » Пн ноя 09, 2009 10:43 am

dll писал(а):1) Ok
2) Понял вас. Согласен, workaround в данном случае неверное слово. Но в таком случае не совсем понятно зачем в интерфейсе xStarter-а есть такая галка, если она, в принципе, не будет работать. Как вы это можете объяснить?

Этот режим не будет работать с данным конкретным сервером. Зато будет работать с другим сервером, который поддерживает эту фичу. Не удалять же поддержку TLS из стартера из-за того, что mail.ru его не поддерживает.

Alex: Ас; Сообщения: 2828; Зарегистрирован: Вт апр 05, 2005 3:28 pm; Откуда: Kaliningrad City; Благодарил (а):
2 раза; Поблагодарили:
91 раз; Контактная информация:

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Сообщение

Alex » Пн ноя 09, 2009 10:46 am

Но в таком случае не совсем понятно зачем в интерфейсе xStarter-а есть такая галка, если она, в принципе, не будет работать. Как вы это можете объяснить?

У меня на DVD проигрывателе есть цифровой SPDF аудио выход, но он почему то не работает… Ааа, у меня же на колонках нет такого входа, поэтому просто некуда было втыкать кабель .

dll: Командир экипажа; Сообщения: 76; Зарегистрирован: Чт июл 23, 2009 4:14 pm; Благодарил (а):
2 раза; Поблагодарили:
1 раз

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Сообщение

dll » Пн ноя 09, 2009 10:48 am

Все понял, туплю Сворачиваем тему.

Источник

Question

Answers

FileZilla Forums

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

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

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

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

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

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

FileZilla Forums

500 Syntax error

500 Syntax error

Re: 500 Syntax error

FileZilla Forums

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

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

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

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

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

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

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

This article explains 500 series response code:

500 FTP Response code

501 FTP Response code

502 FTP Response code

503 FTP Response code

504 FTP Response code

Problem

Symptom

Cause

Diagnosing The Problem

Resolving The Problem

«500 Syntax error, command unrecognized.» при работе с FTP

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Re: «500 Syntax error, command unrecognized.» при работе с FTP

Читайте также:

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

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

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