Open David-Noble-at-work opened 1 year ago
Thank you for opening this issue, we will look into it.
Hi @David-Noble-at-work Find similar issue https://github.com/Azure/azure-cli/issues/23965. | ||
---|---|---|
Issue title | bastion rdp using azure cli | |
Create time | 2022-09-21 | |
Comment number | 13 |
Possible solution:
The error message you are seeing is related to the WinDLL
function from the ctypes
module, which is not available on non-Windows platforms. As mentioned in the previous issue, the bastion rdp
command works best on Windows, and for other operating systems like macOS and Linux, you can use the bastion tunnel
command and then use the client of your choice.
To use the bastion tunnel
command, you can follow the steps mentioned in the Azure documentation:
az network bastion tunnel
command.Please note that signing in using an SSH private key stored in Azure Key Vault isn’t supported with this feature. Before signing in to your Linux VM using an SSH key pair, download your private key to a file on your local machine.
I hope this helps!
Please confirm if this resolves your issue.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @bastionsuppgithub.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @josephkwchan, @jennyhunter-msft.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @bastionsuppgithub.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @josephkwchan, @jennyhunter-msft.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @bastionsuppgithub.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @josephkwchan, @jennyhunter-msft.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @bastionsuppgithub.
@yonzhan Thank you for the recommendation to use this command to workaround the cross-platform bug in az network bastion rep
:
az network bastion tunnel --name "$bastion_name" --resource-group "$bastion_resource_group" --target-resource-id "$virtual_machine_resource_id" --resource-port 3389 --port 50022
I see that I can establish a tunnel, but that my vm is unavailable on port 3389. What do you recommend?
Describe the bug
Please help me to understand this stack and address the issue. Note the reference to this import name:
WinDLL from ctypes
:Related command
Here are the commands that I executed:
Errors
Issue script & Debug output
Expected behavior
The native RDP client on macOS Sonoma starts.
Environment Summary
Additional context
This problem does not manifest on Windows. It seems every version of azure-cli you release has got show stopping issues for me on Linux and macOS. Are you testing sufficiently on these platforms? Have you thought about disabling features with a note when they are untested or unsupported on non-Windows platforms?