CIFS Guest Sharing Stopped

[Robbks]

I've been running 9.10 stable for a couple of weeks
I have two pools with separate CIFS shares, but both have the same "Guest Only" access,
Guest is the owner, and Also the group it belong to is Guest.

I powered down my network and moved it to another location, powered it all back up and the Guest shares no longer work.
I have to login with my Root login details.
I've disabled and re-enabled the CIFS service.
I've tried all combinations of Guest access and only guest access to no avail.

I have a media player that will only see guest shares on the network that cannot see it, even if i manually tell it to look at the FreeNAS IP address (Static)

What have I missed?

 

[Mirfster]

1. Are you wanting this to just be "Read-Only" for your Media Players?
2. Can you post a screenshot of the Pool Permissions?
3. Can you post a screenshot of the CIFS Share (Advanced Mode)?

 

[Robbks]

1) no, full access for each device

 

[anodos]

Post contents of /usr/local/etc/smb4.conf

 

[Robbks]

Via Shell?
I'm new to Shell commands.

 

[anodos]

Via Shell?
I'm new to Shell commands.

You have a variety of options. For instance, you can
(1) enable SSH and use SFTP to just download the file and then paste it here.
(2) type cat /usr/local/etc/smb4.conf, copy the output and paste here.
(3) type less /usr/lcoal/etc/sm4.conf, and copy the output and paste here.
(4) type cat /usr/local/etc/smb4.conf > /mnt/<path>/<to>/<share>/smb4.conf. Then open the file on your share and paste output here.

 

[Robbks]

2)

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

 

[anodos]

2)

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

Please post the file in its entirety or PM me a debug file.

 

[Robbks]

3)

[global]
server max protocol = SMB3_11
encrypt passwords = yes
dns proxy = no
strict locking = no
oplocks = yes
deadtime = 15
max log size = 51200
max open files = 232697
logging = file
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
getwd cache = yes
guest account = guest
map to guest = Bad User
obey pam restrictions = no
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

 

[Robbks]

Dp.

 

[Robbks]

If that's not the whole file, I've got NFI how to get the rest of it.
How does one scroll within a shell window?

Surely the revs can code the display or export of these files into the GUI.

 

[Robbks]

Dp

 

[anodos]

Click on 'system' 'advanced' 'save debug' and send me the file through a private message.

 

[anodos]

There are no obvious culprits in your debug file.

Samba-related changes:

• Under the "Advanced" CIFS Share settings check the box "Only Allow Guest Access". This forces all users accessing the samba server to automatically become "guest".
• Under "services" -> "CIFS" add the auxiliary parameter "oplocks = no". Your samba logs indicate that samba is failing to break oplocks on files. Oplocks aren't terribly useful for home users, and disabling them can improve performance in some situations.
• Change "server max protocol" to "SMB3_00"

ZFS-related changes:
You're sharing your "Jails" dataset through CIFS. You shouldn't do this.
Create separate datasets

• Backup/CIFS
• Backup/Jails

Backup/CIFS should have the permissions type set to "Windows". This is the directory that you should share via Samba.
Backup/Jails should have the permissions type set to "Unix". This should NOT be shared via Samba.

Doing this will help prevent you from accidentally breaking permissions on your jails (if you haven't done this already).

Hardware:
Configure your SMART tests. Your drives are running a bit warm. Work on getting more airflow over them.

You have a single disk acting as your backup pool. It's a "green" disk that has experienced 66C temps over its lifetime. There is a very high "188 Command_Timeout" value for this drive as well. This can indicate serious power supply problems or data cable problems. Swap cables, and keep an eye on the values to see if the continue increasing. If you have another drive, consider swapping this one out. Your system dataset resides on the your "Backup" drive. If this drive is experiencing lots of IO timeouts, then samba will become unhappy with you.

 

[Robbks]

Awesome thanks.
I'll make the config changes and report back.

Yeah I had a fan fail while the box was in a less than ideal location.

As for Jails, I've never configured them.

 

[Robbks]

OK, Changed the config and the one Media box still can't see the share.

is the format of "oplocks = no" critical
with or without spaces and parentheses ?

Also, what's considered "normal", "informational" and "critical" for drive temp.
I've searched and found 5 different threads on here, and there's no mention of it. Just that you need to monitor them.
that would be a great addition to the reporting screen, Drive and CPU temps

thanks again for your patience.
I'm doing as much reading and learning as i can along the way

 

[endebe]

With the KB3189866 update i couldn't connect anomyously with my fileshares in my Homenet.

Stupidly i tried the Username anonmyous without any password. That was also the solution for me. No i have my shares again