Linux - NetworkingThis 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.
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.
I see great advice for using Samba and winbind to authenticate Linux resources against Active Directory. I have searched the forums, but I don't see an answer to an issue I am facing.
We have SLES9 installed on a server and the rest of our network is Win2K3 native domain with WinXP workstations. We have an app on SLES that users access using a VT emulator. Right now, if a user fires up the emulator, they are prompted for a username and password on Linux before they can proceed to our application. We would like to have the user's credentials already authenticated in Active Directory (username, password) available to the terminal session so that when the user connects the terminal session, the username and password already in use in Active Directory are passed to the terminal session and the user is not prompted for their credentials.
Will Samba and winbind take care of that or do I have to use a 3rd party application? If 3rd party, can anyone suggest a product? Thanks to all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
