Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
While scanning the changelog for KDE 3.2 this morning, I noticed something that caught my eye. KDE 3.2 is said to support Windows Remote Desktop protocol now.
Does anyone know what this support includes? Is it just that a system using KDE can connect to a Windows box using Remote desktop (a la integrated rdesktop), or can a Windows box now connect to a KDE system using the remote desktop tool?
If its the latter, thats pretty exciting to me for interoperability purposes and for the fact that I can ditch VNC.
KDE 3.2 was JUST released, and I haven't had time to install it yet. Could it be possible that I was asking this question to help me decide whether or not to try it out right away? I'd say so, but obviously you had a problem considering that so you responded in the way you did.
You also didn't answer my questions at all.
I've used krfb before, but that has not handled RDP in the past. Also, KDE 3.1's krfb/krdc lacks the RDP support and since I do not have 3.2 as its just been released, downloading it would not really help me.
If the RDP support handles Windows-to-Linux and Linux-to-Windows connections, then I will get it very soon.
It includes some form of RDP support, I am just unsure as to what was actually implemented.
rdesktop has allowed connections from a Linux box to a Windows desktop over RDP for sometime, I am just curious as to if KDE 3.2 supports a Linux desktop being shared with a Windows box over a Terminal Services/Remote desktop connection.
I am guessing KDE 3.2 has integrated rdesktop into some tool of its own, but I may be wrong in that assumption.
Sorrodos, could you tell me if you have already found a way to connect to your KDE, using a Windows machine??
The KDE comes with the VNC server, called: krfb. The client is krdc.
I want to connect to this standard VNC server, that comes in KDE, using the Windows XP VNC cliente (I think that you are trying to do the same thing). You can access it, in Windows by start -> programs -> accessories -> communication -> access to a remote desktop area (something like this... I'm from brazil, sorry any wrong word).
If it is possible to access kde from windows, it will be great, because I won't need to install anything on windows, and I won't need to install anything on linux too. This vnc server comes with every KDE, on linux.
I tryed to connect, but I didn't have any lucky so far. I marked the following options on kde control center -> desktop sharing:
1) allow connections withou an invitation
2) anounce service on network
3) allow connections without invitation to control the computer.
But, when I try to access it from windows, I get an error message.