similar to: SerNet Samba Updates

Hi Volker, It would be useful if your 3.3.9 build (currently in recent) included the /var/spool/samba directory - it just took me a while to figure out why Samba printing wasn't working on a new EL5 server ;-) Moray. "To err is human.? To purr, feline"

In samba3-3.3.9-40.el4 and samba3-3.4.7-42.el5 there are 3 .tdb files /var/lib/samba/locking.tdb /var/lib/samba/wins.tdb /var/lib/samba/mutex.tdb which are not documented in http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/install.html# tdbdocs. Are they persistent or temporary? Moray. "To err is human.? To purr, feline"

Hi Moray, ? Thanks for your answer. It could help but only partially. ? The script name logon%u.cmd was a bad example. Actually, a user can log on from WinXP , or Win 7 workstations, and I'like to run different logon scripts depending on the OS . So having logon script = logon%a.cmd in the smb.conf generally works thanks to variable substitution. ? But for user accounts that have been

CentOS 6.4 appears to have been shipped with a broken Samba 3.6. The new NMBDSOCKETDIR option defaults to /var/nmbd, which of course is an invalid directory and should not be created[1]. While hopefully they can fix it with an option to their configure script at build time, could Samba itself provide better defaults so that new options like this don't take OS developers by surprise? Moray.

After upgrading from samba3-3.3.10-40.el5.i386.rpm to samba3-3.4.7-42.el5.i386.rpm, I'm seeing a lot of [2010/05/05 11:06:42, 1] smbd/vfs.c:932(check_reduced_name) reduce_name: couldn't get realpath for addrbook/CVS [2010/05/05 11:06:42, 1] smbd/vfs.c:932(check_reduced_name) reduce_name: couldn't get realpath for beta/CVS [2010/05/05 11:06:42, 1]

Is it possible to access the described class in a shared behavior? I''m trying to do something like this: describe "Siberian feline", :shared => true do described_class_instance_as :feline, :name => "fluffy", :breed => "Siberian" # or maybe before(:all) do @feline = described_class.new(:name => "fluffy", :breed =>

Is "smbclient -M" supposed to work to a Windows 7 machine? Using samba3-3.4.9-42.el5 I get: # echo "Hello world" | smbclient -NM PC167 Connection to PC167 failed. Error NT_STATUS_BAD_NETWORK_NAME The name resolves correctly, and the command works to an XP client with Messenger service enabled. Win 7 has its own "MSG.EXE" program for that sort of thing, which

Hello list, I have been using "smb ports = 445" to get rid of the dreaded "Transport endpoint is not connected" error, and it seemed to be working fine for Windows XP, on SerNet's samba3-3.3.9-40.el5 build. We recently introduced Windows 7 to our network - and the "Transport endpoint" errors are back: Nov 25 17:21:41 experimental smbd[13018]: [2009/11/25

A password set from Windows XP requires a certain level of complexity: by default, Windows will not allow a password of "aaaaaa", but it will allow "Johnny1". I've been experimenting with a check password script so that both would be rejected. That worked. However, when I removed the check password script line from smb.conf and restarted Samba, Windows did not return to

Ivan H Dichev wrote: I've found a threat in Samba forum, about an issues with Win7 and Samba observed by Alex Ferrara. <http://lists.samba.org/archive/samba/2009-December/152353.html> http://lists.samba.org/archive/samba/2009-December/152353.html As I understood, you had similar errors while ago.. Did you realized what was the problem ? Hi Ivan, There appear to be (at

Hi there, I'm wondering if there any patch or recent developement that would allow to include a directory rather than a file in smb.conf Something like includedir = /etc/samba/shares.d/ instead of include = /etc/samba/shares.conf Thanks for your help Santiago ------------------------- *Santiago DIEZ* *Director* *+33 6 37 90 81 98* -------------------------

OS: Debian squeeze Samba: 3.5.6 # testparm --section-name=global -s 2>&1|grep ALIX returns nothing # grep ALIX /etc/samba/smb.conf netbios name = ALIX works -- Regards Harry Jede

I'm not sure that this is the right place to ask about this, but one of my users is having a problem with her files,specifically excel files which she is editing with openoffice. I suspect that she is closing down her PC without logging out or something and so appears to be still logged in. She is using Vista and the server is a Debian Lenny box. Whenever she tries to access the files on

Hi, I've been through a long discussion of this on the CentOS list, where people are quite helpful, yet we've gotten nowhere with it. With smbd Version 3.0.33-3.14.el5 on two different CentOS 5.4 64-bit boxes, "/etc/init.d/smb start" reports OK for both nmbd and smbd, but an instant later smbd stops running, with no errors reported - just fails, no matter what logging level is

Hi all! Is anybody here using rsyslog? I am looking for the right solution how to use rsyslog in CentOS 5 as the default logging daemon. We use it because of filtering using regular expressions. I switched from sysklogd to rsyslog simply using chkconfig --del syslog chkconfig --add rsyslog chkconfig rsyslog on service syslog stop service rsyslog start but this seems not to be

Hi, I'm trying to join a Windows 7 client to a samba domain.? We're running samba 3.3.9 from SerNet.? I've changed the registry settings on the Win7 client per the wiki page (http://wiki.samba.org/index.php/Windows7). Unfortunately, I'm still getting: The following error occurred attempting to join the domain because the following error has occurred: The specified domain either

-----BEGIN PGP SIGNED MESSAGE----- Friday, April 11, 1997 The Litterbox Sean B. Hamor <hamors@litterbox.org> LINUX IP MASQUERADE Synopsis: A problem exists in IP

I have a Debian machine running Unstable acting as a samba server. The server was installed a few days ago after a reinstall of the OS. The older installation's samba configs were backed up and restored after installation. The Samba shares are accessible if I access them from a Windows 7 client. The shares, however, cannot be accessed from a Debian client (newly installed amd64 Testing).

Hi, I'm using Samba (currently samba-3.0.10-1.fc3) in an intranet environment under Fedora Core 3. I learned that I have to upgrade to Samba 3.3.4 or higher in order to join new Windows 7 clients to the domain. Hints to binaries for this setting would be greatly appreciated. Cheers, Jo

I've been running a samba 3.0.28a PDC with XP clients for a while now. The setup has been working flawlessly. I'm considering upgrading some of the clients to Vista. Are there any known issues to Vista using this version of Samba that I should know about. I all need to do is join the Samba domain and connect to a few network shares.