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.

I'm not quite sure what you are asking. None of the slackware packages provide the capability to use Remote Desktop Connection technololy aka microsoft.

There are apps you can get like rdesktop that will allow linux to be a client to a microsoft terminal server.

There is nothing than can make it be the server though. Makes sense since it's a microsoft technology and you need to have a Windows NT Terminal Server, capable of natively speaking Remote Desktop Protocol. Windows XP home can't even do it becuase it doesn't have a Terminal Server.

Howver, there are many ways to do this using a different protocol. VNC protocol being the most common one I think.

Ah yes, the name of the application was confusing me, it is indeed 'rdesktop' that I was using to connect to a Windows server and as you say, it'll need to be something like a Terminal Server to speak to a protocol. Thanks for post in helping me identify why it wasn't possible.

You can use vnc over ssh and then just use putty to connect from the windows box. I am still playing around with getting it working properly but I am doing windows xp pro--->smoothwall router--->windows xp Pro at work.