I'm running two servers. One is the public facing FTP server and the other
is the server where the actual FTP folder is (the public facing server has
its FTP settings to virtually point to a share on the second server for its
default folder).
The servers are both 2008 standard, AD Integrated.
I'm running IIS 7 with an FTP site.
I'm having permissions issues. I've got basic and anonymous authentication
both enabled. No SSL or anyhting like that is enabled. Everything else is
standard.
On the share that the FTP virtual points to (on the second server),
permissions have been set up for various AD user accounts.
When a user account that has write access connects, they can read, upload
and make directories but only within the root folder. Once they make a new
directory int he root folder, they can go into the folder but trying to
upload a file doesn't work. I have even manaully created folders wtihin the
root folder and given full permissions to this specific FTP account and the
account is still unable to write anything to this folder. When I manually
put something into the folder via normal file operations on the local
network, the FTP user can see the file, but cannot view or download the
file.
Another issue is passive mode. No one can connect unless passv mode is
turned OFF in their FTP client. This also means that connecting via a web
browser is not possible unless they go into the security settings and make
the change. Even then, files are now shown properly as in a windows ecplorer
window (when using explorer). Files show up as a list of links only.
How can I fix these issues? Why can't people use the FTP service any deeper
than root level?
TIA,
Jim