Discussion:
Setup 2nd Domain Controller - no NETLOGON or SYSVOL??
(too old to reply)
Eddie Walker
2007-08-25 20:02:40 UTC
Permalink
hey guys..

have another issue: ive promoted my member server that I want to be a 2nd
DC, i also configured dns and that appears to be working.

I have a new problem: after doing the above, i dont have a sysvol or
netlogon. I 'm stumped on this. I looked the issue up on MS website and i
appear to have it setup correctle( in ad sites and svs it has the correct to
and from)

no errors in the event log?

did the server not replicate correctly when it was promoted?

thanks

ed
Mathieu CHATEAU
2007-08-25 21:15:28 UTC
Permalink
Hello,

is the server service up and running ?
On the nework card, do you have MS client and shared files... checked ?
--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com
Post by Eddie Walker
hey guys..
have another issue: ive promoted my member server that I want to be a 2nd
DC, i also configured dns and that appears to be working.
I have a new problem: after doing the above, i dont have a sysvol or
netlogon. I 'm stumped on this. I looked the issue up on MS website and i
appear to have it setup correctle( in ad sites and svs it has the correct
to and from)
no errors in the event log?
did the server not replicate correctly when it was promoted?
thanks
ed
Eddie Walker
2007-08-26 06:05:25 UTC
Permalink
here is the error in event log from server at issue;
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 8/25/2007
Time: 3:41:46 PM
User: N/A
Computer: BEREAN04
Description:
The File Replication Service is having trouble enabling replication from
BEREAN03 to BEREAN04 for c:\windows\sysvol\domain using the DNS name
berean03.bereanwpb.org. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name berean03.bereanwpb.org from
this computer.
[2] FRS is not running on berean03.bereanwpb.org.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.


also at the existing DC here is the error:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 8/23/2007
Time: 7:57:48 PM
User: N/A
Computer: BEREAN03
Description:
The File Replication Service has detected that the replica set "DOMAIN
SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to
read from the NTFS USN journal is not found. This can occur because of one
of the following reasons.

