On a Windows based computer, appears the following error in Remote Desktop Connection: “Your computer could not connect to console session on the remote computer because you already have a console session in progress”.
This tutorial contains instructions to resolve the following Remote Desktop Connection error: “Your computer could not connect to console session on the remote computer because you already have a console session in progress”.
How to FIX: Remote Desktop Connection Couldn’t Connect because you Already have a Console Session in Progress.
The error “Your computer could no connect to console session on the remote computer because you already have a console session in progress”, is caused because one of the network adapters on the local computer has the same IP address with the computer that you are trying to connect to, through the remote desktop. To fix the problem, follow the steps below:
1. Open Command Prompt as Administrator.
2. Give the following command to view the assigned IPv4 Addresses on your PC.
3. Now locate the network adapter that has the same IP address as the computer you are trying to connect to through RDP.
4. When you find which local LAN adapter has the same IP address as the RDP host machine, proceed and change the static IP address of that adapter.
* Note: If the IP address is assigned by a DHCP server, then specify manually a different static IP address, or restart your router, or configure the DHCP server to give IP addresses to a range that does not include the IP address of the RDP host.
That’s all folks! Did it work for you?
Please leave a comment in the comment section below or even better: like and share this blog post in the social networks to help spread the word about this solution.
