I cannot connect to my virtual machine: 1,2,3 error
Problem
I am getting an error "Remote Desktop can’t connect to the remote computer for one of these reasons: 1. Remote access to the server is not enabled; 2. The remote computer is turned off; 3. The remote computer is not available on the network."
Possible solutions
This error is a common error that is generated when there are problems with connection to a running virtual machine. It can have many reasons why this error message is generated. Here we have listed some of the most common reasons and possible solutions. The top 4 are the most likely causes and solutions.
Use Bastion
The easiest solution is to use Bastion to connect to your VM. Learn how to connect with your VM through Bastion here: Azure Bastion to connect to your VM.
Reboot your virtual machine
Just created a VM and want to connect with it right away? Then this error might pop up as well. Deallocate and start your virtual machine again and download a new RDP file. Wait at least a minute before opening an RDP connection and try to login again.
Connecting too fast to the VM after it goes to status running.
There is a slight delay between status running and RDP connection. If you are trying to log in too fast, the 1,2,3 error will appear. Wait at least a minute before opening an RDP connection.
You are connecting withing your institution that doesn't allow RDP
In order to connect to your virtual machine, you are requested to download and open an RDP file. Some institutions do not allow the usage of RDP connections within their network. When RDP is blocked, 1,2,3 error is triggered. Please try connecting to your virtual machine using another network (e.g. Eduroam) or personal computer at home. Please contact your support team for further instructions on how to use RDP connections within your institution's network.
EMC users
Erasmus MC workspaces require an additional security inbound rule. If workspace or the virtual machine was recently created, please create a ticket for the support team. The preferred way for connecting to a VM is however Azure Bastion.
AUMC users
RDP is blocked by AUMC firewall for safety reasons. It is always recommended to use Bastion instead: Azure Bastion to connect to your VM.
UMCG users
UMC Groningen does not allow RDP connection within its network. When working at the office, please connect to myDRE using another network such as Eduroam with your personal computer. Alternatively, use Bastion to connect to your VM.
LUMC users
LUMC does not allow RDP connection within its network. When working at the office, please connect to myDRE using another network such as Eduroam with your personal computer. Alternatively, use Bastion to connect to your VM.
UMC Utrecht users
For UMC Utrecht users, it is always recommended to use Bastion instead of RDP: Azure Bastion to connect to your VM's. For UMC Utrecht's "Virtuele Werkplek", it is not possible anymore to connect with RDP to DRE VM's. There connecting via Bastion is the only option.
Wrong password
This message is also triggered when the wrong password is entered, please make sure that you are connecting to the RDP with the correct password for your @mydre.org login.
Multiple users at once
This message is also triggered when more than one user is trying to open an RPD connection at the same time (within one minute). When working with two users in one virtual machine simultaneously, do not try to log in at the same time, wait at least a minute before opening an RDP connection after the first user has accessed the virtual machine.
Are you using a VPN connection?
Please try to disable your VPN connection and try again.
None of the above applies to me, but:
I am experiencing problems only with this virtual machine but I am able to connect to other virtual machines
- this is a newly created virtual machine, never used before --> create a new VM and delete this one
- everything worked fine, one day VM became very slow, non-responsive --> create a new VM and delete the old one or contact support team for help
I am still not able to login
Please create a ticket for the support team and please include all relevant details:
- name of the workspace (e.g. dws-1234-XXX)
- name of the virtual machine (e.g. dws1234xxxserver1)
- what changed?
- Which user(s) are affected?
- where are you trying to connect from?
- Are you experiencing these problems with other virtual machines as well, also in other workspaces?
- Are you using your own personal computer or computer or a device controlled by your institution?
Related Articles
Virtual Machine Types
This article provides a simplified overview of Virtual Machine types available in Microsoft Azure. For a full overview, please have a look at https://azure.microsoft.com/en-gb/pricing/details/virtual-machines/series/. Make sure to select Region: West ...Network Level Authentication (NLA) error
The problem Incidentally, users can encounter the following error when trying to connect to the Virtual Machine (VM): The solution We have recently identified the cause of this error. The solution is known to us, however it is not self-service for ...[Mitigated] Adding a Virtual Machine: Templates not found error
First version: 2024-03-26 @ 08:38 Last updated: 2024-03-26 @ 11:04 Last change: Added the mitigation, moved article to resolved. What happened? This morning, we found that templates for Virtual Machines (VMs) are not loading correctly and therefore ...The connection was denied because the user account is not authorized for remote login
The problem Incidentally, users can encounter the following error when trying to connect to the Virtual Machine (VM): The solution This error occurs when user groups are not correctly added to the VM. In the user group it is defined which user ...Generalize a VM
Use this process only if you want to create a template for your own Workspace. If you want to create a template for the whole organisation, please contact your local ST member. Introduction Installing the same software on your VM can be tedious and ...