Remote Desktop for Administration issue

[Steve Gould]

Windows Server 2003 Standard

2 of my servers will not allow more than one admin connection through Remote
Desktop for Administration (or local console). All the others will allow a
local connection as well as two remote connections as they should. The two
problem servers have ALL the same settings as the others, the setting to
limit a user to one connection is NOT set, but if you log in at the console
then a remote connection will be disconnected and the same from a remote. If
I am logged in and another admin logs in then I get disconnected. Thse two
servers will only allow ONE connection.

Can someone point me where to look?

 

[Pegasus \(MVP\)]

Windows Server 2003 Standard

2 of my servers will not allow more than one admin connection through Remote
Desktop for Administration (or local console). All the others will allow a
local connection as well as two remote connections as they should. The two
problem servers have ALL the same settings as the others, the setting to
limit a user to one connection is NOT set, but if you log in at the console
then a remote connection will be disconnected and the same from a remote. If
I am logged in and another admin logs in then I get disconnected. Thse two
servers will only allow ONE connection.

Can someone point me where to look?

The behaviour you describe is exactly what one gets on a WinXP
Professional PC. I suppose it's a silly question but I still need to
ask if you're sure that your hosts run Windows Server.

I would also check each and every detail in the three Terminal Server
shortcuts you see under "Administrative Tools". Quite a few details
become visible only when right-clicking various items.

 

[Steve Gould]

Well, I am getting old, but not THAT old All of my servers run Win 2k3.
All standards, no advanced. One server with issue is our IIS server and also
performs inbound RAS and Radius. The other server is running 64bit Win2k3
standard and Exchange 2007 Beta 2 (I'm an RDP tester).

I have been through all the settings in detail. Nothing out of the ordinary
on either server. I couldn't find a knowledge base article on it. Then
again, I might just have been missing the right combo of keywords. That is
why I posted here, hoping someone was familiar with this issue and could
point me at the fix.

 

[Steve Gould]

I have an important update to this issue.

I logged in to one of my two problem servers from a workstation I never
logged in from before and got a second session to open. I disconnected my
session from my main workstation in from a third workstation and was able to
get a new session.

So I was able to have two active sessions. I went to the console and logged
in and it took over the disconnected session that I was using from my main
workstation. So I then had 3 sessions active, two remote sessions and the
console.

Here is what has been happening on server 2 and I suspect the same issue on
server 1, but haven't verified yet.

My workstation, my bosses workstation (the second administrator) and the
actual server console keep taking the same session! When I try to log in
from one of the three it logs off the other connected session instead of
creating a new session.

NOW does anyone have any comments? How can I disassociate these sessions?

Steve

 

[Steve Gould]

I figured out I was being a bonehead. The answer wasn't in the server, but
the client side connection. I found that for both servers I had "Connect to
console" selected on my workstation and on my bosses.

Well that sure was fun.