RemoteApp Disconnected or Remote Desktop Connection Disconnected

By | September 20, 2012

RemoteApp Disconnected or Remote Desktop Connection Disconnected

The common way to manage Windows system is to access it using Microsoft remote desktop/App connection utility. But if we are unable to establish remote desktop connection to a Windows remote computer, we will receive an error message saying “RemoteApp Disconnected”. The common reasons for this failure are,

RemoteApp Disconnected

1) Remote desktop/App connection access to the machine was not enabled.

Resolution: Go to -> My computer -> Right Click Properties -> Remote -> Enable the remote access.

Enable remote desktop connection

By default users granted with Administrator privilege can access the system, any other members other than the Administrator need to be added to the “Selected Users” and “Remote desktop users” Windows group.

The remote desktop users group can be accessible from My Computer -> Right click -> Manage -> Group -> Remote desktop users

2) Be sure that the remote system is powered on; otherwise the RemoteApp Disconnected failure will occurs.

3) Sometime if the system is running with heavy load or experiencing hang state then the same RemoteApp Disconnected occurs.

4) The remote computer is not available on the network. Test the causes that result in the RemoteApp Disconnected error.


Open Windows command prompt and perform the following tests.

A) Ping <ip address of the destination computer> eg: ping (If we receive a timeout or reply failure error, there would be two possibilities.

The target computer is not reachable through network or disconnected from the network.

The ICMP protocol is blocked in the target computer. Large public production servers are always blocked to respond to ICMP protocol to avoid DOS attacks.

B) Ping <fully qualified name> eg:ping (This test ensure proper name resolution is working). Sometime the system name will not resolve correctly causing RemoteApp Disconnected failures.

C) Nslookup <fully qualified name> : eg:nslookup (Testing the name resolution of the target server)

D) Telnet <ip address> 3389 eg: telnet 3389 (Test ensure whether the target remote system’s remote desktop connection port is in opened state). If the test fail’s then we need to check the system internal and router firewall configurations and ensure that there is a proper Inbound/Outbound traffics are enabled to the particular port 3389.



Melbin Mathew

Melbin Mathew

I am Melbin Mathew, Systems Engineer from Kerala, India. I live with my parents, daughter and my wonderful wife. I graduated in 2004 with a bachelor’s degree in Electronics and Hardware from Mahatma Gandhi University, Kottayam and completed certification in MCITP, RHCE, CCNA, VCP ...Read More