Re: Active Directory

Hey Joe and Marc,

I really approciate all of your help; I did get things working. After following all of your direction, I was still having a few problems and it was due to my using the incorrect FQDN. My domain is simply 'moss' so I had to use "DC=moss,DC=local"; the "DC=local" is the part I wasn't providing.

Bob Mixon [SPS MVP]
http://www.ShareSquared.com
http://www.ShareSquared.com/blogs/BobMixon

In the meantime I have a couple of additional questions. When I am
specifying the user name (CN), is it the user name or account name?

The CN (common name) is really the *object* name of the AD object -
which as Joe points out really doesn't necessarily have anything to do
with your user name (first and last name), nor his (or her) account
name (as in Win NT account, "domain\user").

Confusing? Maybe - just think of it that way - you could leave you AD
object alone (it's CN), while still changing first name, last name,
account name, and a plethora of other names, too - but your OBJECT
name is still the same.

Marc



.

Relevant Pages

  • Re: Active Directory
    ... Joe Kaplan-MS MVP Directory Services Programming ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ... is it the user name or account name? ... object alone, while still changing first name, last name, ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Active Directory
    ... is it the user name or account name? ... The CN (common name) is really the *object* name of the AD object - ... object alone, while still changing first name, last name, ... account name, and a plethora of other names, too - but your OBJECT ...
    (microsoft.public.dotnet.framework.aspnet.security)