Re: Windows 2003 Active Directory will not start after power outage.

Tech-Archive recommends: Speed Up your PC by fixing your registry

Here is the output from the commands you pointed out.

C:\Documents and Settings\Administrator.IFM1>netdom query fsmo
Schema owner fileserver.ifm1.com
Domain role owner fileserver.ifm1.com
PDC role fileserver.ifm1.com
RID pool manager fileserver.ifm1.com
Infrastructure owner fileserver.ifm1.com
The command completed successfully.

Here is the output of dnslint:
dnslint /ad /s 10.1.1.2
Root of Active Directory Forest:
ifm1.com
Active Directory Forest Replication GUIDs Found:
DC: SERVER01
GUID: 3f5adc65-d2fb-4ba6-af41-83b3b62e175e
DC: FILESERVER
GUID: a891f126-e4da-42a4-a254-c841c8a55f09
More stuff, no errors, shows queries are working on both servers..blah
blah blah.
Both servers have a copy of the global catalog.

Thanks for the reply Paul. Last night in the wee hours, I found a KB
that was somewhat related to the problems I had and it fixed it (AD
started). All I did was set the BurFlags for NtFrs to D4 on the 5 role
PDC and D2 on the other PDC. I restarted the NtFrs service on both
PDC's and walah. SYSVOL is shared and authentications are working,
ldap queries are working...etc. One problem. I seem to have lost all
of my group policies. I am going through backups now to see if I have
any recent sets. Although, Id rather just start with fresh policies.
If I can delete the links to the old ones.

I am getting this error in Application (Userenv) in the event log on my
workstations.

---------------------------------------------------------------------------------------------------------------------------

Windows cannot access the file gpt.ini for GPO
CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=ifm1,DC=com.
The file must be present at the location
<\\ifm1.com\sysvol\ifm1.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.
(The system cannot find the path specified. ). Group Policy processing
aborted.

----------------------------------------------------------------------------------------------------------------------------
Here is what I got in the event log after making the registry changes
that fixed AD.
----------------------------------------------------------------------------------------------------------------------------
The File Replication Service is no longer preventing the computer
FILESERVER from becoming a domain controller. The system volume has
been successfully initialized and the Netlogon service has been
notified that the system volume is now ready to be shared as SYSVOL.
:-)
---------------------------------------------------------------------------------------------------------------------------

Now I have to figure out where my GPO's went and put them back into
SYSVOL? Would it be easier to just start with new GPO's and remove the
old links? Anyone wanna take a shot at guessing where my GPO's went?



Paul Bergson [MVP-DS] wrote:
My first thought would be you have DNS issues.
From one of your's dc try running dnslint /ad /s "ip address of
your dc"

Also run netdom query fsmo



Check the Sites and Services and verify one of the servers is a GC.
http://support.microsoft.com/default.aspx?scid=kb;en-us;313994

Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error 135
5
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... ifm1.com failed test FsmoCheck

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Rodney King" <rod@xxxxxxxx> wrote in message
news:gK6dnc26_NkMl8TYnZ2dnUVZ_tudnZ2d@xxxxxxxxxxxxxxxx
Here are the results from dcdiag:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.IFM1>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\FILESERVER
Starting test: Connectivity
......................... FILESERVER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\FILESERVER
Starting test: Replications
......................... FILESERVER passed test Replications
Starting test: NCSecDesc
......................... FILESERVER passed test NCSecDesc
Starting test: NetLogons
......................... FILESERVER passed test NetLogons
Starting test: Advertising
Fatal Error:DsGetDcName (FILESERVER) call failed, error 1355
The Locator could not find the server.
......................... FILESERVER failed test Advertising
Starting test: KnowsOfRoleHolders
......................... FILESERVER passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... FILESERVER passed test RidManager
Starting test: MachineAccount
......................... FILESERVER passed test MachineAccount
Starting test: Services
......................... FILESERVER passed test Services
Starting test: ObjectsReplicated
......................... FILESERVER passed test
ObjectsReplicated
Starting test: frssysvol
......................... FILESERVER passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after
the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
......................... FILESERVER failed test frsevent
Starting test: kccevent
......................... FILESERVER passed test kccevent
Starting test: systemlog
......................... FILESERVER passed test systemlog
Starting test: VerifyReferences
......................... FILESERVER passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test
CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test
CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : ifm1
Starting test: CrossRefValidation
......................... ifm1 passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ifm1 passed test CheckSDRefDom

Running enterprise tests on : ifm1.com
Starting test: Intersite
......................... ifm1.com passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error 135
5
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... ifm1.com failed test FsmoCheck

.

Relevant Pages

  • Re: RDP can not logon error
    ... server, go to Terminal Services Configuration in the Administrative Tools, ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... Starting test: CheckSDRefDom ...
    (microsoft.public.windows.server.general)
  • Re: RDP can not logon error
    ... local administrator, try to do a ping or tracert to the DC's. ... I'm trying to connect to a remote server using RDP and receive ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: RDP can not logon error
    ... server, go to Terminal Services Configuration in the Administrative Tools, ... No network provider accepted the given network path.. ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • RDP can not logon error
    ... I'm trying to connect to a remote server using RDP and receive the ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... Starting test: CheckSDRefDom ...
    (microsoft.public.windows.server.general)
  • RE: 2003 DNS problems on VMware
    ... I think is DNS? ... From vmxp1 I can ping the server by IP or DNS ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.active_directory)