Re: Logon difference in Workgroup and domain
- From: "Joe Richards [MVP]" <humorexpress@xxxxxxxxxxx>
- Date: Sat, 16 Dec 2006 09:48:29 -0500
You have the exception of domain resources on domain controllers. If you have file and print, etc on a DC, the same type of passthrough auth will work where a workgroup ID synced with a domain ID will end up using that domain ID. You cannot however use a workgroup ID against a domain member and end up using the domain ID. If you have ever worked in an environment where you were trying to move from OS/2 to Windows you run into this issue and one of the solutions is to start putting resources on Domain Controllers (shudder).
joe
--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net
---O'Reilly Active Directory Third Edition now available---
http://www.joeware.net/win/ad3e.htm
Herb Martin wrote:
"Benny" <wuyuebing@xxxxxxxxx> wrote in message news:1166149622.447584.44050@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.So what is the difference to access network for a local user and a user
in AD?
In general, a local "computer specific" user cannot
access (most) resources on the net and cannot be
given such access DIRECTLY (Guest access might
apply but Guest is in fact a domain account.)
Domain Users can be granted (or selectively denied)
access to domain resources.
In general, "Access to domain resources requires
domain authentication -- either directly or indirectly
through a trusted domain."
- References:
- Logon difference in Workgroup and domain
- From: yuebing . wu
- Re: Logon difference in Workgroup and domain
- From: Herb Martin
- Re: Logon difference in Workgroup and domain
- From: Benny
- Re: Logon difference in Workgroup and domain
- From: Herb Martin
- Logon difference in Workgroup and domain
- Prev by Date: Re: GPO issue
- Next by Date: Re: Enlarge user profile size
- Previous by thread: Re: Logon difference in Workgroup and domain
- Next by thread: restore child domain
- Index(es):