How to fix the strange behavior of Windows Server 2016 - Distributed File System?

Question

Distributed File System

Hello. Question of the Day:
Windows Server 2016 is everywhere.

Domain structure:

City No. 1:
Main domain controller:
Win Srv 2016 The
DFS role has been raised.

City #2:
Slave domain controller:
Win Srv 2016 The
DFS role has been raised.

City #3:
Slave domain controller:
Win Srv 2016 The
DFS role has been raised.

On each domain controller, the DFS role is raised, where a namespace is added, and two folders lead to a central server.
But one folder - Public - everyone has their own in their domain. So that users from Moscow do not pull the 1C installer from Syktyvkar.

Everything works great everywhere:
Users of Moscow open the path \\id.srv.oursite.ru\DFS\Public and see what is on the server in Moscow in public.

Syktyvkar residents open the ball along the same path, and already see our place to the ball.

But damn it! We have an RDP terminal server in Syktyvkar in the domain, and here on it - for some reason, Moscow Public opens and not our local one.

I'm not even going to put my mind to what actually. And how to treat, and how to diagnose.

Does anyone have any ideas? I would be grateful if you share your experience.

Answer 1

Dfs works through AD Sites. What site does your RDP server belong to? Its ip is described in ad Sites subnet?