Part 1 FTP cannot log in...............
If no user can log in, please do the following check
1. Is there a port used to close FTP? Is FTP started?
2. Have you manually changed the FTP home directory?
First try FTP in DOS on the server, start - running, enter cmd
Then enter ftp your IP
Enter the username and password to see if you can log in
530 User xxxx cannot log in, home directory inaccessible.
home directory inaccessible. It means that the home directory of FTP is inaccessible, and by default
IIS--the default FTP site is occupied, and the FTP attributes--the home directory should be in
C:\inetpub\ftproot
Please do not modify the content here, and at the same time, check whether this directory exists. The permissions of this directory are automatically set when installing the controlled terminal.
If only one of the users cannot log in:
First try FTP in DOS on the server, start - running, enter cmd
Then enter ftp your IP
Enter the username and password to see if you can log in
If FTP can be used on the server and the user says that FTP cannot be successful on his computer, 100% is caused by the network, and the reasons are as follows
1. You have restricted the port on the server yourself, such as tcp filtering in the network card attribute, or ports in the Windows Firewall.
Please note that there is no need to restrict the port after using extrastar ipsec. Otherwise, the following problems will be caused:
PASV FTP cannot be used. Only use PORT mode.
2. The user's own network has been restricted. The common situation is that he is an intranet user. He can use cuteftp to upload and try to close the pasv mode.
3. Use the FTP tool falshfxp. If the remote directory is set to /, this is also wrong. This causes the user directory to be unable to enter. You should not set the remote directory, or set the remote directory to /FTP username.
If a user says that FTP was normal but could not log in later, the reason may be that you set the password locking policy in the local security policy on the server yourself, please turn it off, or refer to:
http:///support/freehost/highsafe/
Part 2: The problem of FTP being able to log in but not uploading or deleting files..............
After logging in, the only directories that can be written to are "/ftp username/web", "/ftp username/web" directory, and the "/ftp username/log" directory cannot be written. In addition, the / directory and the "/ftp username" directory cannot be written.
2. If you write to a subdirectory in the web or web directory, the possible reason is that the user's space has been used up, or the permissions in the web directory are incorrect, you can click to restore permissions in the management area, self-service management, and host management. If you click on it, go to the server to set it manually. If you find that there is no security attribute in the web directory that can be set, you need to scan the hard disk to solve the problem. It may also be caused by the user setting the write function in the panel.
3. A small number of users on the intranet have to upload files if they are restricted by networks. This situation can only be solved by users changing to upload the files.
4. Some network administrators have set up firewalls themselves, limiting that FTP can only use ports 20 and 21, which will also cause intranet users to be unable to upload. After using the extra-star security package, the unsafe ports have been automatically closed. Therefore, we do not recommend that you limit ports 20 and 21, because it will affect the use of normal users.
5. If FTP cannot delete files, the following reasons may be:
a). Files are locked, such as ACCESS databases, which allow users to unlock after stopping the virtual host, so they can be deleted. Generally, administrators can delete such files by stopping the pool or recycling the pool.
b). The file index is broken. In a server with millions of files, this is very likely to happen. This type of file cannot be deleted in the above method, and the administrator cannot delete it even if it finds the file on the server. It can only be deleted after scanning the hard disk. The command to scan the hard disk is:
chkdsk d: /r
If no user can log in, please do the following check
1. Is there a port used to close FTP? Is FTP started?
2. Have you manually changed the FTP home directory?
First try FTP in DOS on the server, start - running, enter cmd
Then enter ftp your IP
Enter the username and password to see if you can log in
530 User xxxx cannot log in, home directory inaccessible.
home directory inaccessible. It means that the home directory of FTP is inaccessible, and by default
IIS--the default FTP site is occupied, and the FTP attributes--the home directory should be in
C:\inetpub\ftproot
Please do not modify the content here, and at the same time, check whether this directory exists. The permissions of this directory are automatically set when installing the controlled terminal.
If only one of the users cannot log in:
First try FTP in DOS on the server, start - running, enter cmd
Then enter ftp your IP
Enter the username and password to see if you can log in
If FTP can be used on the server and the user says that FTP cannot be successful on his computer, 100% is caused by the network, and the reasons are as follows
1. You have restricted the port on the server yourself, such as tcp filtering in the network card attribute, or ports in the Windows Firewall.
Please note that there is no need to restrict the port after using extrastar ipsec. Otherwise, the following problems will be caused:
PASV FTP cannot be used. Only use PORT mode.
2. The user's own network has been restricted. The common situation is that he is an intranet user. He can use cuteftp to upload and try to close the pasv mode.
3. Use the FTP tool falshfxp. If the remote directory is set to /, this is also wrong. This causes the user directory to be unable to enter. You should not set the remote directory, or set the remote directory to /FTP username.
If a user says that FTP was normal but could not log in later, the reason may be that you set the password locking policy in the local security policy on the server yourself, please turn it off, or refer to:
http:///support/freehost/highsafe/
Part 2: The problem of FTP being able to log in but not uploading or deleting files..............
After logging in, the only directories that can be written to are "/ftp username/web", "/ftp username/web" directory, and the "/ftp username/log" directory cannot be written. In addition, the / directory and the "/ftp username" directory cannot be written.
2. If you write to a subdirectory in the web or web directory, the possible reason is that the user's space has been used up, or the permissions in the web directory are incorrect, you can click to restore permissions in the management area, self-service management, and host management. If you click on it, go to the server to set it manually. If you find that there is no security attribute in the web directory that can be set, you need to scan the hard disk to solve the problem. It may also be caused by the user setting the write function in the panel.
3. A small number of users on the intranet have to upload files if they are restricted by networks. This situation can only be solved by users changing to upload the files.
4. Some network administrators have set up firewalls themselves, limiting that FTP can only use ports 20 and 21, which will also cause intranet users to be unable to upload. After using the extra-star security package, the unsafe ports have been automatically closed. Therefore, we do not recommend that you limit ports 20 and 21, because it will affect the use of normal users.
5. If FTP cannot delete files, the following reasons may be:
a). Files are locked, such as ACCESS databases, which allow users to unlock after stopping the virtual host, so they can be deleted. Generally, administrators can delete such files by stopping the pool or recycling the pool.
b). The file index is broken. In a server with millions of files, this is very likely to happen. This type of file cannot be deleted in the above method, and the administrator cannot delete it even if it finds the file on the server. It can only be deleted after scanning the hard disk. The command to scan the hard disk is:
chkdsk d: /r