PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Mon, 23 Jul 2001 23:27:29 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (50 lines)
On 23 Jul 2001, at 13:06, Westly Montroos wrote:

> I have more question about Windows 2000. As I wrote in
> my previous e-mail, I have seven computer with Windows
> 2000. All the machines have a network card.
> I want to use one of these machines as a "server"
> machine, but the Operating System of this machine is
> Windows 2000.
> This is my goal:
> The machine, which is going to operate like a server,
> has to place some restrictions on the other machine,
> which are also run by Windows 2000 Professional
> Edition.
>
> Is this possible?
>
> Westly Montroos

  A "workgroup" of Windows 2000 machines can share folders and
printers, but they do not share security information.  By default,
anything shared by one will be accessible by all the others.
  What you *can* do is assign passwords to some of the shares, so
that only users who have the password can access them, and I believe
you can assign separate passwords for read-only and read-write
access.  This "share level" security is pretty primitive.

  If you use NTFS as the file system on the server, you can also
impose "user level" security on files and folders.  Users will need
to "log in" when they connect to the "server", in order to determine
what permissions they have, but will still be able to freely use
resources on other machines, even if they never log in to the server.

  To force users to log in at a "network" level in order to use any
machine/resource, you need a "domain" instead of a workgroup.  A
domain includes one or more mcahines which are designated to hold
user account security information for all machines that are members
of the domain.  Only "server" versions of NT or 2000 can be domain
controllers, however.  [On my home network, I have an NT4 Server
domain controller and a mix of 98SE and 2000 Pro client machines.]

  Can you be more specific about what "restrictions" you want to
impose?  Perhaps your current workgroup arrangement is sufficient for
your purpose.

David Gillett

                         PCBUILD's List Owners:
                      Bob Wright<[log in to unmask]>
                       Drew Dunn<[log in to unmask]>

ATOM RSS1 RSS2