I encountered an bug in samba 2.0.7. With the config option "logon home = \\%N\%U\profile" in smb.conf and roaming profiles, smbd panics when the share "%U" is not listed in smb.conf. I had some users for which i forgot to enter the accompanying share in smb.conf. When such a user logged in or logged off, smbd paniced with signal 11. While on logging off the profiles where written from the client to the server, all profile entries except the directories got lost. As you can imagine, this caused heavy problems when the user "roamed". Unfortunately the error is not reproduceable at _any_ time. Means, sometimes there is no "panic" nor the profiles got lost. But after appling the "workaround" (see end of mail) there were no more "panics" or lost profiles over days. The "panic" only occured to users with shares not explicitly listed in the smb.conf. Also this error didn't occur in versions prior to 2.0.6. I think there is a problem with the new code regarding the differences in "logon home" and "logon path" as the panic only passes on logging on and off. The "environment" for "userX" is: all client systems are Windows95a/b/c. unix username = userX windows logon name = userX home directory of userX in /etc/passwd = "/u/samba/pc/userX" the home directory is rwx for userX and owned by userX there were NO share entry [userX] in smb.conf smb.conf looks like: [global] ... dead time = 15 os level = 65 time server = yes domain master = yes local master = yes preferred master = yes wins support = yes security = USER encrypt passwords = yes lock directory = /u/samba/locks server string = "samba %v on %h workgroup = AWORKGROUP ... preserve case = yes short preserve case = yes client code page = 850 domain logons = yes name resolve order = host wins logon script = startup.bat ;--> logon path deals with WinNT only logon path = \\%N\%U\profile ;--> logon home deals with Win9x (net use h: /home) and profiles logon home = \\%N\%U\profile ... [homes] comment = User Home-Directories browsable = no read only = no public = no create mode = 0700 Workaround! After i added: [userX] comment = Home for UserX path = /u/samba/pc/userX valid users = userX public = no writeable = yes printable = no to smb.conf, no more "panics" are encounterd or profiles got lost. If a member of the samba team needs a log (at loglevel=3) please mail to me. Regards Rudolf Kollien email: Rudolf.Kollien@medas.de Rudolf.Kollien@kollien.de ********************************************************* Never trust a operating system you have no sources for ********************************************************* Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. *********************************************************
Luis Luna
2000-Jun-28 20:05 UTC
Urgent Help pls - NT4.0 Term Server and SAMBA - RDR timeouts
Cris, I had the same error even with NT Servers dishing out the files. I fixed that problem by updating the network card drivers and going to the lastest Service Pack (6a). Also go to this page at support.microsoft.com for more info. http://support.microsoft.com/support/kb/articles/Q148/4/26.ASP?LN=EN-US&SD=g n&FR=0 url maybe wrapped, (?`?.??.???`?.??.???`?.??.???`?.??.???) Luis Carlos Luna, Associate AIA Work: 612.332.1234 mailto:luis@btr-architects.com
We use a single NT4 terminal server and SAMBA 2.07 running under Solaris 2.6 on a SUN Classic. As well as several WIn95/98 and NT clients. I have not seen any problems like yours. The only specials in smb.conf are: nt smb support = no dead time = 5 socket options = SO_KEEPALIVE and lpq cache tome = 40 to cope with the several printers we have some on other slow UNIX servers. We have had problems with NT Terminal server but I am sure these have not been SAMBA related. Robert
Hi to everyone: First sorry about my english, I know its realy bad . I am very new configuring SAMBA. The version I am working is samba-2.0.6-7cl and have windows and Linux Conectiva (whit DOS EMU and PTSDOS) clients. I try to migrate an NT4.0 server to SAMBA. My public files and home directories work ok. But when i probe multiple access to a clipper database whit windows and Linux clients simultaneously the database crashes, and the index introduced by the windows clients disappear . I configure this whit Webmin tools but adds some stuff and duplicate the GLOBAL profile in the smb.conf file, so I decide to modify the file in text mode First the files changed by windows clients appear whit users nobody.nobody, and i correct this, now they appear to be created by root.users, when deny guest allow to this share directory. But my principal trouble is that how i can allow simultaneously access to the database whithout crashes (same as windows systems, but I don't come back to NT) My Linux workstations works mounting the share directory and loading DOSEMU whit PTSDOS. The configuration of the share file is: [ventas] path = /ventas comment = CARPETA VENTAS public = no users = jorge,ventas,.... writable = yes create mask = 0777 # to allow all modify the files locking = yes guest ok = no browseable = yes printable = no This system is in test mode but i really hope that works in order to chance to Linux all my systems. Regards Fabrizio Rossel Conectiva Per? fabrizio@conectiva.com.pe -------------- next part -------------- A non-text attachment was scrubbed... Name: fabrizio.vcf Type: text/x-vcard Size: 342 bytes Desc: Card for Fabrizio Rossel Bocanegra Url : http://lists.samba.org/archive/samba/attachments/20000629/a7281b48/fabrizio.vcf