Tuning/Viewing Log Settings/Entries - CIFS Permissions Issue

Status
Not open for further replies.

Alex Kirk

Cadet
Joined
Nov 16, 2015
Messages
6
Just recently got myself set up on FreeNAS-9.3-STABLE-201511040813, and have used the basic configs to set up a new volume across 3 NAS-grade hard drives and a CIFS share from that volume (with "Allow Guest Access" checked, since I want to make it easy inside the network). I'm having problems seeing the CIFS share on a Mac (I can connect directly to it no problem at all), and writing to it from Win 7 and a Debian-based Linux system.

I've run Samba before on OpenBSD and so I figured I'd just go ahead and turn up verbosity on the logs, read my messages, and figure out what I'd done wrong to get things going from there. That said, I've been all through both the GUI and the manual, and I see virtually no mention of logging. Just to make it extra complex to follow, things seem to be getting split between /var/log/debug.log, /var/log/messages, /var/log/samba4/log.smbd, etc.

Is there a best practice guide to logging that someone could point me to?

Meanwhile, given the following global and then share-specific smb4.conf entries, any thoughts on why my Windows and Linux clients can't write to my "Enterprise" share, while my Mac client can?

Code:
[global]
  server max protocol = SMB2
  encrypt passwords = yes
  dns proxy = no
  strict locking = no
  oplocks = yes
  deadtime = 15
  max log size = 51200
  max open files = 941501
  load printers = no
  printing = bsd
  printcap name = /dev/null
  disable spoolss = yes
  getwd cache = yes
  guest account = nobody
  map to guest = Bad User
  obey pam restrictions = yes
  directory name cache size = 0
  kernel change notify = no
  panic action = /usr/local/libexec/samba/samba-backtrace
  nsupdate command = /usr/local/bin/samba-nsupdate -g
  server string = FreeNAS Server
  ea support = yes
  store dos attributes = yes
  lm announce = yes
  hostname lookups = yes
  time server = yes
  acl allow execute always = true
  acl check permissions = true
  dos filemode = yes
  multicast dns register = yes
  domain logons = no
  local master = yes
  idmap config *: backend = tdb
  idmap config *: range = 90000001-100000000
  server role = standalone
  netbios name = FREENAS
  workgroup = WORKGROUP
  security = user
  pid directory = /var/run/samba
  create mask = 0666
  directory mask = 0777
  client ntlmv2 auth = yes
  dos charset = CP437
  unix charset = UTF-8
  log level = 1

[Enterprise]
  path = /mnt/Enterprise
  printable = no
  veto files = /.snapshot/.windows/.mac/.zfs/
  writeable = yes
  browseable = yes
  vfs objects = zfs_space zfsacl aio_pthread streams_xattr
  hide dot files = yes
  guest ok = yes
  nfs4:mode = special
  nfs4:acedup = merge
  nfs4:chown = true
  zfsacl:acesort = dontcare
 

Alex Kirk

Cadet
Joined
Nov 16, 2015
Messages
6
OK, figured out how to crank up the logging for CIFS - and I suppose editing the service makes sense. Still, I feel like a note on the subject is warranted in the documentation, and that it might even be good to have a page for logging in the interface, even if it did just redirect you around as necessary.

What's the procedure for proposing an update to the docs? I'm happy to write things up myself (I've written FAQs and the like for other open source projects in the past), but would obviously like to follow process so it has a chance of getting in.

Once logging was turned on I see that the issue stems from guest usernames of "guest" vs "nobody". Guess I'll see how to get Windows to connect as the former instead of the latter.
 
Status
Not open for further replies.
Top