DC wont talk

  • Thread starter Thread starter Dan
  • Start date Start date
D

Dan

Hi all,

I've had quite a few problems lately with my DC's, but I
managed to get them all offline except for one. What I
plan to do (since this one DC is on a temporary box) is
get the new server all up & running, dcpromo it, then xfer
all FSMO roles & what not to it, then demote the temp
box. Problem I'm having is that when the new box is
dcpromo'd, replication failes, sysvol never gets shared,
and thus it's just a dead DC that doesnt do anything but
sit there. You should know that to get the temp box to
become a DC that accepted logons, I had to use the
registry hack on the key SysvolReady to get it up &
running (dont dwell on this though as the story behind the
reason I did that is long & arduous). So basically my
system consists of one "hacked" DC that wont talk to
anyone. Here's a dcdiag output from that box:

Doing primary tests

Testing server: Eberls\EBERLS03
Starting test: Replications
......................... EBERLS03 passed test
Replications
Starting test: NCSecDesc
......................... EBERLS03 passed test
NCSecDesc
Starting test: NetLogons
......................... EBERLS03 passed test
NetLogons
Starting test: Advertising
......................... EBERLS03 passed test
Advertising
Starting test: KnowsOfRoleHolders
......................... EBERLS03 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... EBERLS03 passed test
RidManager
Starting test: MachineAccount
......................... EBERLS03 passed test
MachineAccount
Starting test: Services
......................... EBERLS03 passed test
Services
Starting test: ObjectsReplicated
......................... EBERLS03 passed test
ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System,
SYSVOL started.
The Active Directory may be prevented from
starting.
......................... EBERLS03 passed test
frssysvol
Starting test: kccevent
......................... EBERLS03 passed test
kccevent
Starting test: systemlog
......................... EBERLS03 passed test
systemlog
Running enterprise tests on : mydomain.com
Starting test: Intersite
......................... mydomain.com passed
test Intersite
Starting test: FsmoCheck
......................... mydomain.com passed
test FsmoCheck
As you can see I've managed to get everything up & running
on it except for the frssysvol deal. I figure that's there
because it went online from a hack instead of the proper
way.
 
Really probably need to get the errors you're seeing in the logs to get a
better idea of what the problem might be, and also run the dcdiag with the
/v switch to give more info there.
Verify that the existing dc (temp) holds all 5 fsmo roles and is a GC, and
be sure that both dc's are at sp3 or sp4 ("netdom query fsmo").
Also run netdiag /v as well.
Be sure dns is working ok and the existing dc can ping your domain name and
get a reply, and that the new box is Only pointed to it for dns.
If either of these boxes are multihomed, disable the extra nics so you only
have one internal one to deal with.
I also assume that both of these are on the same subnet so in the same AD
site.
Since the "promotion" works, the dcpromo log probably won't give us much,
but take a look at the bottom of it to see if it shows any errors too.


--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
Back
Top