PDC & BDC Sync Problems

I have recently promoted my BDC to a PDC. Since then I'm unable to run User Manager from the BDC. I noticed many errors in the event logs as well. Clearly something's wrong with the domain synchronization between the BDC & PDC. I am running Windows NT Server 4.0 service pack 6a on both.

PDC name = W2KDC01
BDC name = NFSERVER

PDC Event Log

3/3/03     3:15:40 PM     NETLOGON     Information
None     5713     N/A     W2KDC01     The full synchronization request from the server NFSERVER completed successfully. 17 object(s) has(have) been returned to the caller.
3/3/03     3:14:40 PM     NETLOGON     Information
None     5713     N/A     W2KDC01     The full synchronization request from the server NFSERVER completed successfully. 103 object(s) has(have) been returned to the caller.
3/3/03     3:08:10 PM     NETLOGON     Information
None     5713     N/A     W2KDC01     The full synchronization request from the server NFSERVER completed successfully. 11 object(s) has(have) been returned to the caller.

These repeat every couple of minutes!

BDC Event Log

3/3/03     3:07:11 PM     NETLOGON     Warning     None
5718     N/A     NFSERVER     The full synchronization replication of the LSA database from the primary domain controller  failed with the following error: The remote procedure call failed.  
3/3/03     3:05:41 PM     NETLOGON     Warning     None
5718     N/A     NFSERVER     The full synchronization replication of the BUILTIN database from the primary domain controller  failed with the following error: The remote procedure call failed.  
3/3/03     3:04:11 PM     NETLOGON     Warning     None
5718     N/A     NFSERVER     The full synchronization replication of the SAM database from the primary domain controller  failed with the following error: The remote procedure call failed.

These repeat every couple of minutes!

I ran "NLTEST /PDC_Repl" from the PDC, status read successful.

I ran "NLTEST /Server:W2KDC01 /PDC_Repl" from the BDC, status came back:

I_NetLogonControl failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE

Any suggestions would be greatly appreciated!

Ed
ruokonenAsked:
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.

heskyttbergCommented:
Hi!

Make sure the RPC locator and RPC service is running on both PDC and BDC

Regards
/Hans - Erik Skyttberg
0
ProgSysAdminCommented:
Did you demote the former PDC to a BDC first?  You need to do this before you should promote a BDC to PDC.
0
ruokonenAuthor Commented:
Thanks for your quick responses......

Believe it or not, it was a network error. I swapped out the old 10mb ethernet NIC and replaced it with a 3Com 100mb NIC. Everything is syncing up fine! May have been a driver issue or just a board on the brink.

Thanks again!

Ed
0
moduloCommented:
PAQed, with points refunded (50)

modulo
Community Support Moderator
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
Windows OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.