Cannot replicate after reinstalling DC (long)

[Jake]

Hello all. First off, thanks for taking the time to help out with
this problem I'm having.

Here's some background to my replication problem. I have a Windows
2000 AD domain in mixed mode called domain.local with 8 DC's, all in
differnt locations. Recently one of my DC's, I'll call this DC
STPAUL, started having corruption on the OS level (random win32
errors, control panel was corrupt, couldn't open properties for
anything, etc.) Anyway, I demoted STPAUL from AD and reinstalled
Windows and applied all the latest patches - SP4 and all critical
patches afterwards.

I ran DCPROMO on STPAUL and everything worked fine - I did not receive
any error messages. I recreated the Site, Subnet and Inter Site
transports for this location within AD Site and Services and made the
DC a Global Catalog. All this happened on a Saturday. On Monday when
I came in I found the event logs on this server were riddled with
errors. Most of them I have fixed but I have this nagging problem
that I have been unable to resolve.

I keep getting Event ID 13508:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 10/17/2003
Time: 10:35:09 AM
User: N/A
Computer: STPAUL
Description:
The File Replication Service is having trouble enabling replication
from HBO to STPAUL for c:\winnt\sysvol\domain using the DNS name
hbo.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name hbo.domain.local from
this computer.
[2] FRS is not running on hbo.domain.local.
[3] The topology information in the Active Directory for this replica
has not 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: 05 00 00 00 ....

I have spent the past 2 days working on this looking for an answer.
KB article Q272279 did not help. I have tried everything I can
possibly think of and I'm tempted to demote this server again then run
DCPROMO again.

A few odd things I have seen:

In AD Sites and Services ON the STPAUL server I can see the StPaul
Site, the Server, and NTDS Settings, and connections from STPAUL and
HBO. Replmon indicates replication is working successfully.

In AD Sites and Services ON the HBO server I can see the StPaul site,
the Server, but no NTDS Settings below the server icon. I am unable
to add them in manually.

This is telling me somewhere, somehow, something got messed up when I
demoted the server and added it as a DC when I reloaded Windows.
LostAndFoundConfig does not have anything inside the container. DNS
is working properly on each server including the STPAUL server.

Any ideas are welcome. I'm wondering if there is a quick fix to this
before I demote the server again and run DCPROMO again. One thing I
forgot to note is that when I reloaded Windows I gave the server the
exact same name and IP as before. Hopefully that's not a problem.

Jake

 

[Guest]

check out this link.

http://eventid.net/display.asp?eventid=13508&source=ntfrs

 

[Jacob]

-----Original Message-----
Hello all. First off, thanks for taking the time to help out with
this problem I'm having.

Here's some background to my replication problem. I have a Windows
2000 AD domain in mixed mode called domain.local with 8 DC's, all in
differnt locations. Recently one of my DC's, I'll call this DC
STPAUL, started having corruption on the OS level (random win32
errors, control panel was corrupt, couldn't open properties for
anything, etc.) Anyway, I demoted STPAUL from AD and reinstalled
Windows and applied all the latest patches - SP4 and all critical
patches afterwards.

I ran DCPROMO on STPAUL and everything worked fine - I did not receive
any error messages. I recreated the Site, Subnet and Inter Site
transports for this location within AD Site and Services and made the
DC a Global Catalog. All this happened on a Saturday. On Monday when
I came in I found the event logs on this server were riddled with
errors. Most of them I have fixed but I have this nagging problem
that I have been unable to resolve.

I keep getting Event ID 13508:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 10/17/2003
Time: 10:35:09 AM
User: N/A
Computer: STPAUL
Description:
The File Replication Service is having trouble enabling replication
from HBO to STPAUL for c:\winnt\sysvol\domain using the DNS name
hbo.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name hbo.domain.local from
this computer.
[2] FRS is not running on hbo.domain.local.
[3] The topology information in the Active Directory for this replica
has not 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: 05 00 00 00 ....

I have spent the past 2 days working on this looking for an answer.
KB article Q272279 did not help. I have tried everything I can
possibly think of and I'm tempted to demote this server again then run
DCPROMO again.

A few odd things I have seen:

In AD Sites and Services ON the STPAUL server I can see the StPaul
Site, the Server, and NTDS Settings, and connections from STPAUL and
HBO. Replmon indicates replication is working successfully.

In AD Sites and Services ON the HBO server I can see the StPaul site,
the Server, but no NTDS Settings below the server icon. I am unable
to add them in manually.

