RE: Remote Desktop used to work but now no longer



Have you tried (re)applying Windows Server 2003 SP1?

If terminal services isn't working, can you telnet to port 3389 on the
terminal server or see if port 3389 is listening via a netstat -an command?

-M

"Andy" wrote:

> Hi,
>
> We have several machines behind a single firewall using remote desktop.
> We can connect to all but one of them. When we try we get the message
> "The client could not connect to the remote computer".
>
> A little history for this machine:
> The machine is running Windows Server 2003 Standard edition.
> Remote desktop used to work perfectly on this machine, it is only
> recently that it has broken. We noticed the server had a few viruses
> on it so we installed a virus checker and scanned it top to bottom. We
> found a few files were infected but not many. The only one that looked
> semi critical was WMC.EXE
>
> Since this virus activity on the machine we have been unable to connect
> to remote desktop or map a shared folder. We can't browse the network
> using this machine or find it on the network.
>
> Any ideas how to get remote desktop working again?
>
> Thanks
> Andy
>
>
.



Relevant Pages

  • Re: Remote Desktop for Administration for non-Admins?
    ... The Remote Desktop mode of Windows Server 2003 Terminal Services is strictly ... Author of "Windows Server 2003 Terminal Services", ... > Administrator, and this one should get power user rights at best. ...
    (microsoft.public.windows.terminal_services)
  • Re: Windows XP
    ... port 3389 unless they plan to use the same computer one person at a time. ... those other users will have to connect ip:port in the remote desktop program ... > which is built in to XP Pro, but it's not called Terminal Services, ... > own workstation, that should be just fine with you. ...
    (microsoft.public.windows.terminal_services)
  • Re: TS non-existent in SBS 2003
    ... Terminal Services in Application Mode isn't in SBS 2003, ... --Jonathan Maltz [Microsoft MVP - Windows Server, ... TS non-existent in SBS 2003?? ... >>to Remote Desktop, but still uses the Terminal Services ...
    (microsoft.public.windows.terminal_services)
  • RE: Windows Server 2003 Service Pack2
    ... attack on the server. ... (for a long time I couldn't run remote desktop between our sites, ... stopped and started the rdp connection in terminal services configuration. ... to check port 3189. ...
    (microsoft.public.windows.server.general)
  • Re: OfficeJet 7410 All-in-One & 2003 Terminal Services - HELP
    ... A Remote Desktop user with WinXP Pro SP2 with a locally ... > connected to our Windows Server 2003 via Terminal Services. ... Redirected in a Remote Desktop or Terminal Services Session ...
    (microsoft.public.windowsxp.work_remotely)