similar to: FC3 vfs object smb.conf samba 3.0.11

We installed the Samba 3.5.1 rpms for OpenSuSE 10.2 from ftp.sernet.de. The VFS modules seem to be broken. Is this an error in the packaging or do I need to be looking else where. A snippet from the log file follows: <extracted from log> [2010/03/12 19:58:59, 0, pid=28792, effective(0, 0), real(0, 0)] smbd/vfs.c:66(smb_register_vfs) Failed to register vfs module. The module

Hello, i had to upgrade a server from 3.6 to 4.0.10. Now i have a problem had already i solved again. The problem is that a machines program is old and require dos filetime resolution = yes but i does not work with the new 4.0.10 [produktion] path=/home/filestore/produktion browseable = yes writable = yes # create mask = 0777 # directory mask = 0777 #

Hello, been googling this for a while. Read GD's presentation on why printing is such a pain... Anyway, I'm using 3.4.8 on Freebsd 8.1 I've tried a few combinations - best luck is with 3.2.5, but I'd like to move forward a bit. So, I've got the ADS part working pretty good. happy with how that's going. my problem is when I attempt to load printer drivers.

On 1/26/24 02:35, Rowland Penny via samba wrote: > On Thu, 25 Jan 2024 18:45:52 -0800 Peter Carlson via samba > <samba at lists.samba.org> wrote: >> The share mounts and I am a member of the correct groups >> CARLSON\peter at u2gui:~$ cat /etc/fstab //fs.carlson.lab/test /mnt/test >> cifs credentials=/root/smbcreds,multiuser,sec=ntlmssp,_netdev 0 0 > I think

Hello, I'm having a permissions problem I just can't quite figure out. I can not access any directory that is owned by my userid if the permissions are 700. If I change them to 770, with my default group on the directory, then I can access the directory. This was working fine with Fedora 19 for several years, and it broke when I upgraded to Fedora 22, and still broken with F23. my

Hello everyone! After running Samba on several machines for some years, I just came accross a rather strange problem. The short story is that the special user home shares are readable, but not writeable. Here's the long story: The system is a freshly set-up Debian Squeeze, right out of the box. This is the Samba config: -------------------------------- 8<

Hi I need to write a simple VFS module and I have to use C++ instead of C. I took sample files, compiled it and everything does work. However, when I compile it as C++, during the runtime I can see errors in the log: Can't find a vfs module. I am not experienced C or C++ programmer in linux environment, probably I do some silly mistake, but I am really stucked now. I am using Samba version

This problem continues under 3.0.4 on Solaris 8 - attempting to use the "vfs object" parameter in a share prevents access to the share and results in the following in the log files: [2004/05/10 16:04:57, 0] lib/module.c:do_smb_load_module(57) Error trying to resolve symbol 'init_module' in /usr/local/lib/vfs/audit.so: ld.so.1: /usr/local/sbin/smbd: fatal:

Hi, I am running Samba 3.6.19 and making my way through all the Active Directory documentation. I have joined various Linux boxes to a Windows Server 2008 R2 Active Directory domain. Windows 7 users who log on with their domain accounts can mount the correct shares exported by the Linux boxes without having to supply any additional credentials. All working perfectly! However, I have a

Dear All, I have upgrade my samba from 3.0.33 to 3.3.3, that proces are success but I have a problem for samba-vscan. Error : [2012/01/16 10:32:00.074547, 0] smbd/vfs.c:167(vfs_init_custom) error probing vfs module 'vscan-clamav': NT_STATUS_UNSUCCESSFUL [2012/01/16 10:32:00.074559, 0] smbd/vfs.c:309(smbd_vfs_init) smbd_vfs_init: vfs_init_custom failed for vscan-clamav [2012/01/16

Hi, this is my first pos here, please be lenient. My problem shuld be a FAQ and, in fact I found a lot of references googling around, but nothing could really solve my problem, so here I am. I have a Samba server: Very basic wheezy amd64 installation on a small VIRTUAL server (Xen). Only fancy thing is direct access to a couple of RAID1 (mirror) arrays where data is stored. I normally access

I'm seeing a lot of these errors from a Samba 4.13.0 DC running on Debian Buster, the smb.conf is untouched from that which was created via a classic upgrade. =============================== Oct 24 10:25:43 srvr01 samba[26688]: [2020/10/24 10:25:43.886363, 0] ../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler) Oct 24 10:25:43 srvr01 samba[26688]: /usr/local/samba/sbin/samba_dnsupdate:

On 3/3/2016 2:02 PM, Marc Muehlfeld wrote: > It would help if you would provide some information about your system: > - Samba version - smb.conf - "ls -ld" of the directory - etc. Regards, > Marc Hello, version: samba-4.3.4-1.fc23.x86_64 ls -ld: ls -ld /home/blaster drwxrwx--- 76 blaster users 4096 Mar 3 14:15 /home/blaster testparm Load smb config files from

Hi, I'm currently using barplot to generate vertically stacked bar charts. I'd like to be able to use the "asp=1" parameter with barplot(), but doing this causes the y axis to be placed on the far left as shown in the attachment demo.pdf. I could get around this by using the negative values for the line parameter of the axis() function. I'd rather not do this and imagine

Hi, Am 25.03.2019 um 14:12 schrieb Marco Gaiarin via samba: > [...] > Some drivers there's no way to load (for example, some samsung MFP). > Some other load, but you have to do 2-5 try before they work. I did now try many different drivers from different vendors none of them worked thus I think there is something else wrong. I then did some more tests, trying to find anything being

add to each share writeable = yes or read-only = no This Helps! Rauno -----Original Message----- From: werner maes [mailto:werner.maes@cc.kuleuven.ac.be] Sent: 11. mai 2004. a. 16:19 To: samba@samba.org Subject: [Samba] BUG: Vfs audit module & samba 3.0.4 ==> share unaccessible Hello Maybe there's a bug in samba-3.0.4. The following configuration does NO longer work. It did

Samba version : 3.6.3 Filesystem : BTRFS Clients : XP, Win7 Log Level : 5 When we start our samba server everything works fine. After a few days, some of our users are not allowed to connect to shares anymore. When we restart the clients they can connect for a short time and then say have the same problem again. When we restart the server everything works fine for a few days again.

On 24/10/2020 18:05, Sonic wrote: > On Sat, Oct 24, 2020 at 12:46 PM Sonic <sonicsmith at gmail.com> wrote: >>> Who is user '5035' ? >> No clue, all users have a uidNumber in 1000-1999 with all sids ending >> in 2000-2999. > Sorry that was from the AD side, the same client with the > 192.168.7.176 address has a local unix uid of 5035 - I have not yet

Hi, guys. I'm new to all of this and need some help with a problem I've been banging my head against for a while. (Tried troubleshooting, checking logs, and lots of Googling for a few weeks now, but just keep hitting dead ends.) SYMPTOM: Missing file `/usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs.so`, as evidenced by error messages like these: [2018/11/18 07:56:42.551587, 0]

Hello, ? I sent a previous message about this case, but I'm guessing I had too much info.? I'll try to keep it simple. ? I'm looking for ways to further troubleshoot this error: [cstelter at fedorabox system]$ smbclient //fedorabox/sys Enter cstelter's password: Domain=[STELTER] OS=[Unix] Server=[Samba 3.5.6-70.fc14] smb: > dir NT_STATUS_ACCESS_DENIED listing * ???