This is telling me somewhere, somehow, something got messed up when I
demoted the server and added it as a DC when I reloaded Windows.
LostAndFoundConfig does not have anything inside the container. DNS
is working properly on each server including the STPAUL server.

Any ideas are welcome. I'm wondering if there is a quick fix to this
before I demote the server again and run DCPROMO again. One thing I
forgot to note is that when I reloaded Windows I gave the server the
exact same name and IP as before. Hopefully that's not a problem.

Jake
.

Hi Jake

Have you tried looking at the file replication service?
I have the same problem and I found out that the NTFrs
service is missing on one my servers.

regards
Jacob

 

[Jake]

I have already checked eventid.net. Everything on that site I have
tried and nothing seems to fix the problem.

NTfrs is installed and running. I have restarted the service a number
of times only to keep seeing the same replication errors.

Any other suggestions?

-----Original Message-----
Hello all. First off, thanks for taking the time to help out with
this problem I'm having.

Here's some background to my replication problem. I have a Windows
2000 AD domain in mixed mode called domain.local with 8 DC's, all in
differnt locations. Recently one of my DC's, I'll call this DC
STPAUL, started having corruption on the OS level (random win32
errors, control panel was corrupt, couldn't open properties for
anything, etc.) Anyway, I demoted STPAUL from AD and reinstalled
Windows and applied all the latest patches - SP4 and all critical
patches afterwards.

I ran DCPROMO on STPAUL and everything worked fine - I did not receive
any error messages. I recreated the Site, Subnet and Inter Site
transports for this location within AD Site and Services and made the
DC a Global Catalog. All this happened on a Saturday. On Monday when
I came in I found the event logs on this server were riddled with
errors. Most of them I have fixed but I have this nagging problem
that I have been unable to resolve.

I keep getting Event ID 13508:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 10/17/2003
Time: 10:35:09 AM
User: N/A
Computer: STPAUL
Description:
The File Replication Service is having trouble enabling replication
from HBO to STPAUL for c:\winnt\sysvol\domain using the DNS name
hbo.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name hbo.domain.local from
this computer.
[2] FRS is not running on hbo.domain.local.
[3] The topology information in the Active Directory for this replica
has not 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: 05 00 00 00 ....

I have spent the past 2 days working on this looking for an answer.
KB article Q272279 did not help. I have tried everything I can
possibly think of and I'm tempted to demote this server again then run
DCPROMO again.

A few odd things I have seen:

In AD Sites and Services ON the STPAUL server I can see the StPaul
Site, the Server, and NTDS Settings, and connections from STPAUL and
HBO. Replmon indicates replication is working successfully.

In AD Sites and Services ON the HBO server I can see the StPaul site,
the Server, but no NTDS Settings below the server icon. I am unable
to add them in manually.

This is telling me somewhere, somehow, something got messed up when I
demoted the server and added it as a DC when I reloaded Windows.
LostAndFoundConfig does not have anything inside the container. DNS
is working properly on each server including the STPAUL server.

Any ideas are welcome. I'm wondering if there is a quick fix to this
before I demote the server again and run DCPROMO again. One thing I
forgot to note is that when I reloaded Windows I gave the server the
exact same name and IP as before. Hopefully that's not a problem.

Jake
.

Hi Jake

Have you tried looking at the file replication service?
I have the same problem and I found out that the NTFrs
service is missing on one my servers.

regards
Jacob

 

[Jake]

Ok. I've been messing around with some things today and I think I
have an idea where the problem might be. I'm assuming this is a DNS
issue because I'm seeing some very interesting things on the STPAUL
DC. I ran netdiag /v on STPAUL and found an incorrect entry in the
DNS database on our primary DC called HBO. Here is a snip from the
log:

DNS test . . . . . . . . . . . . . : Passed
Interface {6FF83D25-D0E3-49AB-B610-CB612C918FF8}
DNS Domain:
DNS Servers: 172.17.1.225 192.168.1.225
IP Address: 192.168.1.225
Expected registration with PDN (primary DNS domain name):
Hostname: stpaul.domain.local.
Authoritative zone: domain.local.
Primary DNS server: hbo.domain.local 172.17.1.225
Authoritative NS:192.168.8.225 192.168.9.225 192.168.1.225
192.168.3.225 192.168.4.225 192.168.5.225 172.17.1.225 192.168.2.225
Verify DNS registration:
Name: stpaul.domain.local
Expected IP: 192.168.1.225
Server 192.168.8.225: NO_ERROR
Server 192.168.9.225: NO_ERROR
Server 192.168.1.225: NO_ERROR
Server 192.168.3.225: NO_ERROR
Server 192.168.4.225: NO_ERROR
Server 192.168.5.225: NO_ERROR
Server 172.17.1.225: NO_ERROR
Server 192.168.2.225: NO_ERROR
The DNS registration for stpaul.domain.local is correct on all DNS
servers
Check the DNS registration for DCs entries on DNS server
'172.17.1.225'
The Record is different on DNS server '172.17.1.225'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '172.17.1.225', no need to
re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = domain.local.
DNS DATA =
A 192.168.1.225

The record on DNS server 172.17.1.225 is:
DNS NAME = domain.local
DNS DATA =
A 192.168.1.225
A 192.168.4.225
A 192.17.1.225 <----- THIS IP IS WRONG. SHOULD BE
172.17.1.225
A 192.168.5.225
A 192.168.2.225
A 192.168.8.225
A 192.168.3.225
A 192.168.9.225
+------------------------------------------------------+

The Record is different on DNS server '172.17.1.225'.
DNS server has more than one entries for this name, usually this means
there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '172.17.1.225', no need to
re-register.

+------------------------------------------------------+

Now, I'm assuming I fat fingered the IP for hbo.domain.local which
should be 172.17.1.225. But, I cannot for the life of me find, on
either server, where that incorrect IP is. I checked the DNS settings
on STPAUL and HBO and everything is correct. I can ping both servers
by IP and FQDN.

Any ideas on how to change this? I tried ipconfig /flushdns, didn't
work. I tried using NSLOOKUP domain.local and the IP's returned were
all correct.

I have already checked eventid.net. Everything on that site I have
tried and nothing seems to fix the problem.

NTfrs is installed and running. I have restarted the service a number
of times only to keep seeing the same replication errors.

Any other suggestions?

-----Original Message-----
Hello all. First off, thanks for taking the time to help out with
this problem I'm having.

Here's some background to my replication problem. I have a Windows
2000 AD domain in mixed mode called domain.local with 8 DC's, all in
differnt locations. Recently one of my DC's, I'll call this DC
STPAUL, started having corruption on the OS level (random win32
errors, control panel was corrupt, couldn't open properties for
anything, etc.) Anyway, I demoted STPAUL from AD and reinstalled
Windows and applied all the latest patches - SP4 and all critical
patches afterwards.

I ran DCPROMO on STPAUL and everything worked fine - I did not receive
any error messages. I recreated the Site, Subnet and Inter Site
transports for this location within AD Site and Services and made the
DC a Global Catalog. All this happened on a Saturday. On Monday when
I came in I found the event logs on this server were riddled with
errors. Most of them I have fixed but I have this nagging problem
that I have been unable to resolve.

I keep getting Event ID 13508:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 10/17/2003
Time: 10:35:09 AM
User: N/A
Computer: STPAUL
Description:
The File Replication Service is having trouble enabling replication
from HBO to STPAUL for c:\winnt\sysvol\domain using the DNS name
hbo.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name hbo.domain.local from
this computer.
[2] FRS is not running on hbo.domain.local.
[3] The topology information in the Active Directory for this replica
has not 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: 05 00 00 00 ....

I have spent the past 2 days working on this looking for an answer.
KB article Q272279 did not help. I have tried everything I can
possibly think of and I'm tempted to demote this server again then run
DCPROMO again.

A few odd things I have seen:

In AD Sites and Services ON the STPAUL server I can see the StPaul
Site, the Server, and NTDS Settings, and connections from STPAUL and
HBO. Replmon indicates replication is working successfully.

In AD Sites and Services ON the HBO server I can see the StPaul site,
the Server, but no NTDS Settings below the server icon. I am unable
to add them in manually.

This is telling me somewhere, somehow, something got messed up when I
demoted the server and added it as a DC when I reloaded Windows.
LostAndFoundConfig does not have anything inside the container. DNS
is working properly on each server including the STPAUL server.

Any ideas are welcome. I'm wondering if there is a quick fix to this
before I demote the server again and run DCPROMO again. One thing I
forgot to note is that when I reloaded Windows I gave the server the
exact same name and IP as before. Hopefully that's not a problem.

Jake
.

Hi Jake

Have you tried looking at the file replication service?
I have the same problem and I found out that the NTFrs
service is missing on one my servers.

regards
Jacob