Windows Forum

Ask something
Discussion Locked

Cannot Connect To Terminal Services

0 helpful
7 replies

by dragon emperor 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
A client has a system that had XP Home on it. Their temporary license expired. They have now upgraded to XP Pro. When attempting to connect to Terminal Services they get the message "The client could not connect. You are already connected to the console of this computer. A new console session could not be established."

7 replies

by dragon emperor

I have tried renaming their computer, to see if it appears on the Licensing Server. It does not. Disabling the Windows Firewall does not help. The target server is assessible across the VPN, they just can't connect to Terminal Services. No other users have had problems, but this is also the 1st upgrade we have had.

by dragon emperor

I have already checked out both of those. Removing the TS license had no effect. The Terminal Server had all of the patches installed before the 1st client ever connected.

by jmar17

We had a similar problem where a user got the same error message, "The client could not connect...". What I found at http://www.remotenetworktechnology.com/ow.asp?Remote_Network_Home%2FRemoteDesktop%2FFrequentlyAskedQuestionsPage
was a workaround that allowed the user to connect with the remote desktop connection.
The information is in the section titled, "How can I tunnel a Remote Desktop Session using SSH?" I followed the first 7 steps and was able to connect through a remote desktop connection to the user's computer.

Jeff

by dragon emperor

That is not the issue we are having. The client originally had Windows XP Home. Their temporary license expired. They upgraded to Windows XP Pro (which has a built-in license regarding Windows 2000 Terminal Services). However they are still unable to connect. The link you sent is apparently a common issue, just not the one we have.

This discussion is closed to new replies.