Results 1 to 7 of 7

Thread: Remote Desktop: The client could not connect to the remote computer

  1. #1
    crazyglue Guest

    Remote Desktop: The client could not connect to the remote compute

    I have 2 servers on the same network both running Windows Server 2003
    Standard. I can connect via Remote Desktop Connection from an XP
    Professional workstation to one but not the other. The one that isn't
    working gives me the following message:
    "Remote Desktop Disconnected. The client could not connect to the remote
    computer. Remote connections might not be enabled or the computer might be
    too busy to accept new connections. It is also possible that network
    problems are preventing your connection. Please try connecting again later.
    If the problem continues to occur, contact your administrator."
    I enabled Remote Desktop the same way on both machines -- the machine that
    is NOT working is also running Windows Firewall (the machine that IS working
    is NOT running Windows Firewall). Thinking this might be the difference, I
    disabled the firewall, however the same problem occurs.

    I am the only admin of these servers, so noone else would be connected to
    either of them. Also, I've tried this numerous times on different days and
    times, and I always get the same error message.

    Does anyone have any ideas on what might be causing this problem?


  2. #2
    Robert L [MS-MVP] Guest

    Re: Remote Desktop: The client could not connect to the remote compute

    Assuming you have enable RDC on the server, can you RDC to itself?

    Bob Lin, MS-MVP, MCSE & CNE
    Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
    How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
    "crazyglue" <crazyglue@discussions.microsoft.com> wrote in message news:9D573721-050F-4FBA-99FE-11FE3B904E02@microsoft.com...
    I have 2 servers on the same network both running Windows Server 2003
    Standard. I can connect via Remote Desktop Connection from an XP
    Professional workstation to one but not the other. The one that isn't
    working gives me the following message:
    "Remote Desktop Disconnected. The client could not connect to the remote
    computer. Remote connections might not be enabled or the computer might be
    too busy to accept new connections. It is also possible that network
    problems are preventing your connection. Please try connecting again later.
    If the problem continues to occur, contact your administrator."
    I enabled Remote Desktop the same way on both machines -- the machine that
    is NOT working is also running Windows Firewall (the machine that IS working
    is NOT running Windows Firewall). Thinking this might be the difference, I
    disabled the firewall, however the same problem occurs.

    I am the only admin of these servers, so noone else would be connected to
    either of them. Also, I've tried this numerous times on different days and
    times, and I always get the same error message.

    Does anyone have any ideas on what might be causing this problem?


  3. #3
    perfectlemur@gmail.com Guest

    Re: Remote Desktop: The client could not connect to the remote compute

    I am having a similar issue. But my servers had RDP working for months
    before hand. Now 3 of the 10 servers won't allow RDP connections after
    installing Microsoft's December patches. I don't know if the same thing
    could be affecting you.


  4. #4
    crazyglue Guest

    Re: Remote Desktop: The client could not connect to the remote com

    Interesting thought. No, it can't. I get the same error message.

    "Robert L [MS-MVP]" wrote:

    > Assuming you have enable RDC on the server, can you RDC to itself?
    >
    > Bob Lin, MS-MVP, MCSE & CNE
    > Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
    > How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
    > "crazyglue" <crazyglue@discussions.microsoft.com> wrote in message news:9D573721-050F-4FBA-99FE-11FE3B904E02@microsoft.com...
    > I have 2 servers on the same network both running Windows Server 2003
    > Standard. I can connect via Remote Desktop Connection from an XP
    > Professional workstation to one but not the other. The one that isn't
    > working gives me the following message:
    > "Remote Desktop Disconnected. The client could not connect to the remote
    > computer. Remote connections might not be enabled or the computer might be
    > too busy to accept new connections. It is also possible that network
    > problems are preventing your connection. Please try connecting again later.
    > If the problem continues to occur, contact your administrator."
    > I enabled Remote Desktop the same way on both machines -- the machine that
    > is NOT working is also running Windows Firewall (the machine that IS working
    > is NOT running Windows Firewall). Thinking this might be the difference, I
    > disabled the firewall, however the same problem occurs.
    >
    > I am the only admin of these servers, so noone else would be connected to
    > either of them. Also, I've tried this numerous times on different days and
    > times, and I always get the same error message.
    >
    > Does anyone have any ideas on what might be causing this problem?
    >


  5. #5
    mikeindo Guest

    Re: Remote Desktop: The client could not connect to the remote com

    uh-oh... same problem here. only one of two w2k3 servers won't allow remote
    desktop connections. port 3389 just not listening. might try re-assigning
    RDP port in Reg to see. cant telnet to 3389 either. RDP-TCP not disabled in
    TSCC.msc either. services seem fine. fortunately, i can use Dameware Mini
    Remote Control to get desktop, but of course only cuz uses different port!

  6. #6
    Join Date
    Feb 2009
    Posts
    1

    Re: Remote Desktop: The client could not connect to the remote compute

    Is the server that is not connecting a new machine? I had the same trouble and it wasn't until I went to my power settings and set my "Turn Hard Disk off to NEVER." before I could connect. The default was set to 1 hour. You may have been trying after the hard disk shut down by itself.

  7. #7
    Alister Guest

    Remote Desktop: The client could not connect to the remote computer

    On Feb 23, 9:02 pm, Joseph fantozzi <Joseph.fantozzi.
    3o2...@DoNotSpam.com> wrote:

    This is a known issue following some security patches from December.
    On initial reboot after applying the patches, terminal services is
    disabled, and if you go into Administrative Tools/Services the option
    to change the startup type is greyed out. I run 30 2003 servers at a
    datacentre and found the only option was to logon to another machine
    which hadn't been rebooted and issue a remote shutdown -r to the
    affected server. The second reboot cures the problem.
    AFAIK Microsoft have done nothing about this issue, but it is
    mentioned numerous times in various forums if you do a google.

    Alister

Similar Threads

  1. Replies: 7
    Last Post: 28-07-2009, 01:24 PM
  2. Replies: 2
    Last Post: 12-11-2008, 01:32 PM
  3. remote web workplace rww stops working connect to remote computer
    By Dharuna in forum Small Business Server
    Replies: 3
    Last Post: 24-09-2008, 04:19 PM
  4. Replies: 7
    Last Post: 26-10-2007, 12:28 AM
  5. Replies: 2
    Last Post: 22-12-2006, 10:57 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,675,217,154.55735 seconds with 17 queries