Q: When I try to connect using Azure Bastion, I can't connect to the target VM, and I get a black screen in the Azure portal.Ī: This happens when there's either a network connectivity issue between your web browser and Azure Bastion (your client Internet firewall may be blocking WebSockets traffic or similar), or between the Azure Bastion and your target VM. Q: Is file transfer supported with Azure Bastion?Ī: File transfer isn't supported at this time. For more information, see Connection Troubleshoot. To start, choose a source to start the connection from, and the destination you wish to connect to and select "Check". Network Watcher Connection Troubleshoot provides the capability to check a direct TCP connection from a virtual machine (VM) to a VM, fully qualified domain name (FQDN), URI, or IPv4 address. Q: I'm unable to connect to my virtual machine (and I'm not experiencing the problems above).Ī: You can troubleshoot your connectivity issues by navigating to the Connection Troubleshoot tab (in the Monitoring section) of your Azure Bastion resource in the Azure portal. It isn't supported for Azure AD-joined-only virtual machines. This is supported for domain-joined or hybrid-joined (both domain-joined and Azure AD-joined) virtual machines. When specifying the domain credentials in the Azure portal, use the UPN format instead of domain\username format to sign in. Q: I'm unable to connect to my Windows virtual machine that is domain-joined.Ī: Azure Bastion supports domain-joined VM sign-in for username-password based domain sign-in only. Unable to sign in to my Windows domain-joined virtual machine SHA256:c+SBciKXnwceaNQ8Ms8C4h46BsNosYx+9d+AUxdazuE key's randomart image is: Your public key has been saved in /home/ashishj/.ssh/id_rsa.pub. Your identification has been saved in /home/ashishj/.ssh/id_rsa. Ssh-keygen -t rsa -b 4096 -C ssh-keygen -t rsa -b 4096 -C public/private rsa key pair.Įnter file in which to save the key (/home/ashishj/.ssh/id_rsa):Įnter passphrase (empty for no passphrase): Make sure that you browse a key file that is RSA, DSA, or OPENSSH private key for SSH, with public key provisioned on the target VM.Īs an example, you can use the following command to create a new RSA SSH key: Q: When I try to browse my SSH key file, I get the following error: 'SSH Private key must start with -BEGIN RSA/DSA/OPENSSH PRIVATE KEY- and ends with -END RSA/DSA/OPENSSH PRIVATE KEY-'.Ī: Azure Bastion currently supports RSA, DSA, and OPENSSH private keys. Unable to use my SSH key with Azure Bastion If you don't add these rules, the NSG creation/update will fail.Īn example of the NSG rules is available for reference in the quickstart template.įor more information, see NSG guidance for Azure Bastion. For a list of required rules, see Working with NSG access and Azure Bastion. Q: When I try to create an NSG on the Azure Bastion subnet, I get the following error: 'Network security group doesn't have necessary rules for Azure Bastion Subnet AzureBastionSubnet".Ī: If you create and apply an NSG to AzureBastionSubnet, make sure you have added the required rules to the NSG. Unable to create an NSG on AzureBastionSubnet This article shows you how to troubleshoot Azure Bastion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |