451 This command is not valid in the current state. Use ABOR

Message

Gldm · #1 Post by **Gldm** » 2006-03-16 13:30

I seem to get this error constantly. Sometimes files will transfer ok, most of the time it will just start spamming commands that all get this response. The client doesn't seem to acknowledge the error at all, it just keeps spamming away with TYPE I, RETR, and PORT commands. I've tried entering raw FTP commands but the option's usually grayed out. Any ideas how to fix this? Why isn't this error properly handled?

#2 Post by **botg** » 2006-03-16 17:58

And which command is not valid? Please post some complete logs.

Gldm · #3 Post by **Gldm** » 2006-06-21 09:41

Ok.

Response: 220-Gldm's FTP
Response: WarFTPd 1.82.00-RC10 (Jan 25 2005) Ready
Response: (C)opyright 1996 - 2005 by Jarle (jgaa) Aase - all rights reserved.
Response: 220 Please enter your user name.
Command: USER gldm
Response: 331 User name okay, need password.
Command: PASS ******
Response: 230 User gldm logged in from host dsl-165-173-226.telkomadsl.co.za (165.165.173.226)
Command: FEAT
Response: 500 'FEAT': command not understood.
Command: SYST
Response: 215 UNIX Type: L8 Server: "WarFTPd 1.82.00-RC10" OS: "WIN32 (Windows XP 5.1 2600 Pentium II 1-CPU)"
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE A
Response: 200 Type set to A.
Command: PASV
Response: 227 Entering Passive Mode (69,114,98,213,0,1)
Command: LIST
Response: 150 Opening ASCII mode data connection for /bin/ls (495 bytes).
Error: Transfer channel can't be opened. Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Error: Could not retrieve directory listing
Command: TYPE A
Response: 451 This command is not valid in the current state. Use ABOR to abort the current operation.
Command: PWD
Response: 451 This command is not valid in the current state. Use ABOR to abort the current operation.
Command: REST 0
Response: 451 This command is not valid in the current state. Use ABOR to abort the current operation.
Command: TYPE I
Response: 451 This command is not valid in the current state. Use ABOR to abort the current operation.
Command: TYPE A
Response: 451 This command is not valid in the current state. Use ABOR to abort the current operation.
Command: PWD
Response: 451 This command is not valid in the current state. Use ABOR to abort the current operation.
Command: REST 0
Response: 451 This command is not valid in the current state. Use ABOR to abort the current operation.
Response: 426 Error. Transfere aborted.
Command: PWD
Response: 257 "/" is current directory.
Command: PWD
Response: 257 "/" is current directory.
Command: PWD
Response: 257 "/" is current directory.
Command: REST 0
Response: 350 Restarting at byte offset 0. Send STORE or RETRIEVE to initiate transfer.

Need another? I can get a couple hundred examples of when a file transfer times out and it retries 999 times and dies if you want.

Gldm · #4 Post by **Gldm** » 2006-08-11 14:25

So is there any fix for this in the works? This is a lethal problem guys, it makes the program completely unusable.

#5 Post by **botg** » 2006-08-11 23:05

Basically you seem to have a wrong router or firewall configuration. Please configure all routers/firewalls to allow connections to the ports the servers use.

Gldm · #6 Post by **Gldm** » 2006-08-21 07:50

botg wrote:Basically you seem to have a wrong router or firewall configuration. Please configure all routers/firewalls to allow connections to the ports the servers use.

The server's on the DMZ IP of a Linksys WRT54G. The software firewall on the machine has the port enabled, and it's < 1024.

As far as I know, that should work. Why do you think it's a router or firewall config problem?

#7 Post by **botg** » 2006-08-21 08:09

Additional ports have to be forwarded and opened for the data connections. Please read the FAQ in the server forums.