• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Remote Desktop Problem

49erinnc

Platinum Member
I haven't tinkered with any settings or anything which may have screwed something up. However (and totally out of the blue), when I try to use "Remote Desktop" on my laptop to connect to my desktop, I'm getting the following message:

The client could not connect. You are already connected to the console of this computer. A new console session cannot be established.

Never got that before and I'm not already connected to the desktop via the Remote Desktop utility. I get this error when I click on "Connect" in the Remote Desktop Connection box (the one that displays the IP address.

Any ideas? My wireless connection is strong and I have no problem getting online with the laptop. Just can't use Remote Desktop like I normally do because of this issue.
 
are you logged into the desktop at the local keyboard? If I remember correctly XP will only support one connection including the keyboard.
 
Originally posted by: TonyRic
are you logged into the desktop at the local keyboard? If I remember correctly XP will only support one connection including the keyboard.

Pardon my ignorance but can you clarify? I logged off my host/desktop and was just on the XP log in screen but still cannot connect on my lappy. Prior to getting that error message, I could have all sorts of applications running on my desktop while logged in and still connect to it from the laptop without a problem.
 
Originally posted by: TonyRic
are you logged into the desktop at the local keyboard? If I remember correctly XP will only support one connection including the keyboard.

Yeah but the remote session should kick off the local user and take over the session.

Try stopping and starting the terminal service.

start-->run-->type in services.msc locate terminal services and stop it and then start it again.
 
Try this:

Start -> Run ->

mstsc /v:<name or IP address>

Specifying /console will connect you to the console session, leaving it off will lock the console session and allow you in.

Worth a try before you start reloading stuff.
 
Back
Top