search for: nsmb

...ting or browsing samba shares. I have a FreeBSD 4.6.2 running samba, and a share on that called public. when I try to mount that share it asks for password, and then gives an error: ex. libra# mount_smbfs //maxi@samba/public /mnt Password: mount_smbfs: can't get handle to requester (no /dev/nsmb* device) libra# I can list the shares with smbclient, no errors at all. I can not login to the samba like this: libra# smbutil login //maxi@samba Password: smbutil: can't get handle to requester (no /dev/nsmb* device) smbutil: can't get handle to requester (no /dev/nsmb* device) smbutil...

Thanks to Will Saxon I'm finally able to mount Samba shares on my 5.1-R box using the command mount_smbfs -I 129.197.36.34 -W acct01 //bfosdick@129.197.36.34/net-11 /sp/net-11 which then prompts me for my password. So now the question is...how do I put this in /etc/fstab? What do I do about the password?

I can't seem to be able to mount any windows shares all I get is this error smbfs: can't get handle to requester (no /dev/nsmb* device) a quick search on google leads me to believe it is broken, can anyone help me get this fixed?

Hi folks, I have an issue at a weird confluence of macOS Mojave's "nsmb" client, Adobe Lightroom and Photoshop, and Samba 4.7.6-Ubuntu. Since I don't have much control over Apple or Adobe software, I'm hoping there's some smb.conf magic (or other sage advice) that might help me out of this jam. For reference, Samba is configured for SMB2-only access (i...

...streams are disabled on the share, at least illustrator throws error -5000 and states that it was not able to save a preview of the image. so with catia, fruit and streams enabled this might be the point where illustrator crashes the smbfs. but i was able to avoid a crash when editing the /etc/nsmb.conf on my mac with following content: [global] file_ids_off=yes whatever that means (?) but it is stable now regarding vfs_depot: with above option enabled on my mac: illustrator throws error -43, preview could not be saved... (no crash) without above option: the same error -43 (no crash) err...

I disabled client signing from the client side, via OS X's global nsmb.conf file: https://discussions.apple.com/message/30282470#30282470 The performance was back to over 600 MB/s, as compared to 60 MB/s with signing. It just seems a bit weird to me that Apple, in response to the Badlock bug, would have changed the OS X client default to something with such drastic...

Hello! I have a quite large installation that currently supports OSX clients by forcing them to SMB1 with no streams (via the "nsmb.conf") file. This setup forces the OSX clients to generate their own ._[FILENAME] appledouble files for files with resource forks (like adobe documents). We recently discovered the fine work that's been done on vfs_fruit and wanted to see it it could help us. We have setup a test bed wi...

Hi Ralph, Ok, the problem was a PEBKAC issue. :-) Sorry to waste your time. In troubleshooting this earlier, I'd created the file "nsmb.conf" in my user Library directory with the following contents: [default] smb_neg=smb1_only In earlier troubleshooting, some folks suggested that might help the situation. It didn't, and I'd forgotten to remove it. I've removed it now, and now my Yosemite connections are lightn...

...dled, I tried the same copy operation from a Windows VM and it worked great. Very little network traffic, direct disk-to-disk copy on the server. So the server itself is configured correctly, the backing filesystem (ZFS) is configured correctly, etc. The problem must lie between vfs_fruit and macOS nsmb. I've upgraded Samba to 4.17.5 and tried toggling various other vfs_fruit options to see if one of them is conflicting with the copyfile option. No quick fixes, I'm afraid. Hopefully somewhere here can point me in the right direction?or at least confirm this behavior on Samba 4.16 or newer...

Hello, I've got a FreeBSD 5.5 box running Samba 3.0.21 and every-time I try to do a "mount -t smbfs -o username=username,password=password // server/share /mnt/folder" I get the error "smbfs: -o username=: option not supported". I've google'd this with no luck... any help in the right direction is appreciated. --- Jason Zondor

...me copy operation from a Windows VM and it worked > great. Very little network traffic, direct disk-to-disk copy on the server. > So the server itself is configured correctly, the backing filesystem (ZFS) > is configured correctly, etc. The problem must lie between vfs_fruit and > macOS nsmb. > > I've upgraded Samba to 4.17.5 and tried toggling various other vfs_fruit > options to see if one of them is conflicting with the copyfile option. No > quick fixes, I'm afraid. Hopefully somewhere here can point me in the right > direction?or at least confirm this behavio...

