Thank you Juan, I *don't* like that answer as much... ;).... However, that is what I finally did last night. Spun up a windows instance in the cloud, copied the SAS Software Depot to that new instance, and then installed the client packages there, where I could reach my SAS servers on the 'local' network. Unable to open the management console from my desktop (using Mobaxterm since our SAS is on Linux) due to the similar issues. Our direct access to the servers is via tunneling through a bastion server and though I set up a tunnel in Mobaxterm and was able to connect via a Mobaxterm PuTTY session, the sasmc command would not work. Still trying to figure out why SAS cares about the host name outside the LB. I would think that the LB would change the DNS entry/target host name on the URL to the real host (i.e., metadata server name) on the back-end, which means that our SAS should never see that 'external' (to the cloud) host name we are using on the corporate network. Thanks much, D
... View more