All users are inexplicably unable to login to an Azure VM. Yesterday it was working fine.

Seth Spearman 0 Reputation points
2024-11-13T23:15:10.03+00:00

An azure server that I logged into yesterday is now showing this error when ANYONE tries to login to it. Wondering if Patch Tuesday might be the culprit: "The target machine is either currently unreachable or username/password is not correct. Please re-verify your credentials. If the problem persists, please contact support." I do not believe this server is on a domain and is using all local credentials for login. This is an important server and is we are all currently locked out.

The server is running because we can get to hosted APIs on the machine, but we cannot login remotely to the machine. RDP is disabled and we have to use Bastion.

Azure Bastion
Azure Bastion
An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.
293 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sai Prasanna Sinde 6,645 Reputation points Microsoft External Staff Moderator
    2024-11-14T06:29:01.2266667+00:00

    Hi @Seth Spearman,

    Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

    • The error message "The target machine is either currently unreachable or username/password is not correct" usually indicates that there is an issue with the credentials, or the target machine is not reachable.
    • Please make sure that you have entered the correct username and password for the target machine. Also, ensure that the target machine is running and is reachable from the Azure Bastion host. You can try to ping the target machine from the Azure Bastion host to verify the connectivity.
    • If the issue persists, you can try resetting the password for the target machine and try again.
    • You can check your NSG on the VM subnet or nic whether you are allowing inbound access from Bastion subnet to your VM.
    • Please check if you have any firewalls or any network configuration changes that could have occurred recently impacted this.
    • 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. 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.

    Reference: https://learn.microsoft.com/en-us/azure/bastion/troubleshoot#connectivity

    Kindly let us know if the above helps or you need further assistance on this issue.

    Regards,

    Sai Prasanna.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.