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?
--From Ten Forums
For the RDP users, it’s not strange to run into various problems or errors when you control a PC from another PC, such as the error shown above. It is said that the error is mainly caused by one of the network adapters on your computer having the same IP address with the PC you want to connect through Remote Desktop (RDP). Briefly, you get wrong with the IP address of the remote PC. Moreover, the blocks of the firewall also can be another reason causing the error.
How to fix “Your computer could not connect to another console session”?
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. It’s necessary to 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
Meeting with RDP error seems annoying enough to every user, let alone it requires a large amount of time to search for the solutions to fix the issue. It makes you much sadder if you didn’t fix it even though you tried it one by one. Is there any way to efficiently RDP to a server? Absolutely! You can try free third-party remote access software-- AnyViewer, to help us easily avoid the RDP error.
Step 1. Download and install AnyViewer on both computers, open it, and then you can see as the following picture.
Step 2. On the host computer, click on Settings > Recipient, and then tick the 3rd option “Set my security code”, type the security code and then click on “OK”. (You can save the security code so that the next connection is more convenient.)
Step 3. On the local PC, input the device ID of the remote PC, and then click on “Connect”.
Step 4. There will be a window popped up on the local PC, choose the 2nd one, and then input the security code, click on “OK”.
Step 5. Now you can connect remotely.
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.