TS client won't allow Remote Desktop Users Console session..

[JB]

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

I tred to logon to a Windows Server 2003 with a Term Service
connection with console access using a non-admin account and I get the
following error:

"You do not have access to logon to this session."

If you connect to a windows 2003 server with the following command you
can gain console level access:

C:\Program Files\Remote Desktop\mstsc.exe" -v:198.3.185.128 /w:1024
/h:768 /console

I can already start a ts session with a Remoted Desktop User group
account, but I need console access. Any suggestions?

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

You cannot have 2 connections to session 0 at the same time,
so if you connect to the console you will have to log off the
existing session.
Your account does not have the right to logoff the existing
session on the console. You must be the same user who currently
holds the console session, or an Administrator. It probably does
not have the right to "Logon locally" either.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

jbernsen@navisite.com (JB) wrote in
news:fab1fc8d.0404020743.6a6e128f@posting.google.com:

> I tred to logon to a Windows Server 2003 with a Term Service
> connection with console access using a non-admin account and I
> get the following error:
>
> "You do not have access to logon to this session."
>
> If you connect to a windows 2003 server with the following
> command you can gain console level access:
>
> C:\Program Files\Remote Desktop\mstsc.exe" -v:198.3.185.128
> /w:1024 /h:768 /console
>
> I can already start a ts session with a Remoted Desktop User
> group account, but I need console access. Any suggestions?

 

[JB]

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

Thank you for your response. All users have the log on locally and
log on through ts permissions. Also, when I attempt to connect with
the console via TS, there are no sessions currently connected. I can
try that again, but I'm pretty sure there are no other sessions.

Is there a registry entry I can make to allow certain users, other
than administrators, to have console access via TS?

Thanks,
JB

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message news:<Xns94BFE059F42E5veranoesthemutforsse@207.46.248.16>...
> You cannot have 2 connections to session 0 at the same time,
> so if you connect to the console you will have to log off the
> existing session.
> Your account does not have the right to logoff the existing
> session on the console. You must be the same user who currently
> holds the console session, or an Administrator. It probably does
> not have the right to "Logon locally" either.
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

But is the administrator logged on at the *physical* console when
you try to connect with the mstsc /console switch? This login is
using session 0. If the administrator is logged on there, you need
to throw him/her out. And for that, you need administrative power.
Compare with a normal workstation, where a password-protected
screen saver has been activated. Only the same user or an
administrator can deactivate the screen saver and get access to
the session.

Does this explain your situation?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

jbernsen@navisite.com (JB) wrote in
news:fab1fc8d.0404050648.62018a9@posting.google.com:

> Thank you for your response. All users have the log on locally
> and log on through ts permissions. Also, when I attempt to
> connect with the console via TS, there are no sessions currently
> connected. I can try that again, but I'm pretty sure there are
> no other sessions.
>
> Is there a registry entry I can make to allow certain users,
> other than administrators, to have console access via TS?
>
> Thanks,
> JB
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:<Xns94BFE059F42E5veranoesthemutforsse@207.46.248.16>...
>> You cannot have 2 connections to session 0 at the same time,
>> so if you connect to the console you will have to log off the
>> existing session.
>> Your account does not have the right to logoff the existing
>> session on the console. You must be the same user who currently
>> holds the console session, or an Administrator. It probably
>> does not have the right to "Logon locally" either.

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

Hi JB,

Is your problem solved already?

I'm having the same problem and nobody seems to be able to give me the right answer. The standard answer is: Give the non-administrative user "Logon Locally" rights.....DUH!

People, nobody is logged on to the console itself so we don't need administrative rights to throw them off. All permissions are set right and still we are not allowed to connect to the console with an non-administrative account unless the same user is logged on at the console itself (at the keyboard). This being the case we can't reboot the server remotely because we have to walk to the keyboard to log the user back on.

Help...

Regards,
Arjan

"JB" wrote:

> I tred to logon to a Windows Server 2003 with a Term Service
> connection with console access using a non-admin account and I get the
> following error:
>
> "You do not have access to logon to this session."
>
> If you connect to a windows 2003 server with the following command you
> can gain console level access:
>
> C:\Program Files\Remote Desktop\mstsc.exe" -v:198.3.185.128 /w:1024
> /h:768 /console
>
> I can already start a ts session with a Remoted Desktop User group
> account, but I need console access. Any suggestions?
>

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

Actually, for security reasons, non-administrators are not able to remotely
logon to the console, except for when they are already logged in to the
console session. If you really need to be able to log in to the console
session remotely, add your user to the local Administrators group.

Cheers,
Drew

--
This posting is provided "AS IS" with no warranties, and confers no rights.
TS FAQ:
http://www.microsoft.com/windows2000/community/centers/terminal/terminal_faq.asp



"Arjan" <Arjan@discussions.microsoft.com> wrote in message
news:E14F761E-00EF-48A1-A289-886F56BC436E@microsoft.com...
> Hi JB,
>
> Is your problem solved already?
>
> I'm having the same problem and nobody seems to be able to give me the
right answer. The standard answer is: Give the non-administrative user
"Logon Locally" rights.....DUH!
>
> People, nobody is logged on to the console itself so we don't need
administrative rights to throw them off. All permissions are set right and
still we are not allowed to connect to the console with an
non-administrative account unless the same user is logged on at the console
itself (at the keyboard). This being the case we can't reboot the server
remotely because we have to walk to the keyboard to log the user back on.
>
> Help...
>
> Regards,
> Arjan
>
> "JB" wrote:
>
> > I tred to logon to a Windows Server 2003 with a Term Service
> > connection with console access using a non-admin account and I get the
> > following error:
> >
> > "You do not have access to logon to this session."
> >
> > If you connect to a windows 2003 server with the following command you
> > can gain console level access:
> >
> > C:\Program Files\Remote Desktop\mstsc.exe" -v:198.3.185.128 /w:1024
> > /h:768 /console
> >
> > I can already start a ts session with a Remoted Desktop User group
> > account, but I need console access. Any suggestions?
> >