FTP Error 530 User cannot login

问题:

I am trying to FTP to a new FTP site I setup with IIS 7.0 for the Windows Server Web (64-bit) edition. But I get the above error when I try to login to this site. But I can login to my other FTP sites.

Also, when I select this website from IIS Manager, the FTP section does not display in the middle section although it does display in Action panel. And I cannot successfully login to this FTP site either.

I have checked and I have Log on locally selected. I do not have allow only anonymous connections. I have Access this computer from the network selected.

I restarted my IIS and FTP services also.

The one different thing I noticed about this website in IIS different from the other site that has FTP working is that this one there are 3 virtual directories beneath the site. And that when I click on any one of these 3, then the FTP strip does appear in the center pane. Make sense?

How can I debug cause of this error? Any SW tools I can use?

回答1:

Have you tried logging in from the FTP server? If you do this, and have "Show detailed messages from local requests" enabled under FTP Messages, then you'll get a clearer idea as to why the login if failing. In my case I got the following message (I am using IIS Manager Users, and Passthrough authentication)

530-User cannot log in.
 Win32 error:   Access is denied.
 Error details: Filename: \\?\C:\Windows\system32\inetsrv\config\redirection.config
 Error: Cannot read configuration file due to insufficient permissions

To solve this I gave the NETWORK SERVICES user read only access to the config directory specified in the error message. I'm not 100% sure this is the right thing to do, but it certainly fixed this issue for me.

回答2:

In my case I forgot to enable the Basic authentication

回答3:

in my situation, I was missing Role Service FTP extensibility, which is actually allows IIS Manager Auth. This is pretty tricky, as you could allow IIS Manager auth, but still it would not work until you have not installed FTP Extensibility

回答4:

Try submitting your credentials in this format:

UserName: Domain|Username
Password: secretSquirrel

回答5:

There seem to be many different possible causes. In my case, I was unable to login with the plain "username" with the same error as mentioned.

It was solved when I logged in with ".\username" instead.

For some reason the FTP client was trying to login with a domain account, while I just wanted to login with a local computer account.

Hope this helps someone.

回答6:

I had the same problem, I removed the FTP site and followed this:

http://www.iis.net/learn/publish/using-the-ftp-service/configure-ftp-with-iis-manager-authentication-in-iis-7

Prerequisites - I set the permissions on the folders using the 4 command samples but this did not alone fix the issue, so I cannot in good faith say this step is needed, but it is what I did and it now works.

CONFIGURE THE IIS MANAGEMENT SERVICE AND ADD AN IIS 7 MANAGER -

Just do step 4, removing the existing user first and then re-adding them.

Creating a New FTP Site and Configuring an IIS 7 Manager Account -

All the steps here

CONFIGURE THE FTP SITE TO USE IIS 7 MANAGER AUTHENTICATION All 12 steps here, including the "administrator" setting in step 5.

Then it started working for me, I am guessing when I did this without a guide I skipped something simple.

回答7:

Per this knowledgebase article, you would need the log on locally privilege enabled.

http://support.microsoft.com/kb/200475

回答8:

I had the exact same error. In my case, I was using a local user defined on the server running FTP. The username was very short (3 characters). I could "run as" this user on the server, confirming that Windows was Ok with it, and allowed it to authenticate. But when testing FTP, it would return User cannot log in.

Solution? I renamed the user to be longer (4 characters). Of course, updated its name under Authorization as well. Then FTP worked. Hope it helps someone!

回答9:

For me, I've configured the IIS as per usual procedure properly. The anonymous authentication was working but specific user are not.

because, the user accounts were created in IIS. Actually it was also supposed to be created Windows local accounts.

Then it worked.

回答10:

In My case I have made that user a member of IIS_IUSERS.

回答11:

Using IIS Users.

Do not isolate users -> User name directory was working fine. Users started in the right folder.

When I was switching to Isolate Users -> User name Directory I had the following error:

Response:   530 User cannot log in, home directory inaccessible.
Win32 error: The system cannot find the path specified.

For some reason, you need to add the LocalUser virtual directory that points to your root.

It has to be that exact name and it's case sensitive.

That worked for me.

回答12:

Please Check the security of folder which is use that ftp . see if the user or group you select for that ftp is associate with security of that folder .

回答13:

In my case I had to remove domain from user.

So, your user should be like username, not like domain\username.

Hope it helps to somebody.

回答14:

For some reason my user was "locked". So I could "unlock" it at local user manager (computer management). Now it works fine. I hope it helps.

回答15:

I would recommend checking FTP logs first. The status code will give you more information about the issue. Here is the explanation of the status codes: The FTP status codes in IIS 7.0 and later versions

I had this issue because my IIS didn't support passive mode. After entering data in FTP Firewall Support module, the issue was solved.

More scenarios from this post 530 User cannot log in, home directory inaccessible

Authorization rules. Make sure to have an Authorization rule that allows the user or anonymous access. Check “IIS > FTP site > FTP Authorization Rules” page to allow or deny access for certain or all users.

NTFS permissions. The FTP users (local or domain users) should have permissions on the physical folder. Right click the folder and go to Properties. In the Security tab, make sure the user has required permissions. You can ignore Shared tab. It is not used for FTP access.

Locked account. If you local or domain account is locked or expired, you may end up seeing “User cannot log in” error. Check local user properties or Active Directory user settings to make sure the user account is active.

Other permission issues. The user account may not have “Log on locally” or “Allow only anonymous connections security” rights.

回答16:

You can check the reference account you are using to log in. Mine happened to be locked out causing the 530 error.