J
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
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