Home Forums HCL Reviews Tutorials Articles Register Search Today's Posts Mark Forums Read
 LinuxQuestions.org [TUTORIAL] AD integration with Ubuntu 14.04 and winbind
 LinuxQuestions.org Member Success Stories Just spent four hours configuring your favorite program? Just figured out a Linux problem that has been stumping you for months? Post your Linux Success Stories here.

Notices

 08-27-2014, 10:52 AM #1 rabbit2345 Member   Registered: Apr 2007 Location: 中国上海 Distribution: openSUSE 11.3 Posts: 371 Rep: [TUTORIAL] AD integration with Ubuntu 14.04 and winbind So it seems the internet is not short of winbind/smb documentation, but I have yet to find a cohesive start to finish guide for the setup process. So here goes nothing! This guide is for people looking to set up a Linux machine that will authenticate in a 1 forest, 1 domain Active Directory environment. A bit of advice: be patient. This was one of the most frustrating things I have ever set up, mostly due to old/fragmented help around the internet. I strongly recommend against using Ubuntu's official guide, it's outdated and borderline useless. Hopefully I can save someone from a concussion with this. 1. Install winbind and other helper packages. Here are the versions I used while writing this: winbindd: 4.1.6-Ubuntu samba: 4.1.6-Ubuntu smbd: 4.1.6-Ubuntu nmdb: 4.1.6-Ubuntu The command to install all required packages: Code: # apt-get install winbind samba libnss-winbind libpam-winbind krb5-config krb5-locales krb5-user Of course, you'll need to install the dependencies as well. Just say yes to whatever apt-get comes up with. 2. Setup Kerberos authentication. AD uses standard (for once) Kerberos for authentication, which easily fits in with Linux. The environment I'm working in is as follows: Domain controller: ad.bfs.com (10.0.0.20) DNS server: 10.0.0.20 NetBIOS domain name: BFS Kerberos configuration is located at: Code: /etc/krb5.conf The following is my working krb5.conf: Code: [libdefaults] ticket_lifetime = 24000 default_realm = AD.BFS.COM default_tgs_entypes = rc4-hmac des-cbc-md5 default_tkt__enctypes = rc4-hmac des-cbc-md5 permitted_enctypes = rc4-hmac des-cbc-md5 dns_lookup_realm = true dns_lookup_kdc = true dns_fallback = yes [realms] AD.BFS.COM = { kdc = ad.bfs.com:88 default_domain = ad.bfs.com } [domain_realm] .ad.bfs.com = AD.BFS.COM ad.bfs.com = AD.BFS.COM [appdefaults] pam = { debug = false ticket_lifetime = 36000 renew_lifetime = 36000 forwardable = true krb4_convert = false } [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log Capitalization matters! The realm name is just your domain controller's address in all caps. 3. Kerbs authentication Once saved, test the setup with the following command. In this test, I'm looking for myself (brian) in the Kerbs realm of AD.BFS.COM controlled by the server at ad.bfs.com. Code: # kinit brian@AD.BFS.COM This should return a password prompt for your test user, NOT the root user. If you get an error message of any kind, be sure your DC is online and reachable at the specified address + port and the username exists in the directory. Once you successfully authenticate with the DC, we now need to authenticate an account with binding privileges. In my case, it's my ad-brian account. Code: # kinit ad-brian@AD.BFS.COM This should go down like the test user, and you should receive a password prompt for the specified user, and receive nothing back upon completion. 4. winbind setup (the real fun begins now) The default configuration given to you be Ubuntu is lengthy and a bit difficult to read. A much simpler one is given below, you will need to tune my configuration to suit your needs. The file is located at: Code: /etc/samba/smb.conf Code: [global] netbios name = BFS-SCANNER workgroup = BFS security = ADS realm = AD.BFS.COM encrypt passwords = yes idmap config *:backend = rid idmap config *:range = 5000-100000 winbind allow trusted domains = no winbind trusted domains only = no winbind use default domain = yes winbind enum users = yes winbind enum groups = yes winbind refresh tickets = yes template shell = /bin/bash If you must modify this file, I strongly recommend against messing with the idmap section unless you know exactly what you're doing. This by itself is the mother of all bitches to get working if you don't know what you're doing. The rid backend I'm using will work just fine for most workstations. As long as you keep the range consistent between Linux machines, the resulting uid/gid's will stay uniform between machines. 5. Configure nss to make domain accounts locally available. The nss configuration is located at: Code: /etc/nsswitch.conf All you need to do is append winbind to the end of the passwd and group lines. Like this: Code: passwd: compat winbind group: compat winbind shadow: compat hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis 6. Joining the domain. Easiest part of the whole tutorial: Code: # net ads join -k You may get a DNS error, but the important bit is the successful domain joining message. As long as it informs you of this, you are fine. Once joined, start or restart the following three services with this command: Code: # service winbind restart; service nmbd restart; service smbd restart Note: it helps to define this chain as a function for easy refreshed in the future. winbind will crap out on you if you aren't joined to a domain, so no shortcuts. 7. Testing winbind setup. Hopefully you've made it this far, this is about when you'll start hitting enormous brick walls. Chin up! The rid backend will enumerate all domain accounts and groups and add them to a local database (not /etc/passwd). You need to first verify rid has correctly mapped out UID's and other info. Code: # wbinfo -u # wbinfo -g # wbinfo -i brian # getent passwd # getend group All 5 commands must return correct information before you can proceed. If this were some Ubuntu guide, I'd just leave it at that. Thankfully, it's not. wbinfo -u: all domain users wbinfo -g: all domain groups wbinfo -i brian: user information for brian Code: brian:*:6106:5513:Brian:/home/BFS/brian:/bin/bash getent passwd: all locally available accounts. Domain accounts will be at the bottom. getent group: all locally available groups. Domain groups will be at the bottom. If wbinfo -u and -g are successful, but you get this for wbinfo -i brian: Code: failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND Could not get info for user brian that likely indicates something wrong in the idmap section and is very bad. The above configuration posted is confirmed to work fine with Ubuntu 14.04 and the versions listed above. It could also mean the user you asked for does not exist. If wbinfo -i brian returns this: Code: brian:*:4294967295:4294967295:Brian:/home/BFS/brian:/bin/bash This is also very bad. winbind is not properly enumerating UID/GID's from the domain. If you nss configuration is alright, then this is almost certainly caused by bad idmap options. Again, the smb.conf file posted above is confirmed to work. The same goes for getent passwd and groups. If the id's on the users or groups are 4294967295 and not within the range specified, this is wrong and will not function correctly. Take another look at your idmap section. Just in case you did, it should be noted the idmap backend = ad does not do what you think it does. This will attempt to pull all user information from the directory, including UID, login shell, etc. If you did not set these for each user in the domain on the DC, this won't work since there will be nothing to pull down! The UNIX attributes tab for each user is where you will need to go if you insist on going this route. I will stick with the rid method in this tutorial. The Samba page gives the options needed to use each backend correctly. After each configuration file edit, be it smb.conf, nsswitch.conf, etc. you need to restart all Samba services: Code: # redo() { service winbind restart; service nmbd restart; service smbd restart; } # redo winbind stop/waiting winbind start/running, process 30540 nmbd stop/waiting nmbd start/running, process 30556 smbd stop/waiting smbd start/running, process 30568 # 8. PAM integration. If you made it this far congratulations! The worst is now over! PAM configuration is nice and easy, just run: Code: pam-auth-update and ensure the Winbind NT/Active Directory authentication box is checked. PAM by default does not create new home directories, so run this to append to your PAM configuration: Code: echo 'session required pam_mkhomedir.so skel=/etc/skel umask=0022' >> /etc/pam.d/common-account To test your new domain authentication setup, simply try logging in: Code: # login BFS-SCANNER login: brian Password: [stuff] brian@BFS-SCANNER:~$pwd /home/BFS/brian brian@BFS-SCANNER:~$ Yay! I have a home directory and login using my domain credentials!! One tiny downside to this setup is that passwd for domain accounts does not appear to work. I get an error every time, but that's minor anyways. Also, I strongly recommend version locking your winbind, samba, libnss-winbind, and libpam-winbind packages. It is a well-known fact the Samba team loves to drop random syntax changes between versions, and this will almost certainly break your setup. If it works, then leave it at that and don't touch it, you never know what might break from an update. Good luck everyone! If I missed anything, tell me and I'll add it.
