FTP Error 530 User cannot login

Viewed 109747

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?

17 Answers

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.

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

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.

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.

enter image description here

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.

I spent long time looking for a solution, I've tried every shared answer on the internet and nothing could solve the issue. It is an issue I was ignoring for years and I never could fix.

Ok, I've Plesk installed and I'm not sure if it has some effect on IIS FTP to do the following behavior ...

Using Process Monitor tool, and making ftp login request and watching the tool and doing your investigation using this tool, you can get a hint about the REAL reason of the problem.

For me, I found out that IIS FTP was trying to access the ftp folder from a path DIFFERENT than the actual ftp path I've set, I do not know why, but maybe Plesk has some effect on this.

The actual ftp path is

C:\inetpub\vhosts\zidapp

The path that IIS FTP was trying to access DURING the login process is

C:\inetpub\vhosts\Servers\7\localuser\zid_app_ftp_user

I fixed the issue by creating a folder link from 'actual' folder path to the path IIS was trying to access - using the tool mklink tool

CMD command

mklink /d C:\inetpub\vhosts\Servers\7\localuser\zid_app_ftp_user "C:\inetpub\vhosts\zidapp" 

I've fixed the issue that way, so wen FTP is trying to access the folder from the wrong path, it is now goes to the correct one.

Please note doing folder shortcut wont work for this, you need a link like linux, not a shortcut ...

I hope it will help you :)

Related