similar to: Samba 3.3.12/3.4.7/3.5.2 on "ancient" server stops responding/dies

Hi all, i have installed samba in RHEL 5 with likewise backend authentication . everything is working but am unable to access samba shares from windows 7 and vista machines . It is simply giving error as "the specified server cannot perform the requested operation" I have spent many days working on this but no luck . please help me :( following is the log . when i try to access samba

Hi, I'm always working on my Samba server, and put the log level to 10 like Volker said in a previous message. But, when i read any log files i see a troubling message : "got a SHUTDOWN message" Every minutes !!! Is this behavior normal ?? Following, the paste of 2 sequences (so 2 minutes of a log file) : [2009/10/04 23:09:45, 10] lib/events.c:105(run_events) Running timed

Hi, I'm facing an issue with at least two Samba servers in production both showing important number of log entries like: smbd[27355]: PANIC: assert failed at smbd/oplock.c(149): exclusive_oplocks_open>=0 Looking at the source code, this panic is triggered when the number of exclusive oplocks for a given file becomes negative. Once triggered for one smbd process, this process can

Running Samba mostly on Redhat 5 with version 3.5.4-0.83 Also failed on Debian 3.5.6 and Solaris with a 3.5 version. Logging details here are from Redhat case. We have a similar problem on all Unix/Linux systems using ADS as the backend authentication for samba shares on Unix/Linux. It was working before today and we didn't change anything. Today, any time we try smbclient or a Windows drive

Dear I have upgraded from 3.5.11 to 3.6.0 in old version, Server was connected to an Active Directory and no problems occurs. when restarting winbind : Sep 19 01:17:34 onesys-samba winbindd[4818]: [2011/09/19 01:17:34.326691, 0] winbindd/winbindd_util.c:635(init_domain_list) Sep 19 01:17:34 onesys-samba winbindd[4818]: Could not fetch our SID - did we join? Sep 19 01:17:34 onesys-samba

Hi. I'm using CentOS 5 with samba3x packages (Samba 3.5.10) and Solaris 10 (Samba 3.5.8) for achieving AD integration. Samba hosts are added as domain members. Now, I've tried to add CentOS 6, which also uses 3.5.10, but have encountered a problem -> users cannot authenticate for some reason. Configurations are pretty much the same across the board, and they look like this: #

Greetings, Before I get to far digging I was wondering if anyone else was seeing problems with Samba 3.2 on Solaris 10 (Sparc.) I built Samba with gcc 3.4.3. Clients are denied access to server resources and I'm seeing the following in the logs: [2008/07/02 15:47:38, 3] smbd/password.c:register_existing_vuid(326) register_existing_vuid: UNIX uid 10000 is UNIX user CSUNET\1001362,

Hello! I see where this came up on the list a few months and never really ws resolved. Someone resolved it by linking libnss_winbind ... But that's not my problem... I'm getting " Failed to join domain: failed to set machine spn: Operations error" when I do a net ads join. I've used this user account (me) to join many Samba 3.5.6 servers to the domain. Config file and

I have some trouble with a samba 3.5.8 server when setting directory attributes. On a windows XP I execute a small peace of code that calls 'SetFileAttributes' for the directory 'test-dir' located on the samba server. Using log level 10 I find this: [2011/05/26 15:27:02.144060, 3] smbd/process.c:1298 (switch_message) switch message SMBtrans2 (pid 28903) conn 0x7f5e35f0dbb0

Hello, I'm testing windows 7 with samba 3.4.7 and I'm using PrintUIEntry to connect the printers. With some of those printers the connection fails (client side) with error 0x000003e6. The strange thing is that: 1) trying the same connection against samba 3.0.11 works (alas, no domain functionality with that old version) and 2) two of the failing printers share the same driver with

Hello, last friday I switched my users from an old server running 2.2.12 to a new one running 3.0.10 (that I've been testing myself and with smbtorture). After a while I had to switch back to the old server because some users were having serious problems. This is one of the logs (the others are very similar): [2005/03/04 12:25:05, 0] tdb/tdbutil.c:tdb_log(725)

Due to the problems I experienced switching my users to a new server, I'd like now to migrate only some workstations at a time. Since they all have to work on the same files, I though of nfs mounting the new server disk on the old one, so the old server would be sharing the nfs mounted directory while the new one would be sharing the same directory but from its own disk. Is this an

Ok, I finally deployed samba 3.5.2 (upgrading from 3.0.11) on the real server after testing for a while in virtualbox. There's a strange problem with printing: sometimes an application gives an error printing (of course the error message is meaningless, this is windows after all) and/or the job gets lost in transit. After that stopping and restarting the local print spool service solves the

Is there a way to take users samba passwords from an old 2.x Samba server, and insert them into a new 3.x Samba server that using an LDAP backend? The new server is already populated with all users and groups in LDAP and is currently on a test network. All that is needed is the users samba passwords from the old server that is using the smbpasswd file. Thanks -- Matt Lung Midwest Tool &

When you follow chapter 2 of SBE ( http://www.samba.org/samba/docs/man/Samba3-ByExample/small.html ) you get a working PDC. However there is one problem: if you create a document in a shared folder only the owner can edit this document. Others in the same group can't edit the document and get a 'permission denied' error. Permission are arranged with groups, new files get the permission

Maybe there's a trivial solution to this, but it's confused the hell out of me. I'm trying to upload the latest Windows XP PCL6 driver for our Laserjet 4250TN to my Samba 3.0.11 server. It works, and uploads the driver files, but then at the end it produces an error on the XP client "the operation could not be completed". The logs on the samba server state:

Hello there. I have a network with 35 new Windows 7 (64 bit) PCs that should connect to printers via a cups/samba server. I want them to use their own windows drivers, and I want these to be installed automatically from print$ when they first connect. I'm trying to install the drivers from the clients as described here:

Hello, after our harwarechrash we had to change the serversystem to another hardware. I copied all necessary samba files (I hope I did) to the new hardware and restarted Samba. Now when I try to log on the domain the client ist no longer trusted by the domain. When I add the client to the domain to solve these problem, I get an new profile after login. And this is my problem. All our

Dear all, I have samba 3.2.15 PDC running with an openldap backend and smbd4wins on the same host. There is also a BDC the same as my PDC. After I did an update to 3.3.12 on my BDC this worked on the fly without problems. Then I went on doing the same update on my PDC with the result of chaos. No user was able to logon anymore , when I did a smbclient -L mypdc -N it was extremely slow, and my

My Configuration, On my PDC: Samba version 3.2.15 /LDAP-Master (slurpd)/SMBD4wins <-- version 3.3.12 not working. Downgrade again On my BDC: Samba version 3.3.12 /LDAP-Slave <-- version 3.3.12 working [global] on PDC [global] workgroup = tuepdc.local bind interfaces only = true interfaces = 192.168.135.143/24 127.0.0.0/8 socket address = 192.168.135.255 profile acls = no hosts allow