Windows NT unable to Remote Control to WinXP from Windows 2003 Domain Control

  • Thread starter Thread starter duckinpv
  • Start date Start date
D

duckinpv

Our workstations are running Windows XP.
They are part of a Windows 2003 Domain.
In the Remote Control tab of Properties for "My Computer", the settings are:
- Enable Remote Control
- Not reuqire user's permission
- Level of Control = interact with the session

From a Windows 2003 Domain Controller, I opened Terminal Service Manager,
click Actions | Connect to Computer. it gives me the message "Server was not
found". I thought I used to be able to do this over a year ago. Not sure
what I changed so now I no longer can connect to remotely control the XP
workstations. Please help. Thanks!



I enter the IP address of an XP Workstation to try to Remote Control it, but
it gives me the message
 
You have to do this from within a TS session. Shadowing doesn't
work from the console of the server.

_________________________________________________________
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?ZHVja2lucHY=?= <duckinpv@discussions.microsoft.com>
wrote on 20 aug 2007 in
microsoft.public.windows.terminal_services:

> Our workstations are running Windows XP.
> They are part of a Windows 2003 Domain.
> In the Remote Control tab of Properties for "My Computer", the
> settings are: - Enable Remote Control
> - Not reuqire user's permission
> - Level of Control = interact with the session
>
> From a Windows 2003 Domain Controller, I opened Terminal Service
> Manager, click Actions | Connect to Computer. it gives me the
> message "Server was not found". I thought I used to be able to
> do this over a year ago. Not sure what I changed so now I no
> longer can connect to remotely control the XP workstations.
> Please help. Thanks!
>
>
>
> I enter the IP address of an XP Workstation to try to Remote
> Control it, but it gives me the message
 
Re: unable to Remote Control to WinXP from Windows 2003 Domain Con

Can you please explain how to do this from a TS session? Not sure how to get
to a TS session. Terminal Services was installed in Administration Mode.
Does it need to be in Application Mode?

"Vera Noest [MVP]" wrote:

> You have to do this from within a TS session. Shadowing doesn't
> work from the console of the server.
>
> _________________________________________________________
> 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?ZHVja2lucHY=?= <duckinpv@discussions.microsoft.com>
> wrote on 20 aug 2007 in
> microsoft.public.windows.terminal_services:
>
> > Our workstations are running Windows XP.
> > They are part of a Windows 2003 Domain.
> > In the Remote Control tab of Properties for "My Computer", the
> > settings are: - Enable Remote Control
> > - Not reuqire user's permission
> > - Level of Control = interact with the session
> >
> > From a Windows 2003 Domain Controller, I opened Terminal Service
> > Manager, click Actions | Connect to Computer. it gives me the
> > message "Server was not found". I thought I used to be able to
> > do this over a year ago. Not sure what I changed so now I no
> > longer can connect to remotely control the XP workstations.
> > Please help. Thanks!
> >
> >
> >
> > I enter the IP address of an XP Workstation to try to Remote
> > Control it, but it gives me the message

>
 
Re: unable to Remote Control to WinXP from Windows 2003 Domain Con

OK, sorry, I thought you wanted to shadow another rdp session.
Let's try this one instead :-)

From
http://ts.veranoest.net/ts_faq_administration.htm#XPSP2remote

Q: How can I Remote Control my Windows XP SP2 client from within
Terminal Services Manager?

A: ServicePack 2 disabled this feature. You can enable it again by
creating the following registry entry on the XP client:

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
"AllowRemoteRPC" = REG_DWORD:1

Also make sure that the Windows firewall on the client is
configured to allow File and Print sharing, as well as Remote
Desktop.
_________________________________________________________
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?ZHVja2lucHY=?= <duckinpv@discussions.microsoft.com>
wrote on 20 aug 2007 in
microsoft.public.windows.terminal_services:

> Can you please explain how to do this from a TS session? Not
> sure how to get to a TS session. Terminal Services was
> installed in Administration Mode. Does it need to be in
> Application Mode?
>
> "Vera Noest [MVP]" wrote:
>
>> You have to do this from within a TS session. Shadowing doesn't
>> work from the console of the server.
>>
>> _________________________________________________________
>> 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?ZHVja2lucHY=?= <duckinpv@discussions.microsoft.com>
>> wrote on 20 aug 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > Our workstations are running Windows XP.
>> > They are part of a Windows 2003 Domain.
>> > In the Remote Control tab of Properties for "My Computer",
>> > the settings are: - Enable Remote Control
>> > - Not reuqire user's permission
>> > - Level of Control = interact with the session
>> >
>> > From a Windows 2003 Domain Controller, I opened Terminal
>> > Service Manager, click Actions | Connect to Computer. it
>> > gives me the message "Server was not found". I thought I
>> > used to be able to do this over a year ago. Not sure what I
>> > changed so now I no longer can connect to remotely control
>> > the XP workstations. Please help. Thanks!
>> >
>> >
>> >
>> > I enter the IP address of an XP Workstation to try to Remote
>> > Control it, but it gives me the message
 
Re: unable to Remote Control to WinXP from Windows 2003 Domain Con

works great! Thanks

"Vera Noest [MVP]" wrote:

> OK, sorry, I thought you wanted to shadow another rdp session.
> Let's try this one instead :-)
>
> From
> http://ts.veranoest.net/ts_faq_administration.htm#XPSP2remote
>
> Q: How can I Remote Control my Windows XP SP2 client from within
> Terminal Services Manager?
>
> A: ServicePack 2 disabled this feature. You can enable it again by
> creating the following registry entry on the XP client:
>
> HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
> "AllowRemoteRPC" = REG_DWORD:1
>
> Also make sure that the Windows firewall on the client is
> configured to allow File and Print sharing, as well as Remote
> Desktop.
> _________________________________________________________
> 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?ZHVja2lucHY=?= <duckinpv@discussions.microsoft.com>
> wrote on 20 aug 2007 in
> microsoft.public.windows.terminal_services:
>
> > Can you please explain how to do this from a TS session? Not
> > sure how to get to a TS session. Terminal Services was
> > installed in Administration Mode. Does it need to be in
> > Application Mode?
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> You have to do this from within a TS session. Shadowing doesn't
> >> work from the console of the server.
> >>
> >> _________________________________________________________
> >> 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?ZHVja2lucHY=?= <duckinpv@discussions.microsoft.com>
> >> wrote on 20 aug 2007 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > Our workstations are running Windows XP.
> >> > They are part of a Windows 2003 Domain.
> >> > In the Remote Control tab of Properties for "My Computer",
> >> > the settings are: - Enable Remote Control
> >> > - Not reuqire user's permission
> >> > - Level of Control = interact with the session
> >> >
> >> > From a Windows 2003 Domain Controller, I opened Terminal
> >> > Service Manager, click Actions | Connect to Computer. it
> >> > gives me the message "Server was not found". I thought I
> >> > used to be able to do this over a year ago. Not sure what I
> >> > changed so now I no longer can connect to remotely control
> >> > the XP workstations. Please help. Thanks!
> >> >
> >> >
> >> >
> >> > I enter the IP address of an XP Workstation to try to Remote
> >> > Control it, but it gives me the message

>
 
Re: unable to Remote Control to WinXP from Windows 2003 Domain Con

You're welcome! I'm glad that it works now, and thanks for
reporting the result back here!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?ZHVja2lucHY=?= <duckinpv@discussions.microsoft.com>
wrote on 20 aug 2007:

> works great! Thanks
>
> "Vera Noest [MVP]" wrote:
>
>> OK, sorry, I thought you wanted to shadow another rdp session.
>> Let's try this one instead :-)
>>
>> From
>> http://ts.veranoest.net/ts_faq_administration.htm#XPSP2remote
>>
>> Q: How can I Remote Control my Windows XP SP2 client from
>> within Terminal Services Manager?
>>
>> A: ServicePack 2 disabled this feature. You can enable it again
>> by creating the following registry entry on the XP client:
>>
>> HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
>> "AllowRemoteRPC" = REG_DWORD:1
>>
>> Also make sure that the Windows firewall on the client is
>> configured to allow File and Print sharing, as well as Remote
>> Desktop.
>> _________________________________________________________
>> 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?ZHVja2lucHY=?= <duckinpv@discussions.microsoft.com>
>> wrote on 20 aug 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > Can you please explain how to do this from a TS session? Not
>> > sure how to get to a TS session. Terminal Services was
>> > installed in Administration Mode. Does it need to be in
>> > Application Mode?
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> You have to do this from within a TS session. Shadowing
>> >> doesn't work from the console of the server.
>> >>
>> >> _________________________________________________________
>> >> 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?ZHVja2lucHY=?=
>> >> <duckinpv@discussions.microsoft.com> wrote on 20 aug 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > Our workstations are running Windows XP.
>> >> > They are part of a Windows 2003 Domain.
>> >> > In the Remote Control tab of Properties for "My Computer",
>> >> > the settings are: - Enable Remote Control
>> >> > - Not reuqire user's permission
>> >> > - Level of Control = interact with the session
>> >> >
>> >> > From a Windows 2003 Domain Controller, I opened Terminal
>> >> > Service Manager, click Actions | Connect to Computer. it
>> >> > gives me the message "Server was not found". I thought I
>> >> > used to be able to do this over a year ago. Not sure what
>> >> > I changed so now I no longer can connect to remotely
>> >> > control the XP workstations. Please help. Thanks!
>> >> >
>> >> >
>> >> >
>> >> > I enter the IP address of an XP Workstation to try to
>> >> > Remote Control it, but it gives me the message
 
Back
Top