similar to: Windows 7 Error Logs

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 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"

Hi all, Earlier I emailed the list on some issues I was having with Windows 7, and one of those issues was the trust relationship breaking down after one month. I think I have some more light to shed on this topic. First, some environmental facts I am running Ubuntu Karmic 9.10 with Samba 3.4.0-3ubuntu5.1 I have installed the latest LDAP schema into OpenLDAP 2.4.18-0ubuntu1 I have a working

I'm wondering if anybody's got this work with windows server 2008 R2 RC (build 7100). I'm able to join my samba domain after making all of the posted registry modifications, but I too am getting the "The trust relationship between this workstation and the primary domain failed" message when I try to login. I upgraded to Samba 3.3.6 (from 3.0.33) and joined the machine

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.

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 =>

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]

Thanks to all at SerNet for the timely updates to your Samba packages! Your CentOS rpms do not automatically restart Samba after an update, so "yum update" must be followed by "service smb restart". Is this a deliberate design? Most RHEL/Fedora daemon packages include a "service x condrestart" in the postinstall script, so that yum updates can be completely

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

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 !!! I've Samba 3.3.12 running on AIX, I have a few windows 7 using a shared resource on that server. This is the shared resource definition: [shared_disk] comment = shared_disk path = /home2/nfs-chiappe/shared_disk valid users = user1,user2 write list = @staff read only = No create mask = 0764 This particular Windows 7 Computer is driving

On Wed, 4 Jan 2017 15:58:39 -0300 Andres Tarallo via samba <samba at lists.samba.org> wrote: > Hi !!! > > I've Samba 3.3.12 running on AIX, I have a few windows 7 using a > shared resource on that server. > > This is the shared resource definition: > > [shared_disk] > comment = shared_disk > path = /home2/nfs-chiappe/shared_disk >

This samba is scheduled for upgrade. We've been testing samba 4.3.8 packages (from BULLFreeware) on other AIX. It was not easy the install, even with RPM packages. I hope to do the upgrade soon, but I need to have this particular user working now. What puzzles me is that I have other windows 7 PCs happily working on the same resource. 2017-01-04 16:21 GMT-03:00 Rowland Penny via samba

I am trying to access a samba share from windows 7. The samba version is 3.3.3 on FreeBSD 7.2, The samba daemons are running and I can see the server in my Network Places on the Windows client. When I try to login using the username "spacebizall" and password (the same as the account on the server) I receive an "unknown username or password" error. I installed the registry

Every so often I will see this in my log file: smbd[1034]: [2009/02/02 08:47:21, 0] lib/util_sock.c:get_peer_addr_internal(1607) smbd[1034]: getpeername failed. Error was Transport endpoint is not connected smbd[1034]: read_socket_with_timeout: client 0.0.0.0 read error = Connection reset by peer. smbd[1036]: [2009/02/02 08:47:22, 0] lib/util_sock.c:read_socket_with_timeout(939) smbd[1036]:

Samba 3.2.5 I'm running into an issue when using Vista to access Samba shares. I'm able to connect intermitently and it stays connected for a brief period of time (under 60 seconds) before I get the following error on the Vista box: "Network path was not found" In syslog it shows: [begin] [2008/12/09 11:09:03, 2] auth/auth.c:check_ntlm_password(308) check_ntlm_password:

Every so often I will see this in my log file: Feb 2 08:47:21 int-torino smbd[1034]: [2009/02/02 08:47:21, 0] lib/util_sock.c:get_peer_addr_internal(1607) Feb 2 08:47:21 int-torino smbd[1034]: getpeername failed. Error was Transport endpoint is not connected Feb 2 08:47:21 int-torino smbd[1034]: read_socket_with_timeout: client 0.0.0.0 read error = Connection reset by peer. Feb 2

Hi All, I installed OpenSUSE 11.0, updated samba server to 3.2.4 version. Added two users in linux and samba with user names "test1" and "Test2". (Please note the capital letter in Test2). Created two shares in /srv/samba/shares "test1" and "Test2". The permissions of the shares are as below. drwx------ 2 test1 users 4096 2009-12-11 12:42 test1 drwx------