Not why the Mac client feels the need to resolve the target name when it's told to use a RDG host (and provides no option to control this name resolution, as does the Windows RDP client). This explains why the Mac client always sees the same target host, but Note: refers to the external IP address of tmg01 RDP (0): Resolved '-bdc01.fqdn' to '' using NameResolveMethod_DNS(1) and if within your network, all your IP addresses are attributed through a correctly tracked process of IP managment: DHCP or radius or 802. For some reason, all internal host names are being resolved to the same external IP address. Checked VNCs support site, but they have outdated. The obvious solution here would be to approve VNC logins: The same way SSH is enabled, but clicking the '+' brings up a drop-down menu to select an application. If the name resolves to a valid IP address, the RDP client will use a direct connection The connection fails with 'The computers network could not be contacted.' With 'Stealth Mode' disabled, VNC still will not connect. It seems that even if the Mac RDP client is told to use a gateway to reach the target host, it will still try to perform name resolution before communicating with the gateway. I was finally able to read the RDP client log file and it's clear that it's resolving the remote target as a public IP address which leads to a single IP address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |