RE: To Serve FTP or Not to Serve that is the question!!
From: paul (paul_at_discussions.microsoft.com)
Date: 09/16/04
- Next message: SBS Rookie: "Re: Adding Users"
- Previous message: Wes: "Re: XP server service missing"
- In reply to: Yosemite Sam: "To Serve FTP or Not to Serve that is the question!!"
- Next in thread: Yosemite Sam: "Re: To Serve FTP or Not to Serve that is the question!!"
- Reply: Yosemite Sam: "Re: To Serve FTP or Not to Serve that is the question!!"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 16 Sep 2004 09:35:14 -0700
Hey Sam -
Have you considered creating a SharePoint site using the Windows SharePoint
Services built into Win Server 2003? It's free, but each logged-in client
uses a CAL to access the site.
It's pretty secure (given your network is secure) and feature-rich. I've
been using it and creating seperate subwebs for clients and contractors,
where one can't see the other. User roles and user security is a bit tricky
to master, though. And, I belive you can deny access to RWW, but allow access
through port 444. E.g. www.mydomain.com:444
Just a suggestion over FTP, and like always, make sure this works with your
current security model.
Take a look on the Window Server site and read some of SharePoint deployment
guides. You'll get a good idea on how you want proceed if you do decide to
use WSS.
"Yosemite Sam" wrote:
> All,
>
> Need quick tip here.
> 1. Customer knows FTP on SBS is Free
> 2. Customer knows he trusts some Clients and Vendors.
> 3. Customer wants to allow a Free file exchange solution.
> 4. Customer is willing to add "Select" Clients/Vendors an AD account.
> 5. Customer does NOT want Vendors/Clients to see who else has access.
> 6. Customer does NOT want Vendors/Clients to see Remote Web Workplace.
> 7. Customer has a web site hosted elsewhere.
> 8. Linksys router between DSL modem and Server
> 9. Server "SBS2003 standard" has 2 NICs and in house net on one with
> Linksys router on other.
>
>
> I concidered turning up FTP server and hosting individual sites for each
> Vendor/Client and hosting each on a unique and unusual port i.g.
> xxx.xxx.xxx.xxx:39500
> Yes FTP is insecure on SBS and Yes passwords are open txt. but if user has
> only access to one folder on the server with read write only permissions and
> no trace back to internet of the usual port 21. How risky is it still?
>
> Given all that how would one setup the permissions for the non annonymous
> ftp user to upload and download files?
>
> Or am I just crazy for even thinking about this in the first place
>
> any other suggestions without spending big bucks?
> What about limited access to RWW for file swapping? lots of Large Autocad
> drawings must fly both ways almost daily.
>
> Thanks in advance for any help.
>
>
>
- Next message: SBS Rookie: "Re: Adding Users"
- Previous message: Wes: "Re: XP server service missing"
- In reply to: Yosemite Sam: "To Serve FTP or Not to Serve that is the question!!"
- Next in thread: Yosemite Sam: "Re: To Serve FTP or Not to Serve that is the question!!"
- Reply: Yosemite Sam: "Re: To Serve FTP or Not to Serve that is the question!!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|