[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can
truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long
time.
[5] File Replication Service could not keep up with the rate of Disk IO
activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1
will cause the following recovery steps to be taken to automatically recover
from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be
deleted from the replica set. If you do not want to wait 5 minutes, then run
"net stop ntfrs" followed by "net start ntfrs" to restart the File
Replication Service.
[2] At the poll following the deletion this computer will be re-added to
the replica set. The re-addition will trigger a full tree sync for the
replica set.

WARNING: During the recovery process data in the replica tree may be
unavailable. You should reset the registry parameter described above to 0 to
prevent automatic recovery from making the data unexpectedly unavailable if
this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the New->DWORD Value
function under the Edit Menu item. Type the value name exactly as shown
above.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Mathieu CHATEAU
2007-08-26 08:00:25 UTC
Permalink
Run :
dcdiag
netdiag
dnsdiag

to have a more clear view on the heatlh of your ad
--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com
Post by Eddie Walker
here is the error in event log from server at issue;
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 8/25/2007
Time: 3:41:46 PM
User: N/A
Computer: BEREAN04
The File Replication Service is having trouble enabling replication from
BEREAN03 to BEREAN04 for c:\windows\sysvol\domain using the DNS name
berean03.bereanwpb.org. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name berean03.bereanwpb.org from
this computer.
[2] FRS is not running on berean03.bereanwpb.org.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 8/23/2007
Time: 7:57:48 PM
User: N/A
Computer: BEREAN03
The File Replication Service has detected that the replica set "DOMAIN
SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to
read from the NTFS USN journal is not found. This can occur because of
one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can
truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long
time.
[5] File Replication Service could not keep up with the rate of Disk IO
activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to
1 will cause the following recovery steps to be taken to automatically
recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will
be deleted from the replica set. If you do not want to wait 5 minutes,
then run "net stop ntfrs" followed by "net start ntfrs" to restart the
File Replication Service.
[2] At the poll following the deletion this computer will be re-added to
the replica set. The re-addition will trigger a full tree sync for the
replica set.
WARNING: During the recovery process data in the replica tree may be
unavailable. You should reset the registry parameter described above to 0
to prevent automatic recovery from making the data unexpectedly
unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value
function under the Edit Menu item. Type the value name exactly as shown
above.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Eddie Walker
2007-08-27 03:16:30 UTC
Permalink
here is dcdiag:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\WalkerEM>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Berean\BEREAN03
Starting test: Connectivity
......................... BEREAN03 passed test Connectivity

Doing primary tests

Testing server: Berean\BEREAN03
Starting test: Replications
......................... BEREAN03 passed test Replications
Starting test: NCSecDesc
......................... BEREAN03 passed test NCSecDesc
Starting test: NetLogons
......................... BEREAN03 passed test NetLogons
Starting test: Advertising
......................... BEREAN03 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... BEREAN03 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... BEREAN03 passed test RidManager
Starting test: MachineAccount
......................... BEREAN03 passed test MachineAccount
Starting test: Services
......................... BEREAN03 passed test Services
Starting test: ObjectsReplicated
......................... BEREAN03 passed test ObjectsReplicated
Starting test: frssysvol
......................... BEREAN03 passed test frssysvol
Starting test: frsevent
......................... BEREAN03 passed test frsevent
Starting test: kccevent
......................... BEREAN03 passed test kccevent
Starting test: systemlog
......................... BEREAN03 passed test systemlog
Starting test: VerifyReferences
......................... BEREAN03 passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : bereanwpb
Starting test: CrossRefValidation
......................... bereanwpb passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... bereanwpb passed test CheckSDRefDom

Running enterprise tests on : bereanwpb.org
Starting test: Intersite
......................... bereanwpb.org passed test Intersite
Starting test: FsmoCheck
......................... bereanwpb.org passed test FsmoCheck

C:\Documents and Settings\WalkerEM>

here is netdiag:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\WalkerEM>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Berean\BEREAN03
Starting test: Connectivity
......................... BEREAN03 passed test Connectivity

Doing primary tests

Testing server: Berean\BEREAN03
Starting test: Replications
......................... BEREAN03 passed test Replications
Starting test: NCSecDesc
......................... BEREAN03 passed test NCSecDesc
Starting test: NetLogons
......................... BEREAN03 passed test NetLogons
Starting test: Advertising
......................... BEREAN03 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... BEREAN03 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... BEREAN03 passed test RidManager
Starting test: MachineAccount
......................... BEREAN03 passed test MachineAccount
Starting test: Services
......................... BEREAN03 passed test Services
Starting test: ObjectsReplicated
......................... BEREAN03 passed test ObjectsReplicated
Starting test: frssysvol
......................... BEREAN03 passed test frssysvol
Starting test: frsevent
......................... BEREAN03 passed test frsevent
Starting test: kccevent
......................... BEREAN03 passed test kccevent
Starting test: systemlog
......................... BEREAN03 passed test systemlog
Starting test: VerifyReferences
......................... BEREAN03 passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : bereanwpb
Starting test: CrossRefValidation
......................... bereanwpb passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... bereanwpb passed test CheckSDRefDom

Running enterprise tests on : bereanwpb.org
Starting test: Intersite
......................... bereanwpb.org passed test Intersite
Starting test: FsmoCheck
......................... bereanwpb.org passed test FsmoCheck

C:\Documents and Settings\WalkerEM>netdiag

....................................

Computer Name: BEREAN03
DNS Host Name: berean03.bereanwpb.org
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
List of installed hotfixes :
KB911564
KB925398_WMP64
KB931836
Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : berean03
IP Address . . . . . . . . : 216.52.204.14
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 216.52.204.1
Dns Servers. . . . . . . . : 216.52.204.14


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{7111021F-F6FD-41FC-9640-078FAC3C4510}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'216.52.204.1
4' and other DCs also have some of the names registered.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{7111021F-F6FD-41FC-9640-078FAC3C4510}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{7111021F-F6FD-41FC-9640-078FAC3C4510}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

C:\Documents and Settings\WalkerEM>


i cant find DNS DIAG
where is it or whree can i download it?

thanks for your help

ed

Eddie Walker
2007-08-25 21:18:37 UTC
Permalink
Post by Eddie Walker
hey guys..
have another issue: ive promoted my member server that I want to be a 2nd
DC, i also configured dns and that appears to be working.
I have a new problem: after doing the above, i dont have a sysvol or
netlogon. I 'm stumped on this. I looked the issue up on MS website and i
appear to have it setup correctle( in ad sites and svs it has the correct
to and from)
no errors in the event log?
did the server not replicate correctly when it was promoted?
thanks
ed
Eddie Walker
2007-08-27 03:12:37 UTC
Permalink
here is the error in event log from server at issue;
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 8/25/2007
Time: 3:41:46 PM
User: N/A
Computer: BEREAN04
Description:
The File Replication Service is having trouble enabling replication from
BEREAN03 to BEREAN04 for c:\windows\sysvol\domain using the DNS name
berean03.bereanwpb.org. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name berean03.bereanwpb.org from
this computer.
[2] FRS is not running on berean03.bereanwpb.org.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.


also at the existing DC here is the error:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 8/23/2007
Time: 7:57:48 PM
User: N/A
Computer: BEREAN03
Description:
The File Replication Service has detected that the replica set "DOMAIN
SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to
read from the NTFS USN journal is not found. This can occur because of one
of the following reasons.

[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can
truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long
time.
[5] File Replication Service could not keep up with the rate of Disk IO
activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1
will cause the following recovery steps to be taken to automatically recover
from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be
deleted from the replica set. If you do not want to wait 5 minutes, then run
"net stop ntfrs" followed by "net start ntfrs" to restart the File
Replication Service.
[2] At the poll following the deletion this computer will be re-added to
the replica set. The re-addition will trigger a full tree sync for the
replica set.

WARNING: During the recovery process data in the replica tree may be
unavailable. You should reset the registry parameter described above to 0 to
prevent automatic recovery from making the data unexpectedly unavailable if
this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the New->DWORD Value
function under the Edit Menu item. Type the value name exactly as shown
above.

For more information, see Help and Support Center at
http://go.microsoft.co
Post by Eddie Walker
hey guys..
have another issue: ive promoted my member server that I want to be a 2nd
DC, i also configured dns and that appears to be working.
I have a new problem: after doing the above, i dont have a sysvol or
netlogon. I 'm stumped on this. I looked the issue up on MS website and i
appear to have it setup correctle( in ad sites and svs it has the correct
to and from)
no errors in the event log?
did the server not replicate correctly when it was promoted?
thanks
ed
Continue reading on narkive:
Loading...