From: Johansson, F. <fjo...@em...> - 2003-01-31 11:19:37
|
Hi list, I got the same error on my AIX 433 ML10 box. "ERROR: recv: Connection reset by peer." I got the same error on rdesktop 1.1.0 and 1.2.0 Can someone please give me a hint what's the problem is? Mvh / Regards Fredrik Johansson -----Original Message----- From: Wendy S [mailto:wen...@ho...] Sent: den 30 januari 2003 16:10 To: rde...@li... Subject: [rdesktop-users] Re: ERROR: recv: Connection reset by peer > Connection successful. > ERROR: recv: Connection reset by peer > Disconnecting... > Broken pipe I am getting the exact same thing, connecting to a Win2000 Terminal Server from Redhat 8.0. It's very strange, because nothing changed on my end and suddenly I could no longer get in. They have been making routing and firewall changes at work, which they say should not affect me. I can still get into the server using the Windows XP box at home, but not from Linux. I see that there is a new version just today, so I'll try that tonight. -- Wendy in Chandler, AZ ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ rdesktop-users mailing list rde...@li... https://lists.sourceforge.net/lists/listinfo/rdesktop-users |
From: Rich D. <ri...@op...> - 2003-01-31 11:27:56
|
On 31 Jan 2003, Johansson, Fredrik wrote: > Hi list, > > I got the same error on my AIX 433 ML10 box. > "ERROR: recv: Connection reset by peer." > I got the same error on rdesktop 1.1.0 and 1.2.0 > > Can someone please give me a hint what's the problem is? we got a similar error when using high encryption on win2k after applying service pack 3. seems MS did something to encryption. medium/ low encruption worked fine though. your error could be completely unrelated though. hth - Rich Doughty [...] > > Connection successful. > > ERROR: recv: Connection reset by peer > > Disconnecting... > > Broken pipe > > I am getting the exact same thing, connecting to a Win2000 Terminal Server > from Redhat 8.0. It's very strange, because nothing changed on my end and > suddenly I could no longer get in. They have been making routing and > firewall changes at work, which they say should not affect me. I can still > get into the server using the Windows XP box at home, but not from Linux. > > I see that there is a new version just today, so I'll try that tonight. > > -- > Wendy in Chandler, AZ |
From: Vinay S. <br...@ma...> - 2003-01-31 15:03:33
|
I have tried using medium and low encryption settings, but i still get the same error. Does the w2k server have a terminal server log ?? My Terminal Services Configuration Connections: RDP-Tcp tcp MS RDP 5.0 Server Settings: Terminal server mode Application Server Delete temp files on exit YEs Use temp folders per session Yes Internet Connector Licensing Disable Active Desktop Enable Permission Compatilbility Terminal Server 4.0 Users TIA, Vinay On Fri, 31 Jan 2003, Rich Doughty wrote: > On 31 Jan 2003, Johansson, Fredrik wrote: > > Hi list, > > > > I got the same error on my AIX 433 ML10 box. > > "ERROR: recv: Connection reset by peer." > > I got the same error on rdesktop 1.1.0 and 1.2.0 > > > > Can someone please give me a hint what's the problem is? > > we got a similar error when using high encryption on win2k after applying > service pack 3. seems MS did something to encryption. medium/ low encruption > worked fine though. > > your error could be completely unrelated though. > > hth > > - Rich Doughty > > [...] > > > > Connection successful. > > > ERROR: recv: Connection reset by peer > > > Disconnecting... > > > Broken pipe > > > > I am getting the exact same thing, connecting to a Win2000 Terminal Server > > from Redhat 8.0. It's very strange, because nothing changed on my end and > > suddenly I could no longer get in. They have been making routing and > > firewall changes at work, which they say should not affect me. I can still > > get into the server using the Windows XP box at home, but not from Linux. > > > > I see that there is a new version just today, so I'll try that tonight. > > > > -- > > Wendy in Chandler, AZ > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > |
From: Wendy S <wen...@ho...> - 2003-01-31 15:39:26
|
> Connections: RDP-Tcp tcp MS RDP 5.0 Isn't this the problem? I thought RDesktop is still speaking RDP 4.0. My problems started after a "maintenance weekend" during which patches were applied to the terminal server. I don't know what they changed, but after that I started getting the 'Connection reset by peer' message. Just curious: Those of you who *are* able to connect to Win2000 Terminal Servers using rdesktop, are you connecting to fully patched servers? -- Wendy in Chandler, AZ |
From: Rich D. <ri...@op...> - 2003-01-31 15:56:26
|
On 31 Jan 2003, Wendy S wrote: > > Connections: RDP-Tcp tcp MS RDP 5.0 > > Isn't this the problem? I thought RDesktop is still speaking RDP 4.0. > > My problems started after a "maintenance weekend" during which patches were > applied to the terminal server. I don't know what they changed, but after > that I started getting the 'Connection reset by peer' message. if they applied service pack 3, and you use high encryption, then i that's your problem. > Just curious: Those of you who *are* able to connect to Win2000 Terminal > Servers using rdesktop, are you connecting to fully patched servers? > > -- > Wendy in Chandler, AZ > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users - Rich Doughty |
From: Igor F. <ig...@os...> - 2003-01-31 16:00:11
|
Wendy, I'm connecting to Win2K SP3 using rdesktop 1.1.0 from linux and 1.2beta1 from IRIX with no problem. I've configured terminal services on win2k box to use old (RDP 4) protocol though. Igor On Fri, 31 Jan 2003, Wendy S wrote: > > Connections: RDP-Tcp tcp MS RDP 5.0 > > Isn't this the problem? I thought RDesktop is still speaking RDP 4.0. > > My problems started after a "maintenance weekend" during which patches were > applied to the terminal server. I don't know what they changed, but after > that I started getting the 'Connection reset by peer' message. > > Just curious: Those of you who *are* able to connect to Win2000 Terminal > Servers using rdesktop, are you connecting to fully patched servers? > > -- > Wendy in Chandler, AZ > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > |
From: Vinay S. <br...@ma...> - 2003-01-31 16:27:35
|
Igor, How did you change the configuration to use RDP 4 ?? Vinay On Fri, 31 Jan 2003, Igor Filippov wrote: > Wendy, > > I'm connecting to Win2K SP3 using rdesktop 1.1.0 from linux and > 1.2beta1 from IRIX with no problem. I've configured terminal services > on win2k box to use old (RDP 4) protocol though. > > Igor > > > > On Fri, 31 Jan 2003, Wendy S wrote: > > > > Connections: RDP-Tcp tcp MS RDP 5.0 > > > > Isn't this the problem? I thought RDesktop is still speaking RDP 4.0. > > > > My problems started after a "maintenance weekend" during which patches were > > applied to the terminal server. I don't know what they changed, but after > > that I started getting the 'Connection reset by peer' message. > > > > Just curious: Those of you who *are* able to connect to Win2000 Terminal > > Servers using rdesktop, are you connecting to fully patched servers? > > > > -- > > Wendy in Chandler, AZ > > > > > > ------------------------------------------------------- > > This SF.NET email is sponsored by: > > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > > http://www.vasoftware.com > > _______________________________________________ > > rdesktop-users mailing list > > rde...@li... > > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > |
From: Vinay S. <br...@ma...> - 2003-01-31 16:32:56
|
Igor, Do I need to license the client devices that will be accessing Windows Terminal Services using rdesktop ?? Vinay |
From: Igor F. <ig...@os...> - 2003-01-31 17:25:26
|
Vinay, Hmm, I guess I'm in the wrong, probably what I should have said was "configured to use Server 4.0 compatibility" - don't know if it affects anything, but it seems it's RDP 5.0, not 4.0... I set it up tfrom the very beginning when I installed win2k, but I believe you can change it in "Administrative Tools/Terminal Services Configuration" -> Server Settings -> Permission Compatibility Probably not what are you looking for, sorry. Igor On Fri, 31 Jan 2003, Vinay Sequeira wrote: > > Igor, > > How did you change the configuration to use RDP 4 ?? > > Vinay > > > On Fri, 31 Jan 2003, Igor Filippov wrote: > > > Wendy, > > > > I'm connecting to Win2K SP3 using rdesktop 1.1.0 from linux and > > 1.2beta1 from IRIX with no problem. I've configured terminal services > > on win2k box to use old (RDP 4) protocol though. > > > > Igor > > > > > > > > On Fri, 31 Jan 2003, Wendy S wrote: > > > > > > Connections: RDP-Tcp tcp MS RDP 5.0 > > > > > > Isn't this the problem? I thought RDesktop is still speaking RDP 4.0. > > > > > > My problems started after a "maintenance weekend" during which patches were > > > applied to the terminal server. I don't know what they changed, but after > > > that I started getting the 'Connection reset by peer' message. > > > > > > Just curious: Those of you who *are* able to connect to Win2000 Terminal > > > Servers using rdesktop, are you connecting to fully patched servers? > > > > > > -- > > > Wendy in Chandler, AZ > > > > > > > > > ------------------------------------------------------- > > > This SF.NET email is sponsored by: > > > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > > > http://www.vasoftware.com > > > _______________________________________________ > > > rdesktop-users mailing list > > > rde...@li... > > > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > > > > > > > > > > > ------------------------------------------------------- > > This SF.NET email is sponsored by: > > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > > http://www.vasoftware.com > > _______________________________________________ > > rdesktop-users mailing list > > rde...@li... > > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > > > |
From: dr j. h. <jo...@fr...> - 2003-01-31 17:49:04
|
On Friday 31 January 2003 16:32, Vinay Sequeira wrote: >Do I need to license the client devices that will be accessing Windows >Terminal Services using rdesktop ?? Yes. If you've run out of licenses, or temporary licenses, you'll get a 'Connection reset by peer' message from rdesktop and a message in the event log on the server saying "Could not issue a client license". cheers john |
From: Vinay S. <br...@ma...> - 2003-02-02 22:51:01
|
Hi, I got rdesktop working again.. I activated the terminal licensing on the w2k server and boom it started accepting connections again.. Thanks to everyone(especially to Igor, John and Wendy), who provided some input,, Vinay On Fri, 31 Jan 2003, dr john halewood wrote: > On Friday 31 January 2003 16:32, Vinay Sequeira wrote: > >Do I need to license the client devices that will be accessing Windows > >Terminal Services using rdesktop ?? > > Yes. If you've run out of licenses, or temporary licenses, you'll get a > 'Connection reset by peer' message from rdesktop and a message in the event > log on the server saying "Could not issue a client license". > > cheers > john > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > |
From: Steve F. <st...@ne...> - 2003-02-01 04:55:49
|
Wendy, I currently use rdesktop with Win2k Server at Service Pack 3 with no issues. I just built the latest release and it works great too. Best, Steve On Fri, 2003-01-31 at 08:38, Wendy S wrote: > > Connections: RDP-Tcp tcp MS RDP 5.0 > > Isn't this the problem? I thought RDesktop is still speaking RDP 4.0. > > My problems started after a "maintenance weekend" during which patches were > applied to the terminal server. I don't know what they changed, but after > that I started getting the 'Connection reset by peer' message. > > Just curious: Those of you who *are* able to connect to Win2000 Terminal > Servers using rdesktop, are you connecting to fully patched servers? > > -- > Wendy in Chandler, AZ > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > |