• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Help with Small Network

M

Maverick07

Junior Member
Alright this company previously had two servers running, server 1 and server 2. Server 1, which I know 100% for sure was running DNS and was listed as a primary domain controller, crashed due to a hard drive failure. The drive was replaced for me and I reloaded Windows 2000 server on it.

Server 2 is running the active directory, DNS, and is a primary domain controller. As of right now, server 1 is only running as a file server since it is up and running. In my event viewer on Server 2, I'm receiving two errors several times a day.

5719 (No Windows NT or Windows 2000 Domain Controller is available for domain XXX. The following error occurred:
There are currently no logon servers available to service the logon request. )

and

5781 (Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.)

In the AD for Server 2, Server 1 is still listed as a primary domain controller, even though server 1 is only running as a file server. Should I remove this entry? What else needs to be removed and re-configured to end these errors?

Thanks,
Lance
 
Was server 2 a backup to server 1, and it's still looking for server 1 to sync up with? If not, it just sounds like the 2 servers' roles were reversed and server 2 doesn't "know" about it.
 
Couple terminology things here. In W2K, there is no such thing as a primary and backup domain controller. That is a WinNT holdover. What is in an AD W2K is a role known as a PDC emulator. The PDC emulator is one of 5 FSMO roles a DC holds in an AD domain.

Now, with that being said, it sounds like server 1 was the first DC in the domain so it held the FSMO roles. Server two was the second DC.

With the crash of the first DC, I suspect the FSMO roles were not transferred to the second server.

Below is a MS link on how to seize the FSMO roles and make the second DC the main guy.

MS Link

The second problem is DNS related to the loss of the first DC. You will need to look at DNS and remove a possible NS record for the first DC. Look at the link below to see if it is apprpriate.

DNS

Fair warning:

Seizing roles and changing DNS in an AD environment should be carefully planned out. MS has lots of help in its knowledge base.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top