Advertisement
Guest User

Untitled

a guest
Aug 25th, 2017
270
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.46 KB | None | 0 0
  1. >smbconfig
  2.  
  3.  
  4. CIFS Configuration Utility
  5.  
  6. Use this utility to configure the server role, create TCP/IP
  7. services, and configure other options.
  8.  
  9. The following conditions must be met prior to configuring CIFS:
  10.  
  11. 1. Log into OpenVMS using a privileged system account.
  12.  
  13. 2. Shutdown CIFS. If CIFS is running on multiple cluster
  14. members, shutdown CIFS on all cluster members which
  15. share the same SAMBA$ROOT: directory tree as the node
  16. being configured.
  17.  
  18. Restrictions:
  19.  
  20. This utility should not be used if you use SWAT for configuring
  21. or managing CIFS Server shares.
  22.  
  23. For more information about CIFS Server configuration,
  24. please refer to HP OpenVMS CIFS Administrator's Guide.
  25.  
  26. If CIFS Server is being configured afresh on this node, choose
  27. the following option from HP OpenVMS CIFS Main Configuration
  28. Options Menu:
  29.  
  30. A - Configure options 1 - 3
  31.  
  32. Press Enter to continue:
  33.  
  34. Checking for existing CIFS Server configuration...
  35.  
  36. CIFS Server configuration is already present on this node.
  37.  
  38. Cleaning up temporary TDB files before initiating
  39. CIFS Server reconfiguration...
  40.  
  41. Converting existing TDB files...
  42.  
  43. Gathering information about current CIFS Server
  44. configuration. Please wait...
  45.  
  46.  
  47. HP OpenVMS CIFS Main Configuration Options Menu
  48.  
  49. Configuration options:
  50.  
  51. 1 - Core environment
  52. 2 - Generic options
  53. 3 - System specific setup
  54. A - Configure options 1 - 3
  55. [E] - Exit Menu
  56.  
  57. Enter configuration option:1
  58.  
  59.  
  60.  
  61.  
  62.  
  63.  
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70.  
  71. HP OpenVMS CIFS Core Configuration Menu
  72.  
  73. The CIFS core configuration menu allows you to configure basic server
  74. configuration parameters and to set the role of the server.
  75.  
  76. ************************** W A R N I N G **************************
  77. Changing any of the options in this menu may cause the existing
  78. databases to be RE-INITIALIZED resulting in the loss of any data
  79. currently in these databases (for example, user accounts, group
  80. names, identifier mapping information etc).
  81. *******************************************************************
  82.  
  83. 1. Enable WINBIND mapping: no
  84. 2. Passdb backend: tdbsam
  85. 3. Domain/Workgroup name: BAR
  86. 4. Server role: STANDALONE
  87. 5. Server computer/netbios name: RX2800
  88.  
  89. Enter item number or press Enter to accept current values [Done]: 3
  90.  
  91. **************************** W A R N I N G *****************************
  92. You chose item number 3 from the menu. Changing the domain name
  93. will cause the existing databases to be RE-INITIALIZED resulting in
  94. the loss of any data currently in these databases (for example,
  95. user accounts, group names, identifier mapping etc).
  96. ************************************************************************
  97.  
  98. Do you want to continue with item number 3 (Y/[N]) y
  99.  
  100. A CIFS Server domain is a collection of computers that share a
  101. common account database and policy. Each domain has a unique
  102. name. A network can have many domains.
  103.  
  104. The CIFS Server domain name can be up to 15 characters long.
  105. The domain name must be different than the computer name.
  106.  
  107. Enter CIFS Server domain name for this system: [BAR] FOO
  108.  
  109.  
  110.  
  111. HP OpenVMS CIFS Core Configuration Menu
  112.  
  113. The CIFS core configuration menu allows you to configure basic server
  114. configuration parameters and to set the role of the server.
  115.  
  116. ************************** W A R N I N G **************************
  117. Changing any of the options in this menu may cause the existing
  118. databases to be RE-INITIALIZED resulting in the loss of any data
  119. currently in these databases (for example, user accounts, group
  120. names, identifier mapping information etc).
  121. *******************************************************************
  122.  
  123. 1. Enable WINBIND mapping: no
  124. 2. Passdb backend: tdbsam
  125. 3. Domain/Workgroup name: FOO
  126. 4. Server role: STANDALONE
  127. 5. Server computer/netbios name: RX2800
  128.  
  129. Enter item number or press Enter to accept current values [Done]: 4
  130.  
  131. The CIFS Server role is the part the server will play in its
  132. domain.
  133.  
  134. A primary domain controller maintains the domain's master user
  135. accounts database and validates logins.
  136.  
  137. A backup domain controller maintains copies of the master database,
  138. validates logins, and can be promoted to primary.
  139.  
  140. A member server does not receive copies of the master database
  141. or validate logins. It relies on domain controllers to validate
  142. user credentials.
  143.  
  144. A standalone server is not part of any domain and is not dependent
  145. upon other servers for validing logins. It provides both resources
  146. and authentication services.
  147.  
  148.  
  149. Enter the server role (P)rimary/(B)ackup/(M)ember/(S)tandalone [S]: m
  150.  
  151. HP OpenVMS CIFS Core Configuration Menu
  152.  
  153. The CIFS core configuration menu allows you to configure basic server
  154. configuration parameters and to set the role of the server.
  155.  
  156. ************************** W A R N I N G **************************
  157. Changing any of the options in this menu may cause the existing
  158. databases to be RE-INITIALIZED resulting in the loss of any data
  159. currently in these databases (for example, user accounts, group
  160. names, identifier mapping information etc).
  161. *******************************************************************
  162.  
  163. 1. Enable WINBIND mapping: no
  164. 2. Passdb backend: tdbsam
  165. 3. Domain/Workgroup name: FOO
  166. 4. Server role: MEMBER
  167. 5. Server computer/netbios name: RX2800
  168.  
  169. Enter item number or press Enter to accept current values [Done]:
  170.  
  171.  
  172.  
  173.  
  174.  
  175.  
  176. Member Server Optional Parameters Configuration Menu
  177.  
  178. The Member Server optional parameters configuration menu allows to
  179. modify Member Server specific parameters which are required for
  180. successful working of CIFS Server as member in a specified domain.
  181.  
  182.  
  183. 1. Enable netlogon secure channel: auto
  184. 2. Require strong session key: no
  185. 3. Member of OpenVMS ASV Domain: no
  186. 4. Password Server: *
  187. 5. Security mode: DOMAIN
  188.  
  189. Enter item number or press Enter to accept current values [Done]:
  190.  
  191. Before joining a domain, the computer must be added to the domain.
  192. The computer is added automatically by this procedure; you must
  193. supply the following information:
  194. - Primary Domain Controller (PDC) name of the domain.
  195. - Administrator account and password in the domain.
  196.  
  197. When prompted for a PDC name, if you are joining CIFS server to an
  198. Advanced Server for OpenVMS (ASV) domain and if ASV PDC is running
  199. in an OpenVMS cluster, specify ASV cluster-alias as PDC name. You
  200. can specify the ASV cluster-alias name without the DNS suffix.
  201.  
  202. Enter Fully Qualified Domain Name (FQDN) of the primary domain
  203. controller for domain FOO:
  204. [e.g., pdcname.pdcdomain.myorg.com] sovereign.foo.local
  205.  
  206. Confirming domain name with SOVEREIGN.FOO.LOCAL ...
  207.  
  208. Successfully confirmed domain name FOO for SOVEREIGN.FOO.LOCAL.
  209.  
  210. Enter the administrator account name for FOO: [Administrator]
  211. Enter the password for account Administrator:
  212. Re-enter to verify password:
  213.  
  214.  
  215. The CIFS Server administrator account is used administer the
  216. server. This utility allows you to specify an administrator
  217. account name of your choice. Once the account name is entered,
  218. this utility verifies if a matching account name exists in
  219. SYSUAF. If a match is not found, an entry for this account is
  220. created in SYSUAF. An account by the same name is added to
  221. CIFS Server account database.
  222.  
  223. If no name is specified, the default administrator account name
  224. is set to CIFSADMIN. The specified name should be less than
  225. or equal to 12 characters.
  226.  
  227. Enter the local CIFS administrator account name: [CIFSADMIN]
  228. Enter the password for account CIFSADMIN:
  229. Re-enter to verify password:
  230.  
  231.  
  232. CIFS Server can be managed by using domain user accounts which
  233. have admin user privilege in CIFS Server configuration file. This
  234. configuration utility can grant the required admin user privilege
  235. to domain user accounts.
  236.  
  237. Do you want to specify domain user accounts to manage CIFS? [y] n
  238.  
  239. The CIFS Configuration Utility found changes in CIFS Server
  240. core configuration. The required changes are:
  241.  
  242. - Updating CIFS Core Configuration file
  243. - Creation of new CIFS Server databases
  244. - Join CIFS Server to the domain FOO
  245. - Create CIFS Admin Account
  246.  
  247. Do you want this utility to do the required changes? [y/n]: [y]
  248.  
  249. You will not be allowed to interrupt while the configuration
  250. changes are taking place.
  251.  
  252. Starting CIFS core configuration. This may take few minutes.
  253. Please wait...
  254.  
  255. Backing up existing configuration and data files...
  256.  
  257. Warning!!! Persistent TDBs (SECRETS.TDB and PASSDB.TDB) will now be
  258. deleted for re-initialization. Their backup has been taken and its
  259. path will be provided at the end of deletion procedure.
  260.  
  261.  
  262. Previous CIFS Server configuration files are now present
  263. in the directory SAMBA$ROOT:[BACKUP.25AUG2017_102103]
  264.  
  265. Writing to CIFS core configuration file...
  266.  
  267. Joining CIFS Server as MEMBER to domain FOO...
  268.  
  269. Unable to join domain FOO
  270. The failure message reported by the net command is:
  271.  
  272. [2017/08/25 10:21:03, 0] SAMBA$SRC:[SOURCE.LIB]UTIL.C;1:(1181)
  273. gethostname failed
  274. [2017/08/25 10:21:03, 0] SAMBA$SRC:[SOURCE.LIB]UTIL.C;1:(1181)
  275. gethostname failed
  276.  
  277. Previous configuration files have been restored.
  278.  
  279. Unable to configure CIFS Server.
  280. Please take action based on the message displayed above.
  281. >
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement