Re: [Samba] Samba bug 9615
I reverted back to 3.6.6 and everything works again. So, rewording my original question, is winbind authentication against a Windows 2000 DC deprecated and no longer supported by Samba? Please note that the reporter of the bug has proposed a patch to get this working again. Thank you for your time. Dale On 05/23/2013 11:58 AM, Dale Schroeder wrote: Debian testing recently released a large version jump update to Samba (3.6.6 to 3.6.15). After the upgrade, winbind no longer works which, according to the information in the bug report, is due to authentication again a Windows 2000 DC. https://bugzilla.samba.org/show_bug.cgi?id=9615 Are there any plans to patch this bug, or is winbind against a W2K DC forever a nonviable combination? cli_rpc_pipe_open_schannel_with_key failed: NT_STATUS_UNSUCCESSFUL msrpc_sid_to_name: failed to looKup sids: NT_STATUS_UNSUCCESSFUL Thanks, Dale -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba bug 9615
Debian testing recently released a large version jump update to Samba (3.6.6 to 3.6.15). After the upgrade, winbind no longer works which, according to the information in the bug report, is due to authentication again a Windows 2000 DC. https://bugzilla.samba.org/show_bug.cgi?id=9615 Are there any plans to patch this bug, or is winbind against a W2K DC forever a nonviable combination? cli_rpc_pipe_open_schannel_with_key failed: NT_STATUS_UNSUCCESSFUL msrpc_sid_to_name: failed to looKup sids: NT_STATUS_UNSUCCESSFUL Thanks, Dale -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba Bug 8881 still present in Samba 4.0.x?
Hello list, could someone in the know please tell me if Samba Bug #8881 (username map not working in security=ADS) is still present in Samba 4.0.x? Best regards, Heinz Mueller -- Gesendet von meinem /sent from my FSC Scenic P320 ;-) Heinz Mueller PBG MBG SDTS EP HE BS FUJITSU Fujitsu Technology Solutions GmbH Tel:(+49)5251 525 1583 Fax:(+49)5251 525 321583 Email:heinz.muel...@ts.fujitsu.com Web ts.fujitsu.com Company details ts.fujitsu.com/imprint -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba bug 7818 / Debian bug 603729 RESOLVED finally (I think)
I thought I would post this in case it might be of help to someone else who has experienced winbind crashes since moving to 3.5.x. Back in November 2010, after upgrading to Samba 3.5.x, I started experiencing repeated winbind crashed resulting in the generation of winbind_cache.corrupt files. I was premature in saying the problem was resolved and the bugs could be closed because my attempted winbind fix lasted less than 36 hours. In the interim, I've been constantly monitoring and trying other things. A recent unrelated problem affecting the entire LAN apparently enabled me to resolve the repeated winbind crashes. Actually, Steve Langasek provided the necessary clue in December, but I did not know what to do with the info at the time. He said: It's the nature of OpenDNS that if you send a query to it for*any* hostname that doesn't resolve, instead of (properly) giving a no such host message, it instead responds with an IP address pointing to one of its own webservers. So any failure to resolve a name via WINS will result in it being resolved to OpenDNS instead, in this situation. Using redirecting DNS forwarders appears to be the source of my winbind problem. Using DNS Benchmark ( http://www.grc.com/dns/benchmark.htm ), I was able to identify public non-redirecting servers to use. After changing the forwarders, I have not had a winbind crash in 5+ days. Note that I have a server still using 3.2.5 that has not had a single winbind problem during this entire period. In fact, all versions through 3.4.x worked flawlessly, so something in the internal workings of winbind/DNS changed with 3.5. During the entire problem period, the DC was available and fuctioning properly, as was the WINS server. My suspicion is that the DC was not responding as fast as winbind expected it to, then resorting to OpenDNS to resolve the name, resulting in a redirection to an OpenDNS server, ultimately leading to the winbind crash. If my suspicion is correct, this may be another manifestation of one of the bugs fixed in 3.5.8: o Fix Winbind crash bug when no DC is available (bug #7730). So, if you are using Samba 3.5.x and are having winbind problems, ensure that the DNS servers that you are using are non-redirecting. It might give you a reprieve until 3.5.8 comes to your distribution. Dale -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] SAMBA bug??
Hi all, I've download and install Fedora Core 6, and use as fileserver in my cybercafe.. it's for heavy duty use. But it crash few times on 7th of Jan.. here are the log i copy from nmbd.log : [2007/01/07 04:04:16, 0] nmbd/nmbd.c:process(561) Got SIGHUP dumping debug info. [2007/01/07 04:04:16, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(282) dump_workgroups() dump workgroup on subnet 192.168.1.4: netmask= 255.255.255.0: WORKGROUP(1) current master browser = FILESERVER GAMESRV 40819a03 (Samba Server) FILESERVER 40071003 (file server for games file) [2007/01/07 04:04:16, 0] lib/fault.c:fault_report(41) === [2007/01/07 04:04:16, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 6721 (3.0.23c-2) Please read the Trouble-Shooting section of the Samba3-HOWTO [2007/01/07 04:04:16, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2007/01/07 04:04:17, 0] lib/fault.c:fault_report(45) === [2007/01/07 04:04:17, 0] lib/util.c:smb_panic(1614) PANIC (pid 6721): internal error [2007/01/07 04:04:17, 0] lib/util.c:log_stack_trace(1721) BACKTRACE: 9 stack frames: #0 nmbd(log_stack_trace+0x1c) [0x555f88bc] #1 nmbd(smb_panic+0x43) [0x555f89a3] #2 nmbd [0x555e6d72] #3 /lib64/libc.so.6 [0x2c485210] #4 nmbd(tdb_traverse+0x17) [0x5560d567] #5 nmbd(initiate_wins_processing+0x5f) [0x5559711f] #6 nmbd(main+0x7ff) [0x55581bbf] #7 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2c472a44] #8 nmbd [0x55580219] [2007/01/07 04:04:18, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/nmbd [2007/01/07 06:22:37, 0] nmbd/nmbd.c:main(700) Netbios nameserver version 3.0.23c-2 started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2007/01/07 08:41:02, 0] nmbd/nmbd.c:main(700) Netbios nameserver version 3.0.23c-2 started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2007/01/07 13:35:38, 0] nmbd/nmbd.c:main(700) Netbios nameserver version 3.0.23c-2 started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2007/01/07 14:57:55, 0] nmbd/nmbd.c:main(700) Netbios nameserver version 3.0.23c-2 started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2007/01/07 14:59:49, 0] nmbd/nmbd.c:terminate(58) Got SIGTERM: going down... [2007/01/07 15:01:41, 0] nmbd/nmbd.c:main(700) Netbios nameserver version 3.0.23c-2 started. Copyright Andrew Tridgell and the Samba Team 1992-2006 Is this a Samba bug?? How can i solve it?/ Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba bug: 1 out of 387 files off by 1 hour (DST/ST bug)
Summary: There appears to be a bug in the time range Samba is using on dates where time is scheduled to Spring Forward from Standard to Daylight Savings time. Might want to review the code for Falling back, as well... Details: This started out with my thinking it was an rsync problem, but it appears to be something to do with how samba is exporting the file time (!? or Windows is reading 1 file). I have 2 files in a windows directory, /tmp/files: fo1.mp3, fo2.mp3. I rsynced them to a directory on a linux box running SuSE 9.1 with samba-3.0.9-2.6. On the linux/samba server, I see times: target ll --full-time total 6264 -rwxr- 1 user 2532415 2000-04-02 01:34:50.0 -0800 fo1.mp3* -rwxr- 1 user 3876671 2000-03-12 22:33:20.0 -0800 fo2.mp3* (which are the same times as on the Windows source dir:) /tmp/files ll --full-time total 6272 -rw-r- 1 user 2532415 2000-04-02 01:34:50.0 -0800 fo1.mp3 -rw-r- 1 user 3876671 2000-03-12 21:33:20.0 -0800 fo2.mp3 But, the Win XP's view of the remote files differs on 1 file: /tmp/files ll --full-time /k/target/ total 7168 -rw-r- 1 user 2532415 2000-04-02 00:34:50.0 -0800 fo1.mp3 ---^ -rw-r- 1 user 3876671 2000-03-12 21:33:20.0 -0800 fo2.mp3 This is 1 file out of 387 that has this problem. The same problem occurs when I use smbmount on the server to mount the exported samba share (but mounted by root): -rwxr-xr-x 1 root 2532415 2000-04-02 00:34:50.0 -0800 fo1.mp3 ---^ -rwxr-xr-x 1 root 3876671 2000-03-12 21:33:20.0 -0800 fo2.mp3 - Note -- same time as seen on the Windows box, but this time it is seen through the linux based smbmounted view. It seems to be a bug related to the the time changing on that date from Standard to Daylight Saving Time. To be more particular, on that date, times in the range =2:00AM and 3:00AM would not exist. It would appear the code for time checking is using the wrong time range on that date. Linda -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba bug
Hi. I have some trouble with my samba domain controller. Every time I try to logout my windows workstation, I get an error that the share is no longer availible. I estimate that this happens around the time when windows tries to copy my user profile back to the server. (because when I change profile type to local the error no longer occurs) on the samba side the following error is logged. === [2005/06/06 16:56:22, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 13277 (3.0.14a) Please read the appendix Bugs of the Samba HOWTO collection [2005/06/06 16:56:22, 0] lib/fault.c:fault_report(39) === [2005/06/06 16:56:22, 0] lib/util.c:smb_panic2(1495) PANIC: internal error [2005/06/06 16:56:22, 0] lib/util.c:smb_panic2(1503) BACKTRACE: 22 stack frames: #0 smbd(smb_panic2+0x1bb) [0x81dcf83] #1 smbd(smb_panic+0x19) [0x81dcdc6] #2 smbd [0x81cac51] #3 smbd [0x81cacc6] #4 /lib/libc.so.6 [0x402b1168] #5 /lib/libc.so.6(__getmntent_r+0x36) [0x4035ed66] #6 /lib/libc.so.6(getmntent+0x55) [0x4035ec05] #7 smbd [0x80db11e] #8 smbd(sys_get_quota+0xa0) [0x80dba4e] #9 smbd(disk_quotas+0x46) [0x80df1ae] #10 smbd [0x8086a41] #11 smbd(sys_disk_free+0x2d) [0x8086ca8] #12 smbd(vfswrap_disk_free+0x2d) [0x80cac2c] #13 smbd [0x80b70ea] #14 smbd(reply_trans2+0x938) [0x80bf3be] #15 smbd [0x80d6b58] #16 smbd [0x80d6c08] #17 smbd(process_smb+0x1eb) [0x80d6f4d] #18 smbd(smbd_process+0x171) [0x80d7b43] #19 smbd(main+0x843) [0x82528e9] #20 /lib/libc.so.6(__libc_start_main+0xce) [0x4029d8de] #21 smbd(chroot+0x31) [0x8079321] anyone any idea as to what might cause this problem? Mark Hannessen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba bug
On Mon, Jun 06, 2005 at 09:03:57PM +0200, Mark Hannessen wrote: Hi. I have some trouble with my samba domain controller. Every time I try to logout my windows workstation, I get an error that the share is no longer availible. I estimate that this happens around the time when windows tries to copy my user profile back to the server. (because when I change profile type to local the error no longer occurs) on the samba side the following error is logged. === [2005/06/06 16:56:22, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 13277 (3.0.14a) Please read the appendix Bugs of the Samba HOWTO collection [2005/06/06 16:56:22, 0] lib/fault.c:fault_report(39) === [2005/06/06 16:56:22, 0] lib/util.c:smb_panic2(1495) PANIC: internal error [2005/06/06 16:56:22, 0] lib/util.c:smb_panic2(1503) BACKTRACE: 22 stack frames: #0 smbd(smb_panic2+0x1bb) [0x81dcf83] #1 smbd(smb_panic+0x19) [0x81dcdc6] #2 smbd [0x81cac51] #3 smbd [0x81cacc6] #4 /lib/libc.so.6 [0x402b1168] #5 /lib/libc.so.6(__getmntent_r+0x36) [0x4035ed66] #6 /lib/libc.so.6(getmntent+0x55) [0x4035ec05] #7 smbd [0x80db11e] #8 smbd(sys_get_quota+0xa0) [0x80dba4e] #9 smbd(disk_quotas+0x46) [0x80df1ae] #10 smbd [0x8086a41] #11 smbd(sys_disk_free+0x2d) [0x8086ca8] #12 smbd(vfswrap_disk_free+0x2d) [0x80cac2c] #13 smbd [0x80b70ea] #14 smbd(reply_trans2+0x938) [0x80bf3be] #15 smbd [0x80d6b58] #16 smbd [0x80d6c08] #17 smbd(process_smb+0x1eb) [0x80d6f4d] #18 smbd(smbd_process+0x171) [0x80d7b43] #19 smbd(main+0x843) [0x82528e9] #20 /lib/libc.so.6(__libc_start_main+0xce) [0x4029d8de] #21 smbd(chroot+0x31) [0x8079321] What OS are you running Samba on ? 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 bug
On Monday 06 June 2005 21:09, Jeremy Allison wrote: On Mon, Jun 06, 2005 at 09:03:57PM +0200, Mark Hannessen wrote: Hi. I have some trouble with my samba domain controller. Every time I try to logout my windows workstation, I get an error that the share is no longer availible. I estimate that this happens around the time when windows tries to copy my user profile back to the server. (because when I change profile type to local the error no longer occurs) on the samba side the following error is logged. === [2005/06/06 16:56:22, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 13277 (3.0.14a) Please read the appendix Bugs of the Samba HOWTO collection [2005/06/06 16:56:22, 0] lib/fault.c:fault_report(39) === [2005/06/06 16:56:22, 0] lib/util.c:smb_panic2(1495) PANIC: internal error [2005/06/06 16:56:22, 0] lib/util.c:smb_panic2(1503) BACKTRACE: 22 stack frames: #0 smbd(smb_panic2+0x1bb) [0x81dcf83] #1 smbd(smb_panic+0x19) [0x81dcdc6] #2 smbd [0x81cac51] #3 smbd [0x81cacc6] #4 /lib/libc.so.6 [0x402b1168] #5 /lib/libc.so.6(__getmntent_r+0x36) [0x4035ed66] #6 /lib/libc.so.6(getmntent+0x55) [0x4035ec05] #7 smbd [0x80db11e] #8 smbd(sys_get_quota+0xa0) [0x80dba4e] #9 smbd(disk_quotas+0x46) [0x80df1ae] #10 smbd [0x8086a41] #11 smbd(sys_disk_free+0x2d) [0x8086ca8] #12 smbd(vfswrap_disk_free+0x2d) [0x80cac2c] #13 smbd [0x80b70ea] #14 smbd(reply_trans2+0x938) [0x80bf3be] #15 smbd [0x80d6b58] #16 smbd [0x80d6c08] #17 smbd(process_smb+0x1eb) [0x80d6f4d] #18 smbd(smbd_process+0x171) [0x80d7b43] #19 smbd(main+0x843) [0x82528e9] #20 /lib/libc.so.6(__libc_start_main+0xce) [0x4029d8de] #21 smbd(chroot+0x31) [0x8079321] What OS are you running Samba on ? Jeremy. LFS 5.0 (http://www.nl.linuxfromscratch.org/lfs/news.html) with some mods and additions. (right now it's somewhere between 5.0 and 6.0) I compiled it myself, It's all very custom build. but all the software is origional. no patches and such, other then those provided by the lfs team. It a very small distro, mainly intended so I work with samba in a chroot. It was my intension to strip the rest of the distro away when I get samba fully working. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Bug?
Hi, I'm running Samba 3 with Windows XP clients and I get an extrange problem. I have a share on the server and XP clients do not show all files in the share, Linux shows all files but XP doesn't. The directory and the files on it has 0770 permissions. The share has the following config [datos] comment = Datos path = /datos create mask = 0770 directory mask = 0770 browseable = yes guest ok = no writeable = yes This is very extrange and I want to know if is this a bug of samba or a config problem. Thanks Hector Iturre ___ 100mb gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo http://correo.yahoo.com.ar -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba bug or by design - browsing root
Dear Technical Support, We have a user who just accidentally mapped a network drive by entering \\hostname\root and it worked eventhough root is not defined for sharing in smb.conf file. Now that we know, we are able to browse the root level on the UNIX server just by keying in \\hostname\root from IE or Windows explorer. Is this a setting/configuration problem or by design for samba? Is there a way to avoid this since we do want users to be able to browse root (/). Any help on this matter would be greatly appreciated. I'm currently running on the following environment: OS = DGUX R4.20MU06 Samba version = 2.2.8a Thanks, Van Ta -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba bug or by design - browsing root
On Tue, 13 Jan 2004 [EMAIL PROTECTED] wrote: Dear Technical Support, We have a user who just accidentally mapped a network drive by entering \\hostname\root and it worked eventhough root is not defined for sharing in smb.conf file. Now that we know, we are able to browse the root level on the UNIX server just by keying in \\hostname\root from IE or Windows explorer. Is this a setting/configuration problem or by design for samba? Is there a way to avoid this since we do want users to be able to browse root (/). Any help on this matter would be greatly appreciated. I'm currently running on the following environment: OS = DGUX R4.20MU06 Samba version = 2.2.8a Your Samba server is very definitely not configured correctly. Please contact me off-line and I will try to help you to solve your problem. Cheers, John T. -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
