Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- >smbconfig
- CIFS Configuration Utility
- Use this utility to configure the server role, create TCP/IP
- services, and configure other options.
- The following conditions must be met prior to configuring CIFS:
- 1. Log into OpenVMS using a privileged system account.
- 2. Shutdown CIFS. If CIFS is running on multiple cluster
- members, shutdown CIFS on all cluster members which
- share the same SAMBA$ROOT: directory tree as the node
- being configured.
- Restrictions:
- This utility should not be used if you use SWAT for configuring
- or managing CIFS Server shares.
- For more information about CIFS Server configuration,
- please refer to HP OpenVMS CIFS Administrator's Guide.
- If CIFS Server is being configured afresh on this node, choose
- the following option from HP OpenVMS CIFS Main Configuration
- Options Menu:
- A - Configure options 1 - 3
- Press Enter to continue:
- Checking for existing CIFS Server configuration...
- CIFS Server configuration is already present on this node.
- Cleaning up temporary TDB files before initiating
- CIFS Server reconfiguration...
- Converting existing TDB files...
- Gathering information about current CIFS Server
- configuration. Please wait...
- HP OpenVMS CIFS Main Configuration Options Menu
- Configuration options:
- 1 - Core environment
- 2 - Generic options
- 3 - System specific setup
- A - Configure options 1 - 3
- [E] - Exit Menu
- Enter configuration option:1
- HP OpenVMS CIFS Core Configuration Menu
- The CIFS core configuration menu allows you to configure basic server
- configuration parameters and to set the role of the server.
- ************************** W A R N I N G **************************
- Changing any of the options in this menu may cause the existing
- databases to be RE-INITIALIZED resulting in the loss of any data
- currently in these databases (for example, user accounts, group
- names, identifier mapping information etc).
- *******************************************************************
- 1. Enable WINBIND mapping: no
- 2. Passdb backend: tdbsam
- 3. Domain/Workgroup name: BAR
- 4. Server role: STANDALONE
- 5. Server computer/netbios name: RX2800
- Enter item number or press Enter to accept current values [Done]: 3
- **************************** W A R N I N G *****************************
- You chose item number 3 from the menu. Changing the domain name
- will cause the existing databases to be RE-INITIALIZED resulting in
- the loss of any data currently in these databases (for example,
- user accounts, group names, identifier mapping etc).
- ************************************************************************
- Do you want to continue with item number 3 (Y/[N]) y
- A CIFS Server domain is a collection of computers that share a
- common account database and policy. Each domain has a unique
- name. A network can have many domains.
- The CIFS Server domain name can be up to 15 characters long.
- The domain name must be different than the computer name.
- Enter CIFS Server domain name for this system: [BAR] FOO
- HP OpenVMS CIFS Core Configuration Menu
- The CIFS core configuration menu allows you to configure basic server
- configuration parameters and to set the role of the server.
- ************************** W A R N I N G **************************
- Changing any of the options in this menu may cause the existing
- databases to be RE-INITIALIZED resulting in the loss of any data
- currently in these databases (for example, user accounts, group
- names, identifier mapping information etc).
- *******************************************************************
- 1. Enable WINBIND mapping: no
- 2. Passdb backend: tdbsam
- 3. Domain/Workgroup name: FOO
- 4. Server role: STANDALONE
- 5. Server computer/netbios name: RX2800
- Enter item number or press Enter to accept current values [Done]: 4
- The CIFS Server role is the part the server will play in its
- domain.
- A primary domain controller maintains the domain's master user
- accounts database and validates logins.
- A backup domain controller maintains copies of the master database,
- validates logins, and can be promoted to primary.
- A member server does not receive copies of the master database
- or validate logins. It relies on domain controllers to validate
- user credentials.
- A standalone server is not part of any domain and is not dependent
- upon other servers for validing logins. It provides both resources
- and authentication services.
- Enter the server role (P)rimary/(B)ackup/(M)ember/(S)tandalone [S]: m
- HP OpenVMS CIFS Core Configuration Menu
- The CIFS core configuration menu allows you to configure basic server
- configuration parameters and to set the role of the server.
- ************************** W A R N I N G **************************
- Changing any of the options in this menu may cause the existing
- databases to be RE-INITIALIZED resulting in the loss of any data
- currently in these databases (for example, user accounts, group
- names, identifier mapping information etc).
- *******************************************************************
- 1. Enable WINBIND mapping: no
- 2. Passdb backend: tdbsam
- 3. Domain/Workgroup name: FOO
- 4. Server role: MEMBER
- 5. Server computer/netbios name: RX2800
- Enter item number or press Enter to accept current values [Done]:
- Member Server Optional Parameters Configuration Menu
- The Member Server optional parameters configuration menu allows to
- modify Member Server specific parameters which are required for
- successful working of CIFS Server as member in a specified domain.
- 1. Enable netlogon secure channel: auto
- 2. Require strong session key: no
- 3. Member of OpenVMS ASV Domain: no
- 4. Password Server: *
- 5. Security mode: DOMAIN
- Enter item number or press Enter to accept current values [Done]:
- Before joining a domain, the computer must be added to the domain.
- The computer is added automatically by this procedure; you must
- supply the following information:
- - Primary Domain Controller (PDC) name of the domain.
- - Administrator account and password in the domain.
- When prompted for a PDC name, if you are joining CIFS server to an
- Advanced Server for OpenVMS (ASV) domain and if ASV PDC is running
- in an OpenVMS cluster, specify ASV cluster-alias as PDC name. You
- can specify the ASV cluster-alias name without the DNS suffix.
- Enter Fully Qualified Domain Name (FQDN) of the primary domain
- controller for domain FOO:
- [e.g., pdcname.pdcdomain.myorg.com] sovereign.foo.local
- Confirming domain name with SOVEREIGN.FOO.LOCAL ...
- Successfully confirmed domain name FOO for SOVEREIGN.FOO.LOCAL.
- Enter the administrator account name for FOO: [Administrator]
- Enter the password for account Administrator:
- Re-enter to verify password:
- The CIFS Server administrator account is used administer the
- server. This utility allows you to specify an administrator
- account name of your choice. Once the account name is entered,
- this utility verifies if a matching account name exists in
- SYSUAF. If a match is not found, an entry for this account is
- created in SYSUAF. An account by the same name is added to
- CIFS Server account database.
- If no name is specified, the default administrator account name
- is set to CIFSADMIN. The specified name should be less than
- or equal to 12 characters.
- Enter the local CIFS administrator account name: [CIFSADMIN]
- Enter the password for account CIFSADMIN:
- Re-enter to verify password:
- CIFS Server can be managed by using domain user accounts which
- have admin user privilege in CIFS Server configuration file. This
- configuration utility can grant the required admin user privilege
- to domain user accounts.
- Do you want to specify domain user accounts to manage CIFS? [y] n
- The CIFS Configuration Utility found changes in CIFS Server
- core configuration. The required changes are:
- - Updating CIFS Core Configuration file
- - Creation of new CIFS Server databases
- - Join CIFS Server to the domain FOO
- - Create CIFS Admin Account
- Do you want this utility to do the required changes? [y/n]: [y]
- You will not be allowed to interrupt while the configuration
- changes are taking place.
- Starting CIFS core configuration. This may take few minutes.
- Please wait...
- Backing up existing configuration and data files...
- Warning!!! Persistent TDBs (SECRETS.TDB and PASSDB.TDB) will now be
- deleted for re-initialization. Their backup has been taken and its
- path will be provided at the end of deletion procedure.
- Previous CIFS Server configuration files are now present
- in the directory SAMBA$ROOT:[BACKUP.25AUG2017_102103]
- Writing to CIFS core configuration file...
- Joining CIFS Server as MEMBER to domain FOO...
- Unable to join domain FOO
- The failure message reported by the net command is:
- [2017/08/25 10:21:03, 0] SAMBA$SRC:[SOURCE.LIB]UTIL.C;1:(1181)
- gethostname failed
- [2017/08/25 10:21:03, 0] SAMBA$SRC:[SOURCE.LIB]UTIL.C;1:(1181)
- gethostname failed
- Previous configuration files have been restored.
- Unable to configure CIFS Server.
- Please take action based on the message displayed above.
- >
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement