Results 1 to 6 of 6

Thread: The remote connection has timed out

  1. #1
    Join Date
    Apr 2005
    Posts
    7

    The remote connection has timed out

    Hello all!

    I am encountering a problem when trying to connect to a remote server using the Windows XP Pro (SP2) Remote Desktop. The domain user keeps getting the following error:

    The remote connection has timed out. Please try connecting to the remote computer again.

    Now when I log on using an account with admin rights this does not happen which means that there seems to be a Group Policy setting being applied thus preventing normal users from connecting remotely. We have a Domain Group Policy in place but when checking the settings I cannot seem to find what particular GP setting/s is causing this.
    Could someone please help me troubleshoot this problem?

    Many thanks
    Pierre

  2. #2
    Join Date
    Nov 2008
    Posts
    173

    Re: The remote connection has timed out

    First check the firewall settings at the remote computers, and also confirm that all the machines in your internal LAN are functioning properly with RDP.

    Refer to this microsoft guide: Troubleshooting General Remote Desktop Error Messages

  3. #3
    Join Date
    Apr 2005
    Posts
    7

    Re: The remote connection has timed out

    The firewall is not interfering with the connection. The server is a demo server which is hosted at a supplier. The problem cropped up when one of our domain users tried to connect via Remote Desktop. But when I tried connecting myself with my domain account because I am a sys admin I could connect to this server without any issues. So that is why I am confused as to what could be causing this problem. My suspicion is the GPO but when I checked the settings there didn't seem to be any settings applied.

  4. #4
    Join Date
    Jan 2006
    Posts
    3,792

    Re: The remote connection has timed out

    The remote connection has timed out. Please try connecting to the remote computer again.
    The above error message pops up either when the terminal server disconnected your session because you did not send a response within the time limit set for responses or you are on slow network connection. Try connecting to the terminal server again at a later point of time.

  5. #5
    Join Date
    Jan 2009
    Posts
    289

    Re: The remote connection has timed out

    Quote Originally Posted by tigerdivision View Post
    My suspicion is the GPO but when I checked the settings there didn't seem to be any settings applied.
    Try to change and apply a GP settings and see if you can connect to the server...

  6. #6
    Join Date
    Apr 2005
    Posts
    7

    Re: The remote connection has timed out

    Quote Originally Posted by big fish View Post
    The above error message pops up either when the terminal server disconnected your session because you did not send a response within the time limit set for responses or you are on slow network connection. Try connecting to the terminal server again at a later point of time.
    I don't think speed is an issue here as it would happen to me also.

Similar Threads

  1. The network connection timed out while installing 4.1
    By Banned-BlackBadal in forum Portable Devices
    Replies: 4
    Last Post: 31-10-2010, 07:19 AM
  2. Psp timed out connection problem
    By G.Burgess in forum Networking & Security
    Replies: 5
    Last Post: 16-10-2010, 02:48 PM
  3. Timed out connection problem with utorrent
    By Prateet in forum Windows Software
    Replies: 4
    Last Post: 25-06-2010, 05:21 PM
  4. Connection Timed Out in Leopard
    By Abhisar G in forum Operating Systems
    Replies: 5
    Last Post: 27-04-2010, 04:12 AM
  5. Connection timed out when using putty
    By Leiff in forum Networking & Security
    Replies: 4
    Last Post: 08-02-2010, 12:53 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,713,886,244.62408 seconds with 16 queries