Solutions for occasional Remote Desktop Connection failures, desktop Solutions

Solutions for occasional Remote Desktop Connection failures, desktop Solutions

Recently, the company has a SQL Server with a black screen during Remote Desktop Connection. After a while, a message "two computers cannot match the connection time" was reported.

The following figure is displayed when you connect remotely again:

Because the server is in the idc, and the SQL Server service is normal, the server cannot be restarted by force.

The next year is approaching. In case of any problem with the server during the holidays, you cannot log on remotely ......

------------------------------------------------------------- Save other reasons and 10000 words of nonsense ---------------------------------------------------------------

Finally, the logoff command is used to solve the problem:

-- Query Remote Desktop sessions (Note: if the target server is located in a certain domain, the terminal that performs this operation must also be located in the same domain. Otherwise, access is denied .)

Query session/server: MYSERVER_NM

-- Force cancel Session 2 (Note: if the target server is located in a domain, the terminal that performs this operation must also be in the same domain. Otherwise, the session is not found .)

Logoff 2/server: MYSERVER_NM

-- Query Remote Desktop Session again

Query session/server: MYSERVER_NM

At this time, you can use the Administrator account to log on remotely again.

Bytes -------------------------------------------------------------------------------------------------------------------------------

In addition, I paid several hacker commands:

Tasklist/v/s MYSERVER_NM/u: Administrator
[List all processes on MYSERVER_NM for troubleshooting]

Taskkill/s MYSERVER_NM/u: Administrator/im assumer.exe

Terminate the assumer.exe process on the server myserver_nmfor remote termination. You can add the/f parameter for forcible execution. Once executed, the command cannot be stopped]