[ rdesktop-Support Requests-748755 ] rdesktop was running over months since today...
"SourceForge.net" <[email protected]> Wed, 06 Jul 2011 10:21:04 +0200
| Newsgroups | gmane.network.rdesktop.devel |
|---|---|
| Message-ID | <[email protected]> |
Support Requests item #748755, was opened at 2003-06-04 11:46 Message generated for change (Settings changed) made by samhed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=381348&aid=748755&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: n alb (wurz25) Assigned to: Nobody/Anonymous (nobody) Summary: rdesktop was running over months since today... Initial Comment: rdesktop was running over months since today (or may be yesterday) i become the error: "ERROR: recv: Connection reset by peer" from windows with a ms client it works ok. no changes are made on the client. rdesktop version 1.2 can it be a bug ? is it a new suse update (paches) problem ? can you help ? greetings nico ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-02-06 20:04 Message: Logged In: NO I had this happen when I upgraded tsclient and rdesktop and I found if I manually ran rdesktop using the protocol 4 it would work again. ---------------------------------------------------------------------- Comment By: Tricia Bowen (tricia) Date: 2004-01-26 17:50 Message: Logged In: YES user_id=712534 I've ran into this problem before and had to change my client hostname to get the windows licence server to issue me a new certificate. example: old connection - rdesktop -g 1100x800 -n tricia winmachine new connection - rdesktop -g 1100x800 -n tricia2 winmachine ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-07-22 20:45 Message: Logged In: NO driehuis, He's right, partially. It seems as though the SP4 for Windows 2000 Server disables login's from non-Windows 2000 machines in the free "Remote Administration mode". This is why it still works from Windows 2000/XP clients but not Linux for example. It would likely be simple to fake the originator to be a Win2K client instead of Unix/Linux. Any ideas? ---------------------------------------------------------------------- Comment By: Bert Driehuis (driehuis) Date: 2003-06-16 17:04 Message: Logged In: YES user_id=8475 Check your terminal server logs. Chances are that your tempory client license ran out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=381348&aid=748755&group_id=24366 ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2