PDC-Member server active directory not syncing

We have Two domain controllers.One is PDC and second one member server.last night we restarted PDC. After restart , all servers are giving access is denied when remotely accessible by any user. now we have run gpupdate command through local administrator login into the servers. Now users can login.

But the big issue is what, that what we changes in PDC , not replicate with master server.I m not sure that this is a BDC or master server. Concept is not so cleared.

Now just make sure , i ran ntdsutil command on master server. There are some roles found.But on PDC , it is saying access is denied after ran this command.

Note: Now i facing user's password reset, computer trust relationship issues. So i removed and reinsert those computers in domain again.Problem solved.

But still i need ur help experts.
syinfraSenior Deputy ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

syinfraSenior Deputy ManagerAuthor Commented:
Just to add.When i ran repadmin command on BDC.Below are the output.

C:\Documents and Settings\sezadmin>repadmin /showrepl

repadmin running command /showrepl against server localhost

Default-First-Site-Name\ITL586V2
DC Options: IS_GC
Site Options: (none)
DC object GUID: 9fc9317c-660b-40d7-840e-cd9c00d9187e
DC invocationID: 163eee0e-caec-480c-a574-a28e03c5a47a

==== INBOUND NEIGHBORS ======================================

DC=Infraseepz,DC=lan
    Default-First-Site-Name\SEZITL003V12 via RPC
        DC object GUID: 155eb428-6a23-4f18-9623-afca498fe39c
        Last attempt @ 2013-09-12 18:26:11 failed, result 5 (0x5):
            Access is denied.
        11 consecutive failure(s).
        Last success @ 2013-09-12 13:26:35.

CN=Configuration,DC=Infraseepz,DC=lan
    Default-First-Site-Name\SEZITL003V12 via RPC
        DC object GUID: 155eb428-6a23-4f18-9623-afca498fe39c
        Last attempt @ 2013-09-12 18:26:11 failed, result 5 (0x5):
            Access is denied.
        8 consecutive failure(s).
        Last success @ 2013-09-12 13:26:35.

CN=Schema,CN=Configuration,DC=Infraseepz,DC=lan
    Default-First-Site-Name\SEZITL003V12 via RPC
        DC object GUID: 155eb428-6a23-4f18-9623-afca498fe39c
        Last attempt @ 2013-09-12 18:26:12 failed, result 5 (0x5):
            Access is denied.
        8 consecutive failure(s).
        Last success @ 2013-09-12 13:26:35.

Source: Default-First-Site-Name\SEZLILAC
******* 6 CONSECUTIVE FAILURES since 2013-09-12 17:31:13
Last error: 8524 (0x214c):
            The DSA operation is unable to proceed because of a DNS lookup failu
re.

Naming Context: DC=DomainDnsZones,DC=Infraseepz,DC=lan
Source: Default-First-Site-Name\SEZLILAC
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: CN=Schema,CN=Configuration,DC=Infraseepz,DC=lan
Source: Default-First-Site-Name\SEZLILAC
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=ForestDnsZones,DC=Infraseepz,DC=lan
Source: Default-First-Site-Name\SEZLILAC
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: CN=Configuration,DC=Infraseepz,DC=lan
Source: Default-First-Site-Name\SEZLILAC
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=Infraseepz,DC=lan
Source: Default-First-Site-Name\SEZLILAC
******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: Default-First-Site-Name\SEZITL003V12
******* 11 CONSECUTIVE FAILURES since 2013-09-12 13:26:35
Last error: 5 (0x5):
            Access is denied.


C:\Documents and Settings\sezadmin>
0
Mike KlineCommented:
What eventIDs are you seeing in your logs?  Was anything changed or was this just a reboot last night?

I'm off to work but going to leave you  a few KBs to look at until I can get back

http://support.microsoft.com/kb/2021446  > for the access denied issue

http://support.microsoft.com/kb/2002013 > AD Replication error 5, go through this one first it has a lot of things to look at.

Thanks

Mike
0
JaihuntCommented:
SEZITL003V12 is PDC ? What is the primary DNS configured for ITL586V2. Make sure it configured to any reachable DC or PDC and do ipconfig /registerdns.

The ITL586V2 only facing access denied error. check replication of other servers also

Repadmin /replsum

To reset the computer account follow the below link

http://sumoomicrosoft.blogspot.com/2012/07/reset-domain-controller-computer-account.html
0
syinfraSenior Deputy ManagerAuthor Commented:
Now somehow my team is successful to replicate both , PDC and member servers.But when i looking in event viewer, there are end no. of RPC server is not available errors. We googled and run below command.

repadmin /syncall

and the output is...

C:\Documents and Settings\Administrator.INFRASEEPZ>repadmin /syncall
CALLBACK MESSAGE: Error contacting server 603d80d0-f9e1-4295-95de-6033c733bd01._
msdcs.Infraseepz.lan (network error): 1722 (0x6ba):
    The RPC server is unavailable.
CALLBACK MESSAGE: The following replication is in progress:
    From: 9fc9317c-660b-40d7-840e-cd9c00d9187e._msdcs.Infraseepz.lan
    To  : 155eb428-6a23-4f18-9623-afca498fe39c._msdcs.Infraseepz.lan
CALLBACK MESSAGE: The following replication completed successfully:
    From: 9fc9317c-660b-40d7-840e-cd9c00d9187e._msdcs.Infraseepz.lan
    To  : 155eb428-6a23-4f18-9623-afca498fe39c._msdcs.Infraseepz.lan
CALLBACK MESSAGE: SyncAll Finished.

SyncAll reported the following errors:
Error contacting server 603d80d0-f9e1-4295-95de-6033c733bd01._msdcs.Infraseepz.l
an (network error): 1722 (0x6ba):
    The RPC server is unavailable.


Where as  603d80d0-f9e1-4295-95de-6033c733bd01._msdcs.Infraseepz.l
an this server is our very old server. This server was already crashed and now not on our network, We have searched , there are lots of entries in DNS. So we removed it and did clear cache and restart both servers. But no luck. Same above error.

Plz help with this.
0
JaihuntCommented:
Perform Meta data cleanup for the OLD server. If its 2008 server search its computer object exist and delete

http://www.petri.co.il/delete_failed_dcs_from_ad.htm

http://technet.microsoft.com/en-us/library/cc816907%28v=ws.10%29.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.