Similar Threads
1. Removing Anonymous FTP from directory prevents write access by any
Hi
We are using IIS 6.0 and have a slight problem. When we remove anonymous
ftp access from web directory, it prevents anyone writing to the directory.
The only way we seem to be able to get write access for anyone is to
re-enable anonymous ftp. Any suggestions?
Thanks
Dave Quinn.
2. Separate Anonymous Access User to prevent FTP browsing?
3. Anonymous FTP write access only.
Hi
I currently have an NT4 server running an old version of IIS, this has
been set up so that anonymous FTP users have write access only, this
may seem insecure and we do get a certain ammount of hackers or
taggers testing the system by dropping test files and folders onto the
server, but because anonymous users do not have read access they soon
find that they cannot download anything they upload and go elsewhere.
Due to the demise of NT4 Support at the end of the year we are
currently replacing all our NT servers with either Win2000 or, as in
this case, Win 2003 Servers. This is where my problems have started,
I initialy replicated all the IIS setting and NTFS permission from my
NT box on my 2003 box but so far have been unable to achive the same
result, it appaers that I can only grant anonymous write access if I
grant read access as well, I've tried every different configuration I
can think of but come to the same conclusion.
The message I get on the screen when only write access is enabled
(useing NTFS permissions) is "cannot log in, home directory
inaccessible, Anonymous login failed."
If I enable read and write access I can login OK, write data and then
read it as well (as expected).
Can any one advise how I can set up FTP on my 2003 so that anonymous
users can only write data but cannot list or read anything ?
Thanks in advance.
Phill J.
Torbay,
Devon,
UK
4. Multiple User Access to Anonymous FTP Directory
5. New FTP site alongside default FTP site allowing anonymous access
I need some help on how I go about setting up a ftp server using windows
authentication restricted to an ip address alongside a default FTP server
allowing accessing access from one IP.
I have a default ftp server allowing anonymous access from an ip address
already setup and running. I need to give someone else FTP access to a
particular folder who is not coming from our internal IP address.
My idea is to keep the anonymous default server up and running and setup a
new FTP server to point to the new folder. I plan to create a new FTP server
to a different FTP root and use a virtual directory to point to the folder
they need. I plan on restricting this FTP server to the static IP of the
client.
A couple of questions:
1. How will I the server know which FTP server to goto. I cant seem to see
any setting to identify between the two FTP servers (a bit like host headers
in the websites section) I don have different IP address to allocate to
the server. If they try and access the server from an ip that is not
accepted on the default server will it go to the default one?
2. Will setting up another FTP server affect the default server and cause
any problems
Anyone any tips?
6. Can not access web directory in Win2k3 with anonymous access d
7. Can not access web directory in Win2k3 with anonymous access disab
I am sure this has something to do with a missing (or extra) domain security
policy. Here is the scoop. I have a domain controller and a member server.
The member server is running IIS 2k3 with all the lastest "windows update". I
create a vir. dir. on the server and in it a simple .htm. With anonymous
access enabled, I can open this file from the domain controller running IE.
When I turn anonymous access off and have Integrated Windows Authentication
turned on, I get a prompted to log in. Even providing the correct signon does
not allow me access. (The login on the domain controller is a domain admin.)
This of course works when I do not have the member server in the domain. The
member server and domain controller (also 2k3) are "out of the box" test
setups -- so I am pretty sure that I am missing some security policy. Any
help is appreciated.
8. Allowing Anonymous write access only.