Windows Forum

Ask something
Discussion Locked

FTP Server Security Setup

0 helpful
5 replies

by allan_oh

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I setup ServerA as our FTP server. I setup the default FTP site such that the 'Home Directory' for this FTP site is a share drive on ServerB.

I set the NTFS permission and share permission on \\ServerB\ftproot as
User1 (full control); User2 (read); everyone else(no access).

When I go to the 'Home Directory' property page, I enable READ, WRITE, LOG ACCESS and point to \\ServerB\ftproot, it then asks for 'Connect As'. Here's my problem:

If I enter the User1 account (with full permission) in the 'Connect As' page, when User2 (with only READ access) logs into the FTP site, User2 gets the FULL Access that User1 gets.

If I enter User2 account (with read only) iin the 'Connect As' page, when User1 (with Full access) logs into the FTP site, User1 only gets READ ONLY.

So it looks like the NTFS Permission for the account I specify under 'COnnect As' is the permission given to ALL users who log into the FTP site.

Note: If the Home DIrectory was locally on ServerA (so no needfor 'Connect As'), all permissions are correct.

Does anybody know of a way to work around this so that even if the 'Home Directory' is on a separate server, the permissions are still correct?

Thanks.

5 replies

by rorycarlin

Are you sure you haven't enabled anonymous access? What could be happening is the incoming connection is logging in as 'anonymous' and then assuming the security context of the user specified in the 'Connect as' option. If this is the case disableanonymous access.

Hope this helps.

by ebob

Perhaps on Server A, map to the drive over on B. Let's just call that drive "N:\" on server A.

Then setup your permissions on server A's drive N:\.

by allan_oh

I already tried mapping the drive instead of using UNC. When I put "n:\" as in your example, it automatically changes it to the UNC path.

by maz1980

It is good try to update your NT server with SP6a + post SP6a SRP update + IIS cumulative update. All can be downloaded on microsoft website. I think it can solve the problem

This discussion is closed to new replies.