S%&T Where's my AD Gone!?

[Tezdread]

My signature couldn't be more true!!

My last posts were about getting my DNS sorted, which I've pretty much done but it looks like it's at the cost of my AD??

After rebooting I checked the Event viewer and noticed this:

Event ID: 1126 "Unable to establish connection with global catalog."

I then found this post "

http://www.experts-exchange.com/Operating_Systems/Q_20599887.html"

and looked at the accepted answer which goes on to say that in order to promote a PDC to a GCS I will need to go into AD sites & Services.

When I tried I got this error:Naming information cannont be located because:
The specified doomain either does not exist or could not be contacted.

I get the above error when I try to access 'computers & users' and 'Domains & Trusts' as well...

Netdiag now reports these errors:

DC discovery test. . . . . . . . . : Failed
[FATAL] Cannot find DC in domain 'DREADZONE'. [ERROR_NO_SUCH_DOMAIN]

DC list test . . . . . . . . . . . : Failed
'DREADZONE': Cannot find DC to get DC list from [test skipped].

Trust relationship test. . . . . . : Skipped

Kerberos test. . . . . . . . . . . : Skipped
'DREADZONE': Cannot find DC to get DC list from [test skipped].

LDAP test. . . . . . . . . . . . . : Failed
Cannot find DC to run LDAP tests on. The error occurred was: The specified domain either does not exist or could not be contacted.

And these errors in DCDiag:
Starting test: Advertising
Fatal ErrorsGetDcName (ABSOSERVER) call failed, error 1355
The Locator could not find the server.
......................... ABSOSERVER failed test Advertising

Starting test: Services
NETLOGON Service is stopped on [ABSOSERVER]
......................... ABSOSERVER failed test Starting test: kccevent
An Error Event occured. EventID: 0xC0000466
Time Generated: 11/20/2004 16:33:40
Event String: Unable to establish connection with global

......................... ABSOSERVER failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x0000085A
Time Generated: 11/20/2004 16:18:37
Event String: The Workstation service has not been started.
An Error Event occured. EventID: 0xC0001B70
Time Generated: 11/20/2004 16:18:37
Event String: The Net Logon service terminated with

An Error Event occured. EventID: 0xC0000021
Time Generated: 11/20/2004 16:19:35
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC00009C4
Time Generated: 11/20/2004 16:21:01
Event String: The server failed to start due to an

An Error Event occured. EventID: 0xC00001E1
Time Generated: 11/20/2004 16:21:01
Event String: Site Server LDAP Service cannot initialize the

An Error Event occured. EventID: 0xC000000E
Time Generated: 11/20/2004 16:21:11
Event String: The HTTP Filter DLL

......................... ABSOSERVER failed test systemlog

Running enterprise tests on : DreadZone.local
Starting test: Intersite
......................... DreadZone.local 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(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is 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 1355
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.
......................... DreadZone.local failed test FsmoCheck


How can I get my AD back?

Tezdread
"With every solution comes a new problem"

 

[markdmac]

Wow, what was the last thing that you did to your system before AD went nuts? Can you undo that?

Download a copy of the resource kit utility NETDOM and try running this:
NETDOM QUERY FSMO
and see if it can find a FSMO role holder. If it can't find any which I suspect is the case, try seizing the FSMO roles.

http://support.microsoft.com/?id=255504

Let me know what you find from doing this.


I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[Tezdread]

Previous problems : thread96-951442

I setup DNS on the Standard Primary instead of AD Integrated... not sure if it was that but changing it back to AD Integrated doesn't do anything now.
I also Uninstalled ColdFusion and ran a reg cleaner
------------------------------------------------------------------------------------------------------------------------

netdom results:

The specified domain either does not exist or could not be contacted.
The command failed to complete successfully.

When I typed dcpromo - I get this message

This domain controller is a Global Catalog server. Global Catalogs are used to process user logons. You should make sure other Global Catalogs are accessible to users of this domain before removing Active Directory from this computer.

After that I tried removing AD, specified password etc, and got this error:

The operation failed because:

Failed finding a suitable domain controller for the domain DreadZone.local

"The specified domain either does not exist or could not be contacted."



Tezdread
"With every solution comes a new problem"

 

[markdmac]

How many DCs do you have in your domain?

If you really want to force AD to be removed you can do so by running:

DCPROMO /FORCEREMOVAL

Note, that if you do this you will loose all AD information such as users and mailboxes and Group Policies you may have created. This is an extreme measure. You might be better off spending the $300 for a support call to Microsoft Premier Support.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[GlenJohnson]

• Re-configured them, but this time instead of AD integrated I used the Standard primary so I'm thinking it was this and that there's possibly something in the AD config that was causing the problems?

You didn't re-install ad, you just made a plain ol server. Run dcpromo again and install active directory. Good luck.

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin/Central Florida feel free to join the Tek-Tips in Chicago, Illinois Forum.
TTinChicago
Johnson Computers

 

[Tezdread]

both of those options are pretty extream Mark and if I had $300 to call MS I'd have made sure it was all backed up ;-)

I only have this server and a handful of users/computers so doing a forceremoval wouldn't be so bad...

I'm still unsure on how to reinstall AD though? Can I do it in it's current state Glen?

Tezdread
"With every solution comes a new problem"

 

[Tezdread]

ok I've jumped in currently removing AD using the forceremoval (thanks mark)

I'll let you know how it goes...

Tezdread
"With every solution comes a new problem"

 

[markdmac]

Once you have done the Forceremoval you will be able to run DCPROMO again and start over with the AD Installation. Just choose New Forest/New Domain.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[Tezdread]

Oh dear...not sure why but everytime I tried to uninstall AD I kept getting a message saying it couldn't remove NETLOGON because there wasn't enough storage space??

So I increased the partition size, which seemed to go ok as there were no errors but it just hung on 'preparing network connections' for over an hour each time I rebooted.

I could get into Safe Mode but couldn't get it working... just running through a fresh install now.

Tezdread
"With every solution comes a new problem"

 

[Tezdread]

what did i do to deserve this.........

Things haven't been going to well and I'm on to my second installation of the whole thing. I got it working ok and I thnk I might have traced the problem back to a event log (5781)

http://support.microsoft.com/default.aspx?scid=kb;en-us;259277&sd=tech

I followed the instructions provided and it's the only thing I can think of.

I'm back at the first login, so will configure everything after a backup and see if it is that or not.



Tezdread
"With every solution comes a new problem"

 

[Tezdread]

yep that's the problem....

After a few config changes I rebooted and didn't have any errors, just a few warnings so I followed the instructions in the MS article (after backing everything up) and when I rebooted again it took 15 mins to get logged in and I had several errors and I couldn't access AD again!

my new signature should be

back up, Back Up, BACK UP! would have saved myself a lot of time...

Tezdread
"With every solution comes a new problem"