Open ananace opened 6 years ago
The current ugly hack to solve this issue will cause issues when using direct IP addresses to connect to a cluster, or if two cluster hosts are on different domains.
Perhaps something could be done to instead look up the host FQDN or IP on the current connection, use that value for the connection;
[System.Net.Dns]::GetHostByName('example-host')
This seems to be necessary to properly support clusters
Currently, trying to access a second computer in a PSRemoting session with most transports will fail, like such;
This can be solved by setting up advanced CredSSP chaining or Kerberos credential passing. But a simple solution could also be to launch multiple connections by reusing the original credentials, running the given command on all provided computers, and then aggregating the results.