Windows XP(e) refusing to connect to a terminal server

Thu, 23 Jul 2009 14:48:52 +0000

Today a error message reappeared I thought I wouldn’t see again. We use Wyse Thin Clients and 2X running on two terminal servers, to provide the thin clients with applications. Now, once a while one of the thin clients (not all at once, just a single one) refuse to connect to the terminal server jabbing about this:

`1`	`The remote computer disconnected the session because of an error in the licensing protocol.`

The error message you get from the 2X client ain’t the slightest bit more helpful.

Connecting to a remote console with MSTSC 6-0-6001

Wed, 23 Jul 2008 13:02:00 +0000

Well, as one can read in about every damn post you can find for that topic, the /console switch is now silently ignored, as well as the rdp file option " connect to console:i:1".

Now, what you don’t find anywhere (only in some scenario explanation), that it is allowed to specify the mode (ie /console previously and now /admin) within the full address parameter.

Scenario: In the RDC client UI, you specify Computer_name /console in the Computer box (where Computer_name represents the name of the remote computer to which you want to connect), and then click Connect.

Rdp on BAFM

Windows XP(e) refusing to connect to a terminal server

Connecting to a remote console with MSTSC 6-0-6001