Verify FRS Dependencies

Before you can troubleshoot FRS, you must verify that the FRS dependencies are working properly on the server experiencing problems. If any of the dependencies are not working, any time spent troubleshooting FRS is futile.

After you verify these dependencies, proceed to Choose the Replication Type. If you are not sure how to check these dependencies, contact Microsoft Product Support Services for assistance.

DNS

• Use NETDiag to check for errors. (NETDiag is part of the Windows Support Tools.)
• If possible, point all FRS servers to one Windows 2000 DNS server for testing. For additional information about DNS, see the following articles:
  • 291382, "Frequently Asked Questions About Windows 2000 and Windows Server 2003 DNS" at http://support.microsoft.com/?id=291382.
  • 260371, "Troubleshooting Common Active Directory Setup Issues in Windows 2000" at http://support.microsoft.com/?id=260371.
  • 257623, "Domain Controller’s Domain Name System Suffix Does Not Match Domain Name" at http://support.microsoft.com/?id=257623.
  • 258832, "Cannot Join Windows 2000 Client to a Windows NT Domain" at http://support.microsoft.com/?id=258832.
  • 203009, "DNS Zone Transfer Between Windows 2000 and Windows NT 4.0 Fails" at http://support.microsoft.com/?id=203009.
  • 229840, "DNS Server’s Root Hints and Forwarder Pages Are Unavailable" at http://support.microsoft.com/?id=229840.
  • 246804, "How to Enable/Disable Windows 2000 Dynamic DNS Registrations" at http://support.microsoft.com/?id=246804.
  • 275278, "DNS Server Becomes an Island When a Domain Controller Points to Itself for the _Msdcs.ForestDnsName Domain" at http://support.microsoft.com/?id=275278.
  • 235689, "How to Troubleshoot 7062 Errors Logged in DNS Event Log" at http://support.microsoft.com/?id=235689.
  • 259277, "Troubleshooting Netlogon Event 5774, 5775, and 5781" at http://support.microsoft.com/?id=259277.

Active Directory replication

• Use Replmon and Dcdiag to check Active Directory replication. (Replmon and Dcdiag are part of the Windows Support Tools.)
• Check for NTDS connection objects by running TopChk and making sure objects are present, enabled, and that the replication schedule is on. For more information, see TopChk Remarks and Verify the FRS Topology As Stored in Active Directory.

Network connectivity

• FRS needs reliable links to move data around. If the links are slow or busy, you will run into replication problems.
• Use NETDiag to check to networking-related errors. (NETDiag is part of the Windows Support Tools.)
• Check for firewall and black hole routers. See the following articles for details:
  • 314825, "How to Troubleshoot Black Hole Router Issues" at http://support.microsoft.com/?id=314825.
  • 159211, "Diagnoses and Treatment of Black Hole Routers" at http://support.microsoft.com/?id=159211.
• Use Event Viewer from remote computers to check for RPC connectivity.
  • 319553, "How to Restrict FRS Replication Traffic to a Specific Static Port" at http://support.microsoft.com/?id=319553.
• Use Terminal Server session (if possible) to check for network connectivity.

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.