similar to: Settings on user share

The shared mem size option is set to 102400 by default and change is discouraged: The man page (1.9.18p10) says: This parameter is only useful when Samba has been compiled with FAST_SHARE_MODES. It specifies the size of the shared memory (in bytes) to use between smbd processes. You should never change this parameter unless you have studied the source and know what you are doing.

Here is a re-post of PR#19365 which was originally post back in Aug.. If anyone can help I am still looking for a solution ! Forwarded message: > > Hi Jeremy ! > > Don't know if you remember this one but it is definetely turning > my hair grey :) I have left your original reply at the end. > > I finally have a configuration which works with Bentley's >

Nguyen Cao Dat asked about this: ERROR! Out of file structures - perhaps increase MAX_OPEN_FILES? As it happens I have started getting them too - on a PC Application server - the cause seems to be lots of files needed to be open to run applications - Lotus apps seems to be a particular culprit, but experiments indicate that even opening help on Microsoft Word opens 13 files! MAX_OPEN_FILES

Having received no responses, I will try again. I can't seem to get preexec to work as stated in my earlier email given below. Any help would be most appreciated. I am using samba-2.0.3-19990228 in combination with RH 5.2 with kernel-2.2.1. Thanks, Carey ---------- Forwarded message ---------- Date: Tue, 13 Apr 1999 11:35:03 -0500 (CDT) From: Carey F. Cox <carey@tabasco.lamar.edu>

I have been reading John blair's book "SAMBA:Intergrating UNIX and Windows". There is a reference in the book to Authenticationoptions on page 66 for LAN Encripyted Password Support. I found these lines a version 1.9.16p11 # This is for SMB encrypted (lanman) passwords. # you may wish to add -DREPLACE_GETPASS if your getpass() is limited # to 8 chars # DES_BASE=/usr/local/libdes #

> I have been reading John blair's book "SAMBA:Intergrating UNIX and > Windows". There is a reference in the book to Authenticationoptions > on page 66 for LAN Encripyted Password Support. I found these > lines a version 1.9.16p11 Judy, external librariues are no longer needed to get the LanMan an NT hashed passowrds. Obtain the latest version of samba ( 1.9.18p10

>> From: "Mark Hazen" <mhazen@franklin.uga.edu> >> Subject: Re: Network Neighborhood comment fields and Samba >> >>Have you tried commenting that string out in your smb.conf file, and letting >>the string be set first in the individual configs? That'd be my first >>suggestion. I have tried that, and that just forced the default comment of:

I have been setting up a PDC with one XP client. After about three weeks of smb.conf changes, I understand/like my settings, and it *was* working great. (I've read a zillion times both O'Reilly "Using Samba" books (1st and 2nd editions), and John Blair's (Samba Team) "Samba Integrating UNIX and Windows" book.) This morning I decided to rebuld the XP client since

Hi, We're running Samba version 1.9.16p2 under Solaris 2.5.1 (w HW update 11/97). Our PCs run Windows95 with Network Neighborhood and a few have been upgraded to Windows98. I am currently looking at upgrading to Samba 1.9.18p10. On Fri., 12/4 one of our users reported when she selecting Entire Network she received the error "Unable to browse the network. The specified computer

I have two Caldera Linux Intel boxes running as Samba servers (1.9.18p8) using an NT server (SP3) for user authentication and have no problems. I cannot get a new box to work this way. The new machine is a DEC Alpha running Red Hat 5.1 with Samba 1.9.18p5 (pre-installed). The smb.conf file contains (among other things): encrypt passwords = yes security = server password server = XYZ Using the

Samba, We've been using samba-1.9.16p9 here for a long time, with a tremendous record of success. I've recently compiled and installed 2.0.0, but am having problems. Only about half my users can login now, and who's singled out is *seemingly* random. This is on a DEC Unix 3.2 (osf/1) machine. Threw the old binaries back on, and everyone's happy again. What can I do to get

Folks, A remote admin is trying to add a contractor account to our NT domain with limited rights. Unfortunately, everytime the contractor account is removed from the DomainUsers group, the contractor encounters the following: \\nt-nfs-md\IPC$ and the infamous invalid password. Once the user is re-added to the DomainUsers group, they can access the share fine. My question is what permissions

Hi. So I'm now on the next section of my samba by example book. For the life of me I just couldn't get it to work. That is until I looked into what the %S and %U variables actually meant. In the book it says to put something like the following in your smb.conf: [files] comment = Work area files path = /data/%U valid users = %S read only = No However, from what I understand, %S

Hi All, First post so I hope this is pitched right. I've been successfully using 3.6 as an AD authenticated (winbind) file server for a while, and decided to have a poke around with 4 (I'd read somewhere that someone had got zfs filesystems to work with full windows acls with samba 4). I've got as far as compiling 4.1.6 and setting up a similar share. Server role = member server,

Hi all, I am referring to the official wiki here: https://wiki.samba.org/index.php/Setting_up_a_home_share#Setting_up_the_share_and_filesystem_permissions I was struggling around for many hours before I have found out what caused my issue. Well, I have created the [home] share exactly as epxlained on the How-To, in detail: I am creating on the linux prompt at the member server the directory with

I am trying to solve what I perceive as undesirable behavior of my Samba server. Please understand I am not claiming this is a bug in Samba. It is simply different from the behavior I want, and I'm asking for help in modifying the behavior. My Samba server is version 3.5.4 (release 68.el6) and runs under CentOS 6.0 (x86_64). I happen to use Active Directory (AD) to authenticate, but am not

Hi all, I have noticed that if you create a share to path lets say \\dir1\dir2\dir3 And a user lets say u1 has full control on dir3 BUT no control at all on dir2 then user u1 cannot access the share. Is it right? We have a situation with clients who typically do the following: Create a share to the root of the file system and give only to administrator full control on for the root path

What name does Windows XP Pro use when it accesses a shared folder on a Freebsd/SAMBA file server? Is it the XP's local original account name, a changed account name, the computer name or something else? I'm using an Intel Network Attached Storage appliance that runs FreeBSD with SAMBA. For more info, see http://www.intel.com/pressroom/archive/releases/ib072099.htm and

Hello, I've setup a samba PDC (3.0.31) and I am using Windows Vista clients. Logging on works fine using roaming profiles and folder redirections. I am also able to write to shares, etc. Now I am trying to get the advanced permissions on files to work. So on my share: [share] comment = Shared directories path = /samba/share read only = No guest ok = Yes With the following user rights

All, I'm new to Samba so this may be a very easy fix, but I've not been able to find it anywhere online or in the /Samba-3 By Example/ book. I'm currently testing Samba 3.0.23c with an OpenLDAP v3 backend on CentOS 5. I am able to get OpenLDAP installed and running for authentication and can get Samba installed and configured well enough to request and accept a LDAP user