Remote control default connection via FQDN not NETBIOS. This would allow remote control across multiple trusted domain easily using the cons
When trying to use Remote Control from start->remote control in the console, it is not possible to connect to machine that is not part the same domain as the server as netbios is used. If the FQDN is called than it would be possible to connect to devices in trusted domains.
martin
shared this idea
5 comments
-
Karl Thornley
commented
Can't you work around this by adding the other domains to your DNS suffix search order?
-
Mahmoud87
commented
Hi guys the below link explains how to get this to work until Microsoft fix the issue.
-
Mahmoud87
commented
Just wow Microsoft this request since Feb 14, 2017, yet a year and half later no appropriate solution. Hopefully you guys can fix this simple issue soon.
-
Jon Warnken
commented
This would also be useful for Manage Out for Direct access connected clients.
-
William
commented
I agreed.CMrCViewer shouldn't use NetBIOS for resolution, it fails with DirectAccess clients among other problems.