AdPrep/Forrest Prep not run before 2003 DC was added what to do no

[Guest]

I have a site that the previous network administrator didn't prep the network
properly before adding 2 2003 DC's to a 2000 Domain. I am not sure where to
start to backup and clean the problems up. I think a call to MS is going to
happen just because I don't do AD enough to know all the things to look for.
Any suggestions? Here is the DC Diags when the 2 new DC's were up and
running but they have been offline for at least a month. Not good.

When the new servers are up and running we get problems surfing the network
unless you were already logged in. I'm not sure what was done to do any
prep. Here is the error I get when the 2003 DC's are up and running.

"thell is not accessible. You might not have permission to use this network
resource. Contact the administrator of this server to find out if you have
access permissions.

Windows cannot find the network path. Verifty that the network path is
correct and the destination computer is not busy or turned off. If Windows
still cannot find the network path, contact your network administrator."

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\THELL-CONTROL
Starting test: Connectivity
......................... THELL-CONTROL passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\THELL-CONTROL
Starting test: Replications
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source BONNIE
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source CLYDE
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source CLYDE
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source BONNIE
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
......................... THELL-CONTROL passed test Replications
Starting test: NCSecDesc
......................... THELL-CONTROL passed test NCSecDesc
Starting test: NetLogons
......................... THELL-CONTROL passed test NetLogons
Starting test: Advertising
......................... THELL-CONTROL passed test Advertising
Starting test: KnowsOfRoleHolders
......................... THELL-CONTROL passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... THELL-CONTROL passed test RidManager
Starting test: MachineAccount
......................... THELL-CONTROL passed test MachineAccount
Starting test: Services
SMTPSVC Service is stopped on [THELL-CONTROL]
......................... THELL-CONTROL failed test Services
Starting test: ObjectsReplicated
......................... THELL-CONTROL passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... THELL-CONTROL passed test frssysvol
Starting test: kccevent
......................... THELL-CONTROL passed test kccevent
Starting test: systemlog
......................... THELL-CONTROL passed test systemlog

Running enterprise tests on : thell.edu
Starting test: Intersite
......................... thell passed test Intersite
Starting test: FsmoCheck
......................... thell passed test FsmoCheck