IIS 7 and Above
IIS 10, virtual FTP sever, user isolation, Win 7 client, 530 home dir...
Last post Apr 06, 2019 04:48 PM by BearGFR
Apr 06, 2019 04:48 PM|BearGFR|LINK
This one is strange
I have an IIS 10 ftp site/server set up to enable virtual ftp servers. I have a "default global ftp listener" set up on port 21, no specific host name, anonymous authentication disabled.
I also have a virtual server set up, also on port 21, with a specific binding to host name ftp.<domain name>. The virtual server is configured to allow (but not require) SSL, for user isolation it is configured with "Do not isolate users, start users in
=> user name directory".
Here's where things go off the rails:
If I log in from either a Windows 10 client using the default ftp client, or from a Linux machine using the default command line ftp client, and specify (as documented) "user ftp.<domain name>|userid" and provide the associated password, it all works
just fine as expected. If a user specific home directory exists in the root folder of ftp.<domain name> then the user is placed in that folder. If such a folder does not exist, then the user is logged in and placed into the root folder of the virtual server.
All works like it's supposed to.
HOWEVER - If I try exactly the same things using a Windows 7 default ftp client (ftp.exe) then no matter what combination I try, the login fails with "530 home directory inaccessible" - same ftp server, same configuration, same method(s) of connecting,
even the same user credentials. The only thing that's different between what works and what doesn't is the fact that the client (and OS) are Windows 7 and not Windows 10 or Linux. What gives?
....aw dang - nevermind, I just found the problem. I actually have two ftp servers (redundant) that serve the same site and one of them was lacking the needed ftp authorization rules. I was just being "unlucky" in that my Win 7 client for some reason insisted
on routing to that ftp server.