Re: Security Policy Is not opening.

From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 04/29/05 

Date: Fri, 29 Apr 2005 13:35:49 -0500

Well good to hear that your dns seems to working correctly. See if anything
unusual shows in the application or system logs in Event Viewer and try
accessing the sysvol share as I explained before to see first if you can
access it and then if you can try to navigate to those policies via domain
name\policies\31B2F....\machine\Microsoft\Windows NT\SecEdit where you
should see and be able to open the GptTmpl.inf file there. The policy
starting 31B2F.... is the default domain Group Policy. Also try running the
support tool gpotool to see if it shows at least two Group Policies and if
any problems are reported as far as version numbers. Another thing to check
is to Use Active Directory Users and Computers. Then find your domain, right
click and select properties/Group Policy where you should see default domain
policy. For it select properties/security to make sure that domain admins
have necessary permissions which need to be at least read and write to edit
the Group Policy. Verify that domain admins global group is a member of the
administrators group and that you are logged on as a member of the domain
admins group. --- Steve

"Varadarajam" <Varadarajam@discussions.microsoft.com> wrote in message
news:B72B0975-D61E-4826-93EA-BBDECB3FFE11@microsoft.com...
> Hi Steven
>
> Thanx for your kind suggestion. But we tried Netdiag and Dcdiag tools. But
> we couldn't find any problems in it. We are not using ISP IP as DNS server
> address. What we are suspecting is might be some policies are applied on
> Administrator account. Pls kindly let me know is there any other solution
> to
> opening Security Policies like Domain Security Policy and Domain
> Controller
> Security Policy in Domain Controller or Additional Domain Controller.
> Waiting for your reply.
>
> Thanks and Regards
> Rajam
>
> "Steven L Umbach" wrote:
>
>> That could be a dns problem or a problem with the existence of the sysvol
>> share or permissions for it. From any domain computer you should be able
>> to
>> access the sysvol share by entering in the run box
>> \\domaincontrollername\sysvol. Run the support tools netdiag and dcdiag
>> on
>> the domain controller looking for pertinent problems and also check Event
>> Viewer for Event ID's than may detail a related problem. Support tools
>> are
>> on the install disk in the support/tools folder. See the link below on
>> dns
>> to make sure your dns is correctly configured for the domain and NEVER
>> list
>> an ISP dns server as a preferred dns server in tcp/ip properties of any
>> domain computer or computer you are trying to join to the domain. ---
>> Steve
>>
>> http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382
>>
>> "Varadarajam" <Varadarajam@discussions.microsoft.com> wrote in message
>> news:AF5B03FD-BFDF-4BCF-8150-8C514F1F88AE@microsoft.com...
>> > Hi
>> >
>> > I have Win2000 Domain Controller logged in as domain administrators.
>> >
>> > Problem is : I could not able to open Domain Security Policy or Domain
>> > Controller Security Policy. We would like to apply some policies. But
>> > Domain
>> > Default Policy Editor is not opening at all.
>> >
>> > Its showing a message like "you dont have appropriate permissions.
>> > Details : The System Cannot find path." That is the message i m
>> > getting
>> > whenever i tried to open Domain Security Policy and Domain Security
>> > Policy.
>> >
>> > Please help me in this.
>> >
>> > Thanks and Regards
>> > Rajam.
>> >
>>
>>
>>

Relevant Pages

  • Re: W2K Server / XP Pro Clients / Group Policy -- LOCK TASKBAR
    ... make your dns configuration is correct in that domain controllers point ... The policy you are trying to implement is a "user" configuration policy and therefore ... > machines connecting to a Windows 2000 Domain Controller. ...
    (microsoft.public.windows.server.active_directory)
  • Re: W2K Server / XP Pro Clients / Group Policy -- LOCK TASKBAR
    ... make your dns configuration is correct in that domain controllers point ... The policy you are trying to implement is a "user" configuration policy and therefore ... > machines connecting to a Windows 2000 Domain Controller. ...
    (microsoft.public.windows.server.security)
  • Re: W2K Server / XP Pro Clients / Group Policy -- LOCK TASKBAR
    ... make your dns configuration is correct in that domain controllers point ... The policy you are trying to implement is a "user" configuration policy and therefore ... > machines connecting to a Windows 2000 Domain Controller. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: W2K Server / XP Pro Clients / Group Policy -- LOCK TASKBAR
    ... make your dns configuration is correct in that domain controllers point ... The policy you are trying to implement is a "user" configuration policy and therefore ... > machines connecting to a Windows 2000 Domain Controller. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: W2K Server / XP Pro Clients / Group Policy -- LOCK TASKBAR
    ... make your dns configuration is correct in that domain controllers point ... The policy you are trying to implement is a "user" configuration policy and therefore ... > machines connecting to a Windows 2000 Domain Controller. ...
    (microsoft.public.windowsxp.setup_deployment)