HP CIFS Client A.02.02.03 Administrator's Guide

NOTE: Automounting a CIFS filesystem using the HP ONC+ AutoFS service is only supported on
HP-UX release 11i v1 and v2. If you have the HP-UX 11i v1 system, you must install the ONC
software package, Enhanced AutoFS, available at http://software.hp.com to enable the AutoFS
2.3 support. AutoFS doesn't support HP CIFS Client on HP-UX release 11.0.
Support for Internationalized Clients
The CIFS Client is designed to work with a variety of internationalized clients and servers. It can
use Unicode to transmit multi-byte characters on the network, or any of several character encoding
tables located in /etc/opt/cifsclient/unitables. See the README file in that directory for an index
of the tables.
NTLM, NTLMv2 Password Encryption
NTLM is a challenge-response protocol. The server sends a challenge key to the client which the
client returns to the server encrypted with the user's password. The server performs the same
encryption and verifies that the client's request matches. No semblance of the user's password is
transmitted over the network. The CIFS Client supports NTLM and NTLMv2. NTLM verison 2
(NTLMv2) uses the same challenge-response protocol, but it provides more sophisticated encryption
algorithms than NTLM, and hence better password protection.
Packet Signing
The purpose of CIFS packet signatures is prevention of man-in-the middle attacks: the client and
server are mutually assured of the other's identity by requiring a unique signature on each SMB
packet.
In the CIFS protocol, packet signing is negotiated when the client makes its initial connection to
the server. Starting with the first user login to the server, all SMB packets between the client and
server must be signed.
See “Packet Signing” (page 27) for a description of the smbPacketSigning configuration
parameter.
NetBIOS Name Services, WINS, and DNS
HP CIFS Client A.02.01 or later supports DNS and the NetBIOS Name Services, including WINS,
a Windows name resolution service similar to DNS. The configuration parameters
lookupTryNetbios, lookupTryDns and nbnsWinsIP are used to configure which lookup
mechanisms are used. For detailed information, see “Name Resolution: NetBIOS Name Service,
WINS, DNS, IP Configuration” (page 20).
Microsoft Distributed File System
The HP CIFS Client A.02.02 supports the Microsoft Distributed File System (MS DFS). DFS is a
network server component that enables administrators to build a single, hierarchical view of multiple
file servers and file server shares on their network. DFS unites files on different computers into a
single name space and provides a way to separate the logical view of files and directories that
users see from the actual physical locations of these network.
DFS comprises three major components, the DFS Root, one of more DFS links, and the DFS client.
A DFS Root is a special share on a CIFS Server, that serves as the starting point for DFS functionality.
A DFS link is a special directory within the DFS Root, that maps to another CIFS share on the same
or different server. A DFS client is a CIFS client which is capable of processing DFS links. When
the DFS client accesses a DFS link, it sends a request for the CIFS share that the DFS link maps to,
and establishes a connection to that CIFS share.
HP CIFS Client Features 11