Domain logon error when link between remote RODC and central network is broken?

Question

Active Directory

There is a central office and a remote branch.
At the central office of PDC and BDC. On a remote branch RODC and a terminal server. RODC in dns has itself PDC, BDC. The terminal server in dns has RODC and provider.
End clients: computers outside the domain that connect via rdp to a terminal server with domain credentials. When the connection between the central office and the branch falls, people lose the opportunity to log in to the terminal server. Of the errors - when the connection is broken, NETLOGON is scolded, but this is normal when the connection is broken. According to the law of the genre, with short breaks, the RODC should have allowed connections, but no.
What could be wrong?
Caching has been enabled as stated in the first answer. Cached accounts already appear in the lists, but this did not solve the problem. Still, when the connection to the PDC / BDC fails, users lose the ability to connect to the domain and catch errors like NLA:

Answer 1

Enable caching on the RODC. By default, RODC does not cache user credentials:
https://docs.microsoft.com/en-us/previous-versions...
How to:
https://www.faqforge.com/windows-server-2016/confi. ..