how to setup?
-
I installed my windows 2000 server with IIS 5.0. Now I want to allow users to ftp to server and transfer files between users' client pc and server, But How can I setup the server to achieve that one user can only access to a specified directory on the server and can not access to other users' directory.(ideally,the directory may just be the user name)? And in that user-specified directory,everyone can access that directory(the directory is setup as a web visual path and the specified user can upload website files) via browsers but not ftp? What I have done is: I create a user and according to username a directory on the server harddisk,and setup the path as a visual ftp directory in IIS manager interface,but everyone can visit that path,and if I setup the path's access rights to specified user,then browser to that path is prompt user to provide user and password? Roger's reply: I just went through this hassle - the solution is non-obvious on Win2K Server. Check my thread on the Operating Systems forum; the response from Richard D solved my access problem nicely. Quicklink[^] I couldn't give access to users who had perfectly valid user accounts on my domain. It turned out that local logon rights are denied by default on the Server edition. The link Richard provided gave detailed instructions on how to enable this. Once you enable it, your users should be able to get into the computer and the FTP area. Limiting access to specific shares for each user can probably be done using NTFS rights on each folder. I don't know that for sure because I haven't tried it. Only one user beside myself has access, and I trust that one - I haven't tried limiting access yet. If this doesn't work, move this discussion to the Operating Systems forum and we'll continue it. this is my signature for forums quoted from shog*9: I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
-
I installed my windows 2000 server with IIS 5.0. Now I want to allow users to ftp to server and transfer files between users' client pc and server, But How can I setup the server to achieve that one user can only access to a specified directory on the server and can not access to other users' directory.(ideally,the directory may just be the user name)? And in that user-specified directory,everyone can access that directory(the directory is setup as a web visual path and the specified user can upload website files) via browsers but not ftp? What I have done is: I create a user and according to username a directory on the server harddisk,and setup the path as a visual ftp directory in IIS manager interface,but everyone can visit that path,and if I setup the path's access rights to specified user,then browser to that path is prompt user to provide user and password? Roger's reply: I just went through this hassle - the solution is non-obvious on Win2K Server. Check my thread on the Operating Systems forum; the response from Richard D solved my access problem nicely. Quicklink[^] I couldn't give access to users who had perfectly valid user accounts on my domain. It turned out that local logon rights are denied by default on the Server edition. The link Richard provided gave detailed instructions on how to enable this. Once you enable it, your users should be able to get into the computer and the FTP area. Limiting access to specific shares for each user can probably be done using NTFS rights on each folder. I don't know that for sure because I haven't tried it. Only one user beside myself has access, and I trust that one - I haven't tried limiting access yet. If this doesn't work, move this discussion to the Operating Systems forum and we'll continue it. this is my signature for forums quoted from shog*9: I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
Yes,using NTFS rights on each folder can solve limiting access to specific shares for each user. But another problem occur,since I have setup the user directory as a visual path of default website in IIS manager,when client browse to that web path,he will be prompted a popup windows to provide user name and passord because I have delete that directory's everyone rights. :confused: this is my signature for forums quoted from shog*9: I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
-
Yes,using NTFS rights on each folder can solve limiting access to specific shares for each user. But another problem occur,since I have setup the user directory as a visual path of default website in IIS manager,when client browse to that web path,he will be prompted a popup windows to provide user name and passord because I have delete that directory's everyone rights. :confused: this is my signature for forums quoted from shog*9: I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
Forgive me if I sound dense - It's very late and I'm having some trouble understanding your English. You're doing great, but I'm tired... You should not be using the default website in IIS; put the shared folder in the default FTP site. When your users connect they should use 'ftp://zhoujunsdomain.com' to establish a FTP connection. A logon dialog box should then appear, and they should type in the proper username and password. The next screen they should see is a collection of folders stored in the Default FTP Site location. From there it should be no trouble to open any folder for which that user has permissions to use. Removing the Everyone Group is a good idea, by the way, but you have to be sure to create permissions for each user that you want to have access. I created a group called FTPUsers for just that purpose, and it's working well so far. "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
-
Forgive me if I sound dense - It's very late and I'm having some trouble understanding your English. You're doing great, but I'm tired... You should not be using the default website in IIS; put the shared folder in the default FTP site. When your users connect they should use 'ftp://zhoujunsdomain.com' to establish a FTP connection. A logon dialog box should then appear, and they should type in the proper username and password. The next screen they should see is a collection of folders stored in the Default FTP Site location. From there it should be no trouble to open any folder for which that user has permissions to use. Removing the Everyone Group is a good idea, by the way, but you have to be sure to create permissions for each user that you want to have access. I created a group called FTPUsers for just that purpose, and it's working well so far. "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
It's very late and I'm having some trouble understanding your English. My english is still in practising stage.I am sorry to give you trouble.hehe. :-O I will give an example,say,I create a user account named zhoujun,and I create a directory "c:\zhoujun",and I add a visual ftp path in default ftp site named "zhoujun" mapping to "c:\zhoujun",and I give the "c:\zhoujun" path access rights to only user "zhoujun",then user zhoujun can access to "c:\zhoujun" and other users can not access it. Then I create a visual path for "c:\zhoujun" in default web site,name it to "zhoujun",so the client browsers can access using "http://hostdomainname/zhoujun/index.asp; But since only zhoujun can access to "c:\zhoujun",and everyone have no access rights now,the browser pop up a login windows,then sad story begins. :confused: How to deal with it? this is my signature for forums quoted from shog*9: I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
-
It's very late and I'm having some trouble understanding your English. My english is still in practising stage.I am sorry to give you trouble.hehe. :-O I will give an example,say,I create a user account named zhoujun,and I create a directory "c:\zhoujun",and I add a visual ftp path in default ftp site named "zhoujun" mapping to "c:\zhoujun",and I give the "c:\zhoujun" path access rights to only user "zhoujun",then user zhoujun can access to "c:\zhoujun" and other users can not access it. Then I create a visual path for "c:\zhoujun" in default web site,name it to "zhoujun",so the client browsers can access using "http://hostdomainname/zhoujun/index.asp; But since only zhoujun can access to "c:\zhoujun",and everyone have no access rights now,the browser pop up a login windows,then sad story begins. :confused: How to deal with it? this is my signature for forums quoted from shog*9: I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
Each user will need a local account on your server, and will have to enter a username and password when the login box appears. The shares you want them to be able to access will also have to have permissions set for each user to allow it. Did you follow the instructions in Richard's response to my question? They worked perfectly on my machine. "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long