HP CIFS Server 3.0f Administrator's Guide verison A.02.03

/var/opt/samba/lock path). CIFS does this to prevent the problems with sharing the CIFS Server
configuration as discussed above.
• Avoid using HP CIFS Server to share Veritas CFS directories simultaneously on multiple nodes.
Since NFS and Veritas CFS provides for multiple nodes to read and write the same files concurrently,
you should use extra caution when configuring HP CIFS Server on multiple nodes since most locking
mechanisms do not span across multiple nodes. Simultaneous file access can lead to data corruption
if multiple producers overwrite each others work.
• The smb.conf parameter strict locking may be set to yes to prevent data corruption but it may
also lead to decrease performance.
By default, since HP CIFS Server provides access to files from multiple clients (and from multiple nodes
sharing an NFS or a Veritas CFS), there is the possibility of concurrent file access and hence at least
a remote chance of data corruption. Therefore, HP CIFS Server provides a "strict locking" mechanism
that can be enabled to prevent concurrent file access. When strict locking is set toyes in
smb.conf, the server checks every read and write access for file locks, and denies access if locks
exist. Since this check will be slow on some systems and well behaved clients do ask for lock checks
when it is important, HP recommends that you set strict locking to no in smb.conf for most
environments. The default value for strict locking is no.
NetBIOS Names Are Not Supported on Port 445
HP CIFS Server A.02.* versions (based and Samba 3.0.x) can accept connections on port 445 as well as
the original port 139. However, since port 445 connections are for SMB over TCP and do not support the
NetBIOS protocol. NetBIOS names are not supported on port 445. This means features of Samba that
depend on NetBIOS will not work. For example, the "virtual server" technique depending on an
"include = /etc/opt/samba/smb.conf.%L" which ends up referring to another smb.conf.<netbios
name> will not work.
You can use the smb.conf parametersmb ports to specify which ports the server should listen on for
SMB traffic. Set smb ports to 139 to disable port 445. By default, smb ports is set to 445 139.
Other Samba Configuration Issues 39