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.
Kinda of made it somewhere.
What was stucking the wbinfo commands was a firewall rule. As a test, I gave full acess (full in, full out) to my Linux machine.
The problem is. My AD domain is part a ramification of a greater Microsoft "forest network". When I send a wbinfo -u, -t, -g, -m, whatever, the machine starts looking over in all AD controllers of all the networks in the greater microsoft "forest". That results on each command, although they do list users, groups, RPC calls suceeded and so on, to take about 20 minutes to work, and login doesn't work (probably due to a timeout).
I don't believe there may be a solution to that but, does anyone has a solution?
Your not using a FQDN for your kdc and your also not listing an admin_server. Not sure if that would make any difference but that is a difference between yours and mine. Of course, my AD domain is much smaller than yours.
I am having similar problem but I am maybe a few steps ahead I have configured all the files and gone through a milion documents. I can join the domain but there is still some trouble. wbinfo -u doesnt work but wbinfo -g will give me the groups in the ad. Also when I use the wbinfo -t to check for trust. Trust is established. I think I am very close to the solution. I'm running FC4 and trying to join Samba to a win 2003 domain. When I use the net ads join -u a message saying that I have joined the domain is displayed. This is only for the administrator account, but when I try to log in with other ad user names i get authentication errors.
It would be pretty safe to assume that I have configured all the necessary files.