We had the same problem once when I transferred the PDC FSMO. We
couldn't access Users and Computers, Group Policy snap-in, etc. When I
switched it back to the original machine it worked again.
Have you done a FSMO transfer lately? Might try changing it back.
Also, check DNS....
> -----Original Message-----
> From: Alex Ring [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 19, 2001 11:29 AM
> To: NT System Admin Issues
> Subject: RE: W2K Editing Group Policy
>
>
> I have tried to access the policy in various ways ;
>
> on the FMSO using mmc, and then adding the group policy snap
> in - it fails with the error 'failed to find a domain
> controller - there may be a policy that prevents you from
> selecting another domain controller'
>
> i get the same message when trying to access via the Active
> Directory Users & Computers - Properties - Group Policy
>
> Havent got the adminpak installed on my client, can give it
> a try though.
>
> Both domain controllers & client can ping each other via dns
> hostname (netbios is disabled throughout our network), and
> DNS is not reporting any errors into the event log, nor via
> netdiag /test:dns /v
>
> File & Printer sharing is setup, and is working.
> Unfortunately, cant access the web to search for more info on
> techn et, as internal systems have shutdown web access until
> the Nimda issue is sorted out, so if anyone has any further
> suggestions...that would be great.
>
> Thanks
>
> Alex
>
>
>
> -----Original Message-----
> From: Clayton [mailto:[EMAIL PROTECTED]]
> Sent: 19 September 2001 19:46
> To: NT System Admin Issues
> Subject: RE: W2K Editing Group Policy
>
>
> Alex, a lot of problems I have had in 2000 stem from AD and
> DNS communications. How are you trying to access the Group
> Policy? Are you getting errors in your DNS Event Log? Have
> you installed the admin.msi pack located on the Server CD on
> your client? If so, can the workstation this has been
> installed on be used to administer the domain? Can both
> servers ping each other by computer name? Let me know...
>
> Clayton Doige
> IT Manager MCSE, MCP + I
> Gameday International N.V.
> Bound in a nutshell, King of infinite space...
>
> T: +5 999 736 0309 ext 4537
> C: +5 999 563 1845
> F: +5 999 733 1259
> E: [EMAIL PROTECTED]
>
>
> -----Original Message-----
> From: Alex Ring [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 19, 2001 12:35 PM
> To: NT System Admin Issues
> Subject: RE: W2K Editing Group Policy
>
> Sent this a couple of days ago, but no response as yet.
>
> has anyone got any idea's ? Im pulling my hair out here !!! I just
> cant
> access the group policy. Are there any backdoor ways ?? Or
> is there a way i can just reset, or delete the policy ???
>
> > -----Original Message-----
> > From: Alex Ring
> > Sent: 13 September 2001 01:18
> > To: NT System Admin Issues (E-mail)
> > Subject: W2K Editing Group Policy
> >
> > Hi Guys
> >
> > Pretty new to list, so apols if this one has come up before.
> >
> > Seem to be having problems accessing my domain group policy from
> either of
> > my W2k SP2 servers.
> >
> > Found Article ID: Q257435 on technet (below), and although this
> exactly
> > describes my problem, unfortunately, the suggestion is no
> good for me,
> as
> > file & printer sharing is configured. I have removed it and
> re-installed
> > it on both boxes also, just in case, but still no joy.
> >
> > Anyone come across this before ??
> >
> > Rgds
> >
> > Alex
> >
> > Error Message When Opening or Editing a Domain Group Policy
> Object The
> > information in this article applies to:
> > * Microsoft Windows 2000 Advanced Server
> > * Microsoft Windows 2000 Server
> > SYMPTOMS
> > When you attempt to open or edit a domain Group Policy
> Object (GPO) on
> a
> > computer running Windows 2000 Server, you may receive the following
> error
> > message:
> > The domain controller for Group Policy operations is not available.
> You
> > may cancel this operation for this session or retry using
> one of the
> > following domain controller choices: The one with the Operations
> > Master token for the PDC emulator The one used by the
> Active Directory
> > Snap-ins Use any available domain controller
> > If you choose any of these options, you may receive the following
> error
> > message:
> > Failed to find a domain controller. There may be a policy that
> prevents
> > you from selecting another domain controller.
> > CAUSE
> > This behavior can occur if File and Printer Sharing for Microsoft
> Networks
> > is not enabled on the domain controller.
> > RESOLUTION
> > To resolve this behavior, enable File and Printer Sharing using the
> > following steps:
> > Click Start , point to Settings , click Control Panel , and
> then click
> > Select Network and Dial-up Connections .
> > Right-click Local Area Connection , and then click Properties .
> > Click File and Printer Sharing for Microsoft Networks , and
> then click
> OK
> > .
> > NOTE : If File and Printer Sharing for Microsoft Networks is not
> listed,
> > click Install , and then click Service . Click Add , and then click
> File
> > and Printer Sharing for Microsoft Networks .
> >
>
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
