L
Luc Gagnier
Hi,
We have a win2k domain with two domain controller. Our IP adresses are
172.31.1.15 and 172.31.1.16 with 255.255.0.0 subnet mask. We want to change
there IP adresses for a 192.168.1.2 and 192.168.1.3 with 255.255.255.0
subnet mask. These server are DNS, DHCP and WINS server too. By now, we
have successfuly changed all IP adresses of our 600 PCs. When we are trying
to change the IP of our domain controller nothing going right (see my
previous post "How to change IP addresses on a DC running DNS, DHCP and
Wins"). "No problem, said my partner. We just need to build a fresh new
server in the 192.168.1.X IP, promote it to domain controller, transfert the
role to it, demote the two others, change there IP, repromote them and after
that retransfert the role to our originally "PDC". There's no problem
there!"
Oh yeah! I then build up a fresh new server with the IP 192.168.1.11
255.255.255.0 (yes we have a router between these server) with the DNS
services on it. I successfully joined it to domain and promote too. But
the sysvol isn't replicate. I've done a "dcdiag" and this is the result:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC10
Starting test: Connectivity
......................... DC10 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC10
Starting test: Replications
......................... DC10 passed test Replications
Starting test: NCSecDesc
......................... DC10 passed test NCSecDesc
Starting test: NetLogons
......................... DC10 passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\dc1.colval.lan,
when we
were trying to reach DC10.
Server is not responding or is not considered suitable.
......................... DC10 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... DC10 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... DC10 passed test RidManager
Starting test: MachineAccount
......................... DC10 passed test MachineAccount
Starting test: Services
......................... DC10 passed test Services
Starting test: ObjectsReplicated
......................... DC10 passed test ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... DC10 passed test frssysvol
Starting test: kccevent
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/21/2004 15:17:42
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/21/2004 15:18:03
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/21/2004 15:18:24
(Event String could not be retrieved)
......................... DC10 failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0000FAA
Time Generated: 04/21/2004 14:29:24
Event String: The DNS server was unable to load a resource
An Error Event occured. EventID: 0x00000457
Time Generated: 04/21/2004 14:49:10
Event String: Driver Acrobat PDFWriter required for printer
An Error Event occured. EventID: 0x00000452
Time Generated: 04/21/2004 14:49:10
Event String: The printer could not be installed.
An Error Event occured. EventID: 0x00000457
Time Generated: 04/21/2004 15:00:23
Event String: Driver Acrobat PDFWriter required for printer
An Error Event occured. EventID: 0x00000452
Time Generated: 04/21/2004 15:00:23
Event String: The printer could not be installed.
......................... DC10 failed test systemlog
Running enterprise tests on : colval.lan
Starting test: Intersite
......................... colval.lan passed test Intersite
Starting test: FsmoCheck
......................... colval.lan passed test FsmoCheck
They are the events I received:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13565
Date: 2004-04-21
Time: 15:02:15
User: N/A
Computer: DC10
Description:
File Replication Service is initializing the system volume with data from
another domain controller. Computer DC10 cannot become a domain controller
until this process is complete. The system volume will then be shared as
SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the initialization process, the
SYSVOL share will appear.
The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume, the availability of
other domain controllers, and the replication interval between domain
controllers.
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 2004-04-21
Time: 15:12:00
User: N/A
Computer: DC10
Description:
The File Replication Service is having trouble enabling replication from DC2
to DC10 for c:\winnt\sysvol\domain using the DNS name dc2.colval.lan. FRS
will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name dc2.colval.lan from this
computer.
[2] FRS is not running on dc2.colval.lan.
[3] The topology information in the Active Directory for this replica has n
ot yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
Data:
0000: 00 00 00 00 ....
I've check in the DNS entries and everything seems to be good.
Now I don't know what to check after that!
We have a win2k domain with two domain controller. Our IP adresses are
172.31.1.15 and 172.31.1.16 with 255.255.0.0 subnet mask. We want to change
there IP adresses for a 192.168.1.2 and 192.168.1.3 with 255.255.255.0
subnet mask. These server are DNS, DHCP and WINS server too. By now, we
have successfuly changed all IP adresses of our 600 PCs. When we are trying
to change the IP of our domain controller nothing going right (see my
previous post "How to change IP addresses on a DC running DNS, DHCP and
Wins"). "No problem, said my partner. We just need to build a fresh new
server in the 192.168.1.X IP, promote it to domain controller, transfert the
role to it, demote the two others, change there IP, repromote them and after
that retransfert the role to our originally "PDC". There's no problem
there!"
Oh yeah! I then build up a fresh new server with the IP 192.168.1.11
255.255.255.0 (yes we have a router between these server) with the DNS
services on it. I successfully joined it to domain and promote too. But
the sysvol isn't replicate. I've done a "dcdiag" and this is the result:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC10
Starting test: Connectivity
......................... DC10 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC10
Starting test: Replications
......................... DC10 passed test Replications
Starting test: NCSecDesc
......................... DC10 passed test NCSecDesc
Starting test: NetLogons
......................... DC10 passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\dc1.colval.lan,
when we
were trying to reach DC10.
Server is not responding or is not considered suitable.
......................... DC10 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... DC10 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... DC10 passed test RidManager
Starting test: MachineAccount
......................... DC10 passed test MachineAccount
Starting test: Services
......................... DC10 passed test Services
Starting test: ObjectsReplicated
......................... DC10 passed test ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... DC10 passed test frssysvol
Starting test: kccevent
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/21/2004 15:17:42
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/21/2004 15:18:03
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/21/2004 15:18:24
(Event String could not be retrieved)
......................... DC10 failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0000FAA
Time Generated: 04/21/2004 14:29:24
Event String: The DNS server was unable to load a resource
An Error Event occured. EventID: 0x00000457
Time Generated: 04/21/2004 14:49:10
Event String: Driver Acrobat PDFWriter required for printer
An Error Event occured. EventID: 0x00000452
Time Generated: 04/21/2004 14:49:10
Event String: The printer could not be installed.
An Error Event occured. EventID: 0x00000457
Time Generated: 04/21/2004 15:00:23
Event String: Driver Acrobat PDFWriter required for printer
An Error Event occured. EventID: 0x00000452
Time Generated: 04/21/2004 15:00:23
Event String: The printer could not be installed.
......................... DC10 failed test systemlog
Running enterprise tests on : colval.lan
Starting test: Intersite
......................... colval.lan passed test Intersite
Starting test: FsmoCheck
......................... colval.lan passed test FsmoCheck
They are the events I received:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13565
Date: 2004-04-21
Time: 15:02:15
User: N/A
Computer: DC10
Description:
File Replication Service is initializing the system volume with data from
another domain controller. Computer DC10 cannot become a domain controller
until this process is complete. The system volume will then be shared as
SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the initialization process, the
SYSVOL share will appear.
The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume, the availability of
other domain controllers, and the replication interval between domain
controllers.
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 2004-04-21
Time: 15:12:00
User: N/A
Computer: DC10
Description:
The File Replication Service is having trouble enabling replication from DC2
to DC10 for c:\winnt\sysvol\domain using the DNS name dc2.colval.lan. FRS
will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name dc2.colval.lan from this
computer.
[2] FRS is not running on dc2.colval.lan.
[3] The topology information in the Active Directory for this replica has n
ot yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
Data:
0000: 00 00 00 00 ....
I've check in the DNS entries and everything seems to be good.
Now I don't know what to check after that!