Microsoft KB Archive/872964

= NT File Replication Service does not replicate file modifications to the replication Distributed File System (DFS) nodes or DFS link targets in Windows Server 2003 =

Article ID: 872964

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)

-





SYMPTOMS
When you modify a file in the shared folder of a domain-based Distributed File System (DFS) node or DFS link target, the modification is not replicated to the replication DFS nodes or DFS link targets. When you restart the NT File Replication service (NTFRS), the modification is replicated immediately.



CAUSE
This issue occurs because the firewall disconnects the remote procedure call (RPC) connection if the RPC connection is idle for 10 minutes. When the previous RPC connection calls the DsCrackNames function in the next polling interval, the NTFRS does not receive the RPC from the domain controller because the RPC connection is disconnected. This results in an RPC_S_CALL_FAILED runtime error. If this error occurs, NTFRS may guess the wrong replication partner computer name. This results in an Access Denied error. When this error occurs, NTFRS does not replicate the file modifications.



MORE INFORMATION
When NTFRS guesses the wrong replication partner computer name, the following NTFRS debug logs are generated:

 :DS: ERROR - DsCrackNames(cn=iis01,cn=computers,dc=student,dc=smu,dc=edu,dc=sg,00000002); WStatus: RPC_S_CALL_FAILED

 :DS: WARN: Guess NT4 Account Name forcn=iis01,cn=computers,dc=student,dc=smu,dc=edu,dc=sg

 :DS: Guessingstudent\IIS01$

Keywords: kbtshoot KB872964

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.