DFSR breaks after reboot

Gloria Gu 3,891 Reputation points
2020-07-16T07:16:22.707+00:00

I have set up a replication group and folder between two 2012R2 servers. Replication works fine until I reboot one of them. Then I get Error 1202 in the Events log with this message:

The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.

Additional Information:
Error: 160 (One or more arguments are not correct.)

I cannot tell which argument is not correct.

I am also puzzled why I was able to set up the replication initially, and it works fine, if the two systems can't talk to the domain controller.

I am not sure there is a shutdown timeout and that I am falling in to the 'Dirty shutdown' scenario because I can't find the events 1006 or 1008 indicating DFS stopping/stopped events. This is Windows Server 2012, so the hotfix for 2008 to change the DFS recovery should be applied. And, this is NOT a very active folder so, I expect there is nothing replicating at the time I issue a reboot.

And, when I try the wmic command to resume replication I get an error.

And, I get these messages after reboot.

20180806 16:09:10.500 2572 SYSM 3830 Migration::SysVolMigration::Connect [MIG] Trying to connect to Local or any writable Dc AD
20180806 16:09:10.500 2572 CFAD 311 Config::AdConnection::Connect Binding to dcAddr:\my.dc.ip.address dcDnsName:\my.dc.dns.name
20180806 16:09:10.500 2572 CFAD 143 Config::AdConnection::BindToAd Trying to connect. hostName:my.dc.dns.name
20180806 16:09:10.500 2572 CFAD 162 Config::AdConnection::BindToAd Bound. hostName:my.dns.host.name
20180806 16:09:10.500 2572 CFAD 199 Config::AdConnection::BindToDc Try to bind. hostName:\my.dc.domain.name domainName:<null>
20180806 16:09:10.500 2572 CFAD 3373 [ERROR] Config::DsSession::Bind Failed to DsBind(). dc:\my.dc.domain.name domainName:<null> Error:5
20180806 16:09:10.500 2572 CFAD 215 Config::AdConnection::BindToDc (Ignored) Failed to bind. hostName:\my.dc.domain.name domainName:<null> Error:[Error:5(0x5) Config::DsSession::Bind ad.cpp:streetAddress Access is denied.]
20180806 16:09:10.500 2572 CFAD 199 Config::AdConnection::BindToDc Try to bind. hostName:\my.dc.IP.address domainName:<null>
20180806 16:09:10.500 2572 CFAD 3373 [ERROR] Config::DsSession::Bind Failed to DsBind(). dc:\my.dc.IP.address domainName:<null> Error:87
20180806 16:09:10.500 2572 CFAD 215 Config::AdConnection::BindToDc (Ignored) Failed to bind. hostName:\my.dc.IP.address domainName:<null> Error:[Error:87(0x57) Config::DsSession::Bind ad.cpp:street address The parameter is incorrect.]
20180806 16:09:10.500 2572 W2CH 779 [WARN] ConfigurationHelper::PollAdConfigNow Failed to get migration status. Error:

  • [Error:160(0xa0) Migration::SysVolMigration::IsLocalComputerLongHornLevelDc migration.cpp:StreetAddress One or more arguments are not correct.]
  • [Error:160(0xa0) Migration::SysVolMigration::Connect migration.cpp:StreetAddress One or more arguments are not correct.]
  • [Error:160(0xa0) Config::AdConfig::ConnectToLocalDc ad.cpp:StreetAddress One or more arguments are not correct.]

So, Why am I able to create the DFSR group, and it works until reboot, then it breaks? If there is an AD parameter wrong, which is it, and why does it not find that when I create the replication group?

Thread source link: https://social.technet.microsoft.com/Forums/windowsserver/en-US/5a59e665-01f1-4369-996c-538d1c22a7b6/dfsr-breaks-after-reboot?forum=winserverfiles

Windows Server Storage
Windows Server Storage
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Storage: The hardware and software system used to retain data for subsequent retrieval.
631 questions
{count} votes

Accepted answer
  1. Xiaowei He 9,871 Reputation points
    2020-07-16T07:47:24.777+00:00

    Hi,

    Based on my knowledge, in general, after reboot dfs server, the server will contact the DC to find the dfs database and it should establish the dfs replication with other dfs servers again.

    In your scenario, it seems blocked after reboot. Now you have already disable firewall, it shouldn't be blocked then.

    I'm afraid for dedicated Support about such performance analysis you might need to contact Microsoft Customer Support Services (CSS).

    It is also appreciated that the other members in our forum can share their experience with us about this scenario.

    To obtain the phone numbers for specific technology request, please refer to the website listed below:

    https://www.microsoft.com/en-us/worldwide.aspx

    Appreciate your support and understanding.

    Best Regards,

    0 comments No comments

0 additional answers

Sort by: Most helpful