What to do when the Domain Controller Can’t find its domain!

PROBLEM:

Users unable to login to the domain – DCs not replicating

RESOLUTION:

=> Set the RPC Locator service to Automatic and started on the PDC.
=> Still DCdiag gave errors of 1355.
=> Ran dcdiag on both PDC and BDC – both showed problems with sysvol and netlogon shares
=> Checked and found that both servers did not have sysvol and netlogon shared
=> Found that the SYSVOL was shared as SYSVOLa – unshared it as it looked like manually shared.
=> Checked the PDC server and found that the Policies and Scripts were under the NTFRS-PRE-Existing folder
=> Stopped FRS Service on the BDC and PDC servers
=> Backed the policies and scripts from ntfrs-pre-existing folders to a folder on the desktop on PDC
=> Copied it on to the SYSVOL\sysvol folder
=> Started the FRS Service only on PDC
=> The sysvol and netlogon shares did not get created.
=> Stopped FRS Service again on PDC
=> On registry modified the following :
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
Burflags value to d4
=> Started the FRS service on PDC
=> Got Event id : 13516 NTFRS on the PDC File replication service event log
=> On the BDC modified the registry :
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
Burflags value to d2
=> Started FRS Service on BDC
=> Got Event id : 13516 NTFRS on the BDC File Replication service event log
=> Checked replication using repadmin /syncall – looks fine on both servers
=> Ran dcdiag /q on BDC and got no errors
=> Ran dcdiag /q on PDC and got one warning of 13508 and 13509 being reported on the eventlogs
=> Restarted FRS service on the PDC and reran dcdiag /q – got no errors now
=> All looks fine

I researched the Event ID received from the following portion of a dcdiag on PDC: Continue reading »

Shofkom’s World Grand Opening!

Welcome to the grand opening of Shofkom’s world of Information Technology!  I put this site together for the following reasons;

  1. A reference and knowledge base for Information Technology FAQ’s, specifically for those of us in a system administrator, network engineer, or project manager role.  Most of what you will find in this blog will relate to actual real world experiences that I have encountered while working in I.T. for the last 15 years.
  2. A showcase for my personal work ethic, and ways to improve your well being, both mentally and physically, in the roles mentioned above.
  3. A landing place for potential employers, head hunters, and I.T recruiters to review my accomplishments and contact me about potential opportunities in the Information Technology field.
  4. A general information reference point for fellow I.T. workers, and like minded individuals.

It is my goal to make this site both interesting and imformative, so take a look around and feel free to comment on what you like.  I hope you enjoy what I’ve put together, and remember, this is a work in progress!