SimonWGoldsmith
asked on
IIS 5 FTP User directory problems...
Good morning folks!
I own a Windows 2000 Server with 1 ip address using host headers to run mutliple domains and websites.
I know I can only have one FTP website because of the one IP address issue, so I use virtual directories under the main ftp website pointing to the same directories where users the websites files are located.
Example!
www.domain1.co.uk(website) -> c:\websites\domain1
domain1ftp(virtual directory under main ftp website) -> c:\websites\domain1
My problem is this...
How do I setup users for each website and redirect them to their website directory when they use an FTP client???
Any help greatly appreciated as I can not find any decent information on securing directories on a server using 1 IP address.
I own a Windows 2000 Server with 1 ip address using host headers to run mutliple domains and websites.
I know I can only have one FTP website because of the one IP address issue, so I use virtual directories under the main ftp website pointing to the same directories where users the websites files are located.
Example!
www.domain1.co.uk(website) -> c:\websites\domain1
domain1ftp(virtual directory under main ftp website) -> c:\websites\domain1
My problem is this...
How do I setup users for each website and redirect them to their website directory when they use an FTP client???
Any help greatly appreciated as I can not find any decent information on securing directories on a server using 1 IP address.
After you setup a new user on the server, right click on the new user and select properties. Then select the Profile tab. Set the user's home directory to the website directory. Hope this helps!
ASKER
Any chance of a step by step rough guide from setting up the virtual folder onwards???
I know most of it but I think I must be doing something wrong. :(
Below is how I would setup an ftp user.
1) Create the virtual directory under "Default FTP Website".
2) Set permissions on the directory being mapped to via the virtual directory.
3) Add users who should be able to see and have access to this directory.
4) Then I guess I do what you have said and set a home directory???
I know most of it but I think I must be doing something wrong. :(
Below is how I would setup an ftp user.
1) Create the virtual directory under "Default FTP Website".
2) Set permissions on the directory being mapped to via the virtual directory.
3) Add users who should be able to see and have access to this directory.
4) Then I guess I do what you have said and set a home directory???
ASKER
BTW does the user have to have the same name as the directory as well?
ASKER
Ignore that last comment I figured it out, but is there away to stop users being able to get out of their directory???
Setting their home directory to the path of the website should do this...did you test it?
I did a little test to make sure I told you correctly
I did the steps that you outlined above
I then set my test user's home directory to the path of my virtual directory
I ftp'd to my server and tried to get out of the home directory by using commands like:
cd ..
cd c:\
Try that on your server and see if the users can get out of their home directory (they shouldn't be able to).
Let me know how it turns out.
I did a little test to make sure I told you correctly
I did the steps that you outlined above
I then set my test user's home directory to the path of my virtual directory
I ftp'd to my server and tried to get out of the home directory by using commands like:
cd ..
cd c:\
Try that on your server and see if the users can get out of their home directory (they shouldn't be able to).
Let me know how it turns out.
ASKER
It doesn't stop users getting out of their default directory! :(
I am sure there is a way.
I am sure there is a way.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
oops, that's only for 2003 server, sorry
ASKER
thanks for your help.
I have sorted it by disallowing users access to the wwroot folder! ;)
I have sorted it by disallowing users access to the wwroot folder! ;)