Clients unable to login - NETLOGON and SYSVOL shares not present

Hi experts

The scenario is that my client's Windows Small Biz Svr 2000 (It's a PDC without another server) had a power failure (or something) resulting in an unexpected shutdown a few days ago. Now, they do not logon as before. They can ALL logon but using cached credentials only. Most of the clients cannot access the server's drives except for 2 XP machines, which can access the mapped drives and other resources!

Anyway, after some digging, I found 3 Exchange services not running (resulting in everyone's Outlook not working) and the SYSVOL and NETLOGON shares have disappeared.

I found some references to an old server that was on the network a while ago. Believing this might be interfering, I deleted references to this server using LDP.exe.

DHCP is working, and the clients use the server as their gateway and their DNS server and their WINS server.

I have rebuilt DNS back to default, with new AD-Integrated zones. I believe DNS is working OK.

DCDIAG reveals...

Starting test: kccevent
         * The KCC Event log test
         An Error Event occured.  EventID: 0xC0000466
            Time Generated: 01/03/2006   17:39:38
            Event String: Unable to establish connection with global catalog.
         ......................... <SERVER_NAME_HERE_DELETED> failed test kccevent

And...

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.
  PDC Name: \\<SERVER_NAME_HERE_DELETED>
         Locator Flags: 0xe00001fd
         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.
         .........................  failed test FsmoCheck

And...

 Starting test: Advertising
         Fatal Error:DsGetDcName (<SERVER_NAME_HERE_DELETED>) call failed, error 1355
         The Locator could not find the server.
         ......................... <SERVER_NAME_HERE_DELETED> failed test Advertising

NETDIAG reveals...

    Testing Kerberos authentication... Failed

And...

Domain membership test . . . . . . : Failed
    [WARNING] Ths system volume has not been completely replicated to the local machine. This machine is not working properly as a DC.
    Machine is a . . . . . . . . . : Primary Domain Controller Emulator

And...

DC discovery test. . . . . . . . . : Failed

    Find DC in domain '<DOMAIN_NAME_HERE_DELETED>':
        [FATAL] Cannot find DC in domain '<DOMAIN_NAME_HERE_DELETED>'. [ERROR_NO_SUCH_DOMAIN]

DC list test . . . . . . . . . . . : Failed
        '<DOMAIN_NAME_HERE_DELETED>': Cannot find DC to get DC list from [test skipped].
    List of DCs in Domain '<DOMAIN_NAME_HERE_DELETED>':

And...

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.

Event Viewer...

Every 5 mins or so I get an error in the App'n Log (Source Userenv, event ID 1000) saying...

Windows cannot determine the user or computer name. Return value (1355).

And...

Every so often (couple hours) I get a warning in the FRS Log (Source NTFRS, event ID 13566) saying...

File Replication Service is scanning the data in the system volume. Computer SSRSYDSVR cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
 
To check for the SYSVOL share, at the command prompt, type:
net share
 
When File Replication Service completes the scanning process, the SYSVOL share will appear.
 
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.

And the above never seems to finish.

Well that's my situation. I hope you guys and girls can help.