OBS= CADA FTP deverá ser configura FTP Authorization Rules e Isolate users using Active Directory

The File Transfer Protocol (FTP) is a standard network protocol used to transfer computer files from one host to another host over a TCP-based network. FTP is built on Cilent-Server Architecture and it uses separate connections for control and data.

FTP client connects with FTP server with normal Username and Password information called FTP Login details. Following is a complete flow of FTP client – server connection establishment process.

1. FTP client sends a DNS query for domain name to get the FTP server IP address(if you are using ftp.domain.com as FTP hostname).
2. DNS responds back with the IP address.
3. FTP client and server complete three way handshake process.
4. The FTP server then sends a 220 response to indicate that the FTP server is ready to accept a login.
5. The FTP client sends Username through USER command, and Password through PASS command.
6. FTP Server verifies the provided login information.
7. If provided login details are correct, FTP server will in turn sends a Welcome message.
8. FTP client requests a directory listing.
9. FTP server transfer the requested listing.

After specifying FTP credentials, If FTP user does not have required privileges, you may receive following error message in FTP client:

Status: Resolving address of ftp.xxxxx.com

Status: Connecting to xxx.xxx.xxx.xx:21…

Status: Connection established, waiting for welcome message…

Response: 220 Microsoft FTP Service

Command: USER Administrator

Response: 331 Password required for Administrator.

Command: PASS ***************

Response: 530 User cannot log in, home directory inaccessible.

Error: Critical error

Error: Could not connect to server
In most cases, this error occurs only when FTP authorization rules for default FTP site are not set. Let’s see how we can change FTP authorization rules to fix this error.

Step – 1:
Login to the VPS via Remote Desktop connection as an Administrator user.

Step – 2:
Open IIS [Start -> Administrative Tools -> Internet Information Service].

Step – 3:
Expand Sites option from left pane.

Step – 4:
You will see a Default FTP Site in site list, expand this website.

Step – 5:
Now, double click on FTP Authorization Rules option from the center pane.

Step – 6:
From the right pane, click on Add Allow Rule.

Step – 7:
Select the option of All Users and tick the check box of Read and Write permission.

Step – 8:
Click on OK button to save the changes and Restart Microsoft FTP Services to reflect them.

Follow below mentioned steps to restart Microsoft FTP Services.

Step – 1:
Open Services [Start -> Run -> type service.msc and Hit Enter].

Step – 2:
Select the service named Microsoft FTP Service.

Step – 3:
Click on Restart link from the left pane option.

Now, try again to login to the FTP account. If everything goes fine, then you should not receive any error while connecting to your FTP account.

Error message when you try to log on to an FTP site that is running IIS 6.0: “Error: 530 User <UserName> cannot log in, home directory inaccessible”

You try to log on to an FTP site that is hosted on a server that is running Microsoft Windows Server 2003, the Active Directory directory service, and Microsoft Internet Information Services (IIS) 6.0. The FTP site is configured to use “Isolate users using Active Directory” mode. However, you cannot log on to the FTP site. Instead, you receive the following error message:

This problem occurs only when a particular domain controller is offline or unavailable. At other times, you can successfully log on to the FTP site.

https://support.microsoft.com/en-us/kb/932448

http://portal.hostingcontroller.com/KB/a2/ftp-error-530-home-directory-inaccessible.aspx

https://manage.accuwebhosting.com/knowledgebase/941/FTP-Error-530-User-cannot-log-in-home-directory-inaccessible.html

https://manage.accuwebhosting.com/knowledgebase/941/FTP-Error-530-User-cannot-log-in-home-directory-inaccessible.html