remote desktop locks the PC from another session

[graysky]

I originally posted here describing this odd problem with remote desktop. What happens is when I remote desktop into the target machine, everything works fine until I close the session which locks the target machine's screen. If I use the machine locally after going in through remote desktop, and then later in the day, try to get in remotely again, I cannot - I am presented with a login screen through remote desktop and I enter my password but after clicking OK, nothing happens. I cannot connect via remote desktop or via VNC when the machine is in this state. I can get in just fine from the local keyboard and if I leave the machine unlocked, I can get in through VNC, but never again with remote desktop until I reboot. Somehow, the way remote desktop is locking the screen also locks out VNC connections. If I try to hit the "locked" box with VNC, I just get a black screen that I'm unable to unlock it through VNC.

If I reboot and never use remote desktop, VNC works flawlessly and I can lock/unlock with no problems. Some how when I log out with remote desktop it is "super locking" the machine such that the only way I can get back in is from the local keyboard. The final piece of info that doesn't make any sense to me is this: if I reboot the target machine AND I don't use it from the local keyboard at all, I can get in and out many times with remote desktop. This "super locked" state only happens once I use the machine from the local keyboard and then from remote desktop.

Does anyone have any thoughts on this perplexing behavior?

[nmX.Memnoch]

An RDP session locks the console because XP only supports one active login at a time. You can either use the console or you can connect through RDP, but not both at the same time.

I suspect there may be some weird RDP policies set. Check all of the "Terminal Server" items in GPEDIT.MSC. Better yet, since GPEDIT.MSC doesn't show domain settings, run RSOP.MSC and see if there are any "Terminal Server" items set. The settings are located under both Computer and User configurations uder Administrative Templates > Windows Components > Terminal Services. If there are settings and the GPO Name is anything other than "Local Group Policy" then it's a domain policy.

I haven't ever known any policies to cause this sort of problem, but it's worth checking out.

Also, what's the version of your RDP client?

[graysky]

An RDP session locks the console because XP only supports one active login at a time. You can either use the console or you can connect through RDP, but not both at the same time.

Yeah, I know that... I was trying to make it known that there seems to be a difference between when it locks the workstation and when a users locks it: when the user locks it, I can get in via remote desktop. When it locks it, I cannot.

I suspect there may be some weird RDP policies set. Check all of the "Terminal Server" items in GPEDIT.MSC. Better yet, since GPEDIT.MSC doesn't show domain settings, run RSOP.MSC and see if there are any "Terminal Server" items set. The settings are located under both Computer and User configurations uder Administrative Templates > Windows Components > Terminal Services. If there are settings and the GPO Name is anything other than "Local Group Policy" then it's a domain policy.

I haven't ever known any policies to cause this sort of problem, but it's worth checking out.

Also, what's the version of your RDP client?

Thanks for the advice, I'll check it out on monday when I'm back in the office. I'm not sure what version it's running. Both machines are WinXP SP2. How can I get it to display a version number?

[nmX.Memnoch]

When you run the RDP client there should be a Help > About menu option. Try downloading the latest client:

http://www.microsoft.com/downloads/details...;DisplayLang=en

I doubt the client version has anything to do with it unless, and again this goes back to the GPO settings, the connection security has been set to anything other than Client Compatible.

[graysky]

Thanks for the link. Is the screenshot below depicting what you're referring to as the "client"? If so I can't find any menus in it at all and have no idea what version I'm running

Thanks.

[nmX.Memnoch]

You have an "older" client. The 6.0 client looks a little different than that.

If you click the little icon on the upper left you'll get a menu. One of the options will be "About".

[graysky]

I got the new client, but unfortunately I can't install it on the machine since I don't have admin rights. I tried installing it on another machine and copying the mstsc.exe and dll out of the windows dir but it can't run like that

A related question: Is there anyway I can manually install this (i.e. copy files from the archive somewhere?)

Edited March 22, 2007 by graysky