configure file replication between w2k dc's

  • Thread starter Thread starter DjPaolo
  • Start date Start date
D

DjPaolo

A few days ago i've installed a w2k server in the network and promoted
it to a domain controller. This is the second dc in the network. On NT
Server it was possible to configure file replication (netlogon-share)
to replicate files and login-scripts between servers. I would like to
configure this for these 2 domain controllers in the network. Does
anyone have an idea how?

Paolo
 
This will occur by default between all DC's in the same domain as logon
scripts are located in sysvol. Have a look in
c:\winnt\sysvol\sysvol\domainname\scripts, when a new script is copied to
that location it will by default replicate to your other DC.

Although sysvol can be used to replicate files the best way to do this is to
set up DFS, http://support.microsoft.com/?id=812487
 
Simon Geary said:
This will occur by default between all DC's in the same domain as logon
scripts are located in sysvol. Have a look in
c:\winnt\sysvol\sysvol\domainname\scripts, when a new script is copied to
that location it will by default replicate to your other DC.

Although sysvol can be used to replicate files the best way to do this is to
set up DFS, http://support.microsoft.com/?id=812487
Click to expand...


According to Microsoft replication should occur by default but when I
look at the sysvol share on the second DC it is totally empty! How can
this be?

Paolo
 
DjPaolo said:
"Simon Geary" <[email protected]> wrote in message


According to Microsoft replication should occur by default but when I
look at the sysvol share on the second DC it is totally empty! How can
this be?

Paolo
Click to expand...

Something has gone wrong somewhere. Is the sysvol folder shared out
properly? Run net share at a command prompt to check. Also confirm that all
your DNS entries and registrations are correct as an error here could cause
replication to fail.
 
Simon Geary said:
Something has gone wrong somewhere. Is the sysvol folder shared out
properly? Run net share at a command prompt to check. Also confirm that all
your DNS entries and registrations are correct as an error here could cause
replication to fail.
Click to expand...

This morning I've made the second server a member server (dcpromo) and
afterwards I promoted it to a DC. Now the SYSVOL on this server
contains the domain name folder and a policies folder (and the
NtFrs_Preinstall_Directory). The problem now is that there is no data
in this policies folder. On the first DC there are a few directories
in this folder like {21DCCC-etc...). DNS seems to be working fine
(nslookup-checks etc.). Group policies are not working now when they
are applied from this second server. Please give me a solution for
this.....

Paolo
 
DjPaolo said:
"Simon Geary" <[email protected]> wrote in message

This morning I've made the second server a member server (dcpromo) and
afterwards I promoted it to a DC. Now the SYSVOL on this server
contains the domain name folder and a policies folder (and the
NtFrs_Preinstall_Directory). The problem now is that there is no data
in this policies folder. On the first DC there are a few directories
in this folder like {21DCCC-etc...). DNS seems to be working fine
(nslookup-checks etc.). Group policies are not working now when they
are applied from this second server. Please give me a solution for
this.....

Paolo
Click to expand...

On both servers, run "repadmin /showreps" from the command line and post
results back. This tool checks that the two DC's are replication partners
with each other.

You should also run dcdiag /v and netdiag /v on each server to check for any
obvious errors.

In the AD sites & services console, check that the KCC has automatically
created replication between the two servers. I presume you have also checked
the DNS configuration?
 
Simon Geary said:
this
is to

On both servers, run "repadmin /showreps" from the command line and post
results back. This tool checks that the two DC's are replication partners
with each other.

You should also run dcdiag /v and netdiag /v on each server to check for any
obvious errors.

In the AD sites & services console, check that the KCC has automatically
created replication between the two servers. I presume you have also checked
the DNS configuration?
Click to expand...


Below are the "repadmin /showreps" results from both servers. There
are no errors in dcdiag and netdiag results for both servers. I
checked AD sites & services and can see that the 2 servers are shown
like this:

Servers
|
Server1
|
NTDS Settings
|
<automatically generated> SERVER2

|
Server2
|
NTDS Settings
|
<automatically generated> SERVER1

I don't exactly know what you mean by "KCC"? DNS seems to be working
without any problems.

"repadmin /showreps" results:

Server1:

Default-First-Site-Name\SERVER1
DSA Options : IS_GC
objectGuid : 29b0668d-844d-4006-9790-76efff7b3d68
invocationID: b2318a92-97d0-49c9-afa5-a08265dd0652

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 (deleted DSA) via RPC
objectGuid: 0cc61ad6-f67b-4727-b33c-4c9c03be0f18
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f
Last attempt @ 2004-01-21 07:51.27 was successful.

CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 (deleted DSA) via RPC
objectGuid: 0cc61ad6-f67b-4727-b33c-4c9c03be0f18
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f
Last attempt @ 2004-01-21 08:11.03 was successful.

DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 (deleted DSA) via RPC
objectGuid: 0cc61ad6-f67b-4727-b33c-4c9c03be0f18
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f
Last attempt @ 2004-01-21 08:19.00 was successful.

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f

CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f

DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f


-----------------------------------------------------------------------------
Server2:

Default-First-Site-Name\SERVER2
DSA Options : (none)
objectGuid : f046e741-fed4-4db9-9ebc-4ed1a8e9a68f
invocationID: 425c5f4c-d4db-47d9-bf74-c5388c97709d

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68
Last attempt @ 2004-01-21 07:46.14 was successful.

CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68
Last attempt @ 2004-01-21 08:16.31 was successful.

DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68
Last attempt @ 2004-01-21 08:16.01 was successful.

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68

CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68

DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68

Thanks for you support!
 
Below are the "repadmin /showreps" results from both servers. There
are no errors in dcdiag and netdiag results for both servers. I
checked AD sites & services and can see that the 2 servers are shown
like this:

Servers
|
Server1
|
NTDS Settings
|
<automatically generated> SERVER2

|
Server2
|
NTDS Settings
|
<automatically generated> SERVER1

I don't exactly know what you mean by "KCC"? DNS seems to be working
without any problems.

"repadmin /showreps" results:

Server1:

Default-First-Site-Name\SERVER1
DSA Options : IS_GC
objectGuid : 29b0668d-844d-4006-9790-76efff7b3d68
invocationID: b2318a92-97d0-49c9-afa5-a08265dd0652

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 (deleted DSA) via RPC
objectGuid: 0cc61ad6-f67b-4727-b33c-4c9c03be0f18
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f
Last attempt @ 2004-01-21 07:51.27 was successful.

CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 (deleted DSA) via RPC
objectGuid: 0cc61ad6-f67b-4727-b33c-4c9c03be0f18
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f
Last attempt @ 2004-01-21 08:11.03 was successful.

DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 (deleted DSA) via RPC
objectGuid: 0cc61ad6-f67b-4727-b33c-4c9c03be0f18
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f
Last attempt @ 2004-01-21 08:19.00 was successful.

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f

CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f

DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER2 via RPC
objectGuid: f046e741-fed4-4db9-9ebc-4ed1a8e9a68f


-------------------------------------------------------------------------- ---
Server2:

Default-First-Site-Name\SERVER2
DSA Options : (none)
objectGuid : f046e741-fed4-4db9-9ebc-4ed1a8e9a68f
invocationID: 425c5f4c-d4db-47d9-bf74-c5388c97709d

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68
Last attempt @ 2004-01-21 07:46.14 was successful.

CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68
Last attempt @ 2004-01-21 08:16.31 was successful.

DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68
Last attempt @ 2004-01-21 08:16.01 was successful.

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68

CN=Configuration,DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68

DC=domain,DC=nl,DC=domain,DC=com
Default-First-Site-Name\SERVER1 via RPC
objectGuid: 29b0668d-844d-4006-9790-76efff7b3d68

Thanks for you support!
Click to expand...

These results look perfect from a replication point of view. They show that
a replication link has successfully been created between server1 and server2
and also the other direction between server2 and server1.

So what else could be wrong? Check in the Sysvol folders on both servers and
look for any folder that is called "ntfrs_foldername_long number" This would
indicate an FRS problem and is a relatively common cause of GPO problems.

Also check in the evnt logs for Journal Wrap errors and any other FRS
related problems.
 
Simon Geary said:
These results look perfect from a replication point of view. They show that
a replication link has successfully been created between server1 and server2
and also the other direction between server2 and server1.

So what else could be wrong? Check in the Sysvol folders on both servers and
look for any folder that is called "ntfrs_foldername_long number" This would
indicate an FRS problem and is a relatively common cause of GPO problems.

Also check in the evnt logs for Journal Wrap errors and any other FRS
related problems.
Click to expand...

In the Sysvol folder of the second server there is a folder named
"DO_NOT_REMOVE_NtFrs_PreInstall_Directory. This folder does not exist
on the first server Sysvol share. In the logs of the 2nd server there
is a warning in the File Replication Service log: NtFrs, ID 13508:
"The File Replication Service is having trouble enabling replication
from SERVER1 to SERVER2 .....using the DNS name
server1.domain.nl.domain. FRS will keep retrying (....). I've checked
all the possible reasons for this problem but can't find a real
solution.

Thanx for you support!
 
DjPaolo said:
--------------------------------------------------------------------------

These results look perfect from a replication point of view. They show that
a replication link has successfully been created between server1 and server2
and also the other direction between server2 and server1.

So what else could be wrong? Check in the Sysvol folders on both servers and
look for any folder that is called "ntfrs_foldername_long number" This would
indicate an FRS problem and is a relatively common cause of GPO problems.

Also check in the evnt logs for Journal Wrap errors and any other FRS
related problems.
Click to expand...

In the Sysvol folder of the second server there is a folder named
"DO_NOT_REMOVE_NtFrs_PreInstall_Directory. This folder does not exist
on the first server Sysvol share. In the logs of the 2nd server there
is a warning in the File Replication Service log: NtFrs, ID 13508:
"The File Replication Service is having trouble enabling replication
from SERVER1 to SERVER2 .....using the DNS name
server1.domain.nl.domain. FRS will keep retrying (....). I've checked
all the possible reasons for this problem but can't find a real
solution.

Thanx for you support![/QUOTE]

Have a read of this web page for some troubleshooting options.
http://www.eventid.net/display.asp?eventid=13508&source=ntfrs

In summary, make sure the Sysvol folder is shared on both servers and check
the time synchronisation between the two. There are a whole load of other
troubleshooting steps you can try as well suggested by other people.
 
Back
Top