RTM2007
asked on
Setting Up Corporate FTP Server? Instead of e-mailing Large Attachments
I want to stand up an FTP server/file hosting so that we can move away from having people sending attachments to e-mail that are 10, 20, 30 MB, etc.
Looking to see how I should address/research this?
Looking to see how I should address/research this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi RTM2007
One good solution is to setup an FTP server based on Linux , Best known is vsftpd (Very Secure FTP)
You can install CentOS 5.2 (Red Hat Clone Free to Download) and all services you ever want are there including vsftpd.
Note: people can easly ftp from IE or Firefox or a free ftp client like filezilla
Setting up the server is a totaly different story
First you need to put some sort of design like
who access data and what do they access
how many concurrent connections
maximum transfer rate
securtiy.....etc
Best Regards
One good solution is to setup an FTP server based on Linux , Best known is vsftpd (Very Secure FTP)
You can install CentOS 5.2 (Red Hat Clone Free to Download) and all services you ever want are there including vsftpd.
Note: people can easly ftp from IE or Firefox or a free ftp client like filezilla
Setting up the server is a totaly different story
First you need to put some sort of design like
who access data and what do they access
how many concurrent connections
maximum transfer rate
securtiy.....etc
Best Regards
ASKER
And with implemeting a vsFTP solution how easy will the end-user experience be? In other words how easy will it be for people within my organization to relay/upload FTP files for transfer to others outside on the net?
ASKER
I am basically looking to do this with something that will integrate well with Outlook so it is fairly transparent to the end user. It doesn't matter much to me if it is HTTP or FTP however, it DOES need to be as easy to operate for the end user as it is to send an e-mail all in one.
it would be easier to have an external app to send an email and the file in // than having outlook to post a file, which is not a feature you can implement, outook is not open source afaik.
and making an app to send email is not too difficult, but receiving them and decoding, etc... is a lot more complex. And your users wouls still miss the other features, agenda, etc...
very little chance to find a way...
and making an app to send email is not too difficult, but receiving them and decoding, etc... is a lot more complex. And your users wouls still miss the other features, agenda, etc...
very little chance to find a way...
ASKER