similar to: maximum amount of data in a SMB read response packet

Hi, I have a retro LAN running things like Sun SPARCclassics, Ultra1s, Win98 and WinXP. I decided to standardize most of the Sun boxes on the latest versions of OpenBSD that support their architectures (5.9 for Sun4c & Sun4m, 7.4 for Sun4u). I have a Debian 7 server with RAIDs to store all the packages, configs, games, etc. I like to use Samba to transfer the files back and forth between the

Hello, I have a performance problem when I don't connect using root and/or a user in the "admin users". Configuration: Samba 3.5.11 running on SLES11SP1. The share exported is on a GPFS filesystem and the GPFS vfs object is loaded(not loading it doesn't change the described behaviour) clients: Windows 7 and Windows 2008R2 all at latest update level. [testshare] comment

Hello, I seem to be having this exact same issue with several applications that are loading images into a sequence. If I use share level security, force guest only or set a user as admin user, I get good speed at around 50MB/s. If set in any other way, samba doesn't negotiate anything higher than a 4K transfer and the app slows down to about 5MB/s. All clients are Windows 7. This is also a

hi all, in case someone else runs into it, it is the opfed-scripts rpm that has a postinstall and postuninstall script that changes the yum.conf (bad, mellanox, bad) for a pure/regular uninstall it works fine, but to swap ibutils from mlnxofed to ib stack from os, yum obviously doesn't know that the exclude will be removed. i've seen worse in vendor-provided rpms, but i guess it caught

hi akemi, i also forgot about this thread. we already tested the latest kmod last week and it indeed fixes the issue. still no clue how to report issues to centos team to doublecheck packaging mishaps... stijn On 02/06/2018 12:49 AM, Akemi Yagi wrote: > On Tue, Jan 2, 2018 at 10:10 AM, Akemi Yagi <toracat at elrepo.org> wrote: >> >> On Thu, Dec 7, 2017 at 6:23 AM, Stijn De

I have a need to setup the recycle vfs object on our server. On my test server, I have all of the shares on a single drive and have put the following into each share: vfs_objects = recycle recycle:repository = [Actual Path and Partition that the share is located] recycle:directory_mode = 770 recycle:keeptree = Yes recycle:touch_mtime = Yes recycle:versions = Yes It works like a charm. All

Good point Stijn, I am sorry to post without subject and such it must be the early morning. The relevant entries in my rules file: ACCEPT net fw tcp 25 ACCEPT net fw tcp 80 ACCEPT net fw tcp 22 ACCEPT net fw tcp 21 ACCEPT net fw udp 21 REJECT loc

Is the issue below addressed in 3.0.25b? (no freebsd port available yet so I'm still at 3.0.25a) I can't see anything specifically about this in the release notes. I just want to add that I've also seen this behaviour on a windows xp x64 client. It's a pretty serious problem.. so I'm also thinking I may have to revert to an earlier version if it doesn't look like a

Hello, everyone, I'm seeing some inconsistent behavior across SMB clients when configuring shares using the "msdfs proxy" parameter, and was hoping to get some advice from the community on this. My issue is that various SMB clients seem to behave differently when this parameter is pointed as a path that includes a sub-folder under the root share. So, given the following share

Dear Rexperts, First of all let me say that R is a wonderful and useful piece of software. The only thing is that sometimes it takes me a long time to find out how something can be done, especially when aiming to write compact (and efficient) code. For instance, I have the following function (very rudimentary) which takes a (very specific) data frame as input and for certain subsets

Hello all, Got samba with AD integration and extended ACL up and running. Here is what I am trying to do. share1 in smb.conf: [share1] comment = share1 path = /mnt/data/share1 public = no writable = yes printable = no valid users = @DOMAIN+group1 user1 and user2 are members of group1 user3 is not user1 creates

We restored to 3.0.23d after update to 3.0.25a because of strange dfs behavior. the detailed situation: on msdfs root server 'samba' ls -lR dfsroot/: drwxr-xr-x appl1 dfsroot/appl1 lrwxrwxrwx share1 -> msdfs:server1\share1 [dfs] comment = "SaMBa DFS root" path = /path.../dfsroot # next line does not work prior 3.0.25 !!! # hide unreadable = Yes

On Thu, Jan 05, 2023 at 01:28:55PM -0500, Nick Couchman via samba wrote: >Hello, everyone, >I'm seeing some inconsistent behavior across SMB clients when >configuring shares using the "msdfs proxy" parameter, and was hoping >to get some advice from the community on this. My issue is that >various SMB clients seem to behave differently when this parameter is >pointed

Hello Jeremy, I think you missed a "/" in: mount --bind /share1/DVR /medium/DVR mount --bind /share1/Audio /medium/Audio mount --bind /share2/Video /medium/Video mount --bind /share2/Backups /medium/Backups BR, Matt On Thu, Feb 13, 2020 at 5:15 PM Jeremy Allison via samba < samba at lists.samba.org> wrote: > On Thu, Feb 13, 2020 at 04:45:16PM -0500, Hal Vaughan via samba

Hello, I have a problem when uploading file to samba server when the share's volume is under lvm snapshot. I always got "The specified network name is no longer available", this happens when uploading large files like 500MB and the volume has a lvm snapshot(even 1 snapshot). If there are no snapshots, everything is ok, I can transfer large files without problem. my client is

On Tue, Jan 2, 2018 at 10:10 AM, Akemi Yagi <toracat at elrepo.org> wrote: > > On Thu, Dec 7, 2017 at 6:23 AM, Stijn De Weirdt <stijn.deweirdt at ugent.be> wrote: >> latest kmod update 20-15.el7_4.6 is broken on our systems, while >> previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue). >> >> the issue is with modules from mellanox

Hi guys, I haven't seen any replies to this, but im seeing the exact same thing with Fedora 7 samba (with all the currently available patches). using winbind into a an ADS realm. My samba is 3.0.25b. Clients are XP, 2003 r2 SE and EE 32bit, 2003 r2 SE 64 bit. All work ok for a while, then suddenly start doing the same as below. I.e., when mapped it looks fine, then some time in the future

List, I'm having trouble accessing shares, and I'm getting conflicting indications on whether I've successfully joined the domain with my PC and Samba server (which may bear on the share problem). I really could use some help; I've not been able to recognize anything in the docs or via Google that helps. I'm running SUSE 9.3 and Samba 3.0.21a, and I'm trying to

I encountered strange behaviour of "msdfs" when using together with "netbios aliases". E.g I have in smb.conf: [global] netbios name = server netbios aliases = server-oldname .... host msdfs = Yes [share1] path = /var/samba/share1 [share2] msdfs root = Yes msdfs proxy = \penguin\share2 .... From a windows (XP) machine I can now see: \\server\share1 and

I am having trouble with the %S Macro being expanded to an unexpected value. We have a section of disk where each directory under that directory is to be it's own share. This looks like: /export/ /export/share1 /export/share2 . . /export/shareN Rather than listing each share uniquely in the smb.conf, we put this in the global section: default service = export along with all of our