Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I have many users on our LAN who often connect to one PC to use apps that are only installed on that PC. Each user initiates a Remote Desktop Connection to that PC and logs in with the same local username/password.
My problem: When a user is connected via RDP then another user connects, the original user is immediately bumped off without warning. This problem only exists because everyone uses that same local user/password to connect. I could create multiple local user accounts and have each user connect with their unique account. This way they would be warned that the currently logged on user would be logged off before connecting. However I don't want to do this because there are 30+ potential people who log on to this PC and I don't want to create 30 local accounts.
How can I allow for my users to RDP with the same local user account but be prompted that if another user is currently connected (with the same account) that they will be logged off.
Make sense? Thanks in advance...
Ben
No way to do that in XP, that I know of. There may be some obscure registry setting.
But even with different accounts, you may still have problems. If a user only closes the RD window, then their session is still open and the next user won't really know if they are going to log someone off or not.
Michael J
0 
With different accounts, the currently logged on user isn't notified that another account is attempting a RDP connection. It is the 2nd user who is warned when attempting to connect when someone else is already connected.
I need to know if there is a way to turn on the same warning when someone else tries to connect using the same credentials.
0
I would think you may want to reconsider how these users are connecting to the computer in the first place. I think your problem is actually the fact that multiple people are using Remote Desktop at the same time. RDC for 30 different users is a very inefficient way to do this. What application is this, and can't you set time allotments for each user? Or set a schedule? Or, and this is my recommendation, get a network license for the software.
Life's more painless for the brainless.
0
Let me clarify...
My company has dozens of customers who have their own requirements by which we must connect to their systems to provide technical support (site-to-site tunnel, Cisco client VPN connections, Microsoft Client VPN connections, Citrix, telnet, etc).
Setting up all of these connections on each of our support department client PCs as well as our developers' PCs is not only a security problem but could cause problems with their local apps. To simplify this, I created a DMZ and placed two PCs in this DMZ that are fully configured to connect to any one of our customers. Our employees RDC to these PCs then connect to our customers from there.
Using one local logon on these PCs makes it simple for our staff to connect to.
Thoughts?
0
"With different accounts, the currently logged on user isn't notified that another account is attempting a RDP connection. It is the 2nd user who is warned when attempting to connect when someone else is already connected."
Yes, I understand that. Perhaps you didn't read my response close enough. If User A does not properly log off of the RD session (e.g. only clicks the close button), then when User B goes to log into that machine he will get a message telling him that if he continues User A will be logged out. He will ahve no way of knowing if User A is still using that session or not.
I agree with Razor, you need to find a better solution than using RD on Windows XP. I have not used RealVNC for multiple connectinos to the same XP machine, but I would recommend Windows 2003 Server. It allows you to have many different RD connections simultaneously.
Michael J
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
