tsclient connected to Windows server once then failed

Asked by Robin Hall on 2010-11-16

I am trying to connect to a school remote desktop using either tsclient or grdesktop. I successfully connected the first time I used tsclient. Since then, I have not been able to connect using either tsclient or grdesktop. The window closes instantly after connecting. Do these programmes save a profile that I need to edit perhaps?

Thanks,
Robin

I have found out a bit more about the problem. The first time I use TSClient, it creates two new folders in my home folder, .rdesktop and .tsclient. .rdesktop contains a licence document and .tsclient contains two files called last.tsc and mru.tsc. Deleting .rdesktop and .tsclient makes the connection work again.

I have been trying to connect to a Windows Server 2008 R2 Standard.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu tsclient Edit question
Assignee:
No assignee Edit question
Solved by:
Robin Hall
Solved:
2010-12-01
Last query:
2010-12-01
Last reply:
Robin Hall (robinwhall) said : #1

Thanks for sorting this out for me. I'm a bit new to this.

Cheers,
Robin

On 16 November 2010 22:50, marcobra (Marco Braida) <
<email address hidden>> wrote:

> Your question #134326 on tsclient in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/tsclient/+question/134326
>
> Project: Ubuntu => tsclient in ubuntu
>
> --
> You received this question notification because you are a direct
> subscriber of the question.
>

Robin Hall (robinwhall) said : #2

I have found a solution to this. The problem lies in the temporary licence that is stored in the .rdesktop folder. You can stop rdesktop from storing the licence using the following commands in a terminal:

rm -rf .rdesktop
touch .rdesktop

The full description can be found by following this link:
http://h30499.www3.hp.com/t5/Workstations-Thin-Clients/T5145-Remote-Desktop-Services-Terminal-Services-Device-CALs/m-p/1156396

I hope that helps anyone else having the same trouble.

Thanks to Lucifer_tas on the HP community forum for posting his solution.