Ok so every now and then I manage to come up with a truly puzzling thread for these forums, here is one for those of us with experience in network admin....
Currently going to be converting my wife's windows box to a Linux server, and putting her on a Mac(Definite step up
. This server will be replacing one that died some time ago. At any rate here is what I am looking to do, and I am looking for advice/suggestions on this path...
This server will act as a fileserver for the house, it needs to interact with Mac, Linux, and Windows(Roommate) machines.
I would like the login onto a machine to be almost a two step process I suppose. Let me explain my reasoning behind this and see if t here are better solutions to this first as this seems a bit like the wrong way to do things...
Primarily I would like the benefits of remote login still having the same settings(Desktop etc) as much as possible, but I dont want it to happen in a way that if the Server goes down for any reason, it would prevent my wife, or my roommate from using their own computers. This is why I was wondering if a two step process might be better, where the local logon would automatically after succeeding attempt to log on to the server and share Files etc. That way worst case scenario they would be working locally, remember this has to be cross platform compatible with Windows(Which I havent dealt with serious networking in it in some time) and Mac.
Looking at the above it seemed that if I used the server for a PDC etc in a windows style network and used it as the logon authenticator, that if it went down for whatever reason(Power Outage while I am on the road etc.) they might not be able to use their computer which is somewhat unacceptable. Please feel free to correct me if I am wrong.
I figured if I did a 2 step process, I might use rsync to create a local cache of the Home Directory on the local machine. The Home Directory would not be very large in most cases, documents etc. Media is on different directories(See later)
The server may actually end up running a Myth Backend on it as well. In the meantime though I would like to share, not only a home directory, but also the appropriate share directory for my media(Video, Music, etc) as long as permissions are granted for it for that person. Now my understanding in Samba(Previous use of Samba for myself was just to share Home Directories) is that this is done by creating different 'share' sections. My question though would be how to determine if a user has access to those shares, and how to automount those shares in that case on the various OSes.
This wont be happening for another month(When I actually get home, remember that on the road thing I mentioned before? so I intend to use this next month to plan it out so that hopefully I can implement it farily easily. As such comments/suggestions/claims of insanity are quite welcome
Seablade
Currently going to be converting my wife's windows box to a Linux server, and putting her on a Mac(Definite step up
. This server will be replacing one that died some time ago. At any rate here is what I am looking to do, and I am looking for advice/suggestions on this path...This server will act as a fileserver for the house, it needs to interact with Mac, Linux, and Windows(Roommate) machines.
I would like the login onto a machine to be almost a two step process I suppose. Let me explain my reasoning behind this and see if t here are better solutions to this first as this seems a bit like the wrong way to do things...
Primarily I would like the benefits of remote login still having the same settings(Desktop etc) as much as possible, but I dont want it to happen in a way that if the Server goes down for any reason, it would prevent my wife, or my roommate from using their own computers. This is why I was wondering if a two step process might be better, where the local logon would automatically after succeeding attempt to log on to the server and share Files etc. That way worst case scenario they would be working locally, remember this has to be cross platform compatible with Windows(Which I havent dealt with serious networking in it in some time) and Mac.
Looking at the above it seemed that if I used the server for a PDC etc in a windows style network and used it as the logon authenticator, that if it went down for whatever reason(Power Outage while I am on the road etc.) they might not be able to use their computer which is somewhat unacceptable. Please feel free to correct me if I am wrong.
I figured if I did a 2 step process, I might use rsync to create a local cache of the Home Directory on the local machine. The Home Directory would not be very large in most cases, documents etc. Media is on different directories(See later)
The server may actually end up running a Myth Backend on it as well. In the meantime though I would like to share, not only a home directory, but also the appropriate share directory for my media(Video, Music, etc) as long as permissions are granted for it for that person. Now my understanding in Samba(Previous use of Samba for myself was just to share Home Directories) is that this is done by creating different 'share' sections. My question though would be how to determine if a user has access to those shares, and how to automount those shares in that case on the various OSes.
This wont be happening for another month(When I actually get home, remember that on the road thing I mentioned before?
so I intend to use this next month to plan it out so that hopefully I can implement it farily easily. As such comments/suggestions/claims of insanity are quite welcomeSeablade
The router serves a different purpose than the PDC. My concern is how the PDC going down would affect the network. There really wont be sharing going on in between the individual machines, that is what the server is there for and what it would accomplish.
Not that I've tried for a few years, mind.
