Share your knowledge at the LQ Wiki.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 04-14-2014, 03:54 AM   #16
Mark Pettit
Registered: Dec 2008
Location: Cape Town, South Africa
Distribution: Slackware 14.1 64 Multi-Lib
Posts: 476

Rep: Reputation: 158Reputation: 158

Cool - I shall try this over the next few days. I'm a lonely slacker in a company of over 500 microsofities ... :-(
Old 04-14-2014, 11:11 AM   #17
Senior Member
Registered: Jan 2008
Distribution: Arch/Knoppix
Posts: 1,643
Blog Entries: 14

Original Poster
Rep: Reputation: 194Reputation: 194
Set up what exactly? Once you've provisioned the domain, there's literally nothing more you need to do. The provisioning scripts will have created the Kerberos realm, populated the AD database and created the necessary DNS records.

In order to locate the domain controllers in the AD domain, client computers will need to use whichever DNS server holds the AD-specific records.
I guess I mean setup DNS properly. Undoubtedly that's why I can't see my DC from the Windows computers.
Configure the BIND dlz zone if necessary....You'll still have to configure winbind, NSS and PAM
I believe that's what I've got to get a better grasp of.
I think getting Samba to work with A/D is non-trivial
Well, I couldn't agree more. The thing is, setting up Samba 3 was pretty trivial; start it up and there are the shares. I used to have domain logons for Win 98 and XP several years ago, but can't remember how I setup DNS.
Old 10-08-2015, 12:56 AM   #18
Registered: Oct 2008
Posts: 267

Rep: Reputation: 29
Originally Posted by Ser Olmy View Post
You'll still have to configure winbind, NSS and PAM if you want to log on to a Linux system with AD credentials and be able to map Windows SIDs to Unix UIDs and GIDs, just like before.
Hopefully, there is still activity on this thread ...

Your last statement caught my attention. I too have easily and simply provisioned Samba4 AD/DC as a replacement for SBS 2008 and have 10+ Windows workstations authenticating with no problem.

Now, I want to implement Single-Sign-On for Linux workstations. All documentation on the web shows how to do this with OpenLDAP, but as we know, the Samba4 server uses its own Heimdal LDAP, so the web instructions are apparently useless.

Since you say, "You'll still have to configure winbind, NSS and PAM if you want to log on to a Linux system ...", it appears you have some knowledge in this area. What is my first step in getting a Linux workstation to log on using the Samba4 server for authentication?

Need a push in the right direction. I'm lost!
Old 10-08-2015, 10:14 AM   #19
Registered: Jul 2009
Location: Québec, Canada
Distribution: Slackware-current
Posts: 292

Rep: Reputation: 297Reputation: 297Reputation: 297
1 members found this post helpful.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
kerberos Xris718 Linux - Server 9 03-04-2011 03:03 PM
ssh and kerberos error: Server not found in Kerberos database Felipe Linux - Server 1 01-17-2011 04:12 AM
Slackware 12.2, Evolution, Gnome-keyring, Kerberos. meetscott Slackware 2 06-22-2009 03:02 AM
Kerberos 5 1.4.1 Kenji Miyamoto Slackware 1 05-24-2005 08:11 PM
Kerberos krieger Linux - Security 1 01-29-2002 02:40 PM

All times are GMT -5. The time now is 10:04 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration