Group policy default policy cannot be edited because network name not found

-

hey everyone,

i have been having issues on , off domain. pdc crashed (the domain controller). started old server , made domain controller , forced roles over. repaired pdc , elevated back. although appeared work found cannot rid of other dc because pdc can no longer contact domain things group policy or else. start secondary , domain magically reachable. although while secondary down can ping domain , replies ip of pdc appears pdc has no control on anything. questions following.

1. gpos created before crash no longer work. rebuilt sysvol , default problem can't edit default domain policy. don't believe having replication problems new repairing domains setting them , maintaining them of education came from. 

2. if pdc gpo management console can't access gpos can secondary not have installed?

3. why domain unreachable if no dcs online when shutdown secondary.

thanks in advance , try edit dc diag log right there on fails want narrow of out guys concentrate on hardest problems.

matt

edit one:

i installed gpmc on secondary server 2003 , same error happening. missing feel idiot isn't coming me. sysvol folder on both dcs domain there there no guid folders below that. missing policies not there? going delete default , see can recreate.

thanks

matt

ok here more information. 

i created new gpo , appeared ok. can no longer access gpo edit it. saying network path not found on new 1 , old ones. going on here. attached find dc diag  report.

irectory server diagnosis

performing initial setup:
   trying find home server...
   home server = server1
   * identified ad forest.
   done gathering initial info.

doing initial required tests

   testing server: default-first-site-name\server1
      starting test: connectivity
         ......................... server1 passed test connectivity

doing primary tests

   testing server: default-first-site-name\server1
      starting test: advertising
         ......................... server1 passed test advertising
      starting test: frsevent
         there warning or error events within last 24 hours after the
         sysvol has been shared.  failing sysvol replication problems may cause
         group policy problems.
         ......................... server1 passed test frsevent
      starting test: dfsrevent
         ......................... server1 passed test dfsrevent
      starting test: sysvolcheck
         ......................... server1 passed test sysvolcheck
      starting test: kccevent
         ......................... server1 passed test kccevent
      starting test: knowsofroleholders
         ......................... server1 passed test knowsofroleholders
      starting test: machineaccount
         ......................... server1 passed test machineaccount
      starting test: ncsecdesc
         ......................... server1 passed test ncsecdesc
      starting test: netlogons
         unable connect netlogon share! (\\server1\netlogon)
         [server1] net use or lsapolicy operation failed error 67,
         the network name cannot found..
         ......................... server1 failed test netlogons
      starting test: objectsreplicated
         ......................... server1 passed test objectsreplicated
      starting test: replications
         [dellserver] dsbindwithspnex() failed error 1722,
         the rpc server unavailable..
         ......................... server1 failed test replications
      starting test: ridmanager
         ......................... server1 passed test ridmanager
      starting test: services
         ......................... server1 passed test services
      starting test: systemlog
         an error event occurred.  eventid: 0x00000406
            time generated: 02/23/2016   17:58:54
            event string:
            processing of group policy failed. windows attempted retrieve
 new group policy settings user or computer. in details tab fo
r error code , description. windows automatically retry operation at
 the next refresh cycle. computers joined domain must have proper name re
solution , network connectivity domain controller discovery of new gr
oup policy objects , settings. event logged when group policy su
ccessful.
         an error event occurred.  eventid: 0x00000406
            time generated: 02/23/2016   18:03:55
            event string:
            processing of group policy failed. windows attempted retrieve
 new group policy settings user or computer. in details tab fo
r error code , description. windows automatically retry operation at
 the next refresh cycle. computers joined domain must have proper name re
solution , network connectivity domain controller discovery of new gr
oup policy objects , settings. event logged when group policy su
ccessful.
         an error event occurred.  eventid: 0x00000406
            time generated: 02/23/2016   18:08:56
            event string:
            processing of group policy failed. windows attempted retrieve
 new group policy settings user or computer. in details tab fo
r error code , description. windows automatically retry operation at
 the next refresh cycle. computers joined domain must have proper name re
solution , network connectivity domain controller discovery of new gr
oup policy objects , settings. event logged when group policy su
ccessful.
         an error event occurred.  eventid: 0x00000406
            time generated: 02/23/2016   18:13:56
            event string:
            processing of group policy failed. windows attempted retrieve
 new group policy settings user or computer. in details tab fo
r error code , description. windows automatically retry operation at
 the next refresh cycle. computers joined domain must have proper name re
solution , network connectivity domain controller discovery of new gr
oup policy objects , settings. event logged when group policy su
ccessful.
         an error event occurred.  eventid: 0x00000406
            time generated: 02/23/2016   18:18:57
            event string:
            processing of group policy failed. windows attempted retrieve
 new group policy settings user or computer. in details tab fo
r error code , description. windows automatically retry operation at
 the next refresh cycle. computers joined domain must have proper name re
solution , network connectivity domain controller discovery of new gr
oup policy objects , settings. event logged when group policy su
ccessful.
         a warning event occurred.  eventid: 0x000003f6
            time generated: 02/23/2016   18:21:51
            event string:
            name resolution name eitel.local timed out after none of the
 configured dns servers responded.
         an error event occurred.  eventid: 0x00000406
            time generated: 02/23/2016   18:23:57
            event string:
            processing of group policy failed. windows attempted retrieve
 new group policy settings user or computer. in details tab fo
r error code , description. windows automatically retry operation at
 the next refresh cycle. computers joined domain must have proper name re
solution , network connectivity domain controller discovery of new gr
oup policy objects , settings. event logged when group policy su
ccessful.
         an error event occurred.  eventid: 0x0000164a
            time generated: 02/23/2016   18:26:30
            event string:
            netlogon service not create server share c:\windows\sysvol
\sysvol\eitel.local\scripts.  the following error occurred:
         an error event occurred.  eventid: 0x00000422
            time generated: 02/23/2016   18:28:58
            event string:
            processing of group policy failed. windows attempted read the
 file \\eitel.local\sysvol\eitel.local\policies\{6ac1786c-016f-11d2-945f-00c04fb
984f9}\gpt.ini domain controller , not successful. group policy set
tings may not applied until event resolved. issue may transie
nt , caused 1 or more of following:
         an error event occurred.  eventid: 0x00000422
            time generated: 02/23/2016   18:33:58
            event string:
            processing of group policy failed. windows attempted read the
 file \\eitel.local\sysvol\eitel.local\policies\{6ac1786c-016f-11d2-945f-00c04fb
984f9}\gpt.ini domain controller , not successful. group policy set
tings may not applied until event resolved. issue may transie
nt , caused 1 or more of following:
         an error event occurred.  eventid: 0x00000422
            time generated: 02/23/2016   18:38:59
            event string:
            processing of group policy failed. windows attempted read the
 file \\eitel.local\sysvol\eitel.local\policies\{6ac1786c-016f-11d2-945f-00c04fb
984f9}\gpt.ini domain controller , not successful. group policy set
tings may not applied until event resolved. issue may transie
nt , caused 1 or more of following:
         an error event occurred.  eventid: 0x00000422
            time generated: 02/23/2016   18:43:59
            event string:
            processing of group policy failed. windows attempted read the
 file \\eitel.local\sysvol\eitel.local\policies\{6ac1786c-016f-11d2-945f-00c04fb
984f9}\gpt.ini domain controller , not successful. group policy set
tings may not applied until event resolved. issue may transie
nt , caused 1 or more of following:
         an error event occurred.  eventid: 0x00000422
            time generated: 02/23/2016   18:49:00
            event string:
            processing of group policy failed. windows attempted read the
 file \\eitel.local\sysvol\eitel.local\policies\{6ac1786c-016f-11d2-945f-00c04fb
984f9}\gpt.ini domain controller , not successful. group policy set
tings may not applied until event resolved. issue may transie
nt , caused 1 or more of following:
         an error event occurred.  eventid: 0x00000422
            time generated: 02/23/2016   18:54:00
            event string:
            processing of group policy failed. windows attempted read the
 file \\eitel.local\sysvol\eitel.local\policies\{6ac1786c-016f-11d2-945f-00c04fb
984f9}\gpt.ini domain controller , not successful. group policy set
tings may not applied until event resolved. issue may transie
nt , caused 1 or more of following:
         ......................... server1 failed test systemlog
      starting test: verifyreferences
         ......................... server1 passed test verifyreferences


   running partition tests on : forestdnszones
      starting test: checksdrefdom
         ......................... forestdnszones passed test checksdrefdom
      starting test: crossrefvalidation
         ......................... forestdnszones passed test
         crossrefvalidation

   running partition tests on : domaindnszones
      starting test: checksdrefdom
         ......................... domaindnszones passed test checksdrefdom
      starting test: crossrefvalidation
         ......................... domaindnszones passed test
         crossrefvalidation

   running partition tests on : schema
      starting test: checksdrefdom
         ......................... schema passed test checksdrefdom
      starting test: crossrefvalidation
         ......................... schema passed test crossrefvalidation

   running partition tests on : configuration
      starting test: checksdrefdom
         ......................... configuration passed test checksdrefdom
      starting test: crossrefvalidation
         ......................... configuration passed test crossrefvalidation

   running partition tests on : eitel
      starting test: checksdrefdom
         ......................... eitel passed test checksdrefdom
      starting test: crossrefvalidation
         ......................... eitel passed test crossrefvalidation

   running enterprise tests on : eitel.local
      starting test: locatorcheck
         ......................... eitel.local passed test locatorcheck
      starting test: intersite
         ......................... eitel.local passed test intersite

any here incredibly helpful

thanks again 

matt

at heart, active directory domain controllers each host database synchronize 1 another.  there key factors maintain state of replication, , things turn bad when servers crash , old ones brought life (as mentioned did).  there tools available repair these sorts of things, notably ntdsutil, involves taking dc offline it.  involving marking authoritative directory service instance, first, after noticing errors in dcdiag output, let's idea of things stand right @ more macro level.   send output of following each dc can compare thinks has what.  output indicate 1 focus repair efforts on.

netdom query fsmo

repadmin /replsum /bysrc /bydest

ipconfig /all

best regards, todd heron | active directory consultant



Windows Server  >  Group Policy



Comments

Post a Comment

Popular posts from this blog

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authenticati...
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema ...
Read more

Failed to setup initiator portal. Error status is given in the dump data.

-
hi team, server configured boot san  after booting  facing issue windows server 2008 r2 system logs continuously generating iscsi port error event id 5 failed setup initiator portal. error status given in dump data. eventdata \device\raidport1 000004000100000000000000050000c0000000000000000000000000000000000000000000000000070200c0 binary data: in words 0000: 00040000 00000001 00000000 c0000005 0008: 00000000 00000000 00000000 00000000 0010: 00000000 00000000 c0000207 in bytes 0000: 00 00 04 00 01 00 00 00 ........ 0008: 00 00 00 00 05 00 00 c0 .......À 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 07 02 00 c0 ...À hi, please read through article below troubleshoot issue: error event id 5 logged in system log on computer uses iscsi software initiator connect iscsi target device http://suppo...
Read more