Windows Server

Problems with RDP Connections on Windows Server 2008 R2

Recently we came across a nasty issue when remotely connecting to Windows Server 2008 R2 machines via RDP (Remote Desktop Protocol). In this case, these servers were actually Domain Controllers and not full featured terminal servers, but we’ve seen issues with these as well. Failing to use RDP to these servers caused the administrators to have to physically go to the servers and log on locally, or use some other sort of remote management software such as HP iLO. If these are virtual machines, it’s also possible to connect to their console using the virtualization software management suite. Either way, failing to use RDP to manage these servers may cause a significant issue for some.

RDP Connection Problems in Windows Server 2008 R2

The symptoms for the RDP problem include the following:

    1. A user with administrative rights and permissions to RDP into the server(s), who was able to successfully connect to these machines, now reports that they can no longer connect to the machines.

Note: It seems that in some cases, this issue also happens for Windows 7 machines as well.

    1. Once the user opens an MSTSC window and attempts to RDP into the server(s), they are prompted to enter their credentials. They do so, but just before their desktop appears, an error warning appears:“The connection to the remote computer was broken. This may have been caused by a network error. Please try connecting to the remote server again.”The user acknowledges the error message, and then the MSTSC window closes.
    2. Checking the services on the remote server shows that the Remote Desktop Service is in a stopped state.Remote Desktop Service - stopped state
    3. If you restart the Remote Desktop Service, the service runs till the next remote connection attempt. Sometimes, rebooting the server helps for a while.

 

Sponsored Content

Read the Best Personal and Business Tech without Ads

Staying updated on what is happening in the technology sector is important to your career and your personal life but ads can make reading news, distracting. With Thurrott Premium, you can enjoy the best coverage in tech without the annoying ads.

  1. Checking the Event Viewer on the remote server shows these events:Log Name: Application
    Source: Application Error
    Date: 04/06/2012 14:11:38
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer:
    Description:
    Faulting application name: svchost.exe_TermService, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
    Faulting module name: rdpcorekmts.dll, version: 6.1.7600.16952, time stamp: 0x4f1f9e66
    Exception code: 0xc0000005
    Fault offset: 0x000000000000a793
    Faulting process id: 0x22e8
    Faulting application start time: 0x01cd4242c6fd4162
    Faulting application path: C:\Windows\System32\svchost.exe
    Faulting module path: C:\Windows\system32\rdpcorekmts.dllAnd:Log Name: System
    Source: Service Control Manager
    Date: 04/06/2012 14:12:12
    Event ID: 7011
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer:
    Description:
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the TermService service.

    And:

    Log Name: System
    Source: Service Control Manager
    Date: 04/06/2012 14:12:40
    Event ID: 7034
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer:
    Description:
    The Remote Desktop Services service terminated unexpectedly. It has done this 4 time(s).

    And:

    Log Name: System
    Source: Service Control Manager
    Date: 04/06/2012 14:12:10
    Event ID: 7011
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer:
    Description:
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.

Solving the RDP Problem on Windows Server 2008 R2

It turns out that the cause for the problem is two important Windows security updates:

  • KB 2621440
  • KB 2667402

These updates were part of MS012-20, and were downloaded to the servers sometime in the second half of March 2012, if their settings were configured so.

The solution to the problem begins by uninstalling both updates. First, we uninstall KB 2667402:

Uninstall KB 2667402

Uninstall KB 2667402-2

Then we reboot the server.

Reboot the server

Next, we uninstall KB 2621440:

Uninstall KB 2621440

Uninstall KB 2621440 - 2

Then we reboot the server again.

Reboot server again

Now, we need to reinstall the updates, but we need to do so in this particular order.

First, install KB 2667402:

Install KB 2667402

Install KB 2667402 - 2

Then reboot the server.

Reboot Server

Next, we install KB 2621440:

Install KB 2621440

Install KB 2621440 - 2

Then reboot the server again.

Final Reboot

Conclusion

This will solve the RDP problem on your Windows Server 2008 R2 machine.

Related Topics:

BECOME A PETRI MEMBER:

Don't have a login but want to join the conversation? Sign up for a Petri Account

Register
Comments (9)

9 responses to “Problems with RDP Connections on Windows Server 2008 R2”

  1. Problems with RDP Connections on Windows Server 2008 R2 | The Alfred

    [...] https://petri.com/rdp-windows-server-2008-r2.htm Related Posts:Microsoft confirms code execution bug in WindowsPutting all of Your Eggs in One Basket – or How NOT to do LayoffsHere come hypervisors you can trustIndestructible rootkit enslaves 4.5m PCs in 3 monthsWhen you try to install RSAT (Remote Server Administration Tools for Windows 7) on Windows 7 SP1, you will get this error message: “This update is not applicable to your computer”. Posted in Networking, Servers, system admins | Tagged Networking, system admins [...]
  2. Problems in RDP Connections on Windows Server 2008 R2 | IT (Systems, Networks, Security) | Scoop.it

    [...] Learn how to solve RDP problems on your Windows Server 2008 R2 machine.  [...]
  3. RDP issue on Windows 2008 Server R2 | Sysadmin Manhattan

    [...] https://petri.com/rdp-windows-server-2008-r2.htm [...]
  4. Mo

    Hello I done exactly that with the removal of both the updates and I re-installed and rebooted. I still have this issue with remote desktop. Can someone please provide a solution to this. Thanks in advance
  5. Nick Izaak

    This happened on a Windows 2008 R2 Enterprise server running SQL 2012 after installing the latest HP Service Pack. My situation was very different, the port 3389 would refuse to open/listen. Firewalls were off, nothing else was using that port. Looking at the device manager drivers, the Winstation driver was disabled with a code 22 and refused to start. These 2 MS hotfixes fixed the issue (thanks to another user who had a similar issue): KB2666484 and KB2624677. The 2nd one will require a reboot. After that, RDP worked perfectly fine. I didn't have to remove any security patches or copy files from another server or touch any registry settings.
  6. Jeff James

    Thanks for the comments, Nick.
  7. jl89996g

    We have this happening regularly across a very large platform of 500+ servers. None of the hotfixes or suggestions have worked for me, so far. It would be great if there was a real solution.
  8. Senor Blue

    Thank goodness that I found this page, I was thinking I would have to rebuild the server! EDIT: Dang it, It worked until I restarted the server again. I might be screwed...

Leave a Reply

Download this eBook!

External Sharing and Guest User Access in Microsoft 365 and Teams

his eBook will dive into policy considerations you need to make when creating and managing guest user access to your Teams network, as well as the different layers of guest access and the common challenges that accompany a more complicated Microsoft 365 infrastructure. The eBook will also outline some of the major decision points across four general-purpose guest access policy scenarios for how an organization can set this up with standard licensing.

Download Now

Sponsored By