Is there a way to stop RDP from kicking the current user in XP?

[chemwiz]

Is there any way to configure RDP to at least tell a user someone else is connected, or to just disallow the login if another user is on already? We have an XP Pro box running only one app that 7 people need to connect to, but it's aggravating getting booted off with no warning. Or is there a program better suited to this?

Sorry, I think I wasn't being clear enough. I only want one user to be logged in at a time, I don't want multiple connections. But Remote Desktop just kicks off the current user and let's the new one on. I think Vista gives you an option when you login to either kick the current user or else not connect. That's all I need, either a way to block a new connection, or give the user a choice of aborting.

 

[Navid]

Citrix may be?

 

[armstrda]

I think you would need a Windows Server 2003 box with multiple terminals to support that. As far as I know, XP only has 1 terminal available... However, I'd be interested to know how to do this if it's possible.

 

[nova2]

if you do actually need multiple RDP sessions then you can use winconnet xp pro v2.x but not sure if it works on winxp SP3. it does work fine on SP2.

 

[Gooberlx2]

google search "xp pro concurrent remote desktop session"

Here's one result.

I think you adjust the number of allowed sessions in the group policy editor somewhere.

 

[chemwiz]

I don't need to have multiple users on there, I just want whoever is connected to not get bumped off. Or else a warning to the person signing on that somebody is already using it. I've used the hack for concurrent sessions before (it works great), but it's not what I need here. Thanks for all the replies so far!!!

 

[techmanc]

what about using msn messenger remote desktop

 

[ShawnD1]

Originally posted by: Gooberlx2
google search "xp pro concurrent remote desktop session"

Another good string is "concurrent users". You'll need to patch a few files before this can be done.

doing this is illegal. read your license agreement

 

[chemwiz]

Please read the edited question, and thanks for all the replies so far! I checked out Winconnect server XP, they have a 15 day trial version, but it still suffers from the same default behavior, i.e. kicking off the current user. If I put on Vista will that work? I haven't used Vista yet, but the box will handle it.

 

[techmanc]

I use Vista to connect to my XP box and you can setup to be warned this way but it has nothing to do with the other user getting a warning. I think you need a server OS to get the types of connections you want or some kind of hack I am not aware of.

Connect and don't warn me

With this option, even if Remote Desktop Connection cannot verify the identity of the remote computer, it connects anyway.

Warn me

With this option, if Remote Desktop Connection cannot verify the identity of the remote computer, it warns you so that you can choose whether to proceed with the connection or not.

Do not connect

With this option, if Remote Desktop Connection cannot verify the identity of the remote computer, you won't be able to connect.

 

[chemwiz]

Well, I gues Vista is out too. Thanks, techmanc.

 

[Onund]

? we have an XP box at my work that we RDP to and it doesn't allow a connection if someone is already logged on either at the machine or RDP. Maybe its a setting? Are all the users admins?

 

[chemwiz]

All the users are admins (there's only one login besides Administrator), but I could change that. Anyone know if that will work?

 

[Onund]

making them non-admin will not prevent the problem. i just tested it on my personal XP install. There is an interesting read on configuring policies here. You should be able to find what you want in the list of options

Look towards the bottom for steps on 'To access Terminal Services Group Policy'

 

[techmanc]

Maybe this will help dont have time to read through and test it atm.

http://support.microsoft.com/kb/280828

 

[chemwiz]

Well, I think I have it figured out. Using the MMC snap-in (thanks to Onund and techmanc for the links on configuring stuff) and a utility called LaunchRDP.exe which lets me use a command line configuration, I got it to just not allow any connections if there's a user on it already. Thanks to everyone who replied!

 

[RebateMonger]

Originally posted by: chemwiz
But Remote Desktop just kicks off the current user and let's the new one on.

I've never seen that behavior. I use Remote Desktop all day long. If a DIFFERENT User is logged onto the PC, you get a warning when you try to log in. If the account that's logged in is the SAME account that's trying to log in remotely, the remote User takes over the desktop "as-is", with no warning. If the remote User "Disconnects" (rather than logs off) after using the PC remotely, you can log back in at the desktop with the same account and things will be unchanged from when the remote User disconnected.

If you are only using a single User account on the PC, then what you are seeing is expected behavior because Windows assumes you are the same person and just want to log onto your desktop remotely. If you want a warning, use multiple User accounts.