09-18-2014, 02:18 PM   #2
tbeehler
Member

Registered: Aug 2003
Location: Washington State, USA
Distribution: Mainly RH 9.0
Posts: 227

Rep:
Hey there! Love the post! Two quick things. First, in the section below, you have a typo. getend group should be getent group.

[code]# wbinfo -u
# wbinfo -g
# wbinfo -i brian
# getent passwd
# getend group

Secondly, and I'm not sure if you had this already set up, but I had to add a line in my /etc/hosts file

127.0.0.1 server server.domain.local

I didn't have the server.domain.local in my hosts file, so I had to add it. Other than that, this tutorial worked like butter for me! Thanks!

Quote:
 Originally Posted by rabbit2345 So it seems the internet is not short of winbind/smb documentation, but I have yet to find a cohesive start to finish guide for the setup process. So here goes nothing! This guide is for people looking to set up a Linux machine that will authenticate in a 1 forest, 1 domain Active Directory environment. A bit of advice: be patient. This was one of the most frustrating things I have ever set up, mostly due to old/fragmented help around the internet. I strongly recommend against using Ubuntu's official guide, it's outdated and borderline useless. Hopefully I can save someone from a concussion with this. 1. Install winbind and other helper packages. Here are the versions I used while writing this: winbindd: 4.1.6-Ubuntu samba: 4.1.6-Ubuntu smbd: 4.1.6-Ubuntu nmdb: 4.1.6-Ubuntu The command to install all required packages: Code: # apt-get install winbind samba libnss-winbind libpam-winbind krb5-config krb5-locales krb5-user Of course, you'll need to install the dependencies as well. Just say yes to whatever apt-get comes up with. 2. Setup Kerberos authentication. AD uses standard (for once) Kerberos for authentication, which easily fits in with Linux. The environment I'm working in is as follows: Domain controller: ad.bfs.com (10.0.0.20) DNS server: 10.0.0.20 NetBIOS domain name: BFS Kerberos configuration is located at: Code: /etc/krb5.conf The following is my working krb5.conf: Code: [libdefaults] ticket_lifetime = 24000 default_realm = AD.BFS.COM default_tgs_entypes = rc4-hmac des-cbc-md5 default_tkt__enctypes = rc4-hmac des-cbc-md5 permitted_enctypes = rc4-hmac des-cbc-md5 dns_lookup_realm = true dns_lookup_kdc = true dns_fallback = yes [realms] AD.BFS.COM = { kdc = ad.bfs.com:88 default_domain = ad.bfs.com } [domain_realm] .ad.bfs.com = AD.BFS.COM ad.bfs.com = AD.BFS.COM [appdefaults] pam = { debug = false ticket_lifetime = 36000 renew_lifetime = 36000 forwardable = true krb4_convert = false } [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log Capitalization matters! The realm name is just your domain controller's address in all caps. 3. Kerbs authentication Once saved, test the setup with the following command. In this test, I'm looking for myself (brian) in the Kerbs realm of AD.BFS.COM controlled by the server at ad.bfs.com. Code: # kinit brian@AD.BFS.COM This should return a password prompt for your test user, NOT the root user. If you get an error message of any kind, be sure your DC is online and reachable at the specified address + port and the username exists in the directory. Once you successfully authenticate with the DC, we now need to authenticate an account with binding privileges. In my case, it's my ad-brian account. Code: # kinit ad-brian@AD.BFS.COM This should go down like the test user, and you should receive a password prompt for the specified user, and receive nothing back upon completion. 4. winbind setup (the real fun begins now) The default configuration given to you be Ubuntu is lengthy and a bit difficult to read. A much simpler one is given below, you will need to tune my configuration to suit your needs. The file is located at: Code: /etc/samba/smb.conf Code: [global] netbios name = BFS-SCANNER workgroup = BFS security = ADS realm = AD.BFS.COM encrypt passwords = yes idmap config *:backend = rid idmap config *:range = 5000-100000 winbind allow trusted domains = no winbind trusted domains only = no winbind use default domain = yes winbind enum users = yes winbind enum groups = yes winbind refresh tickets = yes template shell = /bin/bash If you must modify this file, I strongly recommend against messing with the idmap section unless you know exactly what you're doing. This by itself is the mother of all bitches to get working if you don't know what you're doing. The rid backend I'm using will work just fine for most workstations. As long as you keep the range consistent between Linux machines, the resulting uid/gid's will stay uniform between machines. 5. Configure nss to make domain accounts locally available. The nss configuration is located at: Code: /etc/nsswitch.conf All you need to do is append winbind to the end of the passwd and group lines. Like this: Code: passwd: compat winbind group: compat winbind shadow: compat hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis 6. Joining the domain. Easiest part of the whole tutorial: Code: # net ads join -k You may get a DNS error, but the important bit is the successful domain joining message. As long as it informs you of this, you are fine. Once joined, start or restart the following three services with this command: Code: # service winbind restart; service nmbd restart; service smbd restart Note: it helps to define this chain as a function for easy refreshed in the future. winbind will crap out on you if you aren't joined to a domain, so no shortcuts. 7. Testing winbind setup. Hopefully you've made it this far, this is about when you'll start hitting enormous brick walls. Chin up! The rid backend will enumerate all domain accounts and groups and add them to a local database (not /etc/passwd). You need to first verify rid has correctly mapped out UID's and other info. Code: # wbinfo -u # wbinfo -g # wbinfo -i brian # getent passwd # getend group All 5 commands must return correct information before you can proceed. If this were some Ubuntu guide, I'd just leave it at that. Thankfully, it's not. wbinfo -u: all domain users wbinfo -g: all domain groups wbinfo -i brian: user information for brian Code: brian:*:6106:5513:Brian:/home/BFS/brian:/bin/bash getent passwd: all locally available accounts. Domain accounts will be at the bottom. getent group: all locally available groups. Domain groups will be at the bottom. If wbinfo -u and -g are successful, but you get this for wbinfo -i brian: Code: failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND Could not get info for user brian that likely indicates something wrong in the idmap section and is very bad. The above configuration posted is confirmed to work fine with Ubuntu 14.04 and the versions listed above. It could also mean the user you asked for does not exist. If wbinfo -i brian returns this: Code: brian:*:4294967295:4294967295:Brian:/home/BFS/brian:/bin/bash This is also very bad. winbind is not properly enumerating UID/GID's from the domain. If you nss configuration is alright, then this is almost certainly caused by bad idmap options. Again, the smb.conf file posted above is confirmed to work. The same goes for getent passwd and groups. If the id's on the users or groups are 4294967295 and not within the range specified, this is wrong and will not function correctly. Take another look at your idmap section. Just in case you did, it should be noted the idmap backend = ad does not do what you think it does. This will attempt to pull all user information from the directory, including UID, login shell, etc. If you did not set these for each user in the domain on the DC, this won't work since there will be nothing to pull down! The UNIX attributes tab for each user is where you will need to go if you insist on going this route. I will stick with the rid method in this tutorial. The Samba page gives the options needed to use each backend correctly. After each configuration file edit, be it smb.conf, nsswitch.conf, etc. you need to restart all Samba services: Code: # redo() { service winbind restart; service nmbd restart; service smbd restart; } # redo winbind stop/waiting winbind start/running, process 30540 nmbd stop/waiting nmbd start/running, process 30556 smbd stop/waiting smbd start/running, process 30568 # 8. PAM integration. If you made it this far congratulations! The worst is now over! PAM configuration is nice and easy, just run: Code: pam-auth-update and ensure the Winbind NT/Active Directory authentication box is checked. PAM by default does not create new home directories, so run this to append to your PAM configuration: Code: echo 'session required pam_mkhomedir.so skel=/etc/skel umask=0022' >> /etc/pam.d/common-account To test your new domain authentication setup, simply try logging in: Code: # login BFS-SCANNER login: brian Password: [stuff] brian@BFS-SCANNER:~$pwd /home/BFS/brian brian@BFS-SCANNER:~$ Yay! I have a home directory and login using my domain credentials!! One tiny downside to this setup is that passwd for domain accounts does not appear to work. I get an error every time, but that's minor anyways. Also, I strongly recommend version locking your winbind, samba, libnss-winbind, and libpam-winbind packages. It is a well-known fact the Samba team loves to drop random syntax changes between versions, and this will almost certainly break your setup. If it works, then leave it at that and don't touch it, you never know what might break from an update. Good luck everyone! If I missed anything, tell me and I'll add it.

 03-12-2015, 05:52 PM #3 micke76 LQ Newbie   Registered: Mar 2006 Posts: 7 Rep: Whem run the commando kinit andrew@x.local I get this error message. kinit: KDC reply did not match expectations while getting initial credentials Can someone help me with problem?
