[Full Guide] How to Fix Your Computer Could not Connect to Another Console Session
This tutorial aims to provide 4 solutions to fix the RDP error “Your computer could not connect to another console session” and analyze the causes of the error. Keep reading.
By Ellie / Updated on March 27, 2023
Your computer could not connect to another console session
{I was trying to connect my PC to the network folder to pass some files, and a message popped up saying: "Your computer could not connect to another console session on the remote computer because you already have a console session in progress." Any suggestions to fix the issue?}
- Question from Ten Forums
Meeting into RDP errors when you control a PC from another PC is fairly annoying. It is said that the error is mainly caused by one of the network adapters on your computer having the same IP address as the PC you want to connect through Remote Desktop (RDP). Moreover, the blockage of the firewall also can be another reason causing the error.
How to fix “Your computer could not connect to another console session”
To fix "Your computer could not connect to another console session on the remote computer" on Windows 10, 11... here we provide you with 4 solutions to help you out of the issue.
Solution 1. Add a user in System Properties
Adding the object user in System properties can make the process of your Remote Desktop Connection smoother and avoid many troubles.
Step 1. Press Win + R and then input “sysdm.cpl” and then hit “OK”.
Step 2. Locate the "Remote" tab, and then tick “Allow remote connections to this computer” and select "Apply".
Step 3. Choose “Select Users...” then.
Step 4. Click on “Add...” and then click on "OK". Enter the object name and then click on “OK”. (If you don’t know the object name you can find in “Advanced...”.
Solution 2. Configure IP address and flush DNS on the host PC
We mentioned that it may be because you didn’t write the correct IP address of the remote PC. Therefore, we can configure the correct IP address and flush DNS on the host PC.
Step 1. Search "cmd" in the search box and select “Run as administrator”.
Step 2. Enter the following command line in the CMD.
Step 3. Reboot your PC and check whether your problem has been fixed.
Solution 3. Turn off Windows Firewall
The blockage of the Firewall can lead to the issue, too. If the solutions above don’t solve the problem, trying to turn off Windows Firewall can be a shot.
Step 1. Search "Firewall" in the search box and open it and then locate “Turn Windows Firewall on or off”.
Step 2. Choose "Turn off Windows Defender Firewall".
Solution 4. Resort to third-party remote access software
Is the RDP error "Your computer could not connect to another console session" on the remote computer has been fixed. If you are not or you don't want to take too much time on it, we recommend an efficient way to RDP to a server-- AnyViewer, which is a free third-party remote access software.
Step 1. Download it. Install and run the utility on both the host computer (the recipient) and the client computer (the controller). Make sure that the two PC are connected to the network.
Step 2. Sign up for an AnyViewer account and sign in to the account on the two computers. The PC will be assigned to the account automatically after login.
Note: To access the remote computer in privacy mode (the screen of the remote PC will be black and the keyboard & mouse of the remote PC will be disabled), you need to upgrade to an advanced plan.
Step 3. Then, click "Device" and find out the remote PC that you want to access. Click "One-click control" to get one-click remote access to the remote PC.
Step 3. Then you can see the desktop of the remote computer and take operations as if you were sitting in front of it.
Conclusion
Here we introduce 4 solutions for the error “Your computer could not connect to another console session”, like configuring the IP address, flushing DNS, and so on. When it comes to the most efficient and reliable one to remotely control, I recommend free access software, AnyViewer, to give you an amazing experience.
