MS 2003 FTP server-2
Access control, Availability, Bandwidth, Browsers, Desktops, DHCP, DNS, filtering, Management, Microsoft Windows, Networking, Networking services, OS, Security, Servers, SQL Server, SSL/TLS, Web security
Hi,
I have several sites accessing applications to download them, like MS office or Antivirus Applications, from the main site. I would like to set up a MS 2003 FTP server in the main site and give authenticated access to remote sites accordingly. I would like to know if there is a way to limit the bandwidth each user consumes per session. Also, if it is possible to just allow the users to install the application directly from the FTP site but not copy the executable files to another location
Thank You
Software/Hardware used:
Software/Hardware used:
ASKED:
September 4, 2006 1:14 AM
UPDATED:
September 5, 2006 8:34 AM
Answer Wiki:
hello threre. I think that you really need to consider what you want to do with using ftp. My approach with this type of service that you intend to provide is to keep local copies on your remote sites for application installation, patches and windows updates instea of using the precious wan bandwith. The new update microsoft free windows update system allows you to setup remote agents.
Julio
To see all answers submitted to the Answer Wiki: View Answer History.
The way we do it where I work is we have one shared mapped drive with our common apps on it – the tech goes to the shared drive (using enterprise server 2003, btw) and do the installs from there – with only read permissions set on the files. FTP is a cool idea and all, but seems to me to be a ham-handed way of getting the job done. Just my $.02…
I agree with previous answer to keep your files located at the remote sites and save costly bandwidth, but if you can’t, I limit my bandwidth at the router. If you don’t have a router in front of the server, then use Windows routing and remote access. I’ve never done it using windows routing, but since it will function as a router, the capability is there.
Bruce