Unable to connect to 2k3 r2 via rdp

  • Thread starter Thread starter Desk Jockey
  • Start date Start date
D

Desk Jockey

I'm attempting to connect to an Windows 2003 R2 server using Remote Desktop.
I get the error message "The client is unable to connect. You are already
connected to the console of this computer. A new console session cannot be
established."

I have rebooted both the client machine (XP Pro) and the server. I don't
even have a monitor, keyboard or mouse on the server so I know I'm not logged
into that machine directly.

Any thoughts? Thanks.
 
Sounds like you are trying to connect to the console session of the
server, with the mstsc /console option.
Maybe there's someone else in the company already connected to the
console session?

Start a normal session on the server (use mstsc without any
switches), and then check in TS Manager which sessions are running
on the server. If that doesn't solve it, can you post the result of
the qwinsta command on the server here?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?RGVzayBKb2NrZXk=?=
<DeskJockey@discussions.microsoft.com> wrote on 12 jun 2008 in
microsoft.public.windows.terminal_services:

> I'm attempting to connect to an Windows 2003 R2 server using
> Remote Desktop. I get the error message "The client is unable
> to connect. You are already connected to the console of this
> computer. A new console session cannot be established."
>
> I have rebooted both the client machine (XP Pro) and the server.
> I don't even have a monitor, keyboard or mouse on the server so
> I know I'm not logged into that machine directly.
>
> Any thoughts? Thanks.
 
At times like this I wish I could delete my post...

I was using the IP address of my localhost... not the destination server. I
know it sounds like a real bonehead move... sort of like bringing a car in
for repairs because it ran out of gas... Thanks for the support but all is
well.

Sorry for the lame post.

Dave

"Vera Noest [MVP]" wrote:

> Sounds like you are trying to connect to the console session of the
> server, with the mstsc /console option.
> Maybe there's someone else in the company already connected to the
> console session?
>
> Start a normal session on the server (use mstsc without any
> switches), and then check in TS Manager which sessions are running
> on the server. If that doesn't solve it, can you post the result of
> the qwinsta command on the server here?
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?RGVzayBKb2NrZXk=?=
> <DeskJockey@discussions.microsoft.com> wrote on 12 jun 2008 in
> microsoft.public.windows.terminal_services:
>
> > I'm attempting to connect to an Windows 2003 R2 server using
> > Remote Desktop. I get the error message "The client is unable
> > to connect. You are already connected to the console of this
> > computer. A new console session cannot be established."
> >
> > I have rebooted both the client machine (XP Pro) and the server.
> > I don't even have a monitor, keyboard or mouse on the server so
> > I know I'm not logged into that machine directly.
> >
> > Any thoughts? Thanks.
>
 
Don't feel bad about it, Dave, such things can happen to all of us!

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?RGVzayBKb2NrZXk=?=
<DeskJockey@discussions.microsoft.com> wrote on 13 jun 2008:

> At times like this I wish I could delete my post...
>
> I was using the IP address of my localhost... not the
> destination server. I know it sounds like a real bonehead
> move... sort of like bringing a car in for repairs because it
> ran out of gas... Thanks for the support but all is well.
>
> Sorry for the lame post.
>
> Dave
>
> "Vera Noest [MVP]" wrote:
>
>> Sounds like you are trying to connect to the console session of
>> the server, with the mstsc /console option.
>> Maybe there's someone else in the company already connected to
>> the console session?
>>
>> Start a normal session on the server (use mstsc without any
>> switches), and then check in TS Manager which sessions are
>> running on the server. If that doesn't solve it, can you post
>> the result of the qwinsta command on the server here?
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?RGVzayBKb2NrZXk=?=
>> <DeskJockey@discussions.microsoft.com> wrote on 12 jun 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > I'm attempting to connect to an Windows 2003 R2 server using
>> > Remote Desktop. I get the error message "The client is
>> > unable to connect. You are already connected to the console
>> > of this computer. A new console session cannot be
>> > established."
>> >
>> > I have rebooted both the client machine (XP Pro) and the
>> > server.
>> > I don't even have a monitor, keyboard or mouse on the server
>> > so
>> > I know I'm not logged into that machine directly.
>> >
>> > Any thoughts? Thanks.
 
Back
Top