Telnet to the current session of Windows Server 2003

[ERROR]:

With Windows XP Telnet Server (Windows Server 2003), each time you log on, the server creates a new session for you and cannot access a server-side logged in session. If some programs on the server are now open and want to monitor program state by Telnet, there is no doubt that you need to log on to the current session of the server.

Find some solutions on the Web:

Method (1), enter "Mstsc.exe/console" at the client command line, and then log on remotely. Try but no, the server will still create a new session.

Method (2), after a normal telnet to the server, enter "Shadow 0" on the server-side command line to launch the console's hidden session. When you enter the above command, your session appears to be frozen when the console output: "Negotiate a remote control license." Please wait a moment ... "。 In the console session on the server, you receive the following message: "Domain" username is requesting remote control of your session. Do you accept the request? , if the user of the console session on the server clicks Yes, you will automatically connect to the console session on a remote server based on Windows Server 2003. If the user of the server console clicks No or does not respond, you receive the following error message at a command prompt on the remote computer: remote control failed. Error code 7051. Error [7051]: The requested session is not configured to allow remote control.

The said configuration allows remote control, which means that the server side also has to allow remote control. To do this: Open the Group Policy snap-in (gpedit.msc), Computer Configuration => Administrative Templates => Windows components => Terminal Services => "set up rules for remote control of Terminal Services user sessions", setting properties in " Enabled, in the Options box, click Full User-authorized control, and then click OK.

Even after the above configuration, someone has to receive shadow 0 of the session request on the server side and click OK. Another disadvantage is that you use the newly created session to control the existing session, with remote control and slow speed. Also, a new session is a waste of server resources, so it's easier to log on to an existing session.

[Reason]:

When Windows XP is upgraded to SP3, you cannot use Mstsc/console to connect to a console Windows XP upgrade to SP3, and the command is replaced by Mstsc/admin to enable XP2 in Mstsc/console.

[Resolve]:

Enter "Mstsc/admin" on the Windows XP client command line and enter the host name, user name, and password as prompted to log on to the session that the server is currently running. Mstsc.exe is actually "Remote Desktop Connection" (the Start menu => All Programs => attachments), but it's easy to give it parameters at the command line.