Re: [Samba] Password problem
Hello Jaap, On Fri, May 18, 2012 at 08:06:22PM +0200, Jaap Winius wrote: Hi folks, My client and I are having a problem getting a portable Esaote ultrasound machine to connect to a Samba server. The unit has an integrated laptop with a Windows XP version that can hardly be modified. Upon delivery the vendor only changed the user name and workgroup for us. When I asked for the user password to make a matching Samba account, the vendor refused because they use a key on a USB stick for that. They said to fill in a name and password for the server every time we needed to access the Windows share. So far I've experimented with the Samba map to guest and guest account options, which should work, but I'd really like to see this machine connect to the Samba server in the usual fashion. Does anyone have any suggestions? Any workarounds, or hacks that I might try? Thanks, Jaap -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba What do you mean with ``connect to the Samba server in the usual fashion''? I guess you want the XP client to be a member of the samba domain. Isn't it? For that, you need to have the rights on the XP client to make it a member of the samba domain (usually admin rights). Without these rights, it will be extremely hard to achieve your goal(s). -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba with ldap+TLS
Dear Bruno, Steve and Samba Friends, If I recall correctly, it is the username used to start smbd, which needs a ldaprc file with apropriate settings. In my case this is root and the file looks like: # # User specific LDAP settings # # Override global directive (if set) TLS_REQCERT demand # client authentication TLS_CERT /root/root.mydomain.com.pem TLS_KEY /root/keys/root.mydomain.com.key But you have to adapt it to your own needs. I hope this helps. On Mon, Nov 07, 2011 at 06:24:42PM +0100, Bruno MACADRE wrote: Hi, No, you don't need CA certificate on win clients 'cause they don't connect directly to the LDAP. Only your Samba server need CA certificate to connect to the LDAP using TLS. Regards, Bruno Le 07/11/2011 18:18, steve a écrit : Hi I know Linux clients need a CA certificate to authenticate via LDAP using TLS. What about win 7 and XP clients using a Samba server? Thanks Steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Password expires every month even though 'Password Must Change' is set to 'never' (Samba+LDAP)
Hello Aaron, To my knowledge, sambaPwdMustChange is obsolete and is simply ignored by Samba. Please correct me if I'm wrong. On Fri, Oct 14, 2011 at 08:30:26AM -0400, Aaron E. wrote: Sounds like you've checked mostly all except your ldap backend... Check your LDAP DB for... (they will be in nix timestamp) sambaPasswordCanChange sambaPasswordLastSet sambaPasswordMustChange setup smbldap-tools package On 10/13/2011 11:00 PM, Jeffrey Chan wrote: I'm using OpenLDAP as backend. On Wed, Oct 12, 2011 at 11:16 PM, Aaron E.ssures...@gmail.com wrote: Just cuirous are you using pam or ldap backend? On 10/12/2011 09:22 AM, Marco Ciampa wrote: On Wed, Oct 12, 2011 at 12:15:16PM +0800, Jeffrey Chan wrote: Hi all, I've posted this a month ago but haven't gotten a reply. Can anyone please help? - Jeff On Mon, Aug 29, 2011 at 5:14 PM, Jeffrey Changoofri...@gmail.com wrote: Hi all, Since a few months ago Samba ask each of our users to change password at log on every month and I have not been able to disable it. I found this page and follow the instructions: http://playingwithsid.**blogspot.com/2010/12/change-** samba-password-expiry-setting.**htmlhttp://playingwithsid.blogspot.com/2010/12/change-samba-password-expiry-setting.html The default ‘Password Must Change’ policy was set to never and pdbedit shows ‘Password Must Change: never’ for each user, yet the passwords still get expire once a month. Can anyone please give me some pointers? - Jeff Just a hint (maybe wrong...) obey pam restrictions = No ... -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/**mailman/options/sambahttps://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Upgrading from 3.0.37 to 3.5.9
Hello Ken and Samba Friends, On Tue, Jul 12, 2011 at 08:32:31AM -0500, Stringer Kenneth M NGA-PRTN USA CTR wrote: Willy, I have not yet attempted the upgrade so unfortunately I have no advice. I am thinking about doing a complete package removal of all previous versions and reinstalling 3.5.9. I only have 8 users, so it's no big deal for them to re-enter their passwords, as long as I back up smb.conf. Ken -Original Message- From: Willy Offermans [mailto:wi...@offermans.rompen.nl] Sent: Tuesday, July 12, 2011 4:08 AM To: Stringer Kenneth M NGA-PRTN USA CTR Cc: samba@lists.samba.org Subject: Re: [Samba] Upgrading from 3.0.37 to 3.5.9 Hello Ken and Samba Friends, On Fri, Jul 08, 2011 at 02:30:39PM -0500, Stringer Kenneth M NGA-PRTN USA CTR wrote: I am upgrading from 3.0.37 to 3.5.9 on the same server and need some advice. I am running Solaris 10 on a domain server that services 10 XP and Win 7 clients. The existing Samba directory structure is not standard. I believe the engineer who built the Solaris install transferred all Samba 2.0 directories from the old server to the current server and then created additional directories for the install and symbolically linked some of the old files to the new install. Anyway, Samba is installed in two different structures on the server: Samba and /etc/samba... and /etc/sfw We are using the sfw directories: The smb.conf file in /etc/samba is symbolically linked to the smb.conf file in /etc/sfw. So here are my questions: 1) How do I migrate the tdbsam database from 3.0.37 to 3.5.9? 2) Can I use the existing smb.conf file? 3) Can I just backup smb.conf and tdbsam files and reinstall to all the default directories and then copy the backup files to the appropriate Samba directories? 4) What else do I need to migrate? I'm sure if I just do a ./configure like the Samba web site says, my whole team will be down until I get it fixed. There seems to be nothing in the documentation, which is very old, to help w/ this issue. Any input to point me in the right direction would be greatly appreciated. When I tried to do a similar update I got (probably) stuck within an upgrade procedure of the tdbsam database. There is a file called group_mapping.tdb.upgraded although the file group_mapping.tdb is missing. Samba complains about the missing file and stops working upon smbclien -L localhost: protocol negotiation failed: NT_STATUS_PIPE_BROKEN. From the log.smbd: snip [2011/07/12 11:03:16, 0] lib/util_tdb.c:tdb_log(664) tdb(/var/db/samba/group_mapping.tdb): tdb_reopen: open failed (No such file or directory) [2011/07/12 11:03:16, 0] lib/util.c:reinit_after_fork(3319) tdb_reopen_all failed. [2011/07/12 11:03:16, 0] smbd/server.c:open_sockets_smbd(570) reinit_after_fork failed. [2011/07/12 11:03:16, 0] lib/util.c:smb_panic(1633) PANIC (pid 80611): reinit_after_fork failed. [2011/07/12 11:03:16, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 4 stack frames: #0 0x122b9fd smb_panic+93 at /usr/local/sbin/smbd #1 0x12ef709 main+5945 at /usr/local/sbin/smbd #2 0x104abdb _start+203 at /usr/local/sbin/smbd #3 0x104ab25 _start+21 at /usr/local/sbin/smbd [2011/07/12 11:03:16, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/smbd /snip Basically nobody can work with samba anylonger since then, and I do not have time to reinstall samba. I already asked for help on this list, but without any success so far. I wonder if you were succesful with the upgrade? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl Yeah! I guess that it is the best solution to reinstall samba completely. However I will take the ``opportunity'' to move on to a LDAP+Samba solution. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Upgrading from 3.0.37 to 3.5.9
Hello Ken and Samba Friends, On Fri, Jul 08, 2011 at 02:30:39PM -0500, Stringer Kenneth M NGA-PRTN USA CTR wrote: I am upgrading from 3.0.37 to 3.5.9 on the same server and need some advice. I am running Solaris 10 on a domain server that services 10 XP and Win 7 clients. The existing Samba directory structure is not standard. I believe the engineer who built the Solaris install transferred all Samba 2.0 directories from the old server to the current server and then created additional directories for the install and symbolically linked some of the old files to the new install. Anyway, Samba is installed in two different structures on the server: Samba and /etc/samba... and /etc/sfw We are using the sfw directories: The smb.conf file in /etc/samba is symbolically linked to the smb.conf file in /etc/sfw. So here are my questions: 1) How do I migrate the tdbsam database from 3.0.37 to 3.5.9? 2) Can I use the existing smb.conf file? 3) Can I just backup smb.conf and tdbsam files and reinstall to all the default directories and then copy the backup files to the appropriate Samba directories? 4) What else do I need to migrate? I'm sure if I just do a ./configure like the Samba web site says, my whole team will be down until I get it fixed. There seems to be nothing in the documentation, which is very old, to help w/ this issue. Any input to point me in the right direction would be greatly appreciated. When I tried to do a similar update I got (probably) stuck within an upgrade procedure of the tdbsam database. There is a file called group_mapping.tdb.upgraded although the file group_mapping.tdb is missing. Samba complains about the missing file and stops working upon smbclien -L localhost: protocol negotiation failed: NT_STATUS_PIPE_BROKEN. From the log.smbd: snip [2011/07/12 11:03:16, 0] lib/util_tdb.c:tdb_log(664) tdb(/var/db/samba/group_mapping.tdb): tdb_reopen: open failed (No such file or directory) [2011/07/12 11:03:16, 0] lib/util.c:reinit_after_fork(3319) tdb_reopen_all failed. [2011/07/12 11:03:16, 0] smbd/server.c:open_sockets_smbd(570) reinit_after_fork failed. [2011/07/12 11:03:16, 0] lib/util.c:smb_panic(1633) PANIC (pid 80611): reinit_after_fork failed. [2011/07/12 11:03:16, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 4 stack frames: #0 0x122b9fd smb_panic+93 at /usr/local/sbin/smbd #1 0x12ef709 main+5945 at /usr/local/sbin/smbd #2 0x104abdb _start+203 at /usr/local/sbin/smbd #3 0x104ab25 _start+21 at /usr/local/sbin/smbd [2011/07/12 11:03:16, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/smbd /snip Basically nobody can work with samba anylonger since then, and I do not have time to reinstall samba. I already asked for help on this list, but without any success so far. I wonder if you were succesful with the upgrade? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] group_mapping.tdb error upon Samba upgrade
Hello Timur and Samba friends, I have done what you suggested. However group_mapping.tdb is renamed to group_mapping.tdb.upgraded again. To me it looks like some update mechanism cannot finalise and got stuck at some point. Any help to overcome this problem is still welcome! On Mon, Jun 20, 2011 at 04:35:26AM +0200, Timur I. Bakeyev wrote: I'd try to rename that *.upgraded file to the normal one, possibly preserving a copy somewhere. On Fri, Jun 3, 2011 at 10:21 AM, Willy Offermans wi...@offermans.rompen.nlwrote: Dear Samba friends, I have recently upgraded from Samba 3.0.36 to Samba 3.5.6. After upgrade I encounter the following error in log.smbd: [2011/06/03 10:09:43, 0] smbd/server.c:1119(main) smbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2011/06/03 10:09:43.379106, 1] param/loadparm.c:7605(lp_do_parameter) WARNING: The share modes option is deprecated [2011/06/03 10:09:43.379286, 1] param/loadparm.c:7605(lp_do_parameter) WARNING: The printer admin option is deprecated [2011/06/03 10:09:43.401015, 1] smbd/files.c:193(file_init) file_init: Information only: requested 16384 open files, 7129 are available. [2011/06/03 10:12:20, 0] lib/util_tdb.c:tdb_log(664) tdb(/var/db/samba/group_mapping.tdb): tdb_reopen: open failed (No such file or directory) [2011/06/03 10:12:20, 0] lib/util.c:reinit_after_fork(3319) tdb_reopen_all failed. [2011/06/03 10:12:20, 0] smbd/server.c:open_sockets_smbd(570) reinit_after_fork failed. [2011/06/03 10:12:20, 0] lib/util.c:smb_panic(1633) PANIC (pid 20164): reinit_after_fork failed. [2011/06/03 10:12:20, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 4 stack frames: #0 0x122b9fd smb_panic+93 at /usr/local/sbin/smbd #1 0x12ef709 main+5945 at /usr/local/sbin/smbd #2 0x104abdb _start+203 at /usr/local/sbin/smbd #3 0x104ab25 _start+21 at /usr/local/sbin/smbd [2011/06/03 10:12:20, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/smbd when issuing the following command: smbclient -L localhost Enter password: protocol negotiation failed: NT_STATUS_PIPE_BROKEN I noticed that there is a file called /var/db/samba/group_mapping.tdb.upgraded but no /var/db/samba/group_mapping.tdb Samba 3.5.6 is running on FreeBSD 8.1-RELEASE #1 What is going on? Do you need more information to solve this issue? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * Dr. W.K. Offermans CAT Postdoctoral Fellow CAT Catalytic Center Institut f�r Technische und Makromolekulare Chemie RWTH Aachen Worringerweg 1, Raum 38C-150 D-52074 Aachen, Germany Phone: +49 241 80 28592 Fax:+49 241 80 22593 Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl e-mail: willy.offerm...@catalyticcenter.rwth-aachen.de Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Remove obsolete sambaPwdMustChange and sambaKickoffTime from LDAP database
Dear Samba friends, From the information I have found on the internet, I understood that sambaPwdMustChange and sambaLogoffTime are obsolete. When there is no use for these attributes in the future, I would recommend to remove them from the samba scheme. What would be the procedure to follow to remove these attributes and to update the ldap database? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] group_mapping.tdb error upon Samba upgrade
Dear Samba friends, I have recently upgraded from Samba 3.0.36 to Samba 3.5.6. After upgrade I encounter the following error in log.smbd: [2011/06/03 10:09:43, 0] smbd/server.c:1119(main) smbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2011/06/03 10:09:43.379106, 1] param/loadparm.c:7605(lp_do_parameter) WARNING: The share modes option is deprecated [2011/06/03 10:09:43.379286, 1] param/loadparm.c:7605(lp_do_parameter) WARNING: The printer admin option is deprecated [2011/06/03 10:09:43.401015, 1] smbd/files.c:193(file_init) file_init: Information only: requested 16384 open files, 7129 are available. [2011/06/03 10:12:20, 0] lib/util_tdb.c:tdb_log(664) tdb(/var/db/samba/group_mapping.tdb): tdb_reopen: open failed (No such file or directory) [2011/06/03 10:12:20, 0] lib/util.c:reinit_after_fork(3319) tdb_reopen_all failed. [2011/06/03 10:12:20, 0] smbd/server.c:open_sockets_smbd(570) reinit_after_fork failed. [2011/06/03 10:12:20, 0] lib/util.c:smb_panic(1633) PANIC (pid 20164): reinit_after_fork failed. [2011/06/03 10:12:20, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 4 stack frames: #0 0x122b9fd smb_panic+93 at /usr/local/sbin/smbd #1 0x12ef709 main+5945 at /usr/local/sbin/smbd #2 0x104abdb _start+203 at /usr/local/sbin/smbd #3 0x104ab25 _start+21 at /usr/local/sbin/smbd [2011/06/03 10:12:20, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/smbd when issuing the following command: smbclient -L localhost Enter password: protocol negotiation failed: NT_STATUS_PIPE_BROKEN I noticed that there is a file called /var/db/samba/group_mapping.tdb.upgraded but no /var/db/samba/group_mapping.tdb Samba 3.5.6 is running on FreeBSD 8.1-RELEASE #1 What is going on? Do you need more information to solve this issue? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printer settings not saved
Hello Thilo and Samba friends, On Thu, May 26, 2011 at 07:42:41PM +0200, Thilo Uttendorfer wrote: Hello Willy, Did you manage to solve this issue? I'm having the same problem for some time now and I have not any clue yet how to solve this. we solved some issues (the user-settings are save now) by deleting all printers and then adding them again. The difference was that we used net rpc printer migrate [security|settings|forms] against a Windows 2003 server on the first try. We skipped that on the second run. But I have no idea why this should not work. Thilo -- Thilo Uttendorfer Linux Information Systems AG Putzbrunner Str. 71, 81739 München Fon: +49 89 993412-11, Fax: +49 89 993412-99 t.uttendor...@linux-ag.com, http://www.linux-ag.com I will try to remove and to reinstall the concerned printer. Maybe that helps. Although I have no clue on the why and what. But thnx a lot for your input. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printer settings not saved
Daer Thilo and Samba friends, On Fri, May 20, 2011 at 02:43:15PM +0200, Willy Offermans wrote: Dear Thilo, Did you manage to solve this issue? I'm having the same problem for some time now and I have not any clue yet how to solve this. On Wed, Apr 20, 2011 at 04:40:28PM +0200, Thilo Uttendorfer wrote: Hi, I have problems to save printer settings like changing the size from letter to A4. This happens for user settings and default printer settings. The settings are always resetted to default values like letter. The system uses samba 3.4.11, I also did some tests with samba 3.5.8, but nothing changed. After downgrading to 3.3.2 everything worked as expected. I didn't change any samba configuration while up- and downgrading. Bug #6727 sounds a little bit like my problem: [...] Also if I change the configuration (e. g. configure 4 cartridges instead of 2), it is not be saved). But this bug should be fixed with 3.5.8, see: https://bugzilla.samba.org/show_bug.cgi?id=6727 Can somebody confirm this bug? Thank you, Thilo Uttendorfer Is anyone able to solve this issue? or at least to point out how to prevent the settings from being changed all the time? We are using Samba version 3.5.6 on FreeBSD 7.2-RELEASE-p2 -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printer settings not saved
Dear Thilo, Did you manage to solve this issue? I'm having the same problem for some time now and I have not any clue yet how to solve this. On Wed, Apr 20, 2011 at 04:40:28PM +0200, Thilo Uttendorfer wrote: Hi, I have problems to save printer settings like changing the size from letter to A4. This happens for user settings and default printer settings. The settings are always resetted to default values like letter. The system uses samba 3.4.11, I also did some tests with samba 3.5.8, but nothing changed. After downgrading to 3.3.2 everything worked as expected. I didn't change any samba configuration while up- and downgrading. Bug #6727 sounds a little bit like my problem: [...] Also if I change the configuration (e. g. configure 4 cartridges instead of 2), it is not be saved). But this bug should be fixed with 3.5.8, see: https://bugzilla.samba.org/show_bug.cgi?id=6727 Can somebody confirm this bug? Thank you, Thilo Uttendorfer -- Thilo Uttendorfer Linux Information Systems AG Putzbrunner Str. 71, 81739 München t.uttendor...@linux-ag.com, http://www.linux-ag.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans e-mail: wi...@offermans.rompen.nl Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba OpenLDAP TLS
Dear Michael and Samba friends, On Fri, Dec 31, 2010 at 11:50:49PM +0200, Michael Wood wrote: Hi On 30 December 2010 14:35, Willy Offermans wi...@offermans.rompen.nl wrote: Dear Samba friends, I have setup a samba server 3.5 on FreeBSD 8.1-RELEASE-p2 with openldap-sasl-server-2.4. I have specified ``TLSVerifyClient demand'' in slapd.conf and want to enforce the clients to connect and show a valid certificate to the ldap server. As far as I have understood, Samba will act as a client as well and in order to access the ldap server it will need a client certificate as well. I do know how to generate a client certificate, but I do not know where to tell samba to use this client certificate. Is this supported by Samba or do I need to lower the constraints regarding the TLSVerifyClient? Maybe to ``TLSVerifyClient try''? Just a guess, but have you tried the TLS_CERT and TLS_KEY options from the LDAP client config? They're listed in ldap.conf(5) as user-only options, so should be specified in $HOME/.ldaprc or ldaprc in the current directory. Not sure where $HOME or the current directory are for Samba, though, but perhaps that will point you in the right direction. Hope that helps. -- Thanks for your answer! I guess $HOME is the home directory of root in this case, but I'm not sure yet. I have created the following file: /root/ldaprc with the following content: snip # # User specific LDAP settings # # Override global directive (if set) TLS_REQCERT demand # client authentication TLS_CERT /root/certs/root.pem TLS_KEY /root/certs/keys/root.key /snip It helped me to work with ldapadd -ZZ ... commands from the command prompt. I hope that samba works in a similar way, meaning that it will make use of /root/ldaprc to show its client certificate. I have not yet tested samba, because I'm still setting up this server and I was distracted by the installation of other programs. If somebody has already experienced that /root/ldaprc will not work for samba, then please give me a hint on how to setup this correctly. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba OpenLDAP TLS
Dear Samba friends, I have setup a samba server 3.5 on FreeBSD 8.1-RELEASE-p2 with openldap-sasl-server-2.4. I have specified ``TLSVerifyClient demand'' in slapd.conf and want to enforce the clients to connect and show a valid certificate to the ldap server. As far as I have understood, Samba will act as a client as well and in order to access the ldap server it will need a client certificate as well. I do know how to generate a client certificate, but I do not know where to tell samba to use this client certificate. Is this supported by Samba or do I need to lower the constraints regarding the TLSVerifyClient? Maybe to ``TLSVerifyClient try''? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade HowTo requested
Hello tms3, On Thu, Dec 16, 2010 at 07:27:17AM -0800, t...@tms3.com wrote: Well, it might be that it has worked in your case, but certainly not in mine. I do not know what happened to the drivers or database of the drivers, but something was really messed up. I like to clarify this and to put it on a higher level. I like to figure out what the procedure is to follow and how we can inform the users about this procedure. Well, it might do you well to go over the list of dependencies that the port installed initially, and upgrade those components as well. I'm not sure what is NOT working for you, but as a general rule, I try to keep those dependecies up to date. -- I do not think that this issue is related to dependencies. Of course I need to be sure that the dependencies are correctly installed as well, but this job is accomplished by ``portupgrade -R -N'' quite well. No, the real problem lays in the settings and databases created in a previous version of samba, which will be lost, altered or corrupted upon an upgrade. To phrase the questions again? Is there a procedure on how to upgrade samba to a newer version? How can the ignorant user be informed when using portupgrade? I'm sorry, I just recall the UPDATING file in /usr/ports/. The following is a cut from this file: snip 20101026: AFFECTS: users of net/samba35 AUTHOR: Timur Bakeyev ti...@freebsd.org This is the latest stable release of the Samba3 distribution. It has been extended with the experimental support of the NFS4-like ACLs on ZFS partitions, thanks to the sysutils/libsunacl library by Edward Tomasz Napierala(trasz). This support haven't been tested thoroughly, so try it on your own risk. This port reverted back to the pre- net/samba34 layout of the directories and now they are again $PREFIX/etc/samba, /var/run/samba, /var/log/samba, /var/db/samba and /var/spool/samba respectively. In case, you are upgrading from net/samba34, please rename corresponding samba34/ subdirectories into samba/ ones. Upgrades from older versions of Samba and fresh installations should be seamless. /snip Especially the last sentence is of interest. I upgraded from samba 3.3.x to 3.5.6 and went smoothly in general, but only the printer drivers were messed up. Maybe this behavior is not covered by the information in UPDATING. Anyway, to my opinion there is a need for information on how to upgrade samba. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * Dr. W.K. Offermans CAT Postdoctoral Fellow CAT Catalytic Center Institut f�r Technische und Makromolekulare Chemie RWTH Aachen Worringerweg 1, Raum 38C-150 D-52074 Aachen, Germany Phone: +49 241 80 28592 Fax:+49 241 80 22593 Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl e-mail: willy.offerm...@catalyticcenter.rwth-aachen.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba upgrade HowTo requested
Dear Samba friends, Last weekend I decided to upgrade the samba server. We were running Samba 3.3 something and FreeBSD portupgrade was complaining that this version should be removed and assumingly replaced by the newest version. I removed the package via portupgrade and installed the 3.5.6 version. The upgrade went quite smoothly in general, but I encountered some difficulties with the printer drivers. Before the upgrade we were able to print on 4 printers. After the upgrade only 1.5 printer was working. 1 Printer worked as expected, 1 printer printed only garbage and 2 printers were not working at all. I only managed to solve the problems by de-installing and re-installing the printer drivers on the samba server. So somehow the databases in /var/db/samba/*.tdb have been messed up. I do not know what went wrong in detail and neither do I know how to prevent these kind of issues in the next upgrade. What is the procedure to upgrade samba to the newest version? How should one proceed and what are the pitfalls? How should we deal with the printer definitions and printer drivers? What should we in general do with the database files, next to backup? And specifically for FreeBSD users: How should we deal with an upgrade of samba via portupgrade? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade HowTo requested
Hello Peter, On Thu, Dec 16, 2010 at 05:42:10PM +0300, Peter Trifonov wrote: Hi Willy, Last weekend I decided to upgrade the samba server. We were running Samba 3.3 something and FreeBSD portupgrade was complaining that this version should be removed and assumingly replaced by the newest version. I removed the package via portupgrade and installed the 3.5.6 version. The Are you running winbindd on this server? If yes, does it work properly? In my case it failed to communicate group IDs to the system, so I had to rollback to v. 3.4.9. And specifically for FreeBSD users: How should we deal with an upgrade of samba via portupgrade? I have upgraded it many times before, and in most cases it was just make deinstall make reinstall. With best regards, P. Trifonov Concerning your first question: No, we are not running winbindd, so I cannot tell you if it might work. To your second remark: Well, it might be that it has worked in your case, but certainly not in mine. I do not know what happened to the drivers or database of the drivers, but something was really messed up. I like to clarify this and to put it on a higher level. I like to figure out what the procedure is to follow and how we can inform the users about this procedure. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Change password via ctrl+alt+del
Hello Samba Friends, I'm using openldap as well. The users can change the password with ctrl+alt+del. However the parameter ``sambaPwdCanChange'' is set to 0. So this can not be the only trick. On Tue, Oct 12, 2010 at 08:03:28AM +0200, Daniel Müller wrote: If you are with openldap You need to set for the user : sambaPwdCanChange=1 For Your Domain: sambaMaxPwdAge to your needs --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Gaiseric Vandal Gesendet: Dienstag, 12. Oktober 2010 01:47 An: samba@lists.samba.org Betreff: Re: [Samba] Change password via ctrl+alt+del Is this an XP machine? Do you have password sync enabled? If password sync is enabled BUT the chat script (or whatever mechanism you use to change the unix password) is broken then password change can fail. The first thing I would try would be disabling the password sync feature and seeing if that works. -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of Rodolfo Barbosa Sent: Monday, October 11, 2010 6:41 PM To: samba@lists.samba.org Subject: [Samba] Change password via ctrl+alt+del Guys, How do I enable the password changing via ctrl+alt+del on a windows workstation? This function worked on my previous PDC but I can't get it work on my actual PDC. I looked at the samba log file of the workstation and I saw the following line: user cannot change password now, must wait until never Debian GNU Linux 5.0 Samba 3.5.5 LDAP backend Thank's -- Rodolfo Barbosa Lunar Consultoria barbosa.rodo...@lunarconsultoria.com.br CEL: +55 (35) 9132-0764 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * Dr. W.K. Offermans -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Problem with Windows XP: Cannot join Samba PDC
Hello Samba friends, Did you check or disable possible firewalls in between the network traffic? This is usually causing this error in my case. On Fri, Jun 18, 2010 at 01:56:46PM +0700, Hung Nguyen Van wrote: I double checked and it's exactly what I do, it seems server netbios name is not available in world of Windows client. It's so weird with me. On Thu, 17 Jun 2010 13:45:48 -0400 Gaiseric Vandal gaiseric.van...@gmail.com wrote: For an NT4/Samba domain, DNS is not relevant. The XP client will locate the PDC via netbios. WINS is not essential but definately helps. On the XP machine, type ipconfig /all and make sure that your XP machine is configured for the WINS server. Also, make sure on your XP TCP/IP settings that you have NOT disabled netbios-over-tcp/ip (NBT.) On 06/17/2010 10:22 AM, Hung Nguyen wrote: I have tried several times to get Windows XP client join SAMBA PDC domain, but no luck. I follow some nice guide from Ubuntu Forum and samba Document, my Samba PDC working with OpenLDAP. When I type join XP to domain I get : http://osvn.pastebin.com/QUpVVq5q http://osvn.pastebin.com/QUpVVq5q DOMAIN is name of workgroup = DOMAIN in my samba group, it seems like XP client cannot find where is DOMAIN. I'm pretty sure that my DNS is working properly, XP can resolve dc.DOMAIN.local to its IP address and use my dns server to connect to internet without problem. Linux Clients can join domain without problem. Does someone face this problem before, please help. I also enable WinS server on Samba configuration. Actually, I dont understand why I need a local DNS here, because when we join Samba Domain, we just type in Domain form NetBios name of server, not full domain name. If you can explain, please give me an answer too. Thank you very much for your help, 2 days working on it did not help me too much. Regards, -- -- Nguyen Van Hung System Administrator SYNAPSYS Co., Ltd 1st Floor, 49 Bui Dinh Tuy St, Binh Thanh Dist, HCMC, Vietnam Tel: ( +84-8 ) 66 599 379 Cell : ( +84 ) 0976 30 22 32 Email: vhngu...@synapsys-vn.com Website: http://www.synapsys-vn.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * Dr. W.K. Offermans CAT Postdoctoral Fellow CAT Catalytic Center Institut f�r Technische und Makromolekulare Chemie RWTH Aachen Worringerweg 1, Raum 38C-150 D-52074 Aachen, Germany Phone: +49 241 80 28592 Fax:+49 241 80 22593 Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl e-mail: willy.offerm...@catalyticcenter.rwth-aachen.de Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Password policies in the LDAP server
Hello Samba Friend, I'm sorry that I cannot help you in finding an answer to your question, but I'm rather interested in how you can add password policies to the LDAP sever. Is this openldap? and how did you implement the policies? On Mon, Jun 28, 2010 at 12:40:09PM +0200, Juan Asensio Sánchez wrote: Hi We have some Samba servers using LDAP (389 DS) as backend. In the LDAP server, we have defined some policies to make the passwords stronger. When a user tries to change his password (Control-Alt-Del), this message appears in the LOGs: == /var/log/samba/xptest == [2010/06/28 12:26:26, 2] auth/auth.c:check_ntlm_password(309) check_ntlm_password: authentication for user [1001S] - [1001S] - [1001S] succeeded [2010/06/28 12:26:26, 2] passdb/pdb_ldap.c:init_sam_from_ldap(545) init_sam_from_ldap: Entry found for user: 1001S [2010/06/28 12:26:26, 2] passdb/pdb_ldap.c:init_group_from_ldap(2167) init_group_from_ldap: Entry found for group: 10001 [2010/06/28 12:26:37, 2] passdb/pdb_ldap.c:init_group_from_ldap(2167) init_group_from_ldap: Entry found for group: 10001 [2010/06/28 12:26:38, 2] passdb/pdb_ldap.c:init_ldap_from_sam(972) init_ldap_from_sam: Setting entry for user: 1001S [2010/06/28 12:26:38, 0] passdb/pdb_ldap.c:ldapsam_modify_entry(1651) ldapsam_modify_entry: LDAP Password could not be changed for user 1001S: Constraint violation Failed to update password == /var/log/dirsrv/slapd-pruebas/audit == time: 20100628122637 dn: uid=1001s,X changetype: modify delete: sambaLMPassword sambaLMPassword: 0182BD0BDBF836077A718CCDF409 - add: sambaLMPassword sambaLMPassword: 39EAD569B79C7EA2C2265B23734E0DAC - delete: sambaNTPassword sambaNTPassword: 259745CB123A52AA2E693AAACCA2DB52 - add: sambaNTPassword sambaNTPassword: 8EC60ADEA316D957D1CF532C5841758D - delete: sambaPwdLastSet sambaPwdLastSet: 1277720109 - add: sambaPwdLastSet sambaPwdLastSet: 1277720798 - replace: modifiersname modifiersname: uid=adminsamba,XXX - replace: modifytimestamp modifytimestamp: 20100628102637Z - So, the Samba passwords are changed, but the unix password is not changed because the LDAP rejects it because it is not as string as required. Is there any way to avoid this? Shouldn't the unix password be changed before the samba passwords to check if the LDAP server accepts it? Regards. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * Dr. W.K. Offermans CAT Postdoctoral Fellow CAT Catalytic Center Institut f�r Technische und Makromolekulare Chemie RWTH Aachen Worringerweg 1, Raum 38C-150 D-52074 Aachen, Germany Phone: +49 241 80 28592 Fax:+49 241 80 22593 Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl e-mail: willy.offerm...@catalyticcenter.rwth-aachen.de Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [3.0.28a] Telling XP to save password?
Hello Gilles, FreeBSD, and Samba friends, On Fri, Jun 27, 2008 at 12:39:46PM +0200, Gilles wrote: Hello We're successfully running Samba 3.0.28a on a FreeBSD server and sharing files with XP clients. There's only one problem: By default, XP doesn't let the user save the password, so they have to type it every time they reboot. Is there a way to tell XP to remember the password between reboots/sessions? Thank you. -- In general, saving a password isn't a good idea. It is annoying to remember a password by heart and to retype it again and again, but it is the best option. So probably there is a way to ``tell XP to remember the password between reboots/sessions``, but that is most probably not what you want. I advice you to re-consider the issue to find a proper solution. In order to help you in a more detailed way, you need to be more verbose and explicit to your problem when mailing it to the list. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * Dr. W.K. Offermans CAT Postdoctoral Fellow CAT Catalytic Center Institut für Technische und Makromolekulare Chemie RWTH Aachen Worringerweg 1, Raum 38C-133 D-52074 Aachen, Germany Phone: +49 241 80 28591 Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Adding Printer drivers with rpcclient
Hello Kyle and Samba friends, On Mon, Jun 23, 2008 at 04:41:13PM -0500, Kyle Schmitt wrote: Hello. I'm having issues trying to add printer drivers using the rpcclient I've got the drivers for one of the printers in the appropriate share, but every time I've tried, I get NT_STATUS_UNSUCCESSFUL So far I've put the drivers under W32X86, W32X86/2 and W32X86/3, to no avail Every time I run the adddriver command, I receive the NT_STATUS_UNSUCCESSFUL, and in the debug message, a rather curious WERR_ACCESS_DENIED error. rpcclient -U root -c 'adddriver Windows NT x86 dellcolor:dlxcrzim.dll :dlxcrzp.ddd:dlxcrziu.dll:dlxcrz.hlp:NULL:RAW:dlxcrjdm.dll,dlxcrzir.xrs,dllzjnie.dll,dlzddmif.dll,dlzdhb32.dll,dllznie1.dll,dlzpmc2.dll,dlzadcmn.dll,dlzarl32.dll,dlzc5102.dll,dlxcrz.cfg,dlxcrz.cnt,dlxcrz.xrs,dlxcrz.cdd ' lxtrfs03 -d 100 Any help would be greatly appreciated. 1 or 2 years ago, I was in the same situation as you know. I tried a lot, but it simply didn't work. Nowadays I follow the route via a windows client to add the printer drivers to the samba server. Something like start run\\Sambaserver Printers Right-click mousebuttonServer properties\ Add driver If you cannot follow, you better check the archives or the handbook where this is better explained. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * Dr. W.K. Offermans CAT Postdoctoral Fellow CAT Catalytic Center Institut für Technische und Makromolekulare Chemie RWTH Aachen Worringerweg 1, Raum 38C-133 D-52074 Aachen, Germany Phone: +49 241 80 28591 Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] No usersidlist
Dear Samba friends, The response to the following command on my Samba server: net usersidlist is: [2008/03/07 09:26:23, 0] utils/net_rpc.c:net_usersidlist(4724) Could not get the user/sid list and somewhat unexpected. How can I obtain the usersidlist? What are the tools to resolve SID to objectnames and vice versa? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] Another Uploading Printer drivers problem.
Hello Richard and Samba Friends, On Thu, Jan 03, 2008 at 10:15:01PM +0900, Richard Chapman wrote: Hi Willy, Dale, Ryan and others Many thanks for hte feedback. I had read the man samba.conf section on use client driver - but I interpreted the MUST not be enabled when valid printer drivers are loaded on the Samba server to mean the case where the drivers were loaded on and RUNNING on the server as opposed to loaded on the server simply to allow them to be loaded onto the windows box. These are presumably different cases - and it is clearly desirable to upload the drivers on the server JUST for download to the windows box even when (especially when) the drivers are running on the client side. Drivers are always loaded and running on the client, whatever you do. However I noticed that some settings are stored on the server side, if you upload the driver and change the settings on the server side. I have tried removing the directive - and I immediately get back the access denied status in the windows printers and faxes window, just as the man pages suggest I should. Since removing the directive (and restarting samba) I have tried again to upload the drivers - but the result is the same. It goes through the motions - and doesn't give an error - but still uploads to the c:\windows.. on the client rather than the print$ share on the samba server. Did you follow the right procedure. I always use a windows domain client to upload the drivers. I follow the procedure: use start - run, type \\server (your samba server) and press OK. Goto Printers and Faxmachines, right click mouse and choose server properties. Choose tab drivers and add new driver. Finally connect driver to printer. That's it. Probably it is also described in many Howto's. Thanks for your references too Dale - but my Access Denied error is seen on the printer and fax status window - rather than when trying to upload drivers. I do not get any errors when uploading the drivers. They just go to the wrong place. No doubt when I get them going to the right place - I may then need to resolve the privileges issue. I will however have a good browse of the howto link you provided. Probably you are doing something wrong. Explain us how you are uploading. I guess it does appear that the use client driver is preventing me from uploading the drivers. Can anyone suggest the best way around this? There are a few linux drivers around for the printer - but they all seem to have problems. Can I install a linux driver - but not use it and still use the windows client side drivers. Will this overcome my problem - and allow me to upload the Windows drives to the linux share? The use client driver directive does not put the driver in the wrong place, e.g. C:\Windows\blahblah, but causes an error message when you try uploading the drivers. Alternatively - can I run the system with a raw mode linux printer - but avoid the use client driver. Is there some other way to get rid of access denied errors - or can I just ignore them? In this case - with no linux driver installed - can I still upload windows printer drivers? One simple question you may be able to answer: Is it the presence of the use client driver directive or the absence of the linux driver which prevents me from uploading? My tests today suggest the latter. The use client driver issue has been discussed and explained. By now you should now what to do. I do not understand the linux driver issue and therefore I cannot comment on that. I have the feeling that you are not clear on what you want. Many thanks again. Richard. You are welcome, Willy Willy Offermans wrote: Hello Richard, On Wed, Jan 02, 2008 at 11:19:04PM +0900, Richard Chapman wrote: Hi. I have been following another thread describing problems uploading printer drives - but I think I have a different problem. In my case I have a Samsung CLP510 colour laser physically connected to a Centos 5.1 X86-64 Linux box with Samba 3.0251514 (3.0.25b-1.el5_1.4 https://192.168.0.201:1/software/edit_pack.cgi?search=sambapackage=sambaversion=3%2E0%2E25b%2D1%2Eel5%5F1%2E4). The Printer is intended to be shared by windows boxes on the network. I have installed the printer as a raw printer - so that windows clients use their own drivers. In order to get rid of the Access Denied errors in the Printers and Faxes status - I have put the use client driver directive into smb.conf. I was hoping that I could still install windows printer drivers on the Linux server so that new windows client machines would not have to find the driver elsewhere. I can't see any reason why this should not be possible. I have created the print$ share and the folders described here: http://wiki.samba.org/index.php/Samba_as_a_print_server It looks like some parts of this wiki are rather incomplete. The printer works fine from the clients
Re: [Samba] Another Uploading Printer drivers problem.
Hello Richard, On Wed, Jan 02, 2008 at 11:19:04PM +0900, Richard Chapman wrote: Hi. I have been following another thread describing problems uploading printer drives - but I think I have a different problem. In my case I have a Samsung CLP510 colour laser physically connected to a Centos 5.1 X86-64 Linux box with Samba 3.0251514 (3.0.25b-1.el5_1.4 https://192.168.0.201:1/software/edit_pack.cgi?search=sambapackage=sambaversion=3%2E0%2E25b%2D1%2Eel5%5F1%2E4). The Printer is intended to be shared by windows boxes on the network. I have installed the printer as a raw printer - so that windows clients use their own drivers. In order to get rid of the Access Denied errors in the Printers and Faxes status - I have put the use client driver directive into smb.conf. I was hoping that I could still install windows printer drivers on the Linux server so that new windows client machines would not have to find the driver elsewhere. I can't see any reason why this should not be possible. I have created the print$ share and the folders described here: http://wiki.samba.org/index.php/Samba_as_a_print_server It looks like some parts of this wiki are rather incomplete. The printer works fine from the clients now (if I provide the client driver elsewhere) - but I cannot get the drivers to load on the server. If I browse the network - from a windows client - and select the properties of the printer within the Printers and Faxes folder - then select Advanced, and then select New Driver - it starts the Add Printer driver wizard. I can select the driver I want and Finish the wizard - but it uploads the driver to the /windows/system32/spool/drivers folder on the local client rather than the server. Can anyone tell me if I am doing something wrong - or if there is something wrong with my configuration which prevents me from uploading the driver to the server? Many thanks. Richard. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba If I recall correctly, then the use client driver directive prohibits the up-/download of printer drivers from the server. Please search the net to be 100% sure. I remember there was a hint about the issue in `man smb.conf`: snip use client driver (S) snip If this parameter is enabled for a printer, then any attempt to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped to PRINTER_ACCESS_USE instead. Thus allowing the Open- PrinterEx() call to succeed. This parameter MUST not be able enabled on a print share which has valid print driver installed on the Samba server. /snip /snip Although the text: This parameter MUST not be ... is not clear for 100% and rather difficult to read, it makes sense that having the printer driver on the server and using the client driver at the same time is ambiguous. Concerning the Access Denied errors, I do not know what happens, after you have removed the appropriate directive in your smb.conf. I hope this helps. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] How to report successfull and unseccessful login attempts
Hello Valerio, On Mon, Oct 15, 2007 at 02:22:04PM +0200, Valerio Daelli wrote: Hi we use samba 3.0.25a on FreeBSD 6.2 and we would like to have in the logs only the successfull and unsuccessfull login attempts. We would like to read in the log file: Authentication for user [%s] - [%s] - [%s] succeeded or Authentication for user [%s] - [%s] FAILED with error We have tried with log level 1 and we get only the successfull logins. We have tried with log level 2 and we get the unsuccessfull as well but with those a million of other irrelevant (for us) events are logged. We know we could patch the source code (I think we should patch source/auth/auth.c) but we prefer taking a simpler approach. Any suggestions? Thanks Valerio Daelli -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Maybe ``grep'' can help you? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printer Drivers on Samba server
Hello Lutieri and Samba Friends, On Tue, Mar 27, 2007 at 05:46:38PM +, Lutieri G. wrote: take a look here: http://www.wlug.org.nz/SambaPrinting and http://samba.org/samba/docs/man/Samba-HOWTO-Collection/CUPS-printing.html#id373732 2007/3/20, Willy Offermans [EMAIL PROTECTED]: Dear Samba friends, I want to have the printer drivers on the samba server. I have created the following share in the smb.conf file: [print$] comment = Printer Driver Download Area path = /usr/local/samba/printers valid users = @XXX write list = @YYY, root, jo, willy printer admin = @YYY browseable = No @XXX are the normal printer users. @YYY are administrators. This is the physical directory: drwxrwxrwx 3 root @YYY 512 Feb 13 16:49 /usr/local/samba/printers There is another share for the printers: [printers] comment = All Printers path = /var/spool/samba printer admin = @RompenStaff guest ok = Yes printable = Yes browseable = No However this share can not be accessed. It cannot be found from the windows xp clients. I do not know how to upload the printer drivers. I do not know if this setup is going to work at all. Can someone help me? I have solved the problem successfully. The key to the solution was the execution of \\sun\print$ from the windows start execute thingy, that did not work. Running \\sun however worked and gave me access to the pinters and faxes subdirectory mouse right click in this area and choose something like server properties. Then if you have configured all right and have added printer admin = user with the right credentials, you may be able to add new printer drivers, after that you can follow the samba handbook and all works like charm. Actually I should write this in clear text and add to the Howto collection. However I do not have time at the moment. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] fam error
On Thu, Mar 01, 2007 at 12:55:04PM +0100, Volker Lendecke wrote: On Fri, Feb 23, 2007 at 04:51:57PM +0100, Willy Offermans wrote: Feb 23 16:48:41 sun smbd[35310]: failed to connect to FAM service ... /snip I have reported this already a long time ago. Nothing happened since then. Currently I'm running Samba version 3.0.24 on FreeBSD 6.1. Does anybody have a clue how to solve this issue? With 3.0.25 we have rewritten the notify (and FAM) support completely. You might want to try the pre1 release. Volker Hello Volker, It is not a critical error, just extremely annoying. I will wait for the next port release of FreeBSD and test it. I will announce the result, so stay tuned ... Oh b.t.w. I notice the following directory on the samba server: drwx-- 2 root wheel 512 Mar 1 10:57 fam-root I have also seen the willy equivalent called fam-willy, but that one disappeared. For the other users I have never noticed such a directory. I have the feeling that error stems from the fact that there should be a fam-user directory for every domain user and not only one owned by root. But maybe I mistake and has this nothing to do with it at all. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printer Drivers on Samba server
Dear Samba friends, I want to have the printer drivers on the samba server. I have created the following share in the smb.conf file: [print$] comment = Printer Driver Download Area path = /usr/local/samba/printers valid users = @XXX write list = @YYY, root, jo, willy printer admin = @YYY browseable = No @XXX are the normal printer users. @YYY are administrators. This is the physical directory: drwxrwxrwx 3 root @YYY 512 Feb 13 16:49 /usr/local/samba/printers There is another share for the printers: [printers] comment = All Printers path = /var/spool/samba printer admin = @RompenStaff guest ok = Yes printable = Yes browseable = No However this share can not be accessed. It cannot be found from the windows xp clients. I do not know how to upload the printer drivers. I do not know if this setup is going to work at all. Can someone help me? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] fam error
Hello James and samba friends, Since Sep 2006 I got the following error again and again: snip ... Feb 23 16:46:17 sun smbd[35310]: [2007/02/23 16:46:17, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:46:17 sun smbd[35310]: failed to connect to FAM service Feb 23 16:46:21 sun smbd[35310]: [2007/02/23 16:46:21, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:46:21 sun smbd[35310]: failed to connect to FAM service Feb 23 16:46:22 sun smbd[35310]: [2007/02/23 16:46:22, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:46:22 sun smbd[35310]: failed to connect to FAM service Feb 23 16:46:44 sun smbd[35310]: [2007/02/23 16:46:44, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:46:44 sun smbd[35310]: failed to connect to FAM service Feb 23 16:46:46 sun smbd[35310]: [2007/02/23 16:46:46, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:46:46 sun smbd[35310]: failed to connect to FAM service Feb 23 16:46:59 sun smbd[35310]: [2007/02/23 16:46:59, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:46:59 sun smbd[35310]: failed to connect to FAM service Feb 23 16:47:12 sun smbd[35310]: [2007/02/23 16:47:12, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:47:12 sun smbd[35310]: failed to connect to FAM service Feb 23 16:47:15 sun smbd[35310]: [2007/02/23 16:47:15, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:47:15 sun smbd[35310]: failed to connect to FAM service Feb 23 16:47:16 sun smbd[35310]: [2007/02/23 16:47:16, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:47:16 sun smbd[35310]: failed to connect to FAM service Feb 23 16:47:20 sun smbd[35310]: [2007/02/23 16:47:20, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:47:20 sun smbd[35310]: failed to connect to FAM service Feb 23 16:47:23 sun smbd[35310]: [2007/02/23 16:47:23, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:47:23 sun smbd[35310]: failed to connect to FAM service Feb 23 16:47:43 sun smbd[35310]: [2007/02/23 16:47:43, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:47:43 sun smbd[35310]: failed to connect to FAM service Feb 23 16:48:34 sun smbd[35310]: [2007/02/23 16:48:34, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:48:34 sun smbd[35310]: failed to connect to FAM service Feb 23 16:48:38 sun smbd[35310]: [2007/02/23 16:48:38, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:48:38 sun smbd[35310]: failed to connect to FAM service Feb 23 16:48:41 sun smbd[35310]: [2007/02/23 16:48:41, 0] smbd/notify_fam.c:fam_check_reconnect(136) Feb 23 16:48:41 sun smbd[35310]: failed to connect to FAM service ... /snip I have reported this already a long time ago. Nothing happened since then. Currently I'm running Samba version 3.0.24 on FreeBSD 6.1. Does anybody have a clue how to solve this issue? On Sat, Sep 09, 2006 at 11:20:21PM +1000, James Peach wrote: On 09/09/06, Willy Offermans [EMAIL PROTECTED] wrote: On Mon, Sep 04, 2006 at 10:27:35PM +1000, James Peach wrote: On 04/09/06, Willy Offermans [EMAIL PROTECTED] wrote: Dear Samba Friends, I got the following error again and again: snip . Sep 4 10:58:18 sun smbd[94479]: [2006/09/04 10:58:18, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:18 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:23 sun smbd[94479]: [2006/09/04 10:58:23, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:23 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:24 sun smbd[94479]: [2006/09/04 10:58:24, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:24 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:25 sun smbd[94479]: [2006/09/04 10:58:25, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:25 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:25 sun smbd[94479]: [2006/09/04 10:58:25, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:25 sun smbd[94479]: failed to connect to FAM service Sep 4 11:23:22 sun smbd[94479]: [2006/09/04 11:23:22, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 11:23:22 sun smbd[94479]: failed to connect to FAM service . /snip I'm using samba-3.0.23b,1 on FreeBSD 6.1 I've only ever tested the FAM support on IRIX. smbd will automatically attempt to use FAM if it appears to be available, but it shouldn't I did not specify anything with respect to fam in my /usr/local/etc/smb.conf file. I have only noticed that a new directory has been created in /tmp/ drwx-- 2 root wheel 512 Sep 4 08:45 /tmp/fam-root/ This directory is empty and updated once and a while. I mean the directory is recreated at a later time. Attributes and owner do not change. In the clients log files I find the following: snip [2006/09/04 11:36:41, 0] smbd/notify_fam.c:fam_check_reconnect(136) failed to connect to FAM service Socket directory
Re: [Samba] host allow
Hello Eric, After our telephone call, I had some thoughts about your problem. First you can ensure that the DNS server which is used by the samba host ``knows'' about all your clients. Static and dynamic IP addresses should be given by DHCP servers, which announce those leases to the DNS server. Look for isc-dhcp3-server or internet software consortium. Then the reverse resolving will work. Make sure that the client-hosts are identified unambiguously. Have also a look to named - Internet domain name server on how to setup name servers, possibly on different levels. Then the hosts allow entry in your smb.conf file will work. Secondly you could use (open)vpn connections for your clients. This would be especially useful for road warriors. It is a bit of an overkill for clients on the safe site behind the firewall. But the advantage could be that you use one way of connecting for all the clients, irrespective where they are located. With the right setup you can give the virtuel tunnel devices IP addresses correlated with the host keys. And in that way you can identify your clients unambiguously. So there are solutions to your problem. I hope this is helpful for you. On Mon, Nov 20, 2006 at 12:17:23PM +0100, Eijkelboom, Eric wrote: For now we decided to use static ip addresses for these PC's. Ben net op jullie website gaan kijken, je woont dus in Heerlen ? Zou het zeer op prijs stellen als je me laat weten als je nog iets te binnen schiet, maar voor nu kiezen we dus voor statische ip adressen. -Original Message- From: Willy Offermans [mailto:[EMAIL PROTECTED] Sent: Monday, November 20, 2006 12:02 PM To: Eijkelboom, Eric Cc: samba@lists.samba.org Subject: Re: [Samba] host allow Hello Eric, To restrict access to your Samba shares on a host basis, you need to identify your clients unambiguously. Since the clients have dynamic IP addresses, this can never be guaranteed. The best thing I can imagine is to use a bridged vpn connection from the client and provide the client an IP address. In this way the client is unambiguously identified. Then you allow only access to your samba via vpn (firewall rule or whatever). In this way you also ensure that the connection client-Samba-host is encrypted. But I have still the feeling that this solution is much too difficult. Let me think about this for a couple of days, maybe I find something better. In the meantime you can give me more details about what you really want. If things are confidential or if it is much easier, you can also contact me in a different way than via this list. As a matter of fact, I live so close to your company, I can even see it from my window on the attic... Funny coincidence. On Mon, Nov 20, 2006 at 11:34:52AM +0100, Eijkelboom, Eric wrote: Correct, I don't want to use the UNIX /etc/hosts.alow file but the host allow option in Samba. I've added for example daelej* so that every PC client that starts with daelej should be able to have acces. Then the user also needs to use their user-id and password. -Original Message- From: Willy Offermans [mailto:[EMAIL PROTECTED] Sent: Monday, November 20, 2006 11:28 AM To: Eijkelboom, Eric Subject: Re: [Samba] host allow Helllo Eric, Now I do understand a bit more your problem. If you talk about hosts allow, you mean the line in your samba configuration file. Not the file hosts.allow, which possibly exists in your /etc directory. So you want to restrict access to your Samba shares on a host basis. This is an interesting problem and unusual at the same time. Usually one restricts access to samba shares on an user basis and not on a host basis. I guess you have to clarify this a bit to help you. On Mon, Nov 20, 2006 at 11:06:48AM +0100, Eijkelboom, Eric wrote: Thanks for the fast respons Willy ! We're using different groups and access rights. But from an audit point of view we also want to restict access to a certain IP range and several hosts which obtain dynamically ip adresses (from several ranges). Reverse DNS is not setup for these clients. If I add these clients to the /etc/hosts file it works ok. But since they are getting there IP addresses dynamicaly, this is not an option. But while getting more information for you I've get beneath error message. It seems I made a syntaxt error. [EMAIL PROTECTED] # /usr/local/samba/bin/testparm Load smb config files from /usr/local/samba/lib/smb.conf Processing section [pnc] Processing section [apps] Processing section [ipacs] Processing section [aps] Processing section [aps1] Loaded services file OK. Invalid character * in hosts allow list (daelej*) for service pnc. Invalid character * in hosts allow list (DAELEJ*) for service pnc. Invalid character * in hosts allow list (eijkee*) for service pnc. Invalid character * in hosts allow list (stijnj1
Re: [Samba] host allow
Hello Eric, On forehand I would say that this is not the best idea to prevent your clients access to your shares. But we need to have more details on how the clients connect. The best thing to prevent access would be to define different groups with different access rights. But you could also use firewall rules and a lot more of different setups. We definitely need more details on setup and configuration to help you. On Fri, Nov 17, 2006 at 02:16:43PM +0100, Eijkelboom, Eric wrote: Hi, We want to restrict acces to the shares on our samba server using hosts allow. Can I get this to work with clients who have dynamic IP addresses and don't have revers DNS lookup ? Best regards, Eric Eijkelboom Sr Systems Manager Medtronic B.V. Heerlen, The Netherlands Phone : +31-(0)45-566.8544 Fax : +31-(0)45-566.8008 www.medtronic.com http://www.medtronic.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Eindhoven University of Technology Department of Chemical Engineering Laboratory of Catalysis (SKA) building ST-W 4.27, PO Box 513 5600 MB Eindhoven, Netherlands Tel:+31 40 247 37 81 Fax:+31 40 245 50 54 Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] http://www.catalysis.nl Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] fam error
On Mon, Sep 04, 2006 at 10:27:35PM +1000, James Peach wrote: On 04/09/06, Willy Offermans [EMAIL PROTECTED] wrote: Dear Samba Friends, I got the following error again and again: snip . Sep 4 10:58:18 sun smbd[94479]: [2006/09/04 10:58:18, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:18 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:23 sun smbd[94479]: [2006/09/04 10:58:23, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:23 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:24 sun smbd[94479]: [2006/09/04 10:58:24, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:24 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:25 sun smbd[94479]: [2006/09/04 10:58:25, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:25 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:25 sun smbd[94479]: [2006/09/04 10:58:25, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:25 sun smbd[94479]: failed to connect to FAM service Sep 4 11:23:22 sun smbd[94479]: [2006/09/04 11:23:22, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 11:23:22 sun smbd[94479]: failed to connect to FAM service . /snip I'm using samba-3.0.23b,1 on FreeBSD 6.1 I've only ever tested the FAM support on IRIX. smbd will automatically attempt to use FAM if it appears to be available, but it shouldn't I did not specify anything with respect to fam in my /usr/local/etc/smb.conf file. I have only noticed that a new directory has been created in /tmp/ drwx-- 2 root wheel 512 Sep 4 08:45 /tmp/fam-root/ This directory is empty and updated once and a while. I mean the directory is recreated at a later time. Attributes and owner do not change. In the clients log files I find the following: snip [2006/09/04 11:36:41, 0] smbd/notify_fam.c:fam_check_reconnect(136) failed to connect to FAM service Socket directory /tmp/fam-root has different owner Failed to remove unsafe path /tmp/fam-root ... /snip It seems that the client tries to access /tmp/fam-root but has not the right user priviliges. Can someone help me out and explain what is going on? How can I solve the problem? You can disable FAM support by setting fam change notify = no in smb.conf. This will get rid of the messages, but obviously you won't get FAM support. I'd have to dig into the FAM implementation on FreeBSD to be more helpful, and I won't be able to do that for a couple of weeks. -- James Peach | [EMAIL PROTECTED] Well, since the error message is only annoying and __not__ critical at the moment, I will just be patient then. I do not know how fam is implemented into samba and if calling the fam function in FreeBSD needs special considerations. I expected that the samba developer, responsible for the fam implementation, would have a look. I do not know if I reach that person via this mailing list. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Eindhoven University of Technology Department of Chemical Engineering Laboratory of Catalysis (SKA) building ST-W 4.27, PO Box 513 5600 MB Eindhoven, Netherlands Tel:+31 40 247 37 81 Fax:+31 40 245 50 54 Home: +31 45 544 49 44 Mobile: +31 650 697 837 e-mail: [EMAIL PROTECTED] http://www.catalysis.nl Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] fam error
Dear Samba Friends, I got the following error again and again: snip . Sep 4 10:58:18 sun smbd[94479]: [2006/09/04 10:58:18, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:18 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:23 sun smbd[94479]: [2006/09/04 10:58:23, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:23 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:24 sun smbd[94479]: [2006/09/04 10:58:24, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:24 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:25 sun smbd[94479]: [2006/09/04 10:58:25, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:25 sun smbd[94479]: failed to connect to FAM service Sep 4 10:58:25 sun smbd[94479]: [2006/09/04 10:58:25, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 10:58:25 sun smbd[94479]: failed to connect to FAM service Sep 4 11:23:22 sun smbd[94479]: [2006/09/04 11:23:22, 0] smbd/notify_fam.c:fam_check_reconnect(136) Sep 4 11:23:22 sun smbd[94479]: failed to connect to FAM service . /snip I'm using samba-3.0.23b,1 on FreeBSD 6.1 I did not specify anything with respect to fam in my /usr/local/etc/smb.conf file. I have only noticed that a new directory has been created in /tmp/ drwx-- 2 root wheel 512 Sep 4 08:45 /tmp/fam-root/ This directory is empty and updated once and a while. I mean the directory is recreated at a later time. Attributes and owner do not change. In the clients log files I find the following: snip [2006/09/04 11:36:41, 0] smbd/notify_fam.c:fam_check_reconnect(136) failed to connect to FAM service Socket directory /tmp/fam-root has different owner Failed to remove unsafe path /tmp/fam-root ... /snip It seems that the client tries to access /tmp/fam-root but has not the right user priviliges. Can someone help me out and explain what is going on? How can I solve the problem? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Eindhoven University of Technology Department of Chemical Engineering Laboratory of Catalysis (SKA) building ST-W 4.27, PO Box 513 5600 MB Eindhoven, Netherlands Tel:+31 40 247 37 81 Fax:+31 40 245 50 54 Home: +31 45 544 49 44 Mobile: +31 650 697 837 e-mail: [EMAIL PROTECTED] http://www.catalysis.nl Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
