On Tue, 2013-07-02 at 09:28 +0200, steve wrote:
[SNIP]
Do I have this?
1. is a domain controller and a file server.
2. is a member server and a file server.
Yes, that is what you have.
Another question, why do you say:
'...its a domain server (or domain controller).'
Which _is_ it?
I'll have a go :)
My 2p:
A Windows domain is an authentication-and-authorisation space, defined
by a database of all usernames known within that space, together with
their passwords, group memberships and much more related stuff. The
username database (held as a set of files of course) is
On Mon, 2013-07-01 at 19:55 -0500, Ricky Nance wrote:
I feel like I am saying what has already been said, so if you could be
more specific about what kind of hierarchy you have, I could give you
a more specific answer. For the most part, if its serving files and in
a domain, but not
Hi Steve
On 2 July 2013 09:28, steve st...@steve-ss.com wrote:
On Mon, 2013-07-01 at 19:55 -0500, Ricky Nance wrote:
I feel like I am saying what has already been said, so if you could be
more specific about what kind of hierarchy you have, I could give you
a more specific answer. For
On Tue, 2013-07-02 at 11:02 +0200, Michael Wood wrote:
Hi Steve
On 2 July 2013 09:28, steve st...@steve-ss.com wrote:
On Mon, 2013-07-01 at 19:55 -0500, Ricky Nance wrote:
I feel like I am saying what has already been said, so if
you could be
On a very general level , a member server is joined to the domain so
that it can use the domain accounts.A member server is typically
a file server but does not have to be (you could be using it as a web
server, or application server or even a workstation.)
A domain controller
On Mon, 2013-07-01 at 09:59 -0400, Gaiseric Vandal wrote:
[SNIP]
A domain controller can be a file server, although in many cases a
domain controller will only provide authentication and logon
functions.It does need to have file shares to provide access to to
the logon scripts and
On Mon, 2013-07-01 at 17:04 +0100, Jonathan Buzzard wrote:
On Mon, 2013-07-01 at 09:59 -0400, Gaiseric Vandal wrote:
[SNIP]
A domain controller can be a file server, although in many cases a
domain controller will only provide authentication and logon
functions.It does need
I don't think it necessarily makes it a member a member server BUT if it
isn't a member server it is going to be pretty useless for serving profiles.
I have not worked with Samba4 myself- I have worked with Samba 3 (and
Windows 200x AD , and NT4) so you may want to review the samba 4
On Mon, 2013-07-01 at 14:35 -0400, Gaiseric Vandal wrote:
I don't think it necessarily makes it a member a member server BUT if it
isn't a member server it is going to be pretty useless for serving profiles.
Ok, so if a samba 4 box can serve profiles, then it is called a member
server, whether
On 01/07/13 19:56, steve wrote:
[SNIP]
Yes. We take stand alone machines and network them by adding a DC and
what we call a file server. What I'd like to know is why some guys here
call what seems to be what we call a file server, a member server. I
feel we're missing out on something.
In
Good explanation. Better than mine.
I tend to think of the roaming profiles as part of the logon experience,
since they sync with your computer when you logon. Actually, I found
roaming profiles to be more trouble than they were worth so I don't use
them anyway.
On 07/01/13 17:36,
On Mon, 2013-07-01 at 22:36 +0100, Jonathan Buzzard wrote:
Thanks for the input. But. . .
In both NT4 style and AD domains you have servers called domain servers
. . .now you've introduced yet another term. What's a domain server? I
could make a guess and I'm almost certain it would be
Steve, in simplest terms, a member server is just that, a member of the
domain serving something (print services, file services, etc). A file
server is generally part of either a member server, or it can be part of
the domain server, its simply the part of the server that is handling how
the files
14 matches
Mail list logo
