Netlogon Errors

[TriggerVDS]

Hi there, when I started my new job I was getting these Netlogon errors and still am. The event ID is 5719, and the error message is:

No windows NT or Windows 2000 DC is available for Domain CRBS. The following error occured:
There are currently no logon servers to service the logon request.

The reason for this is because the CRBS DC was moved to another location before I started. I do I get rid of this error message.

 

[Aslamvs]

http://www.jsifaq.com/SUBJ/tip4600/rh4623.htm

Aslam

 

[Antony13]

I assume there is still a trust between the two domains? If you don't need this, just remove the trust and that should get rid of the errors. Otherwise, way we've got round this here is to put an lmhosts file on the DC with the address of the DC and domain name.

Cheers, Antony

 

[TriggerVDS]

How do I untrust the two domains, I went into Active Directory Domains and Trusts but it dosen't give me the option to remove the trust as the remove button is greyed out.

 

[Antony13]

Are you an administrator in this domain?

 

[TriggerVDS]

Yes, I am the Adminstrator of this domain.

 

[paulray]

Make sure your logged in as the admin for the domain and not the admin for the server. Seems simple, but alot of people do this without thinking.
Paul

 

[TriggerVDS]

I am logged in as the Administrator for the Domain.

 

[TriggerVDS]

Is there anyway of going into the registry to break the trust?

 

[Antony13]

Just had a look on our setup and the only trusts I can't remove because the Remove button is greyed out are trusts to domains in the same forest - is this the case for you? If so, you can't break those trusts with the tool as this is the way AD is designed.

What was the CRBS domain? Has it been removed or deleted without running the proper dcpromo tool to do a clean remove of it? If so, have a look at this MS document to clear up AD after this has happened:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;216498

and

http://support.microsoft.com/default.aspx?scid=kb;en-us;230306

If the above isn't the case, then I'm stumped as I can't find any more information on this.

Cheers, Antony

 

[TriggerVDS]

The two servers were in the same Forest before the CRBS server got moved to another location. The person before me obviously never removed it properly from the Domain. I used the links that you gave me thanks for that, however when I tried to delete the orphaned Domain I got an error 0x2162. I looked this up and it the information that I got was that there was still a Domain Controller Present which there is.

When I go into Site and Services for AD the CRBSSERV DC is still there. I tried to delete this but wasn't successful as the system said that the object couln't be deleted. Any other ideas would be appreciated. I tried deleting the server through the Metadata cleanup but I don't get a choice to select the server. Pretty Weird I know.

 

[Antony13]

Hmmm, hard to tell, but what I'm saying might be applicable! The metadata cleanup only deletes the connection objects i.e. if you go into Sites and Services, go into a server, you see NTDS settings - this is what the metadata cleanup tool gets rid of so the server will still appear in Sites and Services, but you should be able to delete it from here once these connection objects have been deleted.

Have you followed through all the steps in the document including using ADSI edit to remove the other bits of the server from the directory i.e. FRS etc.?

If you have, you could be a bit stuck and may need some serious AD consultant who knows AD, LDAP, ADSI, etc. like the back of his hand to come in and sort it out (I've had troubles before trying to clear up AD in our test lab after simulating lots of DCs going offline and it got very messy indeed so much so I had to delete everything and start again - fortunately mine was in the test lab, hence why I think you might need someone who knows all this stuff backwards).

Sorry I can't help more.

Antony

 

[TriggerVDS]

Hi there again just wanted to post a reply to say thanks, I managed to get it to work with the infromation provided on the article an how to remove data in AD after an unsuccessful Domain Controller demotion. I didn't read it properly the first time sorry. Anyway its all a new learning curve for me, and thanks again for you help.

 

[Antony13]

Excellent! No problem at all!

Cheers, Antony