Marcus Bentley
2005-06-10 11:01:02 UTC
I used to have no problem with using RDP to connect to my 2003 servers, where
is someone was logged on locally to the server and I logged on with RDP we
could both work simultaneously on the same machine. Recently though I have
found that when I start an RDP session it will always logoff the console to
let me login, even when there are no other RDP sessions running.
This is fairly random e.g. me and a collegue were both trying to work on a
server yesterday, me on the local console and him over RDP and we just kept
logging each other out (again despite TS Manager saying there were no other
RDP sessions running) this morning however we have both logged on with no
problem with me on the console and him over RDP.
Has anyone seen this and have any idea how to resolve this.
I do know you can force an RDP session onto the console through a command
line switches and that is not what is causing this (unless there's some kind
of registry key that can force RDP to connect to console sessions that I am
not aware of)
Thanks for any help
is someone was logged on locally to the server and I logged on with RDP we
could both work simultaneously on the same machine. Recently though I have
found that when I start an RDP session it will always logoff the console to
let me login, even when there are no other RDP sessions running.
This is fairly random e.g. me and a collegue were both trying to work on a
server yesterday, me on the local console and him over RDP and we just kept
logging each other out (again despite TS Manager saying there were no other
RDP sessions running) this morning however we have both logged on with no
problem with me on the console and him over RDP.
Has anyone seen this and have any idea how to resolve this.
I do know you can force an RDP session onto the console through a command
line switches and that is not what is causing this (unless there's some kind
of registry key that can force RDP to connect to console sessions that I am
not aware of)
Thanks for any help