Re: Cannot connect to console on two servers using RDP
- From: Blogging IT Guy <BloggingITGuy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 29 Oct 2005 09:44:01 -0700
Hi Vera,
Thanks for the response. I already checked that and the permissions in the
global and local policies are set correctly.
Regards,
Alex
"Vera Noest [MVP]" wrote:
> This seems to be a permission problem. From:
>
> 278845 - How to Connect to and Shadow the Console Session with
> Windows Server 2003 Terminal Services
> http://support.microsoft.com/?kbid=278845
>
> If the Windows Server 2003-based server is not configured to permit
> remote control, you receive the following error message:
> Remote control failed. Error code 7051
> Error [7051]: The requested session is not configured to allow
> Remote Control.
>
> To configure the Windows Server 2003-based server to permit remote
> control, follow these steps:
> 1. Open the Group Policy snap-in (Gpedit.msc).
> 2. In the left pane, under the Computer Configuration branch,
> expand the Administrative Templates branch.
> 3. Expand the Windows Components branch.
> 4. Click the Terminal Services folder.
> 5. In the right pane, double-click Sets rules for remote control of
> Terminal Services user sessions.
> 6. On the Setting tab, click Enabled.
> 7. In the Options box, click Full Control with users' permission,
> and then click OK.
>
> _________________________________________________________
> 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?QmxvZ2dpbmcgSVQgR3V5?= <Blogging IT
> Guy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 28 okt 2005 in
> microsoft.public.windows.terminal_services:
>
> > Having problems connecting to console session of Terminal
> > Services on two Server 2003 SP1 boxes.
> >
> > I have similarly patched and configured servers that properly
> > allow RDP clients to connect to console.
> >
> > Am able to connect to normal admin non-console session on both
> > servers. Problem occurs regardless of type of client used (5.1,
> > 5.2, web RDP, etc.).
> >
> > Have done the fixes for KB902400, no effect. I've checked all
> > the rights and settings that I can find and haven't found
> > anything obvious out of whack.
> >
> > I've enabled logging of Winlogon.exe events to userenv.log, but
> > all it shows for the aborted connects are:
> >
> > USERENV(2fc.dac) 14:37:45:639 InitializePolicyProcessing:
> > Initialised Machine Mutex/Events
> > USERENV(2fc.dac) 14:37:45:639 InitializePolicyProcessing:
> > Initialised User Mutex/Events
> > USERENV(2fc.dac) 14:37:45:639 LibMain: Process Name:
> > \??\C:\WINDOWS\system32\winlogon.exe
> >
> > and goes no further. I've checked the encryption settings (set
> > to default) and everything else I can think of.
> >
> > Also uninstalled the hotfix for KB902400, no effect.
> >
> > Oh and the error that appears whenever I attempt to connect to
> > console with RDP is "Error connecting to existing session for
> > <username> (Id 0). The operation completed successfully."
> >
> > If I try to connect using Terminal Services Manager, I get
> > "Error [7051]: The requested session is not configured to allow
> > Remote Control."
> >
> > Am able to log on to console locally or by using VNC (UltraVNC).
> >
> > Anyone got any other ideas for me?
>
.
- Follow-Ups:
- Re: Cannot connect to console on two servers using RDP
- From: Vera Noest [MVP]
- Re: Cannot connect to console on two servers using RDP
- References:
- Re: Cannot connect to console on two servers using RDP
- From: Vera Noest [MVP]
- Re: Cannot connect to console on two servers using RDP
- Prev by Date: Re: TS Application Mode no connect; Remote admin ok
- Next by Date: Re: TS Application Mode no connect; Remote admin ok
- Previous by thread: Re: Cannot connect to console on two servers using RDP
- Next by thread: Re: Cannot connect to console on two servers using RDP
- Index(es):
Relevant Pages
|