Verify that you are logged on to the network, and then try connecting again. Please insert your smart card and try again.īecause of a security error, the client could not connect to the remote computer. There is no card inserted in the smart card reader. If the problem continues, contact your network administrator or technical support. The connection was lost due to a network error. This computer can't connect to the remote computer. Please attach a smart card reader and try again. Sure the remote computer is turned on and connected to the network, and that remote access is enabled.Ī smart card reader was not detected. Remote Desktop can't connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network Make Please start the smart card service and try again. The two computers couldn't connect in the amount of time allotted. If the problem continues, contact your network administrator Close your other programs, and then try connecting again. Your computer does not have enough virtual memory available. Verify the computer name and domain that you are trying to connect to. This might mean that "" does not belong to the specified network. Remote Desktop can't find the computer "". A network problem occurred.įor help solving the problem, see "Remote Desktop" in Help and Support. An error occurred while the connection was being established. Your Remote Desktop Services session has ended, possibly for one of the following reasons: The administrator has ended the session.
#Microsoft remote desktop client code
This is a generic return code description when the disconnect code in is not found and return description is not valid. NOTE: When running the command below, 'An internal error has occurred.'. If the disconnect code is found the description will be returned. The following snippet is a PowerShell command to query COM MSTscAx with a decimal disconnect code ID. Such as encryption and security level, the client may attempt connection multiple times and disconnect before the final connection is made. When troubleshooting client-side connections, be aware that depending on a configuration If the disconnect code is not found in the Primary Disconnect Reasons table, see the Extended Disconnect Reasons table.
Some of the disconnect codes returned are extended codes. Not all codes are enumerable from the COM method shown below. The RDP client disconnect codes are written to the 'Microsoft-Windows-TerminalServices-RDPClient/Operational' event login 'Applications and Services Logs/Microsoft/Windows' in Event Viewer. Please see parent article Remote Desktop Services RDS Logon Connectivity Overview for additional information. This article contains most of the current Remote Desktop Client disconnect codes and reasons.