03-12-2015, 06:56 PM   #4
Habitual
LQ 5k Club

Registered: Jan 2011
Location: Nowhere near you, thank God.
Distribution: High Sierra
Posts: 8,662
Blog Entries: 17

Rep:
Quote:
 Originally Posted by micke76 Whem run the commando kinit andrew@x.local I get this error message. kinit: KDC reply did not match expectations while getting initial credentials Can someone help me with problem?
"Change the Domain name to 'Upper case' as shown" says Transcript section at http://www.slideshare.net/AshwinPawar/krb5

Is your DomainName UPPER CASE IN /etc/krb5.conf ?

 03-12-2015, 07:03 PM #5 rabbit2345 Member   Registered: Apr 2007 Location: 中国上海 Distribution: openSUSE 11.3 Posts: 371 Original Poster Rep: That, and also make certain your domain is DNA resolve-able. If you still encounter problems, please post the versions of winbindd, samba, smbd, and nmdb. -rabbit
 03-13-2015, 04:55 PM #6 micke76 LQ Newbie   Registered: Mar 2006 Posts: 7 Rep: The version for all four is 4.1.6-Ubuntu. I have managed to join Windows client without problems. I have try to change Domain name to uppercase but it didn't helped. Is there something else I should post in this thread, that might explain this problem?
 03-16-2015, 04:20 PM #7 rabbit2345 Member   Registered: Apr 2007 Location: 中国上海 Distribution: openSUSE 11.3 Posts: 371 Original Poster Rep: Can you post your /etc/krb5.conf and the full kinit command you're using? You can edit out your domain name if you want, but it'd be easier to understand your setup if you just left it on. -rabbit
 03-17-2015, 02:29 PM #8 micke76 LQ Newbie   Registered: Mar 2006 Posts: 7 Rep: I use following kinit command. Code: # kinit andrew@TEST.local Here is my /etc/krb5.conf file Code: [libdefaults] ticket_lifetime = 24000 default_realm = EKHOLM.local default_tgs_entypes = rc4-hmac des-cdc-md5 default_tkt__enctypes = rc4-hmac des-cdc-md5 permitted_enctypes = rc4-hmac des-cbc-md5 dns_lookup_realm = true dns_lookup_kdc = true dns_fallback = yes # The following krb5.conf variables are only for MIT Kerberos. krb4_config = /etc/krb.conf krb4_realms = /etc/krb.realms kdc_timesync = 1 ccache_type = 4 forwardable = true proxiable = true # The following encryption type specification will be used by MIT Kerberos # if uncommented. In general, the defaults in the MIT Kerberos code are # correct and overriding these specifications only serves to disable new # encryption types as they are added, creating interoperability problems. # # Thie only time when you might need to uncomment these lines and change # the enctypes is if you have local software that will break on ticket # caches containing ticket encryption types it doesn't know about (such as # old versions of Sun Java). # default_tgs_enctypes = des3-hmac-sha1 # default_tkt_enctypes = des3-hmac-sha1 # permitted_enctypes = des3-hmac-sha1 # The following libdefaults parameters are only for Heimdal Kerberos. v4_instance_resolve = false v4_name_convert = { host = { rcmd = host ftp = ftp } plain = { something = something-else } } fcc-mit-ticketflags = true [realms] TEST.local = { kdc = test.local default_domain = TEST.local } [domain_realm] .test.local = TEST.LOCAL test.local = TEST.LOCAL [appdefaults] pam = { debug = false ticket_lifetime = 36000 renew_lifetime = 36000 forwardable = true krb4_convert = false } [login] krb4_convert = true krb4_get_tickets = false
 04-17-2015, 01:12 PM #9 masterhades LQ Newbie   Registered: Apr 2015 Posts: 1 Rep: Access from windows 7 to my home in samba That such a friend, great guide, I wanted to consult you two points: In which you mention the user uid shows me this: masterhades: *: 6104: 6122: mastehades: / home / DOMPRU / masterhades: / bin / bash As you comment should be another UID. You could tell me how is this ?. And with regard to access, because I go to a laptop with windows 7 which is within the domain shared access to that server key and asks me immediately, which could be ?. Thanks in advance for the support friend. Atte. Jorge
 04-22-2015, 03:38 PM #10 FrancisMuff LQ Newbie   Registered: Apr 2015 Posts: 1 Rep: Redundant kdc possible? Thanks for the nice how-to. In the [realms] section of the krb5.conf, is it possible to add another server name to be able to create a redundant config for the kdc, like I have written below? [realms] AD.BFS.COM = { kdc = ad.bfs.com:88 kdc2 = ad2.bfs.com:88 default_domain = ad.bfs.com } Thanks!
 04-28-2015, 06:11 PM #11 Josh Scott LQ Newbie   Registered: Apr 2015 Location: Boise, ID Distribution: Debian, Linux Mint, FreeBSD Posts: 14 Rep: Rabbit2345, you are my HERO. I have been banging my head against a brick wall for a couple of days over this. I had everything working for a few days then it quit inexplicably..not sure why.. Everything still worked except for getent would return no domain users or groups and when I would try to access the shares it would say "group does not exist" or something like that. I pretty much had everything setup like yours already, but I corrected anything and everything I had to match your setup anyway. The main change I made that I think may have been the trick that cleared the logjam was changing 'idmap config MYDOMAIN:' to 'idmap config *:' in smb.conf. You also had a bunch of stuff for my krb5.conf that I hadn't seen before. Whatever it was, you saved my bacon. Thank you so much!! -- Josh from Eagle, Idaho (Boise area) -- Ubuntu 14.04 LTS Server with Samba & Winbind as a domain member in Windows 2008 R2 domain.
 04-28-2015, 06:26 PM #12 Josh Scott LQ Newbie   Registered: Apr 2015 Location: Boise, ID Distribution: Debian, Linux Mint, FreeBSD Posts: 14 Rep: Ok well whatever I did solved the getent problem. I can now see all my domain users and groups like I should. But now I can't access the shares at all. I'm going on a business trip for a couple of days but maybe I will post my conf files soon and see if we can figure it out. Thanks again! Josh
