Common FTP login log information

1.

The following are the referenced contents: Connected. Waiting for response. Serv-u FTP Server v4.0 for WinSock ready ... USER Anonymous 530 Sorry, no ANONYMOUS access allowed. QUIT

This is not allowed to log on anonymously.

2.

The following are the referenced contents: Connected. Waiting for response. Serv-u FTP Server v4.0 for WinSock ready ... USER Test 331 User name Okay, need password. Pass XXXXXX 530 not logged in. QUIT

It is generally the information that occurs when a password is entered incorrectly, but for Serv-u, the same error message can occur if there is no such account (test).

3.

Connecting to xxx.xxx.xxx.xxx, Port (#1)

Error:connection timed out

This indicates that the other person is not on, or that the other side is not in the range you can access

4.

Connecting to xxx.xxx.xxx.xxx Port (#1)

Error:connection refused

This generally indicates that the other side has turned on, but did not open the FTP service (not open serv-u)

may also not provide services on this port for each other

5.

The following are the referenced contents: Connecting to xxx.xxx.xxx.xxx, Port (#1) Connected. Waiting for response. Disconnected from server. Connection attempt failed. Waiting for retry ...

This information is really bad luck, you are very likely to be the other ban.

If only a few minutes or a few hours or a day, otherwise only with the webmaster said good words, let him to you to solve it.

6.

The following are the referenced contents: Connecting to xxx.xxx.xxx.xxx, Port (#1) Connected. Waiting for response. USER XXX 331 User name Okay, need password Pass XXXXXX 530 not logged in, unauthorized IP address. QUIT

This is a bit troublesome, your IP is not allowed to access the IP range, only with the webmaster contact, let him put your IP network segment into the Allow access list

7.

The following are the referenced contents: Connected. Waiting for response. Serv-u FTP Server v4.0 for WinSock ready ... User User 421 Too Many users-please try again later.

Haha, this is very common, the user too much, went to the Jiaotong University to know how to do

8.

The following are the referenced contents: Connected. Waiting for response. Serv-u FTP Server v4.0 for WinSock ready ... USER Test 530 not logged in, only one (also possibly two or three) session from same IP allowed at a time. QUIT

Each IP can only open one (also may be two or three) download, do not use multithreading, carefully ban you.

The following are the referenced contents: Restart marker reply. In this case, the "text is exact" particular implementation; It must read:mark yyyy = MMMM where yyyy is user-process the data stream marker, and MMMM server ' s equivalent marker (note th e spaces between markers and "="). The Service ready in nnn minutes. The Data connection already open; Transfer starting. The File status okay; About to open data connection. Command okay. The superfluous Command not implemented, in this site. 211 System Status, or system help reply. 212 Directory status. The 213 File status. 214 Help message. on how to use the server or the meaning of a particular non-standard command. This reply was useful only to the human user. 215 Name System type. Where name is a official system name from the assigned Numbers document. The Service ready for new user. The 221 Service closing control connection. The Data connection open, no transfer in progress. Closing data connection. Requested file action successful (for example, file transfer or file abort). Entering passive Mode (H1,H2,H3,H4,P1,P2). 230 User logged in, proceed. logged out if appropriate. requested file action Okay, completed. 257 "PATHNAME" created. 331 User name Okay, need password. 332 Need account for login. Requested file action pending further information 421 Service not available, closing control connection. This May is a reply to any command if the service knows it must shut down. 425 Can ' t Open data connection. 426 Connection closed; Transfer aborted. 450 requested file action not taken. 451 requested action aborted. Local error in processing. 452 requested action not taken. Insufficient storage spaces in system. File unavailable (e.g., file busy). Syntax error, command unrecognized. This could 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. 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 the current directory or dataset). 553 requested action not taken. File name not allowed 110

Reboot the tag response. In this case the text is OK, it must be: Mark Yyyy=mmmm, where yyyy is the user process data flow token, MMMM is the server tag.

120

The service is ready in nnn minutes.

125

Data connection is turned on, ready for delivery

150

File is in good condition, open data connection

200

Command succeeded

202

Command not implemented

211

System state or system help response

212

Directory Status

213

File status

214

Help information, information only useful to human users

215

Name System type

220

Ready for new User Service

221

The service closes the control connection and can exit the login

225

Data connection open, no transfer in progress

226

Data connection turned off, the requested file operation was successful

227

Enter passive mode

230

User Login

250

The requested file operation is complete

257

Create "PATHNAME"

331

User name is correct, requires password

332

Require account information at login

350

Requested file operation requires further command

421

Cannot provide service, turn off control connection

425

Cannot Open data connection

426

Close connection, Abort transmission

450

The requested file operation was not performed

451

Abort the requested operation: there is a local error

452

Operation not performed: System is low on storage space

500

Bad format, command not recognized

501

Parameter syntax error

502

Command not implemented

503

Command Order Error

504

The command feature under the parameter is not implemented

530

Not logged in

532

Account information required for storing files

550

The requested operation was not performed

551

Request Operation aborted: page type unknown

552

Requested file operation aborted, storage allocation overflow

553

Action not performed: file name is not valid