Re: [Samba] Client driver installation
On Thu, May 21, 2009 at 1:27 AM, Gary L. Greene, Jr. wrote: > > > I've an OpenSuSE based server installed at work that uses Samba to share out > the > prrinters for our users on the AD that will be replacing our aging Windows > 2000 > print server. I'm in the process of getting the printer drivers installed for > Windows clients. At present, I'm installing the drivers for the RICOH Aficio > we > have. When I run the following command: > > printmaster:/var/lib/samba/drivers/W32X86 # rpcclient -U ggreene -c > "adddriver 'Windows NT x86' > 'RICOH:RIC641K.DLL:RIC641K.DLL:RIC641U.DLL:RIC641.HLP:NULL:RAW:RIC641K.DLL,RIC641U.DLL,RIC641.HLP,RIC641P.DLL,RIC641C.DLL,RIC641L.DLL,RIC641X.DLL,RIC641S.DLL,RIC641J.DLL,RIC641Q.EXE,RIC641ZU.DLL,RIC641ZK.DLL,RIC641WU.DLL,RIC641WK.DLL,RIC641PI.DLL,RIC641SR.EXE,RIC641CF.DLL,RIC641X.EXE,TrackID.DLL,TIBase64.dll,TIFmtA.dll,RICJC32.dll,JCUI.exe' > 3" printmaster > > I get the following output: > result was > WERR_UNKNOWN_PRINTER_DRIVER > > With the logging output of the > printdrivers set to 10, I get the following from the logs: > [2009/05/20 > 14:51:58, 0] printing/nt_printing.c:move_driver_to_download_area(1931) > move_driver_to_download_area: Unable to rename [W32X86/RIC641K.DLL] to > [W32X86/3/RIC641K.DLL] > > Any help would be appreciated as I'm trying to > get this done ASAP. > i was strugling a lot with these things and i'm not an expert, but what do you have in your [print$] and [printers] shares in your smb.conf? look for use client drivers directive -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] multiple domain info entries problem
Usually this is a matter of filesystem permissions being wrong. Can (for example) a sales person access the sales share when logged into the server's console? TB Leonardo Carneiro wrote: i still have this problem i have not found any solution. sorry for the 'up' on the topic, but i'm really in trouble with this situation. any idea anyone? Leonardo Carneiro escreveu: after many tries and upgrading my samba to 3.2.5, the sharing is working... kind of. now everyone can access their exclusive folders on the server, also can acess the public folder (anyone can access this folder without authentication). when people try to access folders that they should not access (like a IT guy accessing the Sales folder), the server also forbid the access. But when someone try to access their group folder (like the Sales guy accessing the Sales folder), windows show a error message, telling me the folder is no accessible. any help is welcome. tks in advance. Leonardo Carneiro escreveu: Hi fellows. I'm new to the list and hope I'll have a nice time here. one of my servers running samba+ldap is not working properly. the setup is: Debian 5 fileserver:/etc/samba#smbd --version Version 3.0.24 fileserver:/etc/samba# slapd -V @(#) $OpenLDAP: slapd 2.3.30 (Oct 5 2008 22:08:58) $ j...@galadriel:/home/jmm/ldap/openldap2.3-2.3.30/debian/build/servers/slapd After a samba upgrade via apt-get, the user could not access their shared folders anymore. Looking at the logs i'd saw some strage things: smbd.log: === [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 6550 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(45) === [2009/05/19 08:45:59, 0] lib/util.c:smb_panic(1599) PANIC (pid 6550): internal error [2009/05/19 08:45:59, 0] lib/util.c:log_stack_trace(1706) BACKTRACE: 15 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c3d3] #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c4c6] #2 /usr/sbin/smbd [0x821a69a] #3 [0xb7eff420] #4 /usr/lib/liblber-2.4.so.2(ber_memfree_x+0x50) [0xb76ac300] #5 /usr/lib/libldap_r-2.4.so.2 [0xb76dc274] #6 /usr/lib/libldap_r-2.4.so.2 [0xb76bc6d8] #7 /usr/lib/libldap_r-2.4.so.2 [0xb76eb950] #8 /lib/ld-linux.so.2 [0xb7f0e453] #9 /lib/i686/cmov/libc.so.6(exit+0x89) [0xb7b23ab9] #10 /usr/sbin/smbd [0x82c23bc] #11 /usr/sbin/smbd [0x82c23e0] #12 /usr/sbin/smbd(main+0x10f0) [0x82c3860] #13 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b0b455] #14 /usr/sbin/smbd [0x8082b11] [2009/05/19 08:45:59, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(41) === [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 6556 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(45) === [2009/05/19 08:45:59, 0] lib/util.c:smb_panic(1599) PANIC (pid 6556): internal error [2009/05/19 08:45:59, 0] lib/util.c:log_stack_trace(1706) BACKTRACE: 16 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c3d3] #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c4c6] #2 /usr/sbin/smbd [0x821a69a] #3 [0xb7eff420] #4 /usr/lib/liblber-2.4.so.2(ber_memfree_x+0x50) [0xb76ac300] #5 /usr/lib/libldap_r-2.4.so.2 [0xb76dc274] #6 /usr/lib/libldap_r-2.4.so.2 [0xb76bc6d8] #7 /usr/lib/libldap_r-2.4.so.2 [0xb76eb950] #8 /lib/ld-linux.so.2 [0xb7f0e453] #9 /lib/i686/cmov/libc.so.6(exit+0x89) [0xb7b23ab9] #10 /usr/sbin/smbd [0x82c23bc] #11 /usr/sbin/smbd [0x82c23e0] #12 /usr/sbin/smbd(start_background_queue+0x25c) [0x824893c] #13 /usr/sbin/smbd(main+0x1344) [0x82c3ab4] #14 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b0b455] #15 /usr/sbin/smbd [0x8082b11] [2009/05/19 08:45:59, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd and the 'net getlocalsid' returns me the following: fileserver:/var/log/samba# net getlocalsid [2009/05/19 09:25:19, 0] lib/smbldap_util.c:smbldap_search_domain_info(267) smbldap_search_domain_info: Got too many (2) domain info entries for domain DOMINIO SID for domain DOMINIO is: S-1-5-21-8741790
[Samba] Client driver installation
I've an OpenSuSE based server installed at work that uses Samba to share out the prrinters for our users on the AD that will be replacing our aging Windows 2000 print server. I'm in the process of getting the printer drivers installed for Windows clients. At present, I'm installing the drivers for the RICOH Aficio we have. When I run the following command: printmaster:/var/lib/samba/drivers/W32X86 # rpcclient -U ggreene -c "adddriver 'Windows NT x86' 'RICOH:RIC641K.DLL:RIC641K.DLL:RIC641U.DLL:RIC641.HLP:NULL:RAW:RIC641K.DLL,RIC641U.DLL,RIC641.HLP,RIC641P.DLL,RIC641C.DLL,RIC641L.DLL,RIC641X.DLL,RIC641S.DLL,RIC641J.DLL,RIC641Q.EXE,RIC641ZU.DLL,RIC641ZK.DLL,RIC641WU.DLL,RIC641WK.DLL,RIC641PI.DLL,RIC641SR.EXE,RIC641CF.DLL,RIC641X.EXE,TrackID.DLL,TIBase64.dll,TIFmtA.dll,RICJC32.dll,JCUI.exe' 3" printmaster I get the following output: result was WERR_UNKNOWN_PRINTER_DRIVER With the logging output of the printdrivers set to 10, I get the following from the logs: [2009/05/20 14:51:58, 0] printing/nt_printing.c:move_driver_to_download_area(1931) move_driver_to_download_area: Unable to rename [W32X86/RIC641K.DLL] to [W32X86/3/RIC641K.DLL] Any help would be appreciated as I'm trying to get this done ASAP. -- Gary L. Greene, Jr. Project Lead and Developer for the AltimatOS Project. Volunteer Developer for the KDE Project. This email was sent using SquirrelMail. "Webmail for nuts!" http://squirrelmail.org/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] multiple domain info entries problem
i still have this problem i have not found any solution. sorry for the 'up' on the topic, but i'm really in trouble with this situation. any idea anyone? Leonardo Carneiro escreveu: after many tries and upgrading my samba to 3.2.5, the sharing is working... kind of. now everyone can access their exclusive folders on the server, also can acess the public folder (anyone can access this folder without authentication). when people try to access folders that they should not access (like a IT guy accessing the Sales folder), the server also forbid the access. But when someone try to access their group folder (like the Sales guy accessing the Sales folder), windows show a error message, telling me the folder is no accessible. any help is welcome. tks in advance. Leonardo Carneiro escreveu: Hi fellows. I'm new to the list and hope I'll have a nice time here. one of my servers running samba+ldap is not working properly. the setup is: Debian 5 fileserver:/etc/samba#smbd --version Version 3.0.24 fileserver:/etc/samba# slapd -V @(#) $OpenLDAP: slapd 2.3.30 (Oct 5 2008 22:08:58) $ j...@galadriel:/home/jmm/ldap/openldap2.3-2.3.30/debian/build/servers/slapd After a samba upgrade via apt-get, the user could not access their shared folders anymore. Looking at the logs i'd saw some strage things: smbd.log: === [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 6550 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(45) === [2009/05/19 08:45:59, 0] lib/util.c:smb_panic(1599) PANIC (pid 6550): internal error [2009/05/19 08:45:59, 0] lib/util.c:log_stack_trace(1706) BACKTRACE: 15 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c3d3] #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c4c6] #2 /usr/sbin/smbd [0x821a69a] #3 [0xb7eff420] #4 /usr/lib/liblber-2.4.so.2(ber_memfree_x+0x50) [0xb76ac300] #5 /usr/lib/libldap_r-2.4.so.2 [0xb76dc274] #6 /usr/lib/libldap_r-2.4.so.2 [0xb76bc6d8] #7 /usr/lib/libldap_r-2.4.so.2 [0xb76eb950] #8 /lib/ld-linux.so.2 [0xb7f0e453] #9 /lib/i686/cmov/libc.so.6(exit+0x89) [0xb7b23ab9] #10 /usr/sbin/smbd [0x82c23bc] #11 /usr/sbin/smbd [0x82c23e0] #12 /usr/sbin/smbd(main+0x10f0) [0x82c3860] #13 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b0b455] #14 /usr/sbin/smbd [0x8082b11] [2009/05/19 08:45:59, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(41) === [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 6556 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/05/19 08:45:59, 0] lib/fault.c:fault_report(45) === [2009/05/19 08:45:59, 0] lib/util.c:smb_panic(1599) PANIC (pid 6556): internal error [2009/05/19 08:45:59, 0] lib/util.c:log_stack_trace(1706) BACKTRACE: 16 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c3d3] #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c4c6] #2 /usr/sbin/smbd [0x821a69a] #3 [0xb7eff420] #4 /usr/lib/liblber-2.4.so.2(ber_memfree_x+0x50) [0xb76ac300] #5 /usr/lib/libldap_r-2.4.so.2 [0xb76dc274] #6 /usr/lib/libldap_r-2.4.so.2 [0xb76bc6d8] #7 /usr/lib/libldap_r-2.4.so.2 [0xb76eb950] #8 /lib/ld-linux.so.2 [0xb7f0e453] #9 /lib/i686/cmov/libc.so.6(exit+0x89) [0xb7b23ab9] #10 /usr/sbin/smbd [0x82c23bc] #11 /usr/sbin/smbd [0x82c23e0] #12 /usr/sbin/smbd(start_background_queue+0x25c) [0x824893c] #13 /usr/sbin/smbd(main+0x1344) [0x82c3ab4] #14 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b0b455] #15 /usr/sbin/smbd [0x8082b11] [2009/05/19 08:45:59, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd and the 'net getlocalsid' returns me the following: fileserver:/var/log/samba# net getlocalsid [2009/05/19 09:25:19, 0] lib/smbldap_util.c:smbldap_search_domain_info(267) smbldap_search_domain_info: Got too many (2) domain info entries for domain DOMINIO SID for domain DOMINIO is: S-1-5-21-874179082-3571801642-3889913597 Other tests also returns me the smb_ldap_search_domain_info error, but my ldap only one sambaDomain and sambaDomainName entries. Other apps using ldap like squid ar
[Samba] Intermittently Get "Target filesystem does not support long file names" when copying file to Samba share
I have two CentOS servers running samba3-3.0.34-37. When I connect to a samba share from my Windows 2003 R2 servers, and then try to copy a file to it, I often get the message "target filesystem does not support long filenames." Sometimes it works and sometimes it doesn't. I've been fighting this problem for 2 years. I've replaced my Windows servers, changed my Windows version, replaced my Linux servers, changed my Linux version, and tried various versions of samba, but the problem persists. Does anyone on this list have any idea what causes this and how to fix it? Disclaimer - May 20, 2009 This email and any files transmitted with it are confidential and intended solely for sa...@lists.samba.org. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management and Physician's Managed Care. Warning: Although Physician Select Management and Physician's Managed Care have taken reasonable precautions to ensure no viruses are present in this email, the companies cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] fs_acl_xattr und vfs_acl_tdb in Samba 3.3/3.4
On Wed, May 20, 2009 at 09:13:07AM +0200, Andreas Ladanyi wrote: > Hi volks, > > i want to ask if the "fs_acl_xattr" and "vfs_acl_tdb" in samba 3.3 are > now "stable" or if its planned to be stable in 3.4 There are a couple of features I'd like to add to these modules before I'd consider them "stable". 1). I need to use transactions in the tdb code for ACLs. (you don't want to lose all your ACL db :-). 2). I need to implement the timestamp feature that will allow the ACL modules to detect other programs modifying the acls out from under smbd. I have some code on my laptop for this, but it might not make 3.4.0. > What is the experience with this vfs modules in 3.3 ? I know some OEM's who have tested this, I haven't had any bug reports to either they're stable, or they decided not to use them :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Panic
On Wed, May 20, 2009 at 01:12:48PM +0100, Andrew Porter wrote: > >Volker Lendecke wrote: > > > >>Send more logs -- at least 1000 lines before that event > >>please. bzip2 should nicely compress that. > > > >Attached > > > > Just wondering if anyone had chance to look into this ? It's still a > problem for me. Busy with other stuff right now, sorry. Volker pgpoCfDNgnhNV.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Panic
Andrew Porter wrote: Volker Lendecke wrote: Send more logs -- at least 1000 lines before that event please. bzip2 should nicely compress that. Attached Just wondering if anyone had chance to look into this ? It's still a problem for me. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] SAMBA V. 3.2.3 to ActivDirectory sign on
Hallo, i have a problem with the logon as user. The logon to read on LDAP is ok, then the admin is CN=admin bat user sign on is a attribute. My Config LDAP: OU=Benutzer-ber, OU=Berlin,DC=ldap,DC=de | |--- CN = admin |--- CN = popay\, pop |--- opjectClass = user(sAMAccountName = ppop) OU=Benutzer-ber, OU=Berlin,DC=ldap,DC=de ldap filter = (& (objectClass=user)(sAMAccountName=%u)) ldap user suffix = sAMAccountName My question: can SAMBA interieren? Thanks PS: sorry for my English my German is better ;O) ___ Liebe Grüße aus Berlin ccn Torsten Pregel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Newbie question - force file permission to user's secondary groups.
On Mon, May 18, 2009 at 2:24 PM, Conta Falsa 337 wrote: > I read http://us1.samba.org/samba/docs/man/manpages-3/smb.conf.5.html the > part regarding "group" or "force group" directive, and it's not clear to me > if I can have more than one instance of this directive, since I need the > group to be forced depending on which share the user is creating the file. > > An example: > > user: james > first share: projectX (he is a member of the group projectX) > second share: projectY (he is a member of the group projectY) > > James is a member of both groups, since I don't use PDC (Vista clients), > the first time the user tries to access the shared folder, he will be asked > for the password, say he first opens /projectX, then he will be forced do > group projectX, but what if he opens projectY and tries to write there? To my knowledge - then user connects to server he is asked to submit user and password (if security = user), then server authenticates user and gives him a token with rights for further connections. So it doesn't matter which share you are accessing, you are accessing server with the token you got from first authentication. > - Is it possible to have "force group" on the shares section, so each > share has one? yes it is and that is were I use it. > - Will the user be asked for the password again,if he opens the second > share (without rebooting Windows)? The "change" of the primary group will > happen transparently, or the user would have to disconnect, and then open > the /projectY (therefore having to type his username/password again)? As I said - token is your rights to the server. It is valid until you logoff (maybe command "net use * /d" on workstation may help to forget token without logoff, but I'm not sure). User is asked for a password once to get a token (if security = user in smb.conf). force group directive is working on samba server file system, it does not effect user membership. I think setting force group on share can even be set to group the user does not belong to (again - not sure, but you can test). This directive will force all files and folders created on the share to be owned by group specified in force group directive. You set force group directive to make sure all files in that share are created with appropriate group. > thanks for your time. > > > > 2009/5/15 Liutauras Adomaitis >> >> On Fri, May 15, 2009 at 4:27 PM, Conta Falsa 337 >> wrote: >> > samba version is 3.0.28a-1ubuntu4.7 >> > -- >> > >> > I created users on both samba and the linux system, and created 3 groups >> > on >> > the system. Each of these groups own a specific directory, the directory >> > on >> > the filesystem belongs to root.groupfoo. On my smb.conf I gave each of >> > these >> > groups write access to its directory (@groupfoo to the share /groupfoo). >> > So >> > now every linux user belonging to groupfoo can write there. The problem >> > is, >> > groupfoo is not the user's primary group, so the file is created with >> > permission user1.user1, and not user1.groupfoo, therefore, other users >> > belonging to groupfoo cannot edit or delete that file. I read smb.conf >> > manual, but found no option to enforce that if the top directory belongs >> > to >> > root.groupfoo all files created under there will belong to >> > "userxyz.groupfoo", so I set on the filesystem each of those 3 >> > directories >> > to be setgid, so now every file created under, say, /groupbar (belongs >> > to >> > root.groupbar), has this permission: userabc.groupbar. I would like that >> > the >> > file/directory created belongs to the user executing the operation, and >> > to >> > the toplevel group owning that share, since a user can belong to 2 or >> > all of >> > those 3 groups mentioned, knowing that every user does not have any of >> > those >> > 3 groups as primary group. >> > >> > Is this the right approach or did I misunderstood the manual and I >> > should >> > do this only on smb.conf and not have to enforce it on the filesystem? >> > >> >> Sounds to me this is a force group directive which should take care of >> this. >> >> Liutauras >> -- >> 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
[Samba] fs_acl_xattr und vfs_acl_tdb in Samba 3.3/3.4
Hi volks, i want to ask if the "fs_acl_xattr" and "vfs_acl_tdb" in samba 3.3 are now "stable" or if its planned to be stable in 3.4 What is the experience with this vfs modules in 3.3 ? Bye, Andy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Re: read/write multiplexed support
On Wed, May 20, 2009 at 02:22:34AM +0200, Günter Kukkukk wrote: > Volker, > > i remember our irc talk: > http://samba.sernet.de/irclog/2007/08/20070826-Sun.log Can you file a bug at bugzilla, upload one of the network traces showing readmpx and writempx and assign it to me? I make no promises, but this way it will regularly bug me until I fix that. Thanks, Volker pgpww0au1ZsE0.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
