Re: REMOTE CONTROL (W2K3) stops working after updating WXP Pro SP1 to

Tech-Archive recommends: Speed Up your PC by fixing your registry



In news:OXIBzhFBGHA.3928@xxxxxxxxxxxxxxxxxxxx,
TP <tperson.knowspamn@xxxxxxxxxxxxxxx> typed:
> It has nothing to do with the firewall. This is a "feature" of SP2.

Sorry; perhaps I'm confused about what sort of 'remote control one can have
in TS to a WinXP workstation?

>
> Thanks.
>
> -TP
>
> Lanwench [MVP - Exchange] wrote:
>> In news:9E9E901F-423F-4EAE-BA2E-EDBC76BD9291@xxxxxxxxxxxxx,
>> Bob <Bob@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
>>> Our server has W2K3 on it, and we use Remote Control (Terminal
>>> Services Manager) on our local network as a better alternative to
>>> Remote Desktop.
>>
>> You're still using remote desktop, when you do this.
>>
>>> Everything works OK as long as the working stations
>>> have WXP Pro SP1.
>>>
>>> But if we update the working stations that have WXP Pro from SP1 to
>>> SP2, then the Terminal Services Manager can't see them anymore. The
>>> only thing that happens every time we try to connect to the updated
>>> station is that an error message shows up saying: "You could not be
>>> authenticated on this server" (referring to the station we are
>>> trying to connect to with the Remote Control).
>>>
>>> ¿What changes do we have to make (we suppose...) on the working
>>> stations to be able to use the Remote Control on those stations
>>> again?
>>
>> Set an exception for Remote Desktop in the Windows firewall. You
>> ought to be able to do this with group policy.
>>
>>>
>>> (All the policies and parameters on the server side were already sat
>>> up and work fine, the problem happens when the stations get
>>> updated). We were looking for a comment or solution in the
>>> Knowledge Base but there wasn't any article specifically related to
>>> this situation. Any idea? We need a solution very badly 'cause we
>>> strongly rely on
>>> Remote Control for our daily support to the users...
>>>
>>> Thanks,


.

Relevant Pages

  • Re: Fun with compter tuner
    ... If your computer has Windows Media Center in it, it will automatically scan for all available stations and you can select them directly from your computer. ... you can use a remote control that is supplied with the tuner kit. ... The little stick antenna is kind of finicky with regard to placement. ... I did see a ton of available recording formats, but haven't a clue as to which ones to use. ...
    (rec.boats)
  • Re: REMOTE CONTROL (W2K3) stops working after updating WXP Pro SP1 to
    ... 875357 - Troubleshooting Windows Firewall settings in Windows XP ... MCSE, CCEA, Microsoft MVP - Terminal Server ... > Our server has W2K3 on it, and we use Remote Control (Terminal ... > But if we update the working stations that have WXP Pro from SP1 ...
    (microsoft.public.windows.terminal_services)
  • Re: REMOTE CONTROL (W2K3) stops working after updating WXP Pro SP1 to
    ... > Our server has W2K3 on it, and we use Remote Control (Terminal ... > But if we update the working stations that have WXP Pro from SP1 to ... then the Terminal Services Manager can't see them anymore. ... > authenticated on this server" (referring to the station we are trying ...
    (microsoft.public.windows.terminal_services)
  • Sms 2.0 Remote agent keeps being deleted from clients
    ... trying to remote control stations, im seeing that the remote control agent ... on the stations has been deleted. ... all the rest of the sms services are there ...
    (microsoft.public.sms.admin)
  • Re: REMOTE CONTROL (W2K3) stops working after updating WXP Pro SP1 to
    ... This is a problem with SP2. ... Services Manager) on our local network as a better alternative to Remote Desktop. ... Everything works OK as long as the working stations have WXP Pro SP1. ... Remote Control for our daily support to the users... ...
    (microsoft.public.windows.terminal_services)