SAMBA is probably the best choice for serving files on a Windows network. However, you could use NFS and install an NFS client on each Windows PC. That, or use anonymous FTP and limit access to the local net with the hosts.allow file.
FTP is clunky if you use browsers or "true" FTP clients, but it can provide both general and user-level access. Windows XP and later can even even map an FTP site as a network drive. (2000 may be able to do this, too) So, in that way, you can use FTP and attain most of the functionality available with SAMBA.
You could even have one of the Windows machines map the FTP offering of the file server as a network drive and then offer it up as a true Windows file share to the rest of the network: sort of a file server proxy.
Last edited by foodown; 10-13-2009 at 06:20 PM.
|