On the machine where these misbehaviors are seen it
is likely that the machine's Tcp/Ip settings are set to
allow use of an incorrect DNS server. Only DNS
servers supporting the AD may be used.
--
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4) MCDBA
"Larry Sottile" <(E-Mail Removed)> wrote in message
news:605801c474d3$eb6ce400$(E-Mail Removed)...
> I'm having issues of inconsistency in using (after a
> successful install) the AdminPak for Windows 2003 Server,
> accessing a Win2003 SB Server. On some systems I can
> always Run the Domain Users Admin Tool. On other
> Identical (so I believe) system I can not. On the
> systems I can not I get the following message when it
> fails,
>
> Naming information cannot be located for the following
> reason: The server is not operational.
>
> If you are trying to connect to a domain controller
> running Windows 2000, verify that Windows 2000 Server
> Service Pack 3 or later is installed on the domain
> controller, or use the Windows 2000 administration tools.
> For more information about connecting to domain
> controllers running Windows 2000, see Help and Support.
>
> Additionally, when I try to Add an AD Group or User to a
> Local Group, I can not access the AD under
> the "Locations". Similarly when I try to set Local File
> System Security to Files & Directories, I can not select
> any AD Groups or users. On systems where I can access
> the AD Users Tool, I can set the Local FS Rights for AD
> Groups and Users.
>
> HELP! I've got some Apps where I need AD Users / Groups
> to have Access to Local Files & Folders on a workstation.
> 7-28-2004
>
|