J
Jai Ramachandran
Currently my office has two active directory domain
controllers along with about 20 clients (all running
win2k). Recently the non-root DC had hardware problems
and had to be replaced. The moron who set up the new
server (me) assigned the same netbios/dns/wins name to the
replacement computer as the orginal DC that had the
hardware problems. I thought this would be fine seeing as
how the other machine was now off of the network. Much to
my dismay I am having the following problems
1) The new DC will not act as a logon server, it instead
denies all logon requests, as well as any authentication
requests.
2) This may be a related issue, I tried to add another DC
to the network, but I get an error message saying
that "Please enter an account name that has Enterprise
Administrator privledges" even though the account being
used does have said permissions.
When I run the MPSRPT_DirSvc.exe and I look in the
dcdiag.txt log files for both DCs I see the error:
The nTFRSSubscriber object cn=files,cn=files,cn=a5aec278-
3cf5-46d1-8d9d-45dcd4e2b65d,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ntserver,ou=domain
controllers,dc=darfibernt,dc=local has a invalid value for
the attribute frsMemberReference.
On the root DC. On the second DC that is malfunctioning I
see the error:
An Warning Event occured. EventID: 0x800034FD
Time Generated: 08/15/2003 07:26:36
Event String: File Replication Service is
initializing the
system volume with data from another domain
controller. Computer ROBIN cannot become a domain
controller until this process is complete. The
system volume will then be shared as SYSVOL.
Any help would be appreciated. I have also been told that
I needed to run the "metadata cleanup" before adding the
second dc (after the original crashed). Since I did not
do that, is there any course of action that I could take
to remedy the situation
controllers along with about 20 clients (all running
win2k). Recently the non-root DC had hardware problems
and had to be replaced. The moron who set up the new
server (me) assigned the same netbios/dns/wins name to the
replacement computer as the orginal DC that had the
hardware problems. I thought this would be fine seeing as
how the other machine was now off of the network. Much to
my dismay I am having the following problems
1) The new DC will not act as a logon server, it instead
denies all logon requests, as well as any authentication
requests.
2) This may be a related issue, I tried to add another DC
to the network, but I get an error message saying
that "Please enter an account name that has Enterprise
Administrator privledges" even though the account being
used does have said permissions.
When I run the MPSRPT_DirSvc.exe and I look in the
dcdiag.txt log files for both DCs I see the error:
The nTFRSSubscriber object cn=files,cn=files,cn=a5aec278-
3cf5-46d1-8d9d-45dcd4e2b65d,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ntserver,ou=domain
controllers,dc=darfibernt,dc=local has a invalid value for
the attribute frsMemberReference.
On the root DC. On the second DC that is malfunctioning I
see the error:
An Warning Event occured. EventID: 0x800034FD
Time Generated: 08/15/2003 07:26:36
Event String: File Replication Service is
initializing the
system volume with data from another domain
controller. Computer ROBIN cannot become a domain
controller until this process is complete. The
system volume will then be shared as SYSVOL.
Any help would be appreciated. I have also been told that
I needed to run the "metadata cleanup" before adding the
second dc (after the original crashed). Since I did not
do that, is there any course of action that I could take
to remedy the situation