The error occurs because there the previous sessions or existing RDP connection to the server or host that have not been disconnected or terminated correctly. To make matters worse, unless the terminal server on the network are fully connected to the remote clients, and no additional slots, it is possible for the administrator to sign the server using Terminal Services Manager, to kill any RDP connections.
Instead of rebooting or restarting the host or the server that the user wants to Remote Desktop or remote control, here's an alternative workaround to remotely disable or terminate "stuck" Terminal Services or Remote Desktop sessions and connections.
Method 1
Manager, Terminal Services or Remote Desktop Services Manager can be used to disable and reset any Terminal Services or Remote Desktop connections. Depending on your operating system, there are various ways to start and run the Terminal Services Manager.
Windows XP and Windows Server 2003 or earlier:
Click Start -> Run and type% SystemRoot% \ System32 \ tsadmin.exe
Windows Vista Windows Server 2008:
Click the Start button and type tsadmin.msc in the Start Search box.
Windows 7 and Windows Server 2008 R2 or later:
Click Start, type Remote Desktop Services Manager in the Start Search box.
Tip: The client operating system or workstation, server, remote administrator (RSAT) should be set for the Manager to exist.
After Remote Manager Desktop Services or Terminal Services Manager starts, right-click on the "Remote Desktop Services Manager" or "All options Servers" and select Connect to a computer.
Then type the name or IP-address of the server with remote desktop service that wants to be manageable.
Log on a remote server, if required.
Authenticated server will be listed on the left panel. Select the desired server is not responding to remote desktop session.
In the right pane, navigate to the Session.
Right-click on the session, which would be disabled and then click Disable.
Method 2
Run the command prompt window.
Authentication on the remote computer using the following "NET USE" command:
NET USE / user: Administrator \ \ server name or IP-address> \ C $
Replace the server name or IP-address with the actual NetBIOS name or IP-address of the remote host. For example, "NET USE / user: Administrator \ \ 188.8.8.8 \ C $.
Enter a password.
Terminate any existing Remote Desktop or Terminal Services connection with the following command:
Reset
Replace the server name or IP-address with the actual NetBIOS name or IP-address of the remote host. For
Tip: Do not notified will be displayed when a session is successfully completed.
Method 3
Running a Command Prompt window, and to authenticate remote host using the following "NET USE" command:
NET USE / user: Administrator \ \ server name or IP-address> \ C $
Replace the server name or IP-address with the actual NetBIOS name or IP-address of the remote host. For example, "NET USE / user: Administrator \ \ 188.8.8.8 \ C $.
Enter a password.
In addition, from Windows Explorer, map a network drive share folder on the target server, and log, respectively.
At the command prompt, type the following command:
qwinsta / server: server name or IP-address
Where is the server name or IP-address is the actual computer name or IP-address of the remote host. For example, "qwinsta / server: 188.8.8.8".
The list of active connections and Remote Desktop or Terminal Services Session will be displayed. Define "hung" connections and its identifier.
To reset and disable the remote desktop or session, run the following command:
rwinsta
Replace
Note: qwinsta a query window station and dumped rwinsta Window Station.
After the Remote Desktop or Terminal Services connection or conversation stops and the disabled, the slot will be released and the remote user can remotely login again.
No comments:
Post a Comment