[Samba] Issue with file server (Non-Domain Controller) authenticating off the same LDAP as the PDC
Hi, Samba version 3.2-test(from git) I have a PDC(CS Domain) called kerry with an openldap backend, I have a file server that i want to authenticate off the same ldap as the PDC but i dont want it to be a BDC. This machine is called offaly. I would have thought that this would work pretty smoothly if i just configure domain logons = no. But then the file server generates it own SID and doesnt use the SID for the CS domain and creates its own account policies. Is there any way to have domain logons=yes but not act as a BDC or is it possible for to have domain logons=no and conform to the SID and account policies for the CS Domain. More info, When Domain Logons = no then it generates this in LDAP: dn: sambaDomainName=OFFALY,dc=cs,dc=dit,dc=ie sambaDomainName: OFFALY sambaSID: S-1-5-21-1810654286-1445949878-2619355827 sambaAlgorithmicRidBase: 1000 objectClass: sambaDomain sambaNextUserRid: 1000 structuralObjectClass: sambaDomain entryUUID: 1db04188-79bc-102d-8b3c-bff53cf5d285 creatorsName: cn=admin,dc=cs,dc=dit,dc=ie createTimestamp: 20090118145748Z sambaMinPwdLength: 5 sambaPwdHistoryLength: 0 sambaLogonToChgPwd: 0 sambaMaxPwdAge: -1 sambaMinPwdAge: 0 sambaLockoutDuration: 30 sambaLockoutObservationWindow: 30 sambaLockoutThreshold: 0 sambaForceLogoff: -1 sambaRefuseMachinePwdChange: 0 But it should i want it to use the CS domain one namely: dn: sambaDomainName=CS,dc=cs,dc=dit,dc=ie sambaAlgorithmicRidBase: 1000 sambaNextUserRid: 1000 structuralObjectClass: sambaDomain entryUUID: cf6b1632-7886-102d-88b4-cdd5ec2918da creatorsName: cn=admin,dc=cs,dc=dit,dc=ie createTimestamp: 20090117020342Z sambaRefuseMachinePwdChange: 0 gidNumber: 1000 sambaDomainName: CS sambaSID: S-1-5-21-162219125-2768231107-2725269179 objectClass: top objectClass: sambaDomain objectClass: sambaUnixIdPool sambaLockoutDuration: 10 sambaLockoutObservationWindow: 10 sambaLockoutThreshold: 5 sambaMinPwdLength: 5 sambaPwdHistoryLength: 5 sambaLogonToChgPwd: 0 sambaMaxPwdAge: 7776000 sambaMinPwdAge: 0 sambaForceLogoff: -1 uidNumber: 1009 sambaNextRid: 1002 Any Ideas? Thanks David -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Ntlm_auth authentication problem issue
On Tue, 2009-01-20 at 18:29 -0400, orlandox wrote: > Hi, I have an arquitecture, of squid-Active Directory with NTLM > authentication, I have users registered in Active Directory with > character 'ñ' in this username, with ldap authentication work well, but > with ntlm the user is not found, and can't be authenticated. > > Is a problem of charset?, my linux use utf-8. Maybe change it to latin-1 > could resolve? This is highly unlikely to change anything here, and a very odd failure. (The client sends this as unicode, and the interface we use here *should* just convert to unix charset properly, and back to unicode for the SamLogon call) But for best luck, ensure everything is set to UTF8 (ie, leave at the defaults). Turning up the debugging in winbindd should show what the incoming user is when winbind first sees it. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. http://redhat.com signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Ntlm_auth authentication problem issue
Hi, I have an arquitecture, of squid-Active Directory with NTLM authentication, I have users registered in Active Directory with character 'ñ' in this username, with ldap authentication work well, but with ntlm the user is not found, and can't be authenticated. Is a problem of charset?, my linux use utf-8. Maybe change it to latin-1 could resolve? with the variables unix charset, dos charset? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] "Hosts allow" directive is not correctly evaluated for printer shares
On Tue, Jan 20, 2009 at 07:39:25PM +0100, Matthias Nagel wrote: > > These two log message appear, if the client tries to connect to the printer. > Oddly, access it permitted first and then denied in the same moment: > > [2009/01/20 18:40:19, 2] lib/access.c:check_access(323) >Allowed connection from (192.168.1.244) > [2009/01/20 18:40:19, 0] lib/access.c:check_access(327) >Denied connection from (192.168.1.244) > > If I comment out the "allow hosts" directive, the problem stays the same. > Something that is even more strange. Any ideas? Send in a full debug level 10 log from smbd so we can see exactly what is going on here. Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Windows XP SP3 and Samba 3.0.26a-1
Greetings- I have several Debian Sarge boxes running Samba 3.0.26a-1 from samba.org installed. Are there any known observations using XP Pro SP3 with that level of Samba? TIA! -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: open_directory: unable to create *. Error was NT_STATUS_OBJECT_NAME_COLLISION
I'm terribly sorry I forgot to mention the most vital stuff, I'm on the latest rpm build (for FC8): Fedora 8: kernel 2.6.23.1-42.fc8 samba-swat-3.0.33-0.fc8 samba-client-3.0.33-0.fc8 samba-common-3.0.33-0.fc8 samba-3.0.33-0.fc8 On Tue, Jan 20, 2009 at 3:44 PM, fbc wrote: > Hi, I'm having problems moving/renaming files as a member of. I tried to > move "test.txt" from "\\files\public\" to "\\files\public\OfficeWork". > Here's the error I get in windows: > *Cannot move test: access is denied. > Make sure the disk is not full or write-protected and that the file is not > currently in use.* > Here's the error log: > *[2009/01/20 15:10:34, 2] smbd/open.c:open_directory(2092) > open_directory: unable to create OfficeWork. Error was > NT_STATUS_OBJECT_NAME_COLLISION* > > List of permissions in my \\files\public\ directory (ls -al): > drwxrwx--- 9 officeuser1 local_office 4096 2009-01-20 15:14 > OfficeWork > -rwxrwx--- 1 officeuser1 local_office0 2009-01-20 15:28 > test.txt > > The relavent part of my smb.conf: > *[global] > workgroup = OFFICE > netbios aliases = FILES > server string = Samba Server v%v > security = DOMAIN > passdb backend = tdbsam > passwd program = /usr/bin/passwd %u > passwd chat = *Enter\snew\sUNIX\spassword:* %n\n > *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* . > passwd chat debug = Yes > username map = /etc/samba/smbusers > unix password sync = Yes > log level = 2 > syslog = 0 > log file = /var/log/samba/log.%m > max log size = 50 > printcap name = CUPS > add user script = /usr/sbin/useradd -m '%u' -g users -G users > delete user script = /usr/sbin/userdel -r %u > add group script = /usr/sbin/groupadd %g > delete group script = /usr/sbin/groupdel %g > add user to group script = /usr/sbin/usernod -G %g %u > add machine script = /usr/sbin/useradd -s /bin/false/ -d > /var/lib/nobody %u > logon script = %U.bat > logon path = \\%L\profiles\%U\%a > logon drive = H: > domain logons = Yes > os level = 255 > preferred master = Yes > domain master = Yes > wins support = Yes > ldap ssl = no > idmap uid = 15000-2 > idmap gid = 15000-2 > template shell = /bin/bash > profile acls = Yes > cups options = raw > socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 > SO_RCVBUF=8192 > time server = yes > hide dot files = yes > invalid users = bin deamon sys man postfix mail ftp > admin users = george.alexander > smb ports = 445 > vfs object = audit > domain admin group = @smbadmin > domain admin users = root > > [public] > comment = files > path = /home/samba/envision_files > valid users = @local_office > write list = @local_office > writable = Yes > create mask = 0770 > directory mask = 0770 > public = No* > > Here's the user's line in /etc/passwd: > *officeuser1:x:503:502::/home/officeuser1:/bin/bash* > > Here's the local_office group's line from /etc/group: > *local_office:x:502:* > > I've also tried specifying the comma separated usernames after "502:", with > no better results. > > Both files are 770, owned by my group (local_office), and my group is in > the "write list" for the share, so what the heck is going on? > I've also tried increasing the log level, but that seems to give me even > fewer details about what's going on. > Anybody have any ideas? Where should I start!? Thanks! > -guth > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] open_directory: unable to create *. Error was NT_STATUS_OBJECT_NAME_COLLISION
Hi, I'm having problems moving/renaming files as a member of. I tried to move "test.txt" from "\\files\public\" to "\\files\public\OfficeWork". Here's the error I get in windows: *Cannot move test: access is denied. Make sure the disk is not full or write-protected and that the file is not currently in use.* Here's the error log: *[2009/01/20 15:10:34, 2] smbd/open.c:open_directory(2092) open_directory: unable to create OfficeWork. Error was NT_STATUS_OBJECT_NAME_COLLISION* List of permissions in my \\files\public\ directory (ls -al): drwxrwx--- 9 officeuser1 local_office 4096 2009-01-20 15:14 OfficeWork -rwxrwx--- 1 officeuser1 local_office0 2009-01-20 15:28 test.txt The relavent part of my smb.conf: *[global] workgroup = OFFICE netbios aliases = FILES server string = Samba Server v%v security = DOMAIN passdb backend = tdbsam passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* . passwd chat debug = Yes username map = /etc/samba/smbusers unix password sync = Yes log level = 2 syslog = 0 log file = /var/log/samba/log.%m max log size = 50 printcap name = CUPS add user script = /usr/sbin/useradd -m '%u' -g users -G users delete user script = /usr/sbin/userdel -r %u add group script = /usr/sbin/groupadd %g delete group script = /usr/sbin/groupdel %g add user to group script = /usr/sbin/usernod -G %g %u add machine script = /usr/sbin/useradd -s /bin/false/ -d /var/lib/nobody %u logon script = %U.bat logon path = \\%L\profiles\%U\%a logon drive = H: domain logons = Yes os level = 255 preferred master = Yes domain master = Yes wins support = Yes ldap ssl = no idmap uid = 15000-2 idmap gid = 15000-2 template shell = /bin/bash profile acls = Yes cups options = raw socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 SO_RCVBUF=8192 time server = yes hide dot files = yes invalid users = bin deamon sys man postfix mail ftp admin users = george.alexander smb ports = 445 vfs object = audit domain admin group = @smbadmin domain admin users = root [public] comment = files path = /home/samba/envision_files valid users = @local_office write list = @local_office writable = Yes create mask = 0770 directory mask = 0770 public = No* Here's the user's line in /etc/passwd: *officeuser1:x:503:502::/home/officeuser1:/bin/bash* Here's the local_office group's line from /etc/group: *local_office:x:502:* I've also tried specifying the comma separated usernames after "502:", with no better results. Both files are 770, owned by my group (local_office), and my group is in the "write list" for the share, so what the heck is going on? I've also tried increasing the log level, but that seems to give me even fewer details about what's going on. Anybody have any ideas? Where should I start!? Thanks! -guth -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Fwd: Re: [Samba] "Hosts allow" directive is not correctly evaluated for printer shares
Hello, > What about cupsd.conf. Are there any IP restrictions there? > Dale yes, but they are the same as in Samba. Anyway - as fare as I know - this would not matter, because Cups only communicates to Samba on the same machine via the loopback interface and/or(?) a socket and not with the clients. Furthermore the error message comes from "lib/access.c:check_access", which is part of Samba. Matthias > > > Matthias Nagel wrote: > > Hello, > > > > the access to printer shares is denied because the client IP address is > > allegedly not in the "hosts allow" list, although it actually is and access > > to normal shares perfectly works. > > > > I have two samba servers (3.0.33) in two different subnets with pure > > Windows-XP-Clients. The first subnet is 192.168.1.0/24 and the server's ip > > address is 192.168.1.1. Let's call this server A for short. The second > > subnet is 192.168.2.0/24 and the server's ip address is 192.168.2.1. > > (Server B). Routing between both subnets works perfectly and server A is > > configured as a WINS server. Server B and all clients use this WINS server. > > Cross subnet browsing works, too. All hosts from both subnets are supposed > > to be allowed to access shares on both servers. For normal "file" shares it > > works. > > > > If a client tries to print to a printer share on the Samba server in the > > same subnet, access to this printer share is permitted, too. But if a > > client tries to print to a printer share on the Samba server of the other > > subnet, access is denied. Allegedly the ip address is not in the "hosts > > allow" directive. But why? In the example below a client from the first > > subnet with the ip address 192.168.1.244, tries to print to server B > > (192.168.2.1). > > > > Snippets from my smb.conf of client B: > > > > interfaces = 192.168.2.1 127.0.0.1 > > hosts allow = 192.168.2.0/24 192.168.4.0/24 192.168.1.0/24 127.0.0.0/8 > > bind interfaces only = yes > > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > > > > name resolve order = host wins > > wins support = no > > wins server = 192.168.1.1 > > > > printcap name = cups > > load printers = yes > > printing = cups > > > > [printers] > > comment = Alle Drucker > > path = /var/spool/samba > > browseable = no > > writable = no > > printable = yes > > > > [print$] > > comment = Druckertreiber > > path = /var/lib/samba/printers > > browseable = yes > > > > These two log message appear, if the client tries to connect to the > > printer. Oddly, access it permitted first and then denied in the same > > moment: > > > > [2009/01/20 18:40:19, 2] lib/access.c:check_access(323) > > Allowed connection from (192.168.1.244) > > [2009/01/20 18:40:19, 0] lib/access.c:check_access(327) > > Denied connection from (192.168.1.244) > > > > If I comment out the "allow hosts" directive, the problem stays the same. > > Something that is even more strange. Any ideas? > > > > Matthias -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] "Hosts allow" directive is not correctly evaluated for printer shares
Hello, the access to printer shares is denied because the client IP address is allegedly not in the "hosts allow" list, although it actually is and access to normal shares perfectly works. I have two samba servers (3.0.33) in two different subnets with pure Windows-XP-Clients. The first subnet is 192.168.1.0/24 and the server's ip address is 192.168.1.1. Let's call this server A for short. The second subnet is 192.168.2.0/24 and the server's ip address is 192.168.2.1. (Server B). Routing between both subnets works perfectly and server A is configured as a WINS server. Server B and all clients use this WINS server. Cross subnet browsing works, too. All hosts from both subnets are supposed to be allowed to access shares on both servers. For normal "file" shares it works. If a client tries to print to a printer share on the Samba server in the same subnet, access to this printer share is permitted, too. But if a client tries to print to a printer share on the Samba server of the other subnet, access is denied. Allegedly the ip address is not in the "hosts allow" directive. But why? In the example below a client from the first subnet with the ip address 192.168.1.244, tries to print to server B (192.168.2.1). Snippets from my smb.conf of client B: interfaces = 192.168.2.1 127.0.0.1 hosts allow = 192.168.2.0/24 192.168.4.0/24 192.168.1.0/24 127.0.0.0/8 bind interfaces only = yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 name resolve order = host wins wins support = no wins server = 192.168.1.1 printcap name = cups load printers = yes printing = cups [printers] comment = Alle Drucker path = /var/spool/samba browseable = no writable = no printable = yes [print$] comment = Druckertreiber path = /var/lib/samba/printers browseable = yes These two log message appear, if the client tries to connect to the printer. Oddly, access it permitted first and then denied in the same moment: [2009/01/20 18:40:19, 2] lib/access.c:check_access(323) Allowed connection from (192.168.1.244) [2009/01/20 18:40:19, 0] lib/access.c:check_access(327) Denied connection from (192.168.1.244) If I comment out the "allow hosts" directive, the problem stays the same. Something that is even more strange. Any ideas? Matthias ___ Sensationsangebot verlängert: WEB.DE FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.web.de/?ac=OM.AD.AD008K15039B7069a -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2.7 server loses printer - driver assignment - aditional info
On Tue, Jan 20, 2009 at 07:38:08PM +0100, Remy Zandwijk wrote: > Jeremy Allison wrote: >> On Tue, Jan 20, 2009 at 05:07:33PM +0100, Remy Zandwijk wrote: Our Samba/CUPS based printserver loses the info of which driver belongs to a certain printer. The server is running Samba 3.2.7 on Solaris 9. >>> The workstation from which printerdrivers are uploaded runs from a >>> VMware server VM (XP) which is reverted to the last snapshot every >>> time, to have a clean machine. The smb log shows: >>> >>> [2009/01/20 16:30:50, 0] lib/fault.c:(40) >>> === >>> [2009/01/20 16:30:50, 0] lib/fault.c:(41) >>> INTERNAL ERROR: Signal 10 in pid 20404 (3.2.7) >>> Please read the Trouble-Shooting section of the Samba3-HOWTO >>> [2009/01/20 16:30:50, 0] lib/fault.c:(43) >>> >>> From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf >>> [2009/01/20 16:30:50, 0] lib/fault.c:(44) >>> === >>> [2009/01/20 16:30:50, 0] lib/util.c:(1663) >>> PANIC (pid 20404): internal error >>> [2009/01/20 16:30:50, 0] lib/util.c:(1817) >>> unable to produce a stack trace on this platform >>> [2009/01/20 16:30:50, 0] lib/fault.c:(201) >>> dumping core in /var/log/samba/cores/smbd >>> >>> >>> I guess this is badUnfortunately, there is no core dump in that >>> directory. >>> >>> Any comments? >> >> Can you compile with -g and then add the following to >> your smb.conf [global] section please ? >> >> panic action = "/bin/sleep 9" >> >> when you reproduce the crash smbd should be stuck >> waiting for the sleep process to finish. Attach to >> the parent of the sleep process (the crashed smbd) >> with gdb and get a backtrace (the "bt" command). >> >> This should tell us more about where the problem >> happens. > > Hi Jeremy ;-) > > I'll compile a -g install tonight and put the panic action into smb.conf. > Hopefully we can cat it to crash. Great, thanks. If this is repeatable with a decet basktrace we should be able to nail it asap. Cheers, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2.7 server loses printer - driver assignment - aditional info
Jeremy Allison wrote: On Tue, Jan 20, 2009 at 05:07:33PM +0100, Remy Zandwijk wrote: Our Samba/CUPS based printserver loses the info of which driver belongs to a certain printer. The server is running Samba 3.2.7 on Solaris 9. The workstation from which printerdrivers are uploaded runs from a VMware server VM (XP) which is reverted to the last snapshot every time, to have a clean machine. The smb log shows: [2009/01/20 16:30:50, 0] lib/fault.c:(40) === [2009/01/20 16:30:50, 0] lib/fault.c:(41) INTERNAL ERROR: Signal 10 in pid 20404 (3.2.7) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/01/20 16:30:50, 0] lib/fault.c:(43) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/01/20 16:30:50, 0] lib/fault.c:(44) === [2009/01/20 16:30:50, 0] lib/util.c:(1663) PANIC (pid 20404): internal error [2009/01/20 16:30:50, 0] lib/util.c:(1817) unable to produce a stack trace on this platform [2009/01/20 16:30:50, 0] lib/fault.c:(201) dumping core in /var/log/samba/cores/smbd I guess this is badUnfortunately, there is no core dump in that directory. Any comments? Can you compile with -g and then add the following to your smb.conf [global] section please ? panic action = "/bin/sleep 9" when you reproduce the crash smbd should be stuck waiting for the sleep process to finish. Attach to the parent of the sleep process (the crashed smbd) with gdb and get a backtrace (the "bt" command). This should tell us more about where the problem happens. Hi Jeremy ;-) I'll compile a -g install tonight and put the panic action into smb.conf. Hopefully we can cat it to crash. -Remy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: time sync issue
wes wrote: I have done this on the XP machines. I think XP only syncs like once a week or something. I haven't had any trouble with it and it certainly seems to sync at bootup plus some other schedule of which I am less certain. I would like the directions for 2k as well. I still have a few of those around, but they are on the way out. Windows 2000 computers can run the Windows Time Service to synchronize clocks with an ntp server on the network. This is better than the method of setting the clock with a "net time" command in the logon script because it keeps the clock in sync between logins. To make it work follow these steps: 1. If it is already running, stop the Windows Time Service on the workstation. 2. Double click the file "timeset.reg" to update the registry settings. See below for what these are. 3. Set the "Startup Type" of the Windows Time Service to "Automatic" and Start it. The contents of the "timeset.reg" file are as follows. Note that you will have to edit the NtpServer value. An IP address probably works as well as a name. In my case the name is in the workstation "hosts" file. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters] "Period"="SpecialSkew" "NtpServer"="gecko" "Type"="NTP" Note that the "special skew" means that the checks will be performed every 45 minutes until 3 successful checks have been made, then once every 8 hours after that. The Time Service doesn't do any logging, but you can test to see if the sync works with the command: w32tm -once -test -v and you can see what the NtpServer is currently set to with: net time /querysntp Mark Nienberg -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2.7 server loses printer - driver assignment - aditional info
On Tue, Jan 20, 2009 at 05:07:33PM +0100, Remy Zandwijk wrote: >> Our Samba/CUPS based printserver loses the info of which driver belongs >> to a certain printer. The server is running Samba 3.2.7 on Solaris 9. > > The workstation from which printerdrivers are uploaded runs from a VMware > server VM (XP) which is reverted to the last snapshot every time, to have > a clean machine. The smb log shows: > > [2009/01/20 16:30:50, 0] lib/fault.c:(40) > === > [2009/01/20 16:30:50, 0] lib/fault.c:(41) > INTERNAL ERROR: Signal 10 in pid 20404 (3.2.7) > Please read the Trouble-Shooting section of the Samba3-HOWTO > [2009/01/20 16:30:50, 0] lib/fault.c:(43) > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > [2009/01/20 16:30:50, 0] lib/fault.c:(44) > === > [2009/01/20 16:30:50, 0] lib/util.c:(1663) > PANIC (pid 20404): internal error > [2009/01/20 16:30:50, 0] lib/util.c:(1817) > unable to produce a stack trace on this platform > [2009/01/20 16:30:50, 0] lib/fault.c:(201) > dumping core in /var/log/samba/cores/smbd > > > I guess this is badUnfortunately, there is no core dump in that directory. > > Any comments? Can you compile with -g and then add the following to your smb.conf [global] section please ? panic action = "/bin/sleep 9" when you reproduce the crash smbd should be stuck waiting for the sleep process to finish. Attach to the parent of the sleep process (the crashed smbd) with gdb and get a backtrace (the "bt" command). This should tell us more about where the problem happens. Thanks ! Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2.7 server loses printer - driver assignment - aditional info
On Tue, Jan 20, 2009 at 05:07:33PM +0100, Remy Zandwijk wrote: > >Our Samba/CUPS based printserver loses the info of which driver belongs > >to a certain printer. The server is running Samba 3.2.7 on Solaris 9. > > The workstation from which printerdrivers are uploaded runs from a VMware > server VM (XP) which is reverted to the last snapshot every time, to have a > clean machine. The smb log shows: > > [2009/01/20 16:30:50, 0] lib/fault.c:(40) > === > [2009/01/20 16:30:50, 0] lib/fault.c:(41) > INTERNAL ERROR: Signal 10 in pid 20404 (3.2.7) > Please read the Trouble-Shooting section of the Samba3-HOWTO > [2009/01/20 16:30:50, 0] lib/fault.c:(43) > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > [2009/01/20 16:30:50, 0] lib/fault.c:(44) > === > [2009/01/20 16:30:50, 0] lib/util.c:(1663) > PANIC (pid 20404): internal error > [2009/01/20 16:30:50, 0] lib/util.c:(1817) > unable to produce a stack trace on this platform > [2009/01/20 16:30:50, 0] lib/fault.c:(201) > dumping core in /var/log/samba/cores/smbd > > > I guess this is badUnfortunately, there is no core dump in that > directory. Crap, that's another SIGBUS, probably an alignment problem. Can you try if compiling with -g gives any info where this happens? Volker pgpFCnUg90Bez.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2.7 server loses printer - driver assignment - aditional info
Our Samba/CUPS based printserver loses the info of which driver belongs to a certain printer. The server is running Samba 3.2.7 on Solaris 9. The workstation from which printerdrivers are uploaded runs from a VMware server VM (XP) which is reverted to the last snapshot every time, to have a clean machine. The smb log shows: [2009/01/20 16:30:50, 0] lib/fault.c:(40) === [2009/01/20 16:30:50, 0] lib/fault.c:(41) INTERNAL ERROR: Signal 10 in pid 20404 (3.2.7) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/01/20 16:30:50, 0] lib/fault.c:(43) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/01/20 16:30:50, 0] lib/fault.c:(44) === [2009/01/20 16:30:50, 0] lib/util.c:(1663) PANIC (pid 20404): internal error [2009/01/20 16:30:50, 0] lib/util.c:(1817) unable to produce a stack trace on this platform [2009/01/20 16:30:50, 0] lib/fault.c:(201) dumping core in /var/log/samba/cores/smbd I guess this is badUnfortunately, there is no core dump in that directory. Any comments? -Remy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 3.2.7 server loses printer - driver assignment
Hi, Our Samba/CUPS based printserver loses the info of which driver belongs to a certain printer. The server is running Samba 3.2.7 on Solaris 9. Out of the blue, users complain they cannot print. Looking at 'printers and faxes' from a Windows machine shows no info in the 'Model' field. In normal situations this field lists the driver/model name. Weird thing is: nobody is touching the printserver configuration at the time Samba loses the information, although the ntprinters.tdb file's change time is the time the problem occurs. Stopping Samba and replacing the ntprinters.tdb file by a backup file works and we can see the drivers again. What is going on here, but more important: what is the best way to debug this one? -Remy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Chronic Intermittent Problems with "File system does not support long filenames."
When trying to create a file or folder, or sometimes even rename a file, on a samba share (3.0.28-0.el4.9) from a Windows 2003 R2 server, I occasionally receive an error message stating that the target filesystem does not support long filenames. It does not always happen. Also, I have another samba 3.0.28-0.el4.9 server where this does not happen at all. What causes this? Here's the smb.conf from the "bad" server. It's pretty much the same as the "good" server. [global] unix charset = LOCALE workgroup = MYWG netbios name = APP2 realm = MYWG.MD server string = Linux Server security = ADS allow trusted domains = No username map = /etc/samba/smbusers log level = 2 syslog = 0 log file = /var/log/samba/%m.log max log size = 50 printcap name = /etc/printcap ldap ssl = no idmap backend = idmap_rid:MYWG=500-1 idmap uid = 500-1 idmap gid = 500-1 template shell = /bin/false template homedir = /alley/%U winbind use default domain = no winbind nested groups = Yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = no hosts allow = 192.168.5. 192.168.10. 192.168.15. 172.16. 127. 10. load printers = yes cups options = raw hide dot files = yes short preserve case = no client schannel = no -- Eric Robinson Disclaimer - January 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 . Warning: Although has taken reasonable precautions to ensure no viruses are present in this email, the company 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/listinfo/samba
[Samba] auth methods
I would like to understand more about "auth methods" in smb.conf Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] [Announce] Samba 3.0.34 Maintainance Release Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 === "Minds are like parachutes. They only function when they are open." Sir James Dewar === Release Announcements = This is a bug fix release of the Samba 3.0 series. Major enhancements included in Samba 3.0.34 are: o Fix update of machine account passwords. o Fix SMB signing issue on Windows Vista with MS Hotfix KB955302. o Fix Winbind crashes. o Correctly detect if the current dc is the closest one. o Add saf_join_store() function to memorize the dc used at join time. This avoids problems caused by replication delays shortly after domain joins. o Fix write list in setups using "security = share". ## Changes ### Changes since 3.0.33 - o Michael Adam * Fix linking cifs.upcall when nscd_flush_cache() is found. * Fix smbd hanging on Solaris when winbindd closes socket. * Use the reconnect methods instead of the rpc methods directly. o Jeremy Allison * BUG 1254: Fix write list in setups using "security = share". * BUG 5052: Not work cancel inheritance on share. * BUG 5729: Explicitly allow "-valid" parameter. * BUG 5737: Fix Winbind crash in an unusual failure mode. * BUG 5750: Fix SMB signing issue on Windows Vista with MS Hotfix KB955302. * BUG 5751: Backport to fix showing of ACLson DFS with smbclient. * BUG 5790: Fix returning STATUS_OBJECT_NAME_NOT_FOUND on set file disposition call. * BUG 5814: Fix core dump of Winbind while doing "rescan_trusted_domain". * BUG 5873: Fix ACL inheritance. * BUG 5914: Fix build failure (redefinition of struct name_list). * BUG 5937: Fix filenames with "*" char hiding other files. * BUG 6019: File corruption in Clustered SMB/NFS environment managed via CTDB. * BUG 6035: Fix possible race between fcntl F_SETLKW and alarm delivery. * Remove unecessary msync. * Rename cifs.spnego to cifs.upcall. * Fix segfault when execution cifs.upcall without any arguments. * Ensure we emit the notify message before renaming the open files. * Fix use of DLIST_REMOVE. * Cope with bad trans2mkdir requests from System in QNTC IBM SMB client. * Fix memory leak in error path. * Fix logic bug introduced in backport of ccache_regain_all_now. o Kai Blin * Reformat the WBFLAGS defines to prepare for adding a new flag. * Put huge NTLMv2 blobs into extra_data on CRAP auth. o Günther Deschner * BUG 5710: Fix update of machine account passwords. * Define NET_SRVPWSET2 call. * Net should just use machine account creds when changing passwords. * Fix net_io_q_srv_pwset2. o Carsten Dumke * BUG 5892: Fix documentation of net rap printq info. o Dina Fine * BUG 5908: Fix failing of internal change notify on share directory. o Steve French * Fix compile warning in cifs.upcall. * Fix cifs.upcall manpage and comments. o Jeff Layton * Build cifs.upcall by default on Linux. * Fix negatively instantiate keys on error in cifs.upcall. * Handle handle MSKRB5 OID properly in cifs.upcall. * Bump SPNEGO msg version number and don't reject old versions in cifs.upcall. * Fix several problems when mounting subdirectories of shares in mount.cifs. * Don't prompt for password on krb5 mounts in mount.cifs. * Have uppercase_string return success on NULL pointer in mount.cifs. * Make return codes match the return codes for /bin/mount in mount.cifs. * Use lock/unlock_mtab scheme from util-linux-ng mount prog. o Volker Lendecke * BUG 5965: Fix creation of the first share using SWAT. * Fix bug triggered by the RAW-SAMBA3OPLOCKLOGOFF test. o David Leonard * BUG 4516: No IPv6 on Solaris 2.6. o Igor Mammedov * Add support for cifs.spnego helper into configure and Makefile.in. * Add checks for spnego prereq keyutils.h and kerberos in configure.in. * Add helper source for handling cifs kernel module upcall for kerberos authorization. * Add -c option to set service prefix to "cifs" in service principal by default service prefix "host" is used. * Add support for cifs.resolver upcall. o Stefan Metzmacher * Correctly detect if the current dc is the closest one. * For CLDAP we need to use get_sorted_dc_list() to avoid recursion. * Add fallback to return all dcs, when none is available in the requested site. * Add saf_join_store() function to memorize the dc used at join time. * Return an error instead of crashing when no realm is given. * Handle the SMB signing states the same in