04-29-2015, 06:52 AM   #13
Fruchtenstein
LQ Newbie

Registered: Nov 2013
Location: Russia
Distribution: Ubuntu. And FreeBSD, too.
Posts: 3

Rep:
It was reallyreallyreally useful! Thanks, Rabbit2345.

Just a couple of notes.

1. In krb5.conf

Quote:
 default_tgs_entypes = rc4-hmac des-cbc-md5 default_tkt__enctypes = rc4-hmac des-cbc-md5
should be

Quote:
 default_tgs_enctypes = rc4-hmac des-cbc-md5 default_tkt_enctypes = rc4-hmac des-cbc-md5
2. In

Quote:
I had to replace the -k option with -U <user@DOMAIN>:

Quote:

 05-05-2015, 12:35 PM #14 Josh Scott LQ Newbie   Registered: Apr 2015 Location: Boise, ID Distribution: Debian, Linux Mint, FreeBSD Posts: 14 Rep: OK back from my business trip. I decided to post a new thread over at http://www.linuxquestions.org/questi...nux-server-73/ called "Ubuntu 14.04 Samba 4 - share permissions stumper" today. Thanks everyone!
 05-06-2015, 05:51 PM #15 RageKat LQ Newbie   Registered: Jun 2010 Posts: 5 Rep: This guide certainly helped me to get further than I'm able before. That actually makes it a bit frustrating, because while: Code: # wbinfo -u # wbinfo -g # wbinfo -i ragekat # getent passwd # getent group all have the expected results, the final step of simply logging in via 'login' isn't accepting the AD credentials. I'm not even sure where to look at this point for the issue. So of course I check the logs. Code: ==> /var/log/samba/log.nmbd <== [2015/05/06 12:30:25, 0] ../source3/nmbd/nmbd.c:902(main) nmbd version 4.1.6-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2015/05/06 12:30:25, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) Ignoring unknown parameter "winbind allow trusted domains" [2015/05/06 12:30:25, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) Ignoring unknown parameter "winbind allow trusted domains" ==> /var/log/samba/log.smbd <== [2015/05/06 12:30:25, 0] ../source3/smbd/server.c:1198(main) smbd version 4.1.6-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2015/05/06 12:30:25, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) Ignoring unknown parameter "winbind allow trusted domains" [2015/05/06 12:30:25.750583, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) Ignoring unknown parameter "winbind allow trusted domains" [2015/05/06 12:30:25.751119, 0] ../source3/smbd/server.c:1278(main) standard input is not a socket, assuming -D option ==> /var/log/samba/log.wb-DOMAIN <== [2015/05/06 12:30:25.689391, 0] ../source3/libsmb/cliconnect.c:1843(cli_session_setup_spnego_send) Kinit failed: Cannot contact any KDC for requested realm ==> /var/log/samba/log.winbindd <== [2015/05/06 12:30:25, 0] ../source3/winbindd/winbindd.c:1453(main) winbindd version 4.1.6-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2015/05/06 12:30:25, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) Ignoring unknown parameter "winbind allow trusted domains" [2015/05/06 12:30:25.666592, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) Ignoring unknown parameter "winbind allow trusted domains" [2015/05/06 12:30:25.671128, 0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache) initialize_winbindd_cache: clearing cache and re-creating with version number 2 ==> /var/log/samba/log.winbindd-idmap <== The only thing that sticks ouot to me is this bit: "Kinit failed: Cannot contact any KDC for requested realm". Double checking the suggested block I have: Code: [realms] DOMAIN.LOCAL = { kdc = dc01.domain.local:88 default_domain = dc01.domain.local } ...which also looks right to me. And even so, if it couldn't reach the domain controller for some reason, then I suspect that Code: kinit ragekat@DOMAIN.LOCAL` shouldn't have worked either, but it appears to. Any thoughts? Last edited by RageKat; 05-06-2015 at 07:10 PM.

 Tags active directory, integration, ubuntu 14.04, winbind

 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 Forum Rules

 Similar Threads Thread Thread Starter Forum Replies Last Post LXer Syndicated Linux News 0 08-02-2013 03:50 PM LXer Syndicated Linux News 0 04-18-2013 06:20 PM LXer Syndicated Linux News 0 02-18-2013 08:32 PM grungerokker13 Linux - Server 1 12-08-2011 11:03 AM matthewhardwick Fedora 2 09-16-2006 05:54 PM

LinuxQuestions.org

All times are GMT -5. The time now is 06:58 PM.

 Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -