Replication Problem.

[Ashley Gibbon]

I have on server CNB-04 that will not replicate. Its IP is
10.60.0.9. 255.255.0.0

I am on subnet 10.15.0.0 255.255.0.0. Up till this moment
I have only had one site, despite running over a WAN, and
to differing subnet addresses. I have now just created
sites and subnets, and moved servers into the respective
locations. Now everything seems to have stopped working. :-
). Anytime I have used sites in the past it has screwed up
repication completely.

Replication monitor tell me that it has not replicated for
105 attempts.

DNS entries are correct on all servers for all servers. I
can ping by name all servers.

DNSLint confirms all DNS entries are correct.

When I attempt to replcate usinf Replmon, I get RPC server
is unavailable.

When I try and add CNB-04 to the replecation monitor on
say CNB-01, replecation monitor hangs up then give CNB-04
cannot be contacted or you do not have sufficent
permissions. But I can ping it.

At another time I added the server and got yellow
exclaimation marks next to it in Replmon.

All Microsofts tools indicate no problems, DCDiag and
DNSLint.

Please help, what should I try next?

Some messages i am getting in Event viewer are below.
-----------------------------------------------------------
-----------------------------------------------------------

The File Replication Service is having trouble enabling
replication from CNB-HARLAND to CNB-00 for
c:\winnt\sysvol\domain using the DNS name cnb-
harland.cnbmd.com. FRS will keep retrying.
Following are some of the reasons you would see this
warning.

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

----------------------------------------------------------

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

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

 

[Karin Galli [MS]]

Check if you have set the NTFRS service to run with the Local System Account


Cheers.


--
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

I have on server CNB-04 that will not replicate. Its IP is
10.60.0.9. 255.255.0.0

I am on subnet 10.15.0.0 255.255.0.0. Up till this moment
I have only had one site, despite running over a WAN, and
to differing subnet addresses. I have now just created
sites and subnets, and moved servers into the respective
locations. Now everything seems to have stopped working. :-
). Anytime I have used sites in the past it has screwed up
repication completely.

Replication monitor tell me that it has not replicated for
105 attempts.

DNS entries are correct on all servers for all servers. I
can ping by name all servers.

DNSLint confirms all DNS entries are correct.

When I attempt to replcate usinf Replmon, I get RPC server
is unavailable.

When I try and add CNB-04 to the replecation monitor on
say CNB-01, replecation monitor hangs up then give CNB-04
cannot be contacted or you do not have sufficent
permissions. But I can ping it.

At another time I added the server and got yellow
exclaimation marks next to it in Replmon.

All Microsofts tools indicate no problems, DCDiag and
DNSLint.

Please help, what should I try next?

Some messages i am getting in Event viewer are below.
-----------------------------------------------------------
-----------------------------------------------------------

The File Replication Service is having trouble enabling
replication from CNB-HARLAND to CNB-00 for
c:\winnt\sysvol\domain using the DNS name cnb-
harland.cnbmd.com. FRS will keep retrying.
Following are some of the reasons you would see this
warning.

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

----------------------------------------------------------

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

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

 

[Alfredo G]

I have a similar problem indicating that RPC Server is
unavailable. I think this is because the clocks on the
servers are not syncronized and kerberos can not
authenticate. Use "net time". You have to define one
server to manage the hour, and then sincronize the others
with that server.

Let me know if this function.

-----Original Message-----
I have on server CNB-04 that will not replicate. Its IP is
10.60.0.9. 255.255.0.0

I am on subnet 10.15.0.0 255.255.0.0. Up till this moment
I have only had one site, despite running over a WAN, and
to differing subnet addresses. I have now just created
sites and subnets, and moved servers into the respective
locations. Now everything seems to have stopped working. :-
). Anytime I have used sites in the past it has screwed up
repication completely.

Replication monitor tell me that it has not replicated for
105 attempts.

DNS entries are correct on all servers for all servers. I
can ping by name all servers.

DNSLint confirms all DNS entries are correct.

When I attempt to replcate usinf Replmon, I get RPC server
is unavailable.

When I try and add CNB-04 to the replecation monitor on
say CNB-01, replecation monitor hangs up then give CNB-04
cannot be contacted or you do not have sufficent
permissions. But I can ping it.

At another time I added the server and got yellow
exclaimation marks next to it in Replmon.

All Microsofts tools indicate no problems, DCDiag and
DNSLint.

Please help, what should I try next?

Some messages i am getting in Event viewer are below.
---------------------------------------------------------- -

----------------------------------------------------------

-

The File Replication Service is having trouble enabling
replication from CNB-HARLAND to CNB-00 for
c:\winnt\sysvol\domain using the DNS name cnb-
harland.cnbmd.com. FRS will keep retrying.
Following are some of the reasons you would see this
warning.

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

----------------------------------------------------------

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

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

 

[Guest]

Thankyou for looking at my problem.

Time on all servers is exactly the same, as is the date.

NTFRS is set to run as Local System Account, on all
servers.

NTFRS and RPC is actually running on all servers.

Thanks


Ashley

-----Original Message-----
I have a similar problem indicating that RPC Server is
unavailable. I think this is because the clocks on the
servers are not syncronized and kerberos can not
authenticate. Use "net time". You have to define one
server to manage the hour, and then sincronize the others
with that server.

Let me know if this function.

-----Original Message-----
I have on server CNB-04 that will not replicate. Its IP is
10.60.0.9. 255.255.0.0

I am on subnet 10.15.0.0 255.255.0.0. Up till this moment
I have only had one site, despite running over a WAN, and
to differing subnet addresses. I have now just created
sites and subnets, and moved servers into the respective
locations. Now everything seems to have stopped working. :-
). Anytime I have used sites in the past it has screwed up
repication completely.

Replication monitor tell me that it has not replicated for
105 attempts.

DNS entries are correct on all servers for all servers. I
can ping by name all servers.

DNSLint confirms all DNS entries are correct.

When I attempt to replcate usinf Replmon, I get RPC server
is unavailable.

When I try and add CNB-04 to the replecation monitor on
say CNB-01, replecation monitor hangs up then give CNB- 04
cannot be contacted or you do not have sufficent
permissions. But I can ping it.

At another time I added the server and got yellow
exclaimation marks next to it in Replmon.

All Microsofts tools indicate no problems, DCDiag and
DNSLint.

Please help, what should I try next?

Some messages i am getting in Event viewer are below.
---------------------------------------------------------

-

-

-

-

The File Replication Service is having trouble enabling
replication from CNB-HARLAND to CNB-00 for
c:\winnt\sysvol\domain using the DNS name cnb-
harland.cnbmd.com. FRS will keep retrying.
Following are some of the reasons you would see this
warning.

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

--------------------------------------------------------- -

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

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

.