Re: Group Permissions
- From: "Manny Borges" <manny_borges@xxxxxxxxxxx>
- Date: Mon, 6 Mar 2006 06:23:10 -0500
Wow, I haven't played with that kind of network in quite a long while, and
correct me if I am wrong, but I seem to remember the biggest issue with this
is maintenance.
If a user changes thier password on thier local machine, then you have to
make sure that the "Server" has its password changed manually as well(of
course, to the exact same password), right?
Really any kind of directory service would be advisable here. NT4 server is
pretty cheap nowadays, and a machine to run it can be bought for 20 bucks.
--
Manny Borges
MCSE NT4-2003 (+ Security)
MCT, Certified Cheese Master
There are 10 kinds of people in the world. Those who do understand binary
and those who don't.
"Malke" <notreally@xxxxxxxxxxx> wrote in message
news:OZc$MqHQGHA.2828@xxxxxxxxxxxxxxxxxxxxxxx
K Miller wrote:
Thanks for the prompt reply and links Kerry. I knew it would take
someone with a great first name like yours to figure this out! Just
one question, I will need to set up accounts for each user on the
"server" in order to "make sure the user names and passwords
exist..."?
Yes, of course. Here's an example:
You have four users - Kerry, Malke, Bill, and Sue. You have a folder for
Marketing that you only want Sue to be able to get to (and you, of
course).
1. On the pseudo-server, make accounts for all 4 users with the
passwords matching the ones on the users' workstations.
2. On the pseudo-server, make Malke, Bill and Sue just plain users.
Kerry is the Administrator (also a member of users group).
3. On the pseudo-server, create a user group called Marketing. Add users
to this group - Kerry and Sue.
4. Set permissions on the folder so no one except the Marketing group
has read access. Now Malke and Bill won't be able to access that
folder.
One thing I should mention to you if this is a new setup. You have ten
machines, all accessing one pseudo-server. You may very well run into
the inbound concurrent connections limit. Note that inbound connections
doesn't mean *computers*; depending on what you are doing with the
pseudo-server, each workstation can make more than one connection to
it. See this link for more information:
http://support.microsoft.com/?id=314882
concurrent connections:
10 for XP Pro/Tablet/MCE
5 for XP Home
49 for SBS 2000
74 for SBS 2003
Unlimited for full Server O/Ses
If you run into this issue, the only way to get around it is to 1)
replace the XP Pro on the pseudo-server with a real MS server operating
system (SBS would be good for you); or 2) if the pseudo-server is just
a file server and isn't running any Windows programs, replace the XP
Pro on it with an operating system that doesn't have those limitations
such as Linux.
Depending on your business, a real server operating system has many
advantages such as centralized workstation management, antivirus, group
policies, etc.
Malke
--
MS-MVP Windows User/Shell
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"
.
- References:
- Group Permissions
- From: K Miller
- Re: Group Permissions
- From: Kerry Brown
- Re: Group Permissions
- From: K Miller
- Re: Group Permissions
- From: Malke
- Group Permissions
- Prev by Date: Re: screen saver
- Next by Date: Re: Screen capture question
- Previous by thread: Re: Group Permissions
- Next by thread: Re: Group Permissions
- Index(es):
Relevant Pages
|
