FAQs about FTP

The first part of FTP login failure ...................................

If no user can log on, perform the following checks:
1. Are there any ports used to disable FTP and FTP enabled?
2. Have you manually changed the FTP home directory.
First try FTP in DOS on the server, start -- running, Enter cmd

Enter your ftp ip address.

Enter the user name and password to see if you can log on.

530 user XXXX cannot log in, Home Directory inaccessible.

Home Directory inaccessible.

IIS-Default FTP site occupation, FTP properties-the main directory should be in

C: \ Inetpub \ ftproot

Do not modify the contents here and check whether the directory exists. The permission for this directory is automatically set when the controlled end is installed.

If only one of the users cannot log on:

First try FTP in DOS on the server, start -- running, Enter cmd

Enter your ftp ip address.

Enter the user name and password to see if you can log on.

If FTP is available on the server, and the user says FTP is not successful on his computer, 100% is caused by the network, for the following reasons:
1. You have restricted the port on the server, for example, the TCP filter in the NIC attribute or the port in the Windows Firewall.

Note that you do not need to restrict the port after using external IPSec. Otherwise, the following problems may occur:
Pasv ftp cannot be used. You can only use the port mode.

2. the user's network is limited. Generally, the user is an intranet user. You can use CuteFTP to upload files and disable the PASV mode to upload files.

3. Use the FTP tool falshfxp. If the remote directory is set to/, this is also incorrect. As a result, the user directory cannot be entered. Do not set the remote directory or set the remote directory to/FTP user name.

If a user says that FTP is normal and cannot be logged in later, it may be because you have set a password lock policy in the Local Security Policy on the server, close him, or refer:
Http://www.7i24.com/support/freehost/highsafe/107141619369.htm

The second part is about FTP login, but the file cannot be uploaded or deleted ............................ .......

1. after FTP login, only the "/FTP Username/Web", "/FTP Username/Web", and "/FTP Username/log" directories can be written. in addition, the/directory and "/FTP Username" directory cannot be written.

2. if access denied is prompted when a sub-directory is written to the Web or web directory, the possible cause is that the user's space is used up or the permissions of the web directory are incorrect. You can manage the sub-directory in the management area by yourself, in host management, click Restore permission. If it doesn't work, set it manually on the server. if the server finds that the web directory does not have the security attribute, you can set it. You need to scan the hard disk to solve the problem. it may also be caused by the disabled write function in the panel.

3. A small number of users upload files in the internal network, which must be replaced by the network.

4. some network administrators have set their own firewalls, which limit FTP to use ports 20 and 21, which also prevents Intranet users from uploading data. When an out-Of-The-stars security package is used, insecure ports are automatically disabled, therefore, we do not recommend that you set port 20 or port 21 as it affects normal user usage.

5. If an FTP file cannot be deleted, it may be due to the following reasons:
A) the file is locked, such as the access database. These files can be deleted after the user stops the VM. Generally, administrators can stop or recycle the pool to delete such files.

B) The index of the file is broken. This is very likely to happen on a server with millions of files. These files cannot be deleted by using the above methods, and the file cannot be deleted by the Administrator on the server. You can delete a disk only after scanning it. The scan command is:
Chkdsk D:/R