Access to server denied

[Guest]

Hi Chuck,

I am not sure how it is different from workgroup to store and maintain
authentification and authorization information in a central server...etc but
it sure sounds nice if I can add an assistant to tom by grouping. I actually
did try to seperate everything base on groups (ie. Account_Team,
Marketing_Team) but because our company is small, everyone is somehow involve
in a bit of everything. This gets very confusing. If all files in a folder
has same access for almost all staff or only few staff, I do create group and
set it up under security. IE. Mgmt_Goals_ReadOnly (which made up of staff
who have permission to read management goals for specific folder/file). I
wonder if this is similar to what the advantage you mentioned for domain.

XP Home can access domain resources as if there was a workgroup, but they
can't join a domain, no option? This refers to, as long as the name of the
workgroup for the XP Home is the same as the server, it will connect and
access the same way eventhough if the server is changed from workgroup to
domain? This is the same for Win ME? If this is the case, I can start
changing everything to domain before all machines are upgraded. Would this
solve the problem I am having with non computer administrator user account?

-Lucky

 

[Chuck]

Hi Chuck,

I am not sure how it is different from workgroup to store and maintain
authentification and authorization information in a central server...etc but
it sure sounds nice if I can add an assistant to tom by grouping. I actually
did try to seperate everything base on groups (ie. Account_Team,
Marketing_Team) but because our company is small, everyone is somehow involve
in a bit of everything. This gets very confusing. If all files in a folder
has same access for almost all staff or only few staff, I do create group and
set it up under security. IE. Mgmt_Goals_ReadOnly (which made up of staff
who have permission to read management goals for specific folder/file). I
wonder if this is similar to what the advantage you mentioned for domain.

XP Home can access domain resources as if there was a workgroup, but they
can't join a domain, no option? This refers to, as long as the name of the
workgroup for the XP Home is the same as the server, it will connect and
access the same way eventhough if the server is changed from workgroup to
domain? This is the same for Win ME? If this is the case, I can start
changing everything to domain before all machines are upgraded. Would this
solve the problem I am having with non computer administrator user account?

-Lucky

Lucky,

Server 2000 supports Active Directory, which lets you maintain group
relationships in several ways. Here's a good place to start explaining that:
<http://www.microsoft.com/technet/pr...erv/technologies/activedirectory/default.mspx>
http://www.microsoft.com/technet/pr...erv/technologies/activedirectory/default.mspx

And here's a forum like this one, where they discuss AD:
<http://www.microsoft.com/technet/co...?dg=microsoft.public.win2000.active_directory>
http://www.microsoft.com/technet/co...?dg=microsoft.public.win2000.active_directory

Next, computers running XP Home cannot join a domain. If you have a lot of XP
Home systems, that's a domain killer.

You can setup a workgroup (put the computers on a workgroup) with the name
identical to the domain name. That will let the browser subsystem in the domain
(including the domain controller, which will be the domain master browser) serve
the XP Home computers and list the computers in Network Neighborhood. But
you'll still have to setup workgroup accounts on the clients and servers.
Windows 98 and ME, IIRC, will use domain authentication. Just not XP Home.
<http://nitecruzr.blogspot.com/2005/08/setting-up-domain-or-workgroup-plan.html>
http://nitecruzr.blogspot.com/2005/08/setting-up-domain-or-workgroup-plan.html
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#OlderOS>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#OlderOS

I'm still trying to figure out what your problem with the non admin account is.
I recommend that you move to your domain setup only after planning the process,
and only after trying to resolve the workgroup problem first. Any time you move
ahead with a problem still active, you double the effort and embarrassment
involving in moving back. That's called burning your bridges, and I don't
recommend that.

Spend a while reading the TechNet article above. And let's explore the
authentication problem some more. I suspect you need a little more background
in server concepts, before you move up to domain concepts. A domain is,
basically, not terribly different from a workgroup, except that you trust a
third computer to provide the authentication.

In a workgroup, you have a relationship involving two computers - a client
accessing a server. In a domain, you have a relationship involving maybe three
computers - a client accessing a server, being authenticated by a domain
controller. The server (shared files and printers) could be a part of the
domain controller. But there are separate and intricate functions there.

But, when you get to Active Directory, that's another ball of wax. Read the
TechNet article, please.