Last updated on JULY 29, 2016
Applies to:Solaris Operating System - Version 10 3/05 to 10 1/13 U11 [Release 10.0]
Information in this document applies to any platform.
A Solaris 10 system had a Samba share created that was a ZFS filesystem. For example it was named share1:
path = /share1
read only = No
acl check permissions = No
create mask = 0700
inherit permissions = Yes
inherit acls = Yes
inherit owner = Yes
Under the /share1 directory, which was part of a ZFS pool, was a filesystem that was a symbolically linked directory, also known as a symlink in Samba terms, that was from a location outside of the root of the Samba share. In this case it was a NFS mounted file system:
In the /etc/vfstab
The /usr/app/symlink directory was linked to /share1/symlink
Windows Clients could access the /share1 directory content but could not access the /share1/symlink directory. They would receive a Access Denied message when trying to access the share path of \sambaserver\share1\symlink
The following message was recorded repeatedly in the /var/samba/log/log.smbd log file:
Share 'share1' has wide links and unix extensions enabled. These parameters are incompatible. Wide links will be disabled for this share.
The system had been updated from Solaris Samba version 3.0.37 to version 3.5.5 or later.
The Solaris Samba version upgrade would be take place when Solaris 10 Patches 146363-01 or 119757-20 or later (SPARC) or 146364-01 or 119758-20 or later (X86) are installed.
In Samba around version 3.4.x there was a change that determined that when the options wide links and unix extensions are enabled there would be a conflict and wide links would be disabled. the updated version of Solaris Samba now had this functionality where the previous version of 3.0.37 did not.
Refer to the Samba.org smb.conf man page entry for unix extensions for more information:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms