Re: [Samba] Samba/Winbind Question
2011/1/11 Dan Burkland dannyburkl...@gmail.com: I have everything working however I have noticed when I boot a RHEL client or restart the Samba Winbind services (in that order) I get a bunch of log entries in /var/log/messages like the following: Jan 11 08:04:27 mn4s34052 winbindd[10980]: ERROR: Initialization failed for alloc backend, deferred! What do you set idmap alloc backend? Only writeable backend such as ldap, tdb and tdb2 can be set in idmap alloc backend. --- TAKAHASHI Motonobu mo...@samba.gr.jp -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba/Winbind Question
Hello all, I am upgrading some clients on my network to the RHEL 5.5 versions of the Samba/Winbind packages (samba3x-3.3.8-0.52) and have a few questions regarding them. I just upgraded my AD domain controller to the 2008 functional level thus requiring an upgrade of the Samba/Winbind clients so I revisited the configurations I had previously made. I have everything working however I have noticed when I boot a RHEL client or restart the Samba Winbind services (in that order) I get a bunch of log entries in /var/log/messages like the following: Jan 11 08:04:27 mn4s34052 winbindd[10980]: ERROR: Initialization failed for alloc backend, deferred! I then started wondering if I really need the Samba Or NMB services running anymore at all so I disabled both and authentication still continued to work just fine (with no entries like the one above appearing in /var/log/messages). If I am just using the Authentication ID mapping features of Winbind can the Samba NMB services be disabled? Thank you -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] winbind question
After each time I restart winbind I have to rejoin the domain in order for wbinfo -t to succeed or smbclient //server/share -U user to succeed. I am running: samba-3.0.10-0.1 (SuSE 9.1 Pro) heimdal-0.6.1rc3-55.9 The following error is returned from wbinfo -t: FileTest:~ # wbinfo -t checking the trust secret via RPC calls failed error code was NT_STATUS_INVALID_COMPUTER_NAME (0xc122) Could not check secret I also get a NT_STATUS_INVALID_COMPUTER_NAME error from smbclient The following is written to the log: /var/log/samba/log.winbindd [2005/02/17 21:29:24, 0] rpc_client/cli_netlogon.c:cli_nt_setup_creds(256) cli_nt_setup_creds: request challenge failed Clock skew does not appear to be the cause: FileTest:~ # net ads info LDAP server: 192.168.1.201 LDAP server name: win_ads1 Realm: MYCOMPANY.COM Bind Path: dc=MYCOMPANY,dc=COM LDAP port: 389 Server time: Thu, 17 Feb 2005 21:32:19 GMT KDC server: 192.168.1.201 Server time offset: 69 Thanks for any guidance in resolving this issue. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] winbind question - internal module error
I have winbind 2.2.9 on solaris 8, sparc. security = domain winbind use default domain = yes obey pam restrictions = yes I'm getting this error in my /var/adm/messages. pam_winbind[508]: [ID 637597 auth.error] internal module error (retval = 3, user = `someuser' It's not affecting winbind functionality, winbind works fine, but I'm not comfortable having the messages constantly logged. Could anyone offer some advice? Thanks. Ben Kim -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] winbind question
every time a cron job runs I get this in my log.winbindd [2002/10/17 13:45:00, 1] nsswitch/winbindd_group.c:winbindd_getgroups(815) user 'root' does not exist the three important lines in my /etc/nsswitch.conf is: passwd: files winbind nisplus shadow: files nisplus group: files winbind nisplus This is probably due to looking up secondary groups (i.e. the group: line) not getpwnam() calls. Okay, thank you, I think I finally get how this works: When figuring out what groups jarboed is in, first /etc/groups gets hit for secondary groups. *After that, winbind gets hit to see if jarboed is in any other groups.* When winbind use default domain = no in smb.conf (the default) winbind doesn't bother checking because there is no domain associated with jarboed, but when winbind use default domain = yes in smb.conf, winbind will hit the PDC to determine what groups MY_DOMAIN+jarboed is in and tack on the additional MY_DOMAIN+Domain Users, etc, groups to the list of secondary groups for jarboed? And for system accounts that don't exist on the PDC (mostly all of them), winbindd_getgroups just spits up the error that there is no such domain user (like root) to be in any groups? ~ Daniel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] winbind question
2.2.6 installed from rpm's on rh 7.2 system. every time a cron job runs I get this in my log.winbindd [2002/10/17 13:45:00, 1] nsswitch/winbindd_group.c:winbindd_getgroups(815) user 'root' does not exist the three important lines in my /etc/nsswitch.conf is: passwd: files winbind nisplus shadow: files nisplus group: files winbind nisplus I thought with the files first it hits /etc/passwd and shadow and doesn't mess with winbind unless it can't find the entries there. Any idea what I'm missing? What info would be more useful? smbd and nmbd are currently not running, just winbindd. Thanks, Daniel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] winbind question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 17 Oct 2002 [EMAIL PROTECTED] wrote: 2.2.6 installed from rpm's on rh 7.2 system. every time a cron job runs I get this in my log.winbindd [2002/10/17 13:45:00, 1] nsswitch/winbindd_group.c:winbindd_getgroups(815) user 'root' does not exist the three important lines in my /etc/nsswitch.conf is: passwd: files winbind nisplus shadow: files nisplus group: files winbind nisplus I thought with the files first it hits /etc/passwd and shadow and doesn't mess with winbind unless it can't find the entries there. Any idea what I'm missing? What info would be more useful? smbd and nmbd are currently not running, just winbindd. This is probably due to looking up secondary groups (i.e. the group: line) not getpwnam() calls. cheers, jerry - Hewlett-Packard - http://www.hp.com SAMBA Team-- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc ISBN 0-672-32269-2SAMS Teach Yourself Samba in 24 Hours 2ed I never saved anything for the swim back. Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE9rz7cIR7qMdg1EfYRAjbIAJ9So+flW6bp3b/KPl5OIstpJ+pQlACbBxC1 YhXQ2mlQBuL+IgQKe7NaP+Q= =JC0Q -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Winbind question...
After reading the documentation and watching the traffic on my new Samba server, I believe that in order for winbind to work correctly, it needs to be constantly able to connect to the main W2K server to retrieve password and username information. My question is: If I cannot assure this constant connection between the servers, is winbind my best solution for maintaining password and user synchronization? My situation: I have two offices connected via a VPN which allows all traffic to flow between the two offices.My main office has a W2K server and I have set up my remote office with Samba/Winbind. The Internet connection is not extremely stable between the offices. Everytime the connection goes down, even briefly, users at the remote office lose their connections to the server and are not able to re-connect without rebooting their PCs. The ideal solution: I would like to be able to set up winbind (or another program) to check with the W2K server periodically for updates only (maybe every day), otherwise I would like it to maintain the usernames and passwords entirely on the Samba server and not require a connection to the W2K server. Relevant smb.conf info: # Global parameters[global] workgroup = SCHEMMER netbios name = FS1_CB security = DOMAIN encrypt passwords = Yes password server =* winbind uid = 1-2 winbind gid = 1-2 winbind separator = + winbind cache time = 86400 Any help would be greatly appreciated. Thanks in advance! Jeremy Lahners Assistant Manager, I.T. The Schemmer Associates Inc. http://www.schemmer.com
