Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
04-25-2008, 06:17 AM
|
#1
|
LQ Newbie
Registered: Apr 2008
Posts: 4
Rep:
|
rfbdrake failed to extract public key from certificate
I'm running Mandriva's latest stable version and when trying to connect to a remote desktop using rfbdrake (from console, since if running it from the menu, it opens and as soos as I click on Connect, the window closes) I get the following message:
ERROR: Failed to extract public key from certificate
ERROR: send: Connection reset by peer
ERROR: Connection closed
Any clues?
I have already tried reinstalling it....
|
|
|
06-11-2008, 10:57 AM
|
#2
|
LQ Newbie
Registered: Jun 2008
Posts: 2
Rep:
|
randon7533,
Have you found a solution to this problem??? I am having the same thing trying to RDP-connect from a 2X client. Intresting is that before activations License Server connection was OK, and right after I activated it and installed licenses - I am getting this message, and can not connect anymore.
Any clues would be highly appreciated.
|
|
|
06-12-2008, 05:51 AM
|
#3
|
LQ Newbie
Registered: Apr 2008
Posts: 4
Original Poster
Rep:
|
RDPv5
I have been talking to my network admin and apparently this error has something to do with RDP version.
I used to connect to my company's servers using rfbdrake, but finally we realized I was getting this error whenever I tried to connect to a server running Windows Server 2008. I am no longer a Windows user so I don't know exactly but it seems Win Server 2008 is using RDPv5.2 and RDCv6.1 and rfbdrake is not yet compatible.
We also tried connecting to older Windows running servers and we didn't come across that error.
If I find out something else, I'll let you know.
Good luck!
|
|
|
06-12-2008, 05:59 AM
|
#4
|
LQ Newbie
Registered: Apr 2008
Posts: 4
Original Poster
Rep:
|
+ info
According to wikipedia "Microsoft refers to the official RDP client software as either Remote Desktop Connection (RDC) or Terminal Services Client (TSC)." and also "128-bit encryption, using the RC4 encryption algorithm (this is the default security; older clients may use encryption of lesser strength). But because of the man-in-the-middle vulnerability in pre-version 6.0 implementations, in many circumstances the traffic can be decrypted along the way" and "Version 6.1 was released in February 2008 and is included with Windows Server 2008".
Finally, on rdesktop, as of May 2008, "rdesktop is commonly used on desktop Linux installations to connect to Microsoft Windows computers running Terminal Services, including Windows XP Professional, Windows 2000 Terminal Server, Windows Server 2003 and Windows Vista.".
As you can see Windows Server 2008 is not listed above....
|
|
|
06-13-2008, 12:32 AM
|
#5
|
LQ Newbie
Registered: Jun 2008
Posts: 2
Rep:
|
thanks a lot for the info. nothing else but to wait now. i reinstalled server 2003 back and it all works again.
|
|
|
06-20-2008, 05:15 PM
|
#6
|
LQ Newbie
Registered: May 2005
Location: North Carolina
Distribution: Debian, CentOS
Posts: 2
Rep:
|
I had the same problem except I'm using rdesktop on Debian. Installing the latest version of rdesktop (1.6.0) worked for me. Give that a shot.
|
|
|
08-07-2012, 09:27 PM
|
#7
|
LQ Newbie
Registered: Aug 2012
Posts: 1
Rep: 
|
I noticed that Microsoft runs version 4 of rdp however rdektop defaults to version 5
I used the following command and it worked fine
rdesktop -d yourdomain -g 100% 192.168.1.1 -4
Where -4 in the end runs the rdp client in version 4.
If you want to run this command in xterm then:
xterm -e "rdesktop -d yourdomain -g 100% 192.168.1.1 -4"
Hope this helps.
|
|
|
All times are GMT -5. The time now is 06:32 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|