The terminal server exceeds the maximum allowable connection number 1, first you can telnet to this host (regardless of which method you use), of course, if you can directly operate the machine, but you don't have to use the command line. The console is more intuitive, this is not the problem we describe, slightly. 2, after telnet, first look at the user: Enter the command: Query User system Returns: username sessionname ID State Idle Time Logon Time Administrator Console 0 Run. 2004-10-09 15:37 User1 UserMachine1 1 Run. 2004- 10-09 15:37 User2 12 has been disconnected 2004-10-09 15:37 It can be seen at this time that we can do the same, depending on the specific situation. See it? The user of ID 0 is local landing, ID 1 and ID 12 are users of 3389 landing, the former is running, but the latter has been disconnected, but disconnected the system resources and channels, we have to put It kicked off. Operation as follows.
Enter a command: logoff 12
C: /> Query User // Take a look at the username sessionname ID State Idle Time Logon Time Administrator Console 0 run. 2004-10-09 15:37 User1 Usermachine1 1 run. 2004-10-09 15:37 3, if The server closes the Telnet function (this is default), and the stored procedure can also be extended by the XP_Cmdshell of SQLServer, using the format: master.dbo.xp_cmdshell 'command content', the rest can be referred to the second step. This method requires access to XP_cmdshell.