Hello, I just wanted to check in on this list and see what folks know about the new severe performance problems with OS X 10.11.5. There's a comment on Reddit claiming that 10.11.5 is requiring SMB signing, but I haven't found documentation on that. I myself saw performance on my 10 GbE go from 800 MB/s on 10.11.4 to 60 MB/s on 10.11.5. My NAS is running Samba 4.3.6 on FreeNAS, which is

samba-4.2.9-0.fc22.x86_64 with the configuration below a user from a up-to-date Apple client copies a folder with some images (from the share itself) to a different subfolder * he sees the folder * it appears empty in finder - in fact it is not empty * he can not delete it * he can rename it * a different user from a Apple clients sees the files * remove the "vfs objects" line and

...16 at 12:32 AM, Ralph Boehme <slow at samba.org> wrote: > On Fri, Apr 22, 2016 at 03:18:31PM -0700, Scott Call wrote: > > Hello! > > > > I have a quite large installation that currently supports OSX clients by > > forcing them to SMB1 with no streams (via the "nsmb.conf") file. > > > > This setup forces the OSX clients to generate their own ._[FILENAME] > > appledouble files for files with resource forks (like adobe documents). > > > > We recently discovered the fine work that's been done on vfs_fruit and > > wante...

...r was never observed before, with nearly identical share structure, when AFP was used. Maybe it's worth to note that normal users are not allowed to write to the first level of a share. Relevant config-files are written down below. Kind regards, Andreas Huppert Client configuration: #/etc/nsmb.conf [default] smb_neg=smb2_only Server configuration: #/etc/samba/smb.conf workgroup = WORKGROUP server string = %h server (Samba, Ubuntu) dns proxy = no log file = /var/log/samba/samba.log max log size = 10000 syslog = 10 syslog only = yes log level = all:1 ldap ssl = start tls disable netbios...

...ce3/smbd/service.c:1050(close_cnum) 10.11.12.13 (ipv4:10.11.23.13:57939) closed connection to service data The Mac clients don't all do this at the same time. It happens completely irregularly and not at fixed intervals. I've tried all the various possibilities in a Mac client's /etc/nsmb.conf to no avail: [default] protocol_vers_map=4 signing_required=no I've set the most power aggressive energy settings, and even used caffeinate <https://github.com/newmarcel/KeepingYouAwake> to make sure the computer was always awake. I've tested a brand new NIC on the server, u...

...follow symlinks = no > # vfs objects = catia fruit streams_xattr > oplocks = no > level2 oplocks = no - try removing options one by one - which OS X version? There's a serious bug in versions up to 10.10 (possibly fixed in 10.11) that can be worked around by setting $ cat /etc/nsmb.conf [default] file_ids_off=yes ...on the clients. Cheerio! -slow

On Fri, Apr 22, 2016 at 03:18:31PM -0700, Scott Call wrote: > Hello! > > I have a quite large installation that currently supports OSX clients by > forcing them to SMB1 with no streams (via the "nsmb.conf") file. > > This setup forces the OSX clients to generate their own ._[FILENAME] > appledouble files for files with resource forks (like adobe documents). > > We recently discovered the fine work that's been done on vfs_fruit and > wanted to see it it could help us...

On Wed, Jun 01, 2016 at 07:44:26PM +0000, Seth Goldin wrote: > I disabled client signing from the client side, via OS X's global nsmb.conf > file: https://discussions.apple.com/message/30282470#30282470 > > The performance was back to over 600 MB/s, as compared to 60 MB/s with > signing. > > It just seems a bit weird to me that Apple, in response to the Badlock bug, > would have changed the OS X client defa...

...t read and write speeds to SMB-mounted network shares are very poor if packet signing is required (the default on OS X since 10.11.something). Suggestions abound on the Internet that you can restore good throughput by disabling packet signing on the Mac. You do that by creating or editing the /etc/nsmb.conf file and adding: [default] require_signing=no Indeed, customers of my company's products have confirmed that disabling packet signing "makes Samba great again". The problem is, disabling packet signing seems to be an all or nothing proposition. If you disable it on OS X, ap...