[rdesktop-devel] [ rdesktop-Support Requests-901885 ] Connection reset - cannot issue license

[SourceForge.net <no...@so...>]

Support Requests item #901885, was opened at 2004-02-21 22:38
Message generated for change (Comment added) made by samhed
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=381348&aid=901885&group_id=24366

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Priority: 5
Private: No
Submitted By: John Unger (subsynthetic)
Assigned to: Nobody/Anonymous (nobody)
Summary: Connection reset - cannot issue license

Initial Comment:
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. 

----------------------------------------------------------------------

>Comment By: Samuel (samhed)
Date: 2011-07-11 11:53

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

----------------------------------------------------------------------

Comment By: Alex Neilson (daneilson)
Date: 2004-07-27 02:12

Message:
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

----------------------------------------------------------------------

Comment By: Alex Neilson (daneilson)
Date: 2004-07-27 02:12

Message:
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

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2004-05-05 02:12

Message:
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

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2004-04-21 10:44

Message:
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.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=381348&aid=901885&group_id=24366