Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
For some reason, sudo does not recognize my Active Directory groups. Winbind (wbinfo, getent, and the such) works as intended, even returning the group in question. I even tried using one of the users from that Active Directory group, which sudo recognized without problems.
%2007 ALL=(ALL) ALL
does not work, but
nilecirb ALL=(ALL) ALL
does. What could cause something like this to occur?
Thanks in advance,
UPDATE: Trying the primary group listed in getent passwd works, but does not achieve my ideal implementation. Has anyone gotten it working with secondary groups?
Thanks for replying, archtoad6. As a matter of fact, it's running Kubuntu. It's definitely possible that sudo's the one causing all the problems, but how would I determine if that's the case? I just tested local secondary groups with sudo, and those work perfectly.
If it's a Q of getting root privileges for a CLI command, try:
or, if possible:
sudo su -
The problem seems to lie more with sudo authentication than whatever command sudo tried to run. sudo <foo> does not work at all, whether <foo> is "su -" or any other command. My suspicions lean toward the way the sudo in Ubuntu's apt repository is configured. Anyone else have any ideas about the matter or have successfully authenticated with secondary AD groups using Ubuntu's sudo?