NTFRS PROBLEM

[Guest]

I am having a problem with FRS on one of our domain controllers. I am getting
the following error on any dcs that try to replicate with the problem server.
DNS is working fine and so is ping. :

The File Replication Service is having trouble enabling replication from DC1
to DC2 for c:\winnt\sysvol\domain using the DNS name DC1 FRS will keep
retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC1 from this computer.
[2] FRS is not running on DC1
[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.

Any ideas or miracle fixes any one?
thanks,

 

[Guest]

I am having a problem with FRS on one of our domain controllers. I am getting
the following error on any dcs that try to replicate with the problem server.
DNS is working fine and so is ping. :

The File Replication Service is having trouble enabling replication from DC1
to DC2 for c:\winnt\sysvol\domain using the DNS name DC1 FRS will keep
retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC1 from this computer.
[2] FRS is not running on DC1
[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.

Any ideas or miracle fixes any one?
thanks,

Hi Paulo,

I think I have seen this problem before on our Domain Controllers. I think
you will find your Domain Controllers use themselves as their Primary DNS
server.

When the DC starts up it tries to start the services (NTFRS and DNS Server)
at the same time and you cannot resolve the name. This is a known issue and
can be quite easily fixed.

There are two proper ways to fix it.

The first is to set your primary DNS server to be the IP Address of a
DIFFERENT Domain Controller / DNS server which is authoritative for your
domain.

The second is to set a 'dependancy' on the FRS service startup to wait for
the DNS service to start. That way FRS will ALWAYS wait for the DNS server
to be available before trying to connect.

The link to explain how to modify dependancies is below.
http://support.microsoft.com/default.aspx?scid=kb;en-us;193888

Hope it helps...

DJW

 

[Guest]

I tried changing the primary DNS, but no joy. I am able to resolve the FQDN
ok. Not sure what else to try here. Any ideas?

ta,
Paul

I am having a problem with FRS on one of our domain controllers. I am getting
the following error on any dcs that try to replicate with the problem server.
DNS is working fine and so is ping. :

The File Replication Service is having trouble enabling replication from DC1
to DC2 for c:\winnt\sysvol\domain using the DNS name DC1 FRS will keep
retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC1 from this computer.
[2] FRS is not running on DC1
[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.

Any ideas or miracle fixes any one?
thanks,

Hi Paulo,

I think I have seen this problem before on our Domain Controllers. I think
you will find your Domain Controllers use themselves as their Primary DNS
server.

When the DC starts up it tries to start the services (NTFRS and DNS Server)
at the same time and you cannot resolve the name. This is a known issue and
can be quite easily fixed.

There are two proper ways to fix it.

The first is to set your primary DNS server to be the IP Address of a
DIFFERENT Domain Controller / DNS server which is authoritative for your
domain.

The second is to set a 'dependancy' on the FRS service startup to wait for
the DNS service to start. That way FRS will ALWAYS wait for the DNS server
to be available before trying to connect.

The link to explain how to modify dependancies is below.
http://support.microsoft.com/default.aspx?scid=kb;en-us;193888

Hope it helps...

DJW