530 User cannot log in, home directory inaccessible, FTP 7.0 user isolation and Process Monitor

I was trying to reproduce an issue posted on the forums @ (http://forums.iis.net).   As with many posts, I mention use Process Monitor.  Here is a perfect example. 

  • Find out what PID (process ID) in task manager

  • Open Process Monitor and isolate the PID (This helps cutdown on noise)

  • Reproduce the issue. (In my case, notice the highlighted line, it’s looking for c:domainsftprootssuser1).  I have the FTP 7.0 service running on a domain controller.  It means I need to create the SS (NetBIOS name) as a virtual directory for user isolation.  I don’t recommend running FTP on a domain controller, so this is for demo purposes.  PS: Once I added the SS virtual directory, I was able to use FTP user isolation.


Here is an article how to setup FTP 7.0


I thank Mark for creating Process Monitor!


Steve Schofield
Microsoft MVP – IIS


11 thoughts on “530 User cannot log in, home directory inaccessible, FTP 7.0 user isolation and Process Monitor

  1. Good article Steve. I saw that my IIS was looking for D:FTPRootLocalUserusername – if Anyone is having this same problem, try creating a LocalUserusername directory in the ftproot.

  2. Thanks for the article. Now on to the real question: I do not need user isolation (as demonstrated here), how can I configure IIS to not attempt this feature (search for a user directory – I do not have one, do not intend to create one)?

  3. Maybe nice for anyone else…
    Check wheter there are multiple FTP sites running on the machine (under IIS)

    If they both use the same IP, this
    is where your error comes from. ?

    Playing around with this error myself
    learned me that is not possible.

    Hope it helps anyone out there!

  4. I know very little about IIS but am trying to do this exact thing. I did what you said on this post and noticed that mine was adding WCSusername where wcs is our domain. I added a Virtual Directory to the FTP site and pointed it back to the root folder but that didn’t seem to work. Am I doing that right or am I way off?

  5. This is great. It didn’t work for me but I had no idea I could get that much information from Process Monitor so that will be useful for future troubleshooting.

    One thing to check if this solution doesn’t work is to drill down into your sites and check ftp authorization settings.

    For people learning IIS remember that there are a lot of different levels where things can be set, my problem was not at the main level, not at the site level, but below that in aspnet and localuser ftp authorization.

  6. Thank you for the article. I managed to get the default FTP site up and running with your information. Turns out the folder permissions were wrong.

    Then I added a virtual folder (not visible to browsers) and add some security to it. Just basic authentication with a user that has been created on the local server. But I keep getting an error about the home directory being inaccessible.

    My settings clearly state that isolation should not be used.

    Any idea of where I could look? PerfMon says that nothing failed.

    Thank you

  7. Thanks Mans. That worked like charm.
    New FTP with IIS 7.5 has many good features and better manageability. Just create user and folder in FTP Home directory. No need to create virtual directory and no need to set user security settings. Enable the isolation and everything works like charm.

Comments are closed.