search for: smb_neg

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 lightning fast! (well, for sufficiently slow lightning... ;-) ) Thanks again. David On 6/11...

...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 = yes usershare allow g...

Hi, I'm very happy to see the work done on vfs_fruit. This has been a pain-point for our users for a long time now, and it seems like we're finally close to a solution. Thanks, Ralph! That said, we're still having some issues. I've installed Samba 4.2.2 from the SerNet Ubuntu package repo on a test VM running Xubuntu 14.04.2 LTS. I've set up Samba with a simple share

.... 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...