HP CIFS Server Administrator Guide Version A.03.01.03 (5900-2006, October 2011)
Table Of Contents
- HP CIFS Server Administrator Guide Version A.03.01.03
- Contents
- About this document
- 1 Introduction to the HP CIFS Server
- 2 Installing and configuring HP CIFS Server
- HP CIFS Server requirements and limitations
- Step 1: Installing HP CIFS Server software
- Step 2: Running the configuration script
- Step 3: Modify the configuration
- Step 4: Starting HP CIFS Server
- Other Samba configuration issues
- 3 Managing HP-UX file access permissions from Windows NT/XP/2000/Vista/Windows 7
- Introduction
- UNIX file permissions and POSIX ACLs
- Using the Windows NT Explorer GUI to create ACLs
- Using the Windows Vista Explorer GUI to create ACLs
- POSIX ACLs and Windows 2000, Windows XP, Windows Vista, and Windows 7 clients
- HP CIFS Server Directory ACLs and Windows 2000, Windows XP, Windows Vista, and Windows 7 clients
- In conclusion
- 4 Windows style domains
- Introduction
- Configure HP CIFS Server as a PDC
- Configure HP CIFS Server as a BDC
- Domain member server
- Create the Machine Trust Accounts
- Configure domain users
- Join a Windows client to a Samba domain
- Roaming profiles
- Configuring user logon scripts
- Home drive mapping support
- Trust relationships
- 5 Windows 2003 and Windows 2008 domains
- 6 LDAP integration support
- Overview
- Network environments
- Summary of installing and configuring
- Installing and configuring your Directory Server
- Installing LDAP-UX Client Services on an HP CIFS Server
- Configuring the LDAP-UX Client Services
- Enabling Secure Sockets Layer (SSL)
- Extending the Samba subschema into your Directory Server
- Migrating your data to the Directory Server
- Configuring the HP CIFS Server
- Creating Samba users in directory
- Management tools
- 7 Winbind support
- 8 Kerberos support
- 9 HP CIFS deployment models
- Introduction
- Samba Domain Model
- Windows Domain Model
- Unified Domain Model
- 10 Securing HP CIFS Server
- 11 Configuring HA HP CIFS
- 12 HP-UX configuration for HP CIFS
- 13 Tool reference
- Glossary
- Index

User DN [cn=Directory Manager]:
Password:
NOTE: You must enter the DN user password, which you have given in the LDAP server
setup.
Select authentication method for users to bind/authenticate to the server
1. SIMPLE
2. SASL DIGEST-MD5
To accept the default shown in brackets, press the Return key.
Authentication method: [1]:
For high-availability, each LDAP-UX client can look for user and group
information in up to three different directory servers. Please enter either
the fully qualified host name and optional port number
(for example: sys001.hp.com:389) or IP address and optional port number
(for example: 15.13.118.130:389 or [2001:0db8:3c4d:0015:0:0:abcd:ef12]:389)
where your directory is running.
The following hosts are currently specified:
Default search host 1: [dctvm86.ind.hp.com:389 = 15.146.157.80:389]
Default search host 2: [ ]
Default search host 3: [ ]
Enter 0 to accept these hosts and continue with the setup program or
Enter the number of the hosts you want to specify [0]:
Enter the default base DN where LDAP-UX clients should look for user and
group information, (for example: ou=nis, dc=hp, dc=com)
Default base DN [dc=ind,dc=hp,dc=com]:
The setup program has all the information needed to configure a default
profile and client. You can accept default values for the remaining
parameters or configure the remaining parameters.
Accept remaining defaults? (y/n) [y]:
Are you ready to create the Profile Entry? [Yes]:
Each client system must bind to the directory to download the
LDAP-UX configuration profile entry and to access user and group
information. To perform this, the client can bind to the directory
either anonymously or as a proxy user. Anonymous access can also be
attempted if access by proxy fails.
Select the type of client binding you want.
1. Anonymous
2. Proxy
3. Proxy; if proxy fails, then use anonymous
To accept the default shown in brackets, press the Return key.
Client binding: [1]:
Updated directory server at 15.146.157.80:389
with a profile entry at
[cn=pdc1, dc=ind, dc=hp, dc=com]
Updated the local client configuration file
/etc/opt/ldapux/ldapux_client.conf
Updated the local client profile entry LDIF file
/etc/opt/ldapux/ldapux_profile.ldif
Updated the local client profile entry cache file
/etc/opt/ldapux/ldapux_profile.bin
Press any key to continue:
84 LDAP integration support