Question : How to resolve W2k server DC problem

Background:
3 computers running Windows 2000 server
2 computers are PCs running as Domain Controllers
1 computer is a server acting as a file server
Barracuda Web Filter is installed on LAN

On Monday, the primary DC's hard drive crashed. It was turned off. The second DC and the file server were rebooted. Users were able to log in to network but are having intermittent rights issues. Such as:

When they try to access a previously accessible website, the Barracuda web filter is bringing up a log in screen for authorization. (usually no log in screen is displayed as they are given access thru the Barracuda). When they enter their credentials, they don't work. The only log in credentials that work are mine. I am a Admin equivalent and am not a part of any of the groups that are used by the rest of the users. My account was entered into the Barracuda as a single account. The others get their access from being a part of an AD LDAP group. When I try to add that group, Barracuda brings back an error message stating that it cannot access the LDAP server.

2nd issue, they have a dedicated PC running eCopy software as part of their document management system. It is connected to a Konica scanner. The system has to be constantly be reboot as the PC locks up when trying to run a scan. When troubleshooting the condition, I have found that the user that is used to log in to the network is not getting its rights.

Questions:

I thought that when one DC goes down, the second one automatically takes over for it. In this case it is allowing them to log in but not get all their rights. They are able to access the files on the file server, print to networked printers, but otherwise have are not to do business as usual.

What do I have to do to the second DC to get it to take over for the first one?

thanks in advance.

Answer : How to resolve W2k server DC problem

Is the DC that went down coming back up or are you all considering it dead and gone and not fixing it?

If dead and gone

Seize any FSMO roles off that box to DC 2  http://www.petri.co.il/seizing_fsmo_roles.htm

Run a metadata cleanup of the dead DC http://www.petri.co.il/delete_failed_dcs_from_ad.htm

Was DC2 a global catalog server too (hopefull yes)

How is baracuda configured....I've heard the ads but have not used it.  Does it point to DC1 by name or IP?

Another thing to really think about is to now get another DC up once this is fixed.  You are dealing with old boxes and right now if your current DC dies you have a lot more work on your hands.

Thanks

Mike