#83 Connection reset - cannot issue license

closed
nobody
None
5
2011-07-11
2004-02-21
John Unger
No

I am attempting to connect to a Win2K Terminal Server
(licensed) using RDesktop 1.3.1 but always get a "connection
reset by peer" error message. The Terminal Server event log
shows "Event ID: 1004 - The Terminal Server cannot issue a
client connection license."

I am running SuSE 8.2 and have tried both RDP 4 and 5.

Discussion

  • Nobody/Anonymous

    Logged In: NO

    After a server upgrade we struggled for several days with
    this. Try deleting the license file from your ~/.rdesktop
    directory. As far as I can tell this is not documented
    anywhere but it fixed the problem immediately for us.

     
  • Nobody/Anonymous

    Logged In: NO

    This happens because you are trying to an unlicenced
    connection to the Win2k server (terminal server CAL's
    required for all MS Windows 9x, Rdesktop etc). Work around,
    you can get the Win2k server to issue a temporary licence
    for 3 months with a new host (workstation) name, this works
    Ok but you have to change the name every 3 months

     
  • Alex Neilson

    Alex Neilson - 2004-07-27

    Logged In: YES
    user_id=639916

    I've been using rdesktop a long time without
    problems (much longer than 3 months) for
    both admin and application TS configurations.
    Recently, the domain server changed, and I
    get knocked off of some systems like the poster
    in the lead article. Changing names with "-n"
    doens't help. TS server changed perhaps?

    I have noticed that I've never had a ~/.rdesktop
    directory created: is this supposed to happen, at
    least when connecting to an application-configured
    TS box? I tried creating one to prime rdesktop, but
    no license is ever written.

    Thanks,

    AtG

     
  • Alex Neilson

    Alex Neilson - 2004-07-27

    Logged In: YES
    user_id=639916

    I've been using rdesktop a long time without
    problems (much longer than 3 months) for
    both admin and application TS configurations.
    Recently, the domain server changed, and I
    get knocked off of some systems like the poster
    in the lead article. Changing names with "-n"
    doens't help. TS server changed perhaps?

    I have noticed that I've never had a ~/.rdesktop
    directory created: is this supposed to happen, at
    least when connecting to an application-configured
    TS box? I tried creating one to prime rdesktop, but
    no license is ever written.

    Thanks,

    AtG

     
  • Samuel Mannehed

    Samuel Mannehed - 2011-07-11
    • status: open --> closed
     
  • Samuel Mannehed

    Samuel Mannehed - 2011-07-11

    Old request, closing. Try the newest version of RDP.

     
  • Samuel Mannehed

    Samuel Mannehed - 2011-07-11

    Try the newest version of rdesktop, not RDP***