In Terminal Services Manager, Console session shows as an RDP session.

[Pool Shark]

On most of our new Windows 2003 Enterprise x64 servers, all from same
base image, there are times where the session logged in on the console
with show up as an RDP session in TSM. If you go to the console and
unlock the account, sometimes it will flip back to showing as a
console session, sometimes not. Also, when you lock it again,
sometimes it will go back to showing as RDP, sometimes not.

The problem with this is that it makes Windows think one of the RDP
sessions is in use. So if there is one RDP session and an account
logged into the console, since it thinks the console is RDP, it won't
allow another session. Also, it will not say that the connections are
maxed out, it will just say that it can't connect to the remote
computer.

Please help I have to have this resolved by Friday!

[Jeff Pitsch]

So it shows as something other than session 0?

Jeff Pitsch
Microsoft MVP - Terminal Services

[Pool Shark]

it shows up as session 0

I can't quite make this out as now that I'm looking into it further as
each server is a little different. One server will allow 3 "rdp"
sessions with one being id 0 which is really console. Another server
will show 2 RDP sessions, one of which is really a console session,
and it will immediately come up with the error "this computer can't
connect to the remote computer." not even a prompt for password or an
attempt to connect.

[Pool Shark]

ok just did it again, on the one server where it showed 2 RDP
sessions, one which was really console, I went to the console and
unlocked the account. It immediately changed to showing up as
"console" in TSM. I then was able to RDP in as a second session with
no problems. I locked the console session again and it did not change
back to RDP. This is just wierd.