How to Fix Windows Server Remote Desktop Terminated issue EVENT LOG Error 144_TCP Socket was gracefully terminated

Akhilesh SM 0 Reputation points

Hi Team

Facing issue from last 20 days, Remote desktop getting terminated due to EVENT ID 144 TCP SOCKET GRACEFULLY TERMINATED.

Any solution for the above error would be helpfull.

A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
4,966 questions
Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,409 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,461 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,344 questions
{count} votes

1 answer

Sort by: Most helpful
  1. vipullag-MSFT 25,446 Reputation points

    Hello Akhilesh SM

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    Based on the error message you are seeing in the event log with error code 144_TCP Socket was gracefully terminated indicates that the Remote Desktop connection was closed gracefully. This can happen due to various reasons such as network issues, server configuration issues, or client-side issues. Here are some troubleshooting steps you can try to resolve the issue:

    1. Make sure that the network connection between the client and server is stable and not dropping packets. You can use tools like ping or tracert to check the network connectivity.
    2. Make sure that the Remote Desktop settings on the server are configured correctly. Check if the Remote Desktop service is running and if the server is configured to allow Remote Desktop connections.
    3. Make sure that the Remote Desktop client is configured correctly. Check if the client is using the correct credentials to connect to the server and if the client is configured to use the correct Remote Desktop settings.
    4. Make sure that the Remote Desktop client is up to date. You can download the latest version of the Remote Desktop client from the Microsoft website.
    5. Sometimes, third-party software can interfere with the Remote Desktop connection. Try disabling any third-party software that might be causing the issue.

    If none of the above steps work, you can try resetting the Remote Desktop configuration on the server.

    1. Open the Registry Editor on the server.
    2. Navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations
    3. Delete the subkeys named RDP-Tcp and Console.
    4. Restart the Remote Desktop service.

    I hope this helps.

    0 comments No comments