Click to See Complete Forum and Search --> : Building a server for a LAN


Belgian Brownie
04-24-2009, 02:59 AM
I have been doing quite a bit of reading and a bit of "playing" and now I want to build a server for a LAN (as a test).

The server will need to provide, in a first instance, central authentication, file server, remote access and allow Windows clients to connect.

Would I need:

LDAP for authentication
SSH for remote access
Samba for Windows integration
NFS for network file services
PAM to glue the lot together

??

For the server, I am thinking Centos 5.2 and for LDAP using Fedora Directory Server. For clients, a mix of Fedora, Opensuse, Ubuntu and Madriva plus XP/Vista.

Am I missing something? Do I need more? How far off target am I?

Or am I just plain nuts? :eek:

ph34r
04-24-2009, 02:04 PM
I wouldn't bother with both NFS and Samba, since the Linux clients can connect to the Samba shares as well (or better) than the Windows clients...

Belgian Brownie
04-24-2009, 03:32 PM
OK, so if I understand correctly, don't worry about NFS... use Samba for both?

leonpmu
05-01-2009, 11:55 AM
Yes, that is the answer, BTW any particular reason for a Domain?

Belgian Brownie
05-03-2009, 04:41 PM
Yes, that is the answer, BTW any particular reason for a Domain?
Well, I would want centralised control of users, machines, etc... and the best way of doing that would be setting up a local domain, in the Windows world. As I am getting more into it, I am getting the feeling that an ordinary workgroup would suffice and that a linux workgroup can be as efficient as a Windows domain.

Mind you, there would be Windows clients wanting to connect in so a PDC would fit nicely into the scheme of things.

Am I still on track??? :)