Screwed up my REMOTE DESKTOP

Tech-Archive recommends: Fix windows errors by optimizing your registry

Somehow I screwed up my Remote Desktop access to my Windows Server 2003. I
was trying to lock my server down because people keep getting through my
Linksys router and creating names for themselves like 'mike' and I don't
have a Mike associated with anything in my house.

I ended up disabling some services that I didn't know for sure what they
were used for. I now do not have remote desktop access to my server.

What services are required to be started in order for Remote Desktop to
work.

Tony


.

Relevant Pages

  • Re: Terminal Services or Remote Desktop?
    ... Yes, Mike, you've finally got it :-) ... MCSE, CCEA, Microsoft MVP - Terminal Server ... > servr using remote desktop. ... It used to be called Terminal Services client, ...
    (microsoft.public.windows.terminal_services)
  • AW: Remote desktop access policy
    ... Have you ever thought about a terminal server solution. ... Betreff: RE: Remote desktop access policy ...
    (Security-Basics)
  • Re: Screwed up my REMOTE DESKTOP
    ... the port that is usually used '3389' was changed to '1979'. ... Linksys router and creating names for themselves like 'mike' and I don't ... I now do not have remote desktop access to my server. ...
    (microsoft.public.windows.server.setup)
  • Re: Screwed up my REMOTE DESKTOP
    ... PC Mag had an issue 2 months ago on antispyware. ... Linksys router and creating names for themselves like 'mike' and I don't ... I now do not have remote desktop access to my server. ...
    (microsoft.public.windows.server.setup)
  • Re: Turning on Remote Desktop Remotley
    ... Many thanks Mike & KJ ... This is even easier, though still via Registry: ... Here is a link to a free tool that claims to enable Remote Desktop ... reach the server and all of the other workstations. ...
    (microsoft.public.windows.server.sbs)