Siemens Unix V4.0 Overviews & Installation Instructions

Siemens advanced server overview and installation

Table of Contents

Quick Links

Download this manual

Advanced Server UNIX V4.0

Overview and Installation

Edition April 1999

Table of Contents

Troubleshooting

Summary of Contents for Siemens Unix V4.0

Page 1 Advanced Server UNIX V4.0 Overview and Installation Edition April 1999...
Page 2: Copyright And Trademarks
There you will also find the addresses of the relevant User Documentation Department. Copyright and Trademarks Copyright © Siemens AG 1999. All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers Information in this document is subject to change without notice.
Page 3 (LAN, Local Area Network and WAN, Wide Area Network). Advanced Server for UNIX allows the operation of various systems in a network. Advanced Server for UNIX V4.0 (Advanced Server for UNIX in this manual) provides users with server functions for the local network. It extends UNIX Advanced Server for UNIX corresponds to Windows NT Server.
Page 4: Target Group
Clients”, to install these clients. The manual “NetWare Connectivity” contains information on how your MS-DOS client can work simultaneously with Advanced Server for UNIX or LAN Manager servers and with ® NetWare servers. It also contains installation and configuration instructions for NetWare Connectivity.
Page 5: Summary Of Contents
It also provides instructions for trans- ferring the Advanced Server for UNIX software onto the server system as well as all the information required to configure the system and Advanced Server for UNIX software, and to create a development environment for Advanced Server for UNIX applications.
Page 6: Notational Conventions
1.3 Changes since the last version of the manual The documentation has been updated to conform to the software level of Advanced Server for UNIX V4.0B. For a list of differences between Advanced Server for UNIX V4.0B and the previons version, please refer to the section UNIX”.
Page 7 2 Introduction to Advanced Server for UNIX This chapter contains supplementary and additional information on Advanced Server for UNIX that is not contained in the manual entitled The following topics are dealt with: Shared resources and services Connection management Administration...
Page 8 (LAN, Local Area Network and WAN, Wide Area Network) with Advanced Server for UNIX. The server systems provide services and resources in the local network. In contrast, the clients utilize the services and resources of the server and generally do not provide any services and resources themselves in the network.
Page 9 Domain name Product Manual Meaning Name of the UNIX system Each server and client in a network must have a unique computername. A proposed server name is derived from the system name when it is being installed first (maximum 15 characters).
Page 10 It can be changed to any name (with a maximum of fifteen characters) during installation. The server name is stored automatically in the lanman.ini file on the server. It is part of the network name and may only be changed after the installation using special utility programs.
Page 11 2.2.1.4 Sharename If a resource on a server is shared, it gets a sharename. The sharename identifies the resource on the server. A sharename for a resource must appear only once on a server, however the same sharename may be used several times on other servers in the network.
Page 12 The default domain name consists of the first eleven characters of the system name plus the suffix .dom, e.g. the domain name of the server server1 would be server1.dom. The domain name consists of up to fifteen characters: letters from a to z, numbers from 0 to 9 and the special characters -.~!#$%^&()_{}.
Page 13 The attributes r and d are mapped to the relating UNIX mechanisms. The attributes a, s and h, as well as any possible combination of these are translated to Advanced Server for UNIX by means of UNIX group names. The table below, for example, shows how the MS-DOS file BSP.DAT with the attributes a and h and the MS-DOS file READONLY.BSP with the attri-...
Page 14 Every resource deleted using net share /delete is removed from the share table. Advanced Server for UNIX stores the share table in an internal format in the registry. The share table is loaded automatically each time Advanced Server for UNIX is started. The various types of shared resources are introduced in the following sections.
Page 15 Introduction to Advanced Server for UNIX 2.2.4 Shared directory A shared directory is a file tree of a server system, which was shared for the usage in the local network. Users can access the shared directory from a client using the sharename.
Page 16 Older MS-DOS versions or programs are not network-ready, in this case only one user at a time can access a file. Advanced Server for UNIX maps the interfaces available under the MS-DOS, OS/2, Windows, Windows for Workgroups, Windows 95/98 and Windows NT operating systems to UNIX mechanisms in order to manipulate files and directories.
Page 17 (shared client printer). For further information, please refer to the manuals entitled “MS Network Client V2.2” 2.2.5.3 Printer server The output of the printer spooler can also be routed to server and client systems that can share a printer resource (e.g. Windows for Workgroups, Windows NT). 2.2.5.4 Sharing a printer The administrator shares the printer queue on the server (with the computername server1).
Page 18 LM named pipe: An application process with root authorization creates a named pipe on the server. The client process on the client sets up a connection to the known named pipe over the local network. Both processes can then exchange data using the LM named pipe. When the data exchange has ended, the LM named pipe is deleted.
Page 19 Mailslots are unidirectional communication channels. They are created by an application process on the server or by a client process on the client. In contrast to LM named pipes, several processes can write to the same mailslot simultaneously but only the process that created the mailslot can read from it.
Page 20 2.3.2 Auditing Important activities in the network are recorded by this service. These include starting and stopping the server, user sessions and utilization of shared resources by specifying the username and time. This list can be displayed if required. Product Manual...
Page 21 2.3.5 Timesource This is a Advanced Server service which identifies a server as the time source for a domain. Other servers can synchronize their clocks with the time source. UNIX servers cannot synchronise their clocks using this service.
Page 22: Snmp Service
Agent Adapter” (Slsnmpd). 2.3.7 Netrun service The Netrun service enables you to run a UNIX program on Advanced Server for UNIX from an OS/2 or an extended MS-DOS client. The corresponding user interface is not available on Windows for Workgroups, Windows 95/98, and Windows NT.
Page 23: Connection Management
Advanced Server for UNIX is introduced. 2.4.1 Sessions A session is set up between a client and a server the first time when a connection from the client to a server resource was successful. (N.B. Windows NT clients sometimes have two sessions to the same server).
Page 24 Even after you have successfully logged onto a domain, you may need to carry out further steps to be able to use the resource of a server in another domain: If you have a different password for the same user name in another domain, you must enter this password.
Page 25: Remote Administration
Workgroups, Windows NT, or Windows 95/98 is installed. For this reason, the Windows NT Server Tools are supplied with Advanced Server for UNIX. Special NT Server Tools have been developed for the Windows client. Since they have the same functionality, a standard administration interface is available to you on all clients and workstations.
Page 26: Client Software
Advanced Server for UNIX supports the Microsoft Remote Procedure Calls (RPCs). This platform-independent mechanism is used for interprocess communication within a client- server architecture. The new functions of Advanced Server for UNIX are called up internally via RPC. 2.7 Compatibility 2.7.1 Client software The functionality of Advanced Server for UNIX corresponds to the server part of Microsoft Windows NT Server.
Page 27: Server Hardware
You can install Advanced Server for UNIX and LAN Manager/X in a domain with Windows NT servers. Only one Advanced Server for UNIX or Windows NT server can be installed as a primary domain controller in a single domain. LAN Manager/X servers cannot take on the server role of primary domain controller.
Page 28 Introduction to Advanced Server for UNIX 2.7.4 LAN Manager/X V1.1 Version 2.0 and later of LAN Manager/X or Advanced Server for UNIX are compatible with Version 1.1 as regards the following: The environment variable $xLMX The environment variable $LM_HOMEDIR The file /etc/rclmx, in which the environment variables are set...
Page 29 The API of Version 2.0 has been extended. The Targon/31 system is no longer supported. You are now provided with a suggested name for the server name consisting of the first nine characters of the host name and the suffix .srv instead of .serve (e.g. server1.srv).
Page 30 Appendix A of the manual to the tables for these descriptions. Like a Windows NT server, Advanced Server for UNIX can take on the server role of primary domain controller in a domain. The server roles of “member server” and “standalone server” have been omitted. In an upgrade, the member server is given the role of “backup domain controller”...
Page 31 Introduction to Advanced Server for UNIX Administration: The primary administration tool for Advanced Server for UNIX are the Windows NT Server Tools, which can be used from a Windows NT workstation or a Windows NT server. They are also available under Windows 3.1, Windows for Workgroups, and Windows 95/98.
Page 32 With Advanced Server for UNIX, the AT&T and SPOOL V4.x spoolers are supported. 2.7.7 Advanced Server for UNIX V3.5 Advanced Server for UNIX V4.0 is compatible with V3.5 except for the following: Intel systems are not longer supported (e.g. SINIX-L/-M/-Z and UnixWare).
Page 33 Improved installation of asxserver package. Default of servername without ".", that means .srv is omitted. The .srv extension for server names is no longer offered as the default. Warnings occur if server names are incompatible with DNS names. Share table information moved to registry.
Page 34 Introduction to Advanced Server for UNIX Updated description Updated description: New configuration option to spoolin print jobs with the User ID of the mapped UNIX user instead of the User ID of "root". New registry parameters: ConnectTimeout, MaxMpxCt, NetPopup, SpoolinAsUnixUser, DeletedPrintJobTimeOnQ New lanman.ini parameters: maxspoolfds, os2searchfix, ProductType...
Page 35 Processes required for the administration of NetBIOS are not considered here! 3.1 Process model A series of processes are started in order to carry out specific tasks when Advanced Server for UNIX is started. The following sections contain a short description of these processes and their tasks.
Page 36 Advanced Server for UNIX architecture 3.1.2 Overview of the processes The following table lists the daemon processes active when Advanced Server for UNIX has been started in a maximum configuration. Process lmx.ctrl lmx.srv lmx.dmn lmx.alerter lmx.browser lmx.repl lmx.wins lmx.ep lmx.netrun lmx.extd...
Page 37 Advanced Server for UNIX architecture The following diagram clarifies the cooperation between Advanced Server for UNIX processes on a server started with the default configuration: lmx.srv Advanced Server for UNIX processes Product Manual Shared memory lmx.browser lmx.ctrl lmx.srv Process model lmx.dmn...
Page 38 The mslot task receives the mailslot requests and passes them on to the server. It also processes the announce requests from other servers. This task transmits the mailslot messages to the application processes on the server, which can then be read using the API function DosReadMailslot.
Page 39 The daemon process lmx.dmn performs the service network logon security. It also synchro- nizes the individual servers (single system image, SSI) and is used for trust relationships. This process is started by the process lmx.ctrl when Advanced Server for UNIX is being initialized.
Page 40 This process sets up the connection between the SNMP service and Advanced Server for UNIX; it informs the SNMP agent when Advanced Server for UNIX starts and stops. The lmx.nvalert process This process is not supported by Siemens Advanced Server for UNIX. Product Manual Process model U7613-J-Z815-6-76...
Page 41 Advanced Server for UNIX architecture 3.2 Network communication A workstation and an Advanced Server for UNIX communicate in the network using several protocol layers. NetBIOS is implemented in accordance with RFC1001/2. This NetBIOS implementation is based on the standard protocol TCP/IP. The following diagram illustrates the way in which the individual modules work together in the communication process.
Page 42 Advanced Server for UNIX architecture 3.3 Local communication for UNIX systems If a user is working on the server system as an Advanced Server for UNIX user, e.g. administrator, then NetBIOS is used for a local session. The programming interface to Advanced Server for UNIX, the application programming interface (API), is implemented using local interprocess communication (LIPC).
Page 43 Advanced Server for UNIX V4.0. 4.1 Advanced Server for UNIX delivery package All of the software for Advanced Server for UNIX is contained on CD-ROM in package format (PKG). An overview of this is given on the next page.
Page 44: Hardware And Software Requirements
Microsoft Client Software Manual pages for Advanced Server for UNIX Online documentation and Acrobat Reader Advanced Server for UNIX SNMP extension for TransView Extensible Agent This package is only intended for the Siemens Support Service. Hardware and software requirements U7613-J-Z815-6-76...
Page 45 Installing Advanced Server for UNIX 4.2.1.2 Hard disk storage The file systems must have the following available disk space for Advanced Server for UNIX at installation time: File system /usr /usr /usr /var /opt Any file system Any file system...
Page 46: Software Requirements
RM200 RM300 RM400 RM600-xxx If you would like to use the “shared printer” resource with Advanced Server for UNIX, you must configure one of the following spoolers before installing Advanced Server for UNIX: Product name AT&T spooler SPOOL V4.2B or Xprint 5.0 (and later)
Page 47 Installing Advanced Server for UNIX 4.2.2.1 Dependencies You can use Advanced Server for UNIX from clients if one of the client software products described in section 4.3 The installation procedure The software is installed from the CD-ROM using the cdinst utility. cdinst invokes the pkgadd program implicitly.
Page 48 Installing Advanced Server for UNIX 4.4 Deinstalling previous versions Before this version of Advanced Server for UNIX V4.0 is installed, the previous versions must be deinstalled. You must follow the sequence for deinstallation described here in a domain with a primary and one or more backup domain controllers.
Page 49 – not to /var/opt/lanman. If you do not want to modify the server roles and if you are using the replicator service, you only need to back up the logon scripts for the export server.
Page 50 Call /var/opt/lanman/bin/acladm -C -y and /var/opt/lanman/bin/samcheck -r to check and repair the acl database and the account databases. Remove Advanced Server for UNIX V3.5 as described in the manual for the respective Ê version. Deinstall the optional packages including optional Service Packs, the server software, Ê...
Page 51 NetBIOS”. 4.5 Automatic installation with TransView SAX All packages of Advanced Server for UNIX can be distributed with TransView SAX and installed automatically with a response file. Later versions of Advanced Server for UNIX can also be installed with TransView SAX as delta products.
Page 52 Move the cursor to the item you want and press ENTER to select it. Ê Select info to display other information on the Advanced Server for UNIX V4.0 product, e.g. the name of the manufacturer, date of manufacture, version etc. Product Manual...
Page 53 Select pkginfo to display more details on individual packages, e.g. number of files Ê or memory requirements. Select README to display a list of the readme files for the Advanced Server for Ê UNIX product. 4. Select install and then press of the individual packages.
Page 54 Installing Advanced Server for UNIX 5. If you select Package, the following selection is displayed (for contents of the packages, please refer to section AS/X 4.0<version> AS/X 4.0<version> AS/X 4.0<version> AS/X 4.0<version> AS/X 4.0<version> AS/X 4.0<version> AS/X 4.0<version> AS/X 4.0<version>...
Page 55 The README files are always located under this path. The manual page files are numbered consecutively, e.g. the first file for Advanced Server for UNIX V4.0 is stored in the path /opt/readme/asx.D/man400. Since the package is a general UNIX package which is used by different products, the package cannot be removed again.
Page 56 NetBIOS. This can be accomplished in the following ways: To ensure that the primary domain controller can be found if WINS is not used: Ê...
Page 57 If the brdcast_list line! To ensure that the primary domain controller can be found if this server is a WINS client: Ê Edit the file /var/opt/nbrfc/conf/wins.cfg and add the appropriate WINS server addresses. For detailed information on configuring name resolution, refer to section...
Page 58 Product name DCE-THR V2.0A20 (or later) SIthreads This package is only necessary if the machine should run the Advanced Server for UNIX WINS service. The “ SIthreads “ package is included on the operating system CD with more recent operating system versions. This package replaces the previous version “DCE-THR“.
Page 59 This is for security reasons only, because the installation cannot continue if the server is running. The installation will abort if the server is running and you do not choose to stop the server. Because this happens very early during installation, this question is asked every time regardless of the actual system configuration.
Page 60 You can start the non-interactive installation with a default configuration. With this instal- lation type, no further input is required before and during installation. Using this method, the server is always installed as a primary domain controller in it’s own domain. For further information, please refer to the section The steps for interactive installation are presented on the following pages.
Page 61 During a new installation, the role of the server has to be specified. In a domain there is exactly one primary domain controller. The primary domain controller must be the first server that is installed in a domain. Other LM/X and AS/X servers can be backup domain controllers.
Page 62 Name of the primary domain controller If you wish to install a new backup domain controller, you will be asked to enter the server name of the primary domain controller.
Page 63 (Keep in mind that during the preparation of an unattended installation the question is asked to have the setting on the target machine.) If you upgrade an Advanced Server for UNIX V3.5 (primary or backup domain controller), the databases are upgraded from the older version, there is no new initialization to prevent loss of exisiting users and groups.
Page 64 Installing Advanced Server for UNIX If you install an Advanced Server for UNIX V4.0 primary domain controller from scratch or upgrade a LAN Manager/X to be an Advanced Server for UNIX primary domain controller, you can select the domain language for the domain. All builtin objects are initialized using the selected domain language.
Page 65 Installing Advanced Server for UNIX Start the server You can start the server directly during the installation or manually after the installation. Note that after having installed a new NetBIOS, the system must have been rebooted before you can start the server.
Page 66 Please enter the interface name or press ENTER if it is <spool interface>: Enter the interface name of the spooler. Ê Server name The server name is incorporated from the previous version, if possible. Server role The server role is incorporated from the previous version, if possible. Domain name The domain name is incorporated from the previous version, if possible.
Page 67 NOTICE: To upgrade the saved data from LM/X 2.x you have to start the server! Do you want to start the Advanced Server [y/n]? Ê Enter y to start the server during the installation, or n to start it manually after the instal- lation. Upgrade of the accounts database (lmxupgrade)
Page 68 If the primary domain controller of the domain you want to join is located in a different subnet, you have to ensure that the domain name and the server name of the primary domain controller can be resolved by the local NetBIOS. Please refer to the section “Installing NetBIOS”...
Page 69 Please enter the interface name or press ENTER if it is <spool interface>: Enter the interface name of the spooler. Ê Server name The server name is incorporated from the previous version, if possible. Server role The server role is incorporated from the previous version, if possible. Domain name The domain name is incorporated from the previous version, if possible.
Page 70 NOTICE: To upgrade the saved data from LM/X 2.x you have to start the server! Do you want to start the Advanced Server [y/n]? Enter y to start the server during the installation, or n to start it manually after the instal- Ê...
Page 71 Installing Advanced Server for UNIX If the server is not started, the following message gives you information on how to upgrade later: Access Control Entries can be upgraded from the LAN Manager 2.x accounts file (/var/opt/lanman/datafiles/accounts.lm2) after the user accounts and groups have been replicated to this backup controller.
Page 72 Please enter the interface name or press ENTER if it is <spool interface>: Ê Enter the interface name of the spooler. Server name The server name is incorporated from the previous installation, if possible. Server role The server role is incorporated from the previous installation, if possible. Domain name The domain name is incorporated from the previous installation, if possible.
Page 73 (e.g. restore the databases from a system backup). Note that if the previous version was an Advanced Server for UNIX Version 3.5, the domain language will always be ENGLISH. Changing the domain language after the installation is only possible with loss of all user and group accounts.
Page 74 However there is one known problem during the upgrade of an Advanced Server for UNIX Version 3.5 that was a backup domain controller on a server with a german names for builtin objects (either a german Windows NT Server or an Advanced Server for UNIX Version 4.0 with a german domain language).
Page 75 In this very special case, the server name, the administrator on the primary domain controller, the administrator password and the domain language have to be entered. Server name The server name is incorporated from the previous installation, if possible.
Page 76 Installing Advanced Server for UNIX Name of the primary domain controller The name of the primary domain controller is incorporated from the previous installation, if possible. In the case of database corruption, the name of the primary domain controller has to be...
Page 77 Enter y (yes) or n (no). 4.8.6 New installation of a primary domain controller The following sections describe how Advanced Server for UNIX is installed as a primary domain controller on a system on which neither LAN Manager/X nor Advanced Server for UNIX was previously installed or on which the LAN Manager/X or Advanced Server for UNIX installation has been fully deinstalled.
Page 78 Please enter the interface name or press ENTER if it is <spool interface>: Ê Enter the interface name of the spooler. Server name The system generates a default server name from the system name and displays the message Enter the name of the server or press Enter to select <system name>: Ê...
Page 79 Ê Enter the domain name. Confirm choices The server name, the server role and the domain name have to be confirmed now or can be re-entered. Administrator’s password The password of the account Administrator has to be entered twice:...
Page 80 If the primary domain controller of the domain you want to join is located in a different subnet, you have to ensure that the server name of the primary domain controller and the domain name can be resolved by the local NetBIOS. Please refer to the section NetBIOS”...
Page 81 Enter the interface name of the spooler. Ê Server name The system generates a default server name from the system name and displays the message Enter the name of the server or press Enter to select <system name>: Enter the server name.
Page 82 If the problem has to be fixed later, enter n. In this case, the installation will proceed, but the server will become a primary domain controller (!) with a temporary domain name, so that you can complete the configuration after the problem is fixed: Use the command /var/opt/lanman/bin/joindomain to change the role of the server to a Ê...
Page 83: After The Installation
Installing Advanced Server for UNIX Confirm choices The server name, the server role, the domain name and the name of the primary domain controller have to be confirmed now or can be re-entered. Domain Language The system now displays the supported languages (ENGLISH and GERMAN) and outputs the message Please enter the language or press ENTER if it is "ENGLISH":...
Page 84 Upgrade of lanman.ini parameters As a result of upgrading LAN Manager/X or Advanced Server for UNIX most of the values in your previous lanman.ini configuration file are mapped to Advanced Server registry keywords. Some lanman.ini file parameters are not incorporated into the registry but are stored in a new lanman.ini file.
Page 85 For information on memory requirements, please refer to the table in the section storage”. asxman This package contains UNIX manual pages for the API as well as for all Advanced Server for UNIX commands. The manual tures and an overview of the API functions. Please refer to the manual pages of this package for more detailed information.
Page 86 Installing Advanced Server for UNIX asxdocs This package contains the manuals for Advanced Server for UNIX in PDF format as well as a version of Acrobat Reader. asxsnmp This package contains the extensions for the SNMP Service. For further information, please refer to the LAN Manager/X manual 4.9.1 Installing the msclients package...
Page 87 The system now copies the data from the volume to the specified directory. A resource with the sharename astools or astoolsD is shared automatically. For information on installing the server tools from this directory on a PC client or a Windows NT workstation, please refer to the section...
Page 88 4.9.3 Installing the asxman package Installation of the asxman package is optional, but recommended. The package contains UNIX manual pages for the API of Advanced Server for UNIX as well as for all Advanced Server for UNIX commands. The manual an overview of the API functions as a supplement to this.
Page 89 Installing Advanced Server for UNIX 4.10 Installing with the default configuration You can install the asxserver, asxtools, or asxtoolsD and msclients packages with a default configuration without any further input. The default parameters for all packages are listed at the end of this section.
Page 90 Installing Advanced Server for UNIX 4. Select install and then press installation of the individual packages. Install: Installation mode: Installation default file name: Path to response files: Fill in the form and then press SAVE. In the Install selection field you can select between Complete Product, SIreadmeM, and Package.
Page 91 Installing Advanced Server for UNIX Default parameters for the asxserver package: R_INSTTYPE=’automatic’ R_PKGNAME=’Advanced Server 4.0 for UNIX’ R_VERSION=’4.0B0003’ R_LMXSPOOLER=’default’ R_AUTOSTART=’NO’ R_PASSWORD=’password’ R_LANG=’ENGLISH’ R_DOMAINLANG=’ENGLISH’ R_SAVEONREMOVAL=’YES’ R_MAPWARNTOERR=’NO’ SERVERNAME=’default’ DOMAIN=’default’ ROLE=’primary’ PRIMARY=’’ ADMIN_ACCT=’administrator’ STOPSERVER=’YES’ USE_DEFAULT_PASSWD=’NO’ ASK_ABOUT_PRINTER_UPGRADE=’NO’ ALWAYS_USE_UPLEVEL_PRINTING=’NO’ The entry default means that the value for the parameter is automatically formed on the system.
Page 92 Parameter: Value: Installation step: Parameter: Value: Product Manual Output language R_LANG ENGLISH Interface of the spooler used by the server R_LMXSPOOLER default (the spooler configured in UNIX) Server name SERVERNAME default (system name) Server role ROLE Domain name Domain name DOMAIN default (system name with .dom)
Page 93 Installing Advanced Server for UNIX Installation step: Parameter: Value: Parameter: Value: Installation step: Parameter: Value: Installation step: Parameter: Value: Parameter: Value: Installation step: Parameter: Value: Installation step: Parameter: Value: After an default installation of the asxserver package,deinstallation of the package on the target system will also run without any interaction.
Page 94 The /var installation path is used for the msclients package. Default response file for the msclients package: MSCLIENT=’/var/opt/lanman/shares/msclient’ 4.11 Deinstalling Advanced Server for UNIX V4.0 Deinstall the software in the following sequence: begin with the optional packages (including AS/X Service Packs from the field support) then the server followed by NetBIOS.
Page 95 Customized print processor scripts. Information about shared printers (servers and workstations). Printers are either linked directly to the server or to specific workstations (shared client printer). If you enter n here, all data relating to the printer will be deleted.
Page 96 Installing Advanced Server for UNIX 4.11.3 Deinstalling NetBIOS Work through the following steps: 1. Log on as system administrator root. 2. Enter pkgrm nbrfc. Verify with the Ê generated. During this process you will receive a corresponding system wait message.
Page 97 5 Configuring Advanced Server for UNIX This chapter contains the information required to configure Advanced Server for UNIX. You must have root privilege to configure NetBIOS and Advanced Server for UNIX. 5.1 Configuring NetBIOS The following section first gives a brief introduction to NetBIOS.
Page 98 Configuring Advanced Server for UNIX 5.1.1 Introduction to NetBIOS An important part of Advanced Server for UNIX communication is not based directly on TCP/IP protocols but uses NetBIOS. In terms of the OSI Reference Model for a layered networking architecture, NetBIOS is a level 5 protocol (“Session Layer ”...
Page 99 Resolution is the process used to determine the specific IP address for a certain NetBIOS name. An Advanced Server for UNIX computer can use one or more of the following methods to ensure accurate name resolution in TCP/IP internetworks: Broadcast name resolution Broadcast name resolution is a NetBIOS over TCP/IP mode of operation defined in RFC 1001/1002 as b-node.
Page 100 Windows Internet Name Service (WINS) A computer can use WINS if at least one WINS server is available that contains a dynamic database that maps computer names to IP addresses. WINS can be used in conjunction with broadcast name resolution for an internetwork where other name resolution methods are inadequate.
Page 101: Configuring Network Interfaces
The interfaces.cfg file In general every network interface for which TCP/IP is supported can be used by Advanced Server’s NetBIOS.The file /var/opt/nbrfc/conf/interfaces.cfg is used to describe the network interfaces to be used by NetBIOS and their properties. This file is automatically created during NetBIOS installation, if it does not already exist. In many cases it is not necessary to change this automatically created file.
Page 102 NetBIOS will use only active interfaces to send broadcasts and will only use the IP address of active interfaces. If you do not want Advanced Server for UNIX NetBIOS to use a certain interface, mark it with an active=no entry.
Page 103 Configuring Advanced Server for UNIX used_by_wins= This entry is only important if you plan to run the Advanced Server for UNIX WINS service on a multihomed system, i.e. a system having more than one IP address, since the WINS service must use a unique, well known IP address. Mark the interface you want to be used by the Advanced Server for UNIX WINS service with a line used_by_wins=yes.
Page 104 To activate any changes you made to the NetBIOS configuration: If Advanced Server for UNIX is running, Ê Restart the Advanced Server for UNIX using the commands asx stop; asx start else Restart NetBIOS using the commands Ê...
Page 105 Configuring Advanced Server for UNIX 5.1.2.2 Commands used for configuring network interfaces When configuring network interfaces, the following NetBIOS commands from /var/opt/nbrfc/bin are used: The cr_interfaces command creates the /var/opt/nbrfc/conf/interfaces.cfg configuration file based on the information found in the UNIX system at runtime. The program runs at instal- lation time but it can also be executed manually by the administrator e.g.
Page 106 Configuring Advanced Server for UNIX Use nbconfig either to display the current configuration or to dynamically activate or deac- tivate certain interfaces without having to restart NetBIOS. Syntax: nbconfig -i nbconfig -e | -d <interface_no> [<interface no> ... ] nbconfig -E | -D <interface name> | <ip-address>...
Page 107 To find a particular name, the Advanced Server for UNIX computer first queries its primary and/or secondary WINS server. If the WINS servers are not available or unable to map the name to an IP address, the computer switches to b-node but continues to poll for the WINS servers and switches back if a WINS server becomes available.
Page 108 To configure an Advanced Server for UNIX computer as a WINS client: Ê Edit wins.cfg and fill in the IP addresses of a primary and a secondary WINS server. Any WINS-Server within reach – NT WINS or Advanced Server for UNIX 4.0 WINS – can be used.
Page 109 Be sure to have the NetBIOS tuning parameter NBRFCWINSREG set to 1 if you want Advanced Server for UNIX to register names with WINS servers. If the local machine is running the Advanced Server for UNIX 4.0 WINS service, it is recommended to configure both primary and secondary WINS to point to this WINS, i.e.
Page 110 Configuring Advanced Server for UNIX 5.1.3.2 The names.cfg file The names.cfg file is used to specify static mappings of NetBIOS names to IP addresses, thereby allowing name resolution to cross routers. The function of the names.cfg file is similar to the LMHOSTS file known from Microsoft networking components, although the format differs.
Page 111 # Other backup domain controllers (in remote subnet): otherbdc1 otherbdc2 To configure static names on an Advanced Server for UNIX computer: In /var/opt/nbrfc/conf, copy names.sam to names.cfg. Edit names.cfg and fill in all NetBIOS Ê name mappings that are needed for the the local machine.
Page 112 Configuring Advanced Server for UNIX For the example names.cfg above, the output of the nbtstat -c command is: Name ------------------------------------------------------------------------- TRUSTPDC TRUSTPDC TRUSTPDC.DOM TRUSTPDC.DOM TRUSTPDC.DOM OTHERBDC1 OTHERBDC1 OTHERBDC1 OTHERBDC2 OTHERBDC2 OTHERBDC2 The nbtstat command is fully described below. Static mappings from names.cfg are stored together with registered and cached name in a name table within the kernel.
Page 113 Shows some name resolution statistics. Shows the current WINS configuration. The IP addresses as well as the current state of both primary and secondary WINS server – if configured – are displayed together with the currently used registration type. Purges the local name table and reloads it from names.cfg, if the file exists.
Page 114 Configuring Advanced Server for UNIX Example output of a nbtstat -n command: Name -------------------------------------------------------------------------------------------- EXAMPLE *SMBSERVER EXAMPLE EXAMPLE.DOM EXAMPLE.DOM EXAMPLE~X EXAMPLE#BROW EXAMPLE#DMN EXAMPLE.DOM EXAMPLE.DOM EXAMPLE.DOM ..__MSBROWSE__. Example output of the command nbtstat -q domain.dom -e 1c: NetBIOS name resolution result:...
Page 115 Configuring Advanced Server for UNIX Occasionally it may be helpful to be able to dynamically add and delete certain NetBIOS names from the internal name tables without reloading the complete names.cfg file. This can be accomplished by the addname and delname commands: The addname command dynamically adds one or more NetBIOS names to the local name table of NetBIOS.
Page 116 This section contains simple guidelines for configuring static name mappings for a particular Advanced Server computer in situations where WINS servers are not used. In what follows, “PDC ” denotes a Primary Domain Controller and “BDC ” denotes a Backup Domain Controller.
Page 117 Configuring Advanced Server for UNIX NetBIOS maintains an internal name table for mapping NetBIOS names to IP addresses. This internal name table contains a list of names owned by the local machine a name cache consisting of mappings from recently received NetBIOS datagrams (take NBRFCCACHE entries) and a list of static mappings from a names.cfg file.
Page 118 Normally, name responses are only returned – e.g. by a WINS Server – if the client queried with a unicast datagram (like a WINS client normally does). However, for older clients this behavior might be useful, e.g. when static names from a names.cfg are used to get the functionality of a “static WINS ”...
Page 119 Configuring Advanced Server for UNIX 5.1.5 Configuring NetBIOS Startup Parameters Since AS/X V4.0B, the startup options for nbrfcdaemon are presently configured in the /var/opt/nbrfc/conf/nbrfcdaemon.cfg file. Default is “-l2 -f20 -n”. If the file does not exist, it will be created automatically. Changes to this file are not overwritten during an upgrade instal- lation.
Page 120 In this case, set the entries NfsCheck=1 and UseNfsLocks=0. 5.3 Connecting Advanced Server for UNIX to Logging Advanced Server for UNIX has an interface to Logging. If users wish to use Logging it must be installed and started on the server system.
Page 121 Configuring Advanced Server for UNIX The following sections contain the configuration examples for these files; the Advanced Server for UNIX entries in the log3admin file are highlighted in bold font. ;filename ;-------- default #LOGFILE ;filename Kbyte ;-------- ----- cms_error cmsreport...
Page 122 When configuring disks under UNIX, system administrators can limit the disk space that can be used by “normal” users. Advanced Server for UNIX is configured by default to allow all free disk space to be used by all AS/X users.
Page 123 CreateUnixUser=1 If this parameter has the value 0, all Advanced Server for UNIX users are mapped to a UNIX “lmworld“ user. In this case, the total disk space quota for all Advanced Server for UNIX users must not be exceeded, i.e. if one Advanced Server for UNIX user exceeds the permitted capacity this blocks all other Advanced Server for UNIX users at the same time.
Page 124 Configuring Advanced Server for UNIX Create a directory for this user: Ê cd /home mkdir user1 chown user1 user1 chgrp DOS---- user1 chmod 775 user1 Share the directory: Ê net share user1=c:/home/user1 Ê Assign rights for the user “user1”: net perms c:/home/user1 /grant user1:fullcontrol Ê...
Page 125 Before you can use a spooler with Advanced Server for UNIX, you must configure printer classes / groups and printers. You may only use the printers with Advanced Server for UNIX if it is possible to print from UNIX with the configured printers.
Page 126 -dclass_1 /etc/hosts When sharing the printer, link the name of the printer (here asxp_hpl) with the sharename. For information on sharing a printer with Advanced Server for UNIX, please refer to the “Concepts and Planning” manual. 5.5.2 Configuring SPOOL V4.x The following sections explain how to set up SPOOL V4.x for Advanced Server for UNIX.
Page 127 The name of the spool server is returned to the client by means of a job ID for an executed print job, for example. For accurate identification, the spool server must be assigned a name with a maximum of 7 characters. Use the lowercase letters...
Page 128 Setting up the printer group In order to share the printer with the Advanced Server for UNIX server as a printer queue, you can set up a printer group: In order to prevent problems occurring with the net commands under MS-DOS, a printer group name must consist of a maximum of eight characters.
Page 129 In order to restrict delays in working with SPOOL V4.x on only one PC with Advanced Server for UNIX V4.0, you can change the configuration of Advanced Server for UNIX in such a way that each PC receives its own server process. This is an acceptable solution in particular for smaller configurations.
Page 130 PC program print via this connection. Shared client printer via other servers and clients For information on how to share a printer for the shared client printer on a server or a client, please refer to the relevant manuals. 5.6.1 Setting up the shared client printer This section contains an example for setting up the printer queue for shared client printer and share it with Advanced Server for UNIX.
Page 131 Configuring Advanced Server for UNIX 5.6.1.1 Addclipr Purpose: The addclipr command is used to add an Advanced Server client printer device to the configured spooler. Syntax: addclipr where: clientname printername printertype Not all printers are available for Advanced Server for UNIX on some UNIX systems.
Page 132 You can now use this printer from UNIX with following commands: for Spool V4.x: for the LP spooler: 5.6.2 Delclipr Purpose: The delclipr command is used to delete an Advanced Server client printer device from the configured Spooler. Syntax: delclipr where:...
Page 133 Set the correct values for the DOMAIN, USERNAME, and PASSWORD parameters in the Ê /var/opt/lanman/clipr/config/<Client name> file. Please note that in the case of an OS/2 server, the rights for the shared printer are not set automatically for USERS and GUESTS. Furthermore, blank usernames are not accepted here.
Page 134 Configuring Advanced Server for UNIX If an error occurs, Advanced Server for UNIX or the spool system automatically sets the printer to disabled. The print job for which the error was detected cannot be backed up; it must be repeated. All other print jobs remain in the print queue until the error has been recovered.
Page 135 Configuring Advanced Server for UNIX net start server command You can start the Advanced Server for UNIX processes of the server with the net start server command if you have stopped the server with net stop server beforehand for example. You can thus activate a new configuration for example.
Page 136 During installation a link is set up with rc0.d for stopping the NetBIOS administration process automatically. 5.7.6 Stopping and starting individual services The services of Advanced Server for UNIX are started with asx start for example. You can stop and start the following Advanced Server for UNIX services separately: Start command...
Page 137 Configuring Advanced Server for UNIX 5.7.7 Status display of the Advanced Server for UNIX processes You can display the status of the Advanced Server for UNIX and NetBIOS processes using the asx status command. 5.8 Adapting the configuration For further information on the Advanced Server for UNIX configuration refer to chapter “Advanced Server Registry“...
Page 138 Configuring Advanced Server for UNIX 5.9.1 Call options for compilers and linkers If you wish to use the communication mechanisms of Advanced Server for UNIX for devel- opment purposes, you must include the necessary declaration files required for the API function in the source texts.
Page 139 You can change the following server attributes after the installation: Server name The program setservername is available for changing the name of an Advanced Server. Domain name The program setdomainname is available for changing the name of an Advanced Server domain.
Page 140 With setdomainlang you can change the language of predefined objects within a domain. Ê You must be logged on as the system administrator root to change server attributes. Ê The utility programs for changing the server attributes need to stop the server.
Page 141 -o dos parameter. Check whether this parameter is set if errors occur. You could also configure Advanced Server for UNIX is such a way that both uppercase and lowercase usage is possible. To enable this, set the following parameter in the registry: MixedCaseSupport = 1.
Page 142: System Data Backup
You can stop a printer queue for Advanced Server for UNIX using the command net print /hold. This sets all Advanced Server for UNIX print jobs to the status SUSPEND, including jobs which have been newly spooled via Advanced Server for UNIX. Print jobs spooled via xpadd are not affected.
Page 143 Stopping and restarting print jobs Print jobs can be stopped and restarted using the commands net print <job#> /hold and net print <job#> /release. The status of the specified Advanced Server for UNIX print job is set to SUSPEND or WAIT.
Page 144 The net print <job#> /last command is not implemented for the SPOOLV4 interface. 6.5 Administering using the net admin command This command can be used to administer the specified server. For example, if the backup_2 server is the backup domain controller and primary is the primary domain controller, the command net admin \\backup_2 /command <command>...
Page 145 7 Tools for special tasks Advanced Server for UNIX contains tools for the system administrator, which need only be used in special cases. These tools are described in the sections that follow in relation to particular application scenarios. It is recommended that you first of all read the description of the PC tools and then the description of the tools for NetBIOS, as well as other system administration tools.
Page 146 Tools for special tasks An example of program output is given below: Master Browser found on NetBIOS adapter no ’0’ The Master Browser’s adapter address : 00c095ec91ee The following names are available: ---------------------------------------------------------------------------- 01 CLIENT1’’’’’’’’<20> 02 CLIENT1’’’’’’’’<00> 03 DOMAIN1’’’’’’’’<00> 04 CLIENT1’’’’’’’’<03> 05 DOMAIN1’’’’’’’’<1e>...
Page 147 Tools for special tasks The example below shows the output: NetWkstaGetInfo returned 0 LanMan Root Computer Name User Name Lan Group LanMan Version Logon Server Workheuristics SessionTimeout Char Wait Char Time KeepConnections : 600 KeepSearch Max Threads Max Commands NumWorkBuf...
Page 148 Tools for special tasks 7.2 Tools for NetBIOS The following scripts are used for NetBIOS administration. 7.2.1 /var/opt/nbrfc/bin/findbrow This tool helps you to find the Master Browser in a subnetwork for a given domain or workgroup. If found, it lists the master browser’s name table. In contrast to the PC tool of the same name, the UNIX findbrow command can locate a Master Browser both within a local and remote subnetwork.
Page 149 Tools for special tasks NetBIOS Remote Machine Name Table Name --------------------------------------------- SERVER1 SERVER1 *SMBSERVER DOMAIN1 DOMAIN1 SERVER1~X SERVER1#DMN DOMAIN1 SERVER1#BROW DOMAIN1 DOMAIN1 ..__MSBROWSE__.<01> MAC Address = 00-00-00-00-00-00 IP Address = 111.111.111.111 The display shows the NetBIOS name table of the machine which is the master browser for DOMAIN1 in the corresponding subnetwork - in this case the machine is called SERVER1, a primary domain controller.
Page 150 Tools for special tasks 7.2.2 /var/opt/nbrfc/bin/mv_names The mv_names command is used during an update installation of the nbrfc package to convert the configuration of the name table. The NetBIOS name mappings contained in the [ NBRFC ] section of an old style nbrfc.cfg configuration file (used by NetBIOS versions <=3.5A) are written to the names.cfg file.
Page 151 7.3.1 Access permissions in Advanced Server for UNIX Advanced Server for UNIX stores access permissions for files and directories in its ACL database in the /var/opt/lanman directory. In contrast to UNIX permissions, which are stored with each file and directory in the file system, permissions are stored centrally in Advanced Server for UNIX.
Page 152 Tools for special tasks Another option here is to use the accget and accadm programs, which can be used in conjunction with UNIX mechanisms, for example for restoring access permissions following a system crash. Only the access permissions are saved and restored in this case, and not the actual files and directories.
Page 153 Version 3.5B00. The user/group names are stored as readable character strings according to net perms output. The server has to be started if this option is selected. The access permissions for all resources are stored with <user / group SIDs>...
Page 154 Tools for special tasks Saving / restoring of an ACL database with SIDs makes sense only within the domain in which they have been created. After a new installation or after a change of the user/group configuration, the internal representation of the same name has a different SID.
Page 155 Tools for special tasks The ACL database (net ’p’erm) is updated with the content of the /var/opt/lanman/etc/accadm.dat file. New entries are added here, existing entries are updated, and unaffected entries are left as are. The files and directories must exit in a mounted filesystem.
Page 156 UNIX commands. In doing so, the access permissions of the files and directories, which are stored in the Advanced Server for UNIX ACL database, are not adapted automatically. This task is performed by the acladm program ("-M" option). The Advanced Server for UNIX has to be stopped during this process.
Page 157 7.3.5 Saving the user configuration (userget) This tool backs up the current user configuration and group configuration for the specified system. The command can be invoked for the local system or for a remote server. The /var/opt/lanman/etc/useradd.sh_local or /var/opt/lanman/etc/useradd.sh_<name of server> file created can be used for restoring a configuration.
Page 158 Tools for special tasks 7.3.6 Adding and removing server names (addserver/delserver) You can use the addserver command to add an additional server name on a system, in order to enable the clients to access the server with the newly added name.
Page 159 In order to be able to send a mail, the asxpwexp.usr configuration file must be available and provide a mapping between Advanced Server for UNIX users and a mail address for these users. If there is no specific information to be provided to the user, a standard notification is sent.
Page 160 AS/X configuration is up to date. For example, if you change the AS/X MixedCaseSupport registry parameter to a different value than that at Advanced Server runtime, it may happen, for example, that acladm -P will delete too many ACL entries.
Page 161 /var/opt/lanman/bin/blobadm -q -A The method of compressing the ACL database using the accget and accadm utilities is no longer recommended from Version 4.0A of Advanced Server for UNIX. Since the programs work on a higher level than the blobadm program, it may happen in certain configurations that the ACL database is not optimally compressed or even becomes larger in certain exceptional cases.
Page 162 The nbconfig tool is responsible for implementing this. 2. Activate and deactivate additional server names: In the event of a system failing, an additional server name is activated online and then deactivated again before the failed system is rebooted to enable the alternative system to be accessed using the same NetBIOS name as the failed system.
Page 163 Tools for special tasks 7.5.1 Constraints on high availability The following conditions must be fulfilled in order to ensure the concept outlined here of high availability for systems: – Both servers must be operated in one domain. – If a system fails, a “reconnect” is necessary for the PCs connected (and possibly also a restart).
Page 164 Tools for special tasks 7.5.2 Example of how this works Procedure when a system fails: System A fails, System B continues to operate: 1. Activate additional B controller with the IP address of A. 2. Switch disks. 3. Provide resources (from A) on the active system (B). These resources must be identical.
Page 165 Workstation computer. Instructions on how to install AS/U Administrator on Windows NT Workstation computer. Instructions on how to install Windows NT Server Tools on a Windows 95/98 client computer. Useful information about running Windows NT Server Tools on Windows 95/98.
Page 166 TCP/IP for Windows for Workgroups 3.11 (requires 1 diskette) Update for Windows for Workgroups 3.11 (requires 1 diskette) You can create installable client diskettes at the Advanced Server command prompt by using the Advanced Server makeclients command or connecting an MS-DOS client to the MSCLIENT share and using the MS-DOS copydisk command.
Page 167 Connect to the MSCLIENT share on the Advanced Server by typing the following Ê command at the DOS prompt: net use <d:> \\<servername>\msclient Replace <d:> with the drive letter and <servername> with the name of the server. Ê Change to the drive <d:> that connects to the MSCLIENT share. Ê...
Page 168 Use the Network Client Administrator to perform the following tasks: Create a network installation startup disk. With this single disk, you start a client Ê computer, connect to a server that stores installation files, and install the full network software from that server. Ê...
Page 169 Before you can create network installation startup disks for Windows 95/98 or Windows for Workgroups, you first must create a folder on the installation server in the shared clients folder (/var/opt/lanman/shares/msclient by default) and then copy to it the appropriate source files.
Page 170 Regardless of the client software you are installing, the startup disk begins by starting Microsoft Network Client so that it can connect to the server. The network card and its settings are not automatically detected. You must select the correct NIC driver and configure it appropriately.
Page 171 Workstation computers. To install Windows NT Administrative Tools Ê 1. From a Windows NT Workstation computer, log on to the Advanced Server domain. 2. Establish a connection to the ASTOOLS or the ASTOOLSD shared resource on Advanced Server. 3. In the astools or astoolsd directory, click on directory that corresponds with the software that your computer is running.
Page 172 6. Select the Windows Setup tab. 7. Choose the Have Disk button. Specify the directory \Win95 on the network drive (there must be a srvtools.inf file in this directory) that contains the Windows NT Server Tools. Choose OK. 8. Click on the box next to the Windows NT Server Tools entry.
Page 173 Logging on for Windows NT Server Tools If you are not logged on and you start any of the programs in Windows NT Server Tools, you will receive a message that says that the computer is not logged on to the network.
Page 174 Installing Network and Administrative Client Software 8.3.3.4 Using Event Viewer Use the following procedure to use the Event Viewer in Windows NT Server tools on a computer running Windows 95/98. To use Event Viewer on a computer running Windows 95/98 Ê...
Page 175 Main group of Program Manager is simply a shortcut to the Printers list in My Computer. Using File Manager (WINFILE.EXE) in Program Manager. Installing Windows NT Server Tools does not add a Security menu to File Manager as it does for Windows 3. x . 8.3.3.8 Removing Windows NT Server Tools From Windows 95/98 Use the following procedure to remove Windows NT Server Tools from a computer running Windows 95/98.
Page 176 Installing Network and Administrative Client Software 4. Select the Install/Uninstall tab. 5. If you have installed Windows NT Server Tools as described earlier in this section, then you should see the Windows NT Server Tools entry in the Uninstall list. Select it and click on Add/Remove.
Page 177 The system displays the Windows NT Server Tools Setup Program window on the client computer. Click on Continue. Ê Select the Install all files button. Windows NT Server Tools will be installed at the root drive in the srvtools directory. The srvtools directory is created for you. Ê...
Page 178 Installing Network and Administrative Client Software 7. During the installation of Windows NT Server Tools, the Setup program created the new-conf.sys and new-vars.bat files in the workstation’s srvtools directory. Each of these files contains lines that you must copy to the client computer’s config.sys and autoexec.bat files as follows:...
Page 179 / var/opt/lanman/bin and /var/opt/lanman/etc directory. The command makeclients is installed with the msclients package). Net Command — lists the Net commands that are available to administer Advanced Server at the command prompt. 9.1 Advanced Server Commands You can use UNIX system commands at the Advanced Server command prompt to perform several administrative tasks.
Page 180 Access Control List (ACL) database. Used to add an Advanced Server client printer device to the configured spooler. Used to add a server name on a system, in order to enable the clients to access the server with the newly added name.
Page 181 Product Manual Advanced Server Commands Description Schedules commands or programs to run on a server at a specified time or date. (Note there also exists UNIX system and MS-DOS at commands.) Manipulates the Advanced Server share list without server intervention.
Page 182 Used to change the domain name of the local Advanced Server. Changes the output language of net commands, elfread and the Event-Viewer. Used to change the name of the local Advanced Server. Configures the UNIX system spooler for the Advanced Server. Converts the coding of characters from Shift-JIS (S-JIS) to Extended UNIX Code (EUC) encoding.
Page 183 When you administer a server while you are working at the server command prompt, that server is called the local server. If you are administering a server from the command prompt of another server, the server being administered is called the remote server.
Page 184 Net commands. The prompt changes to include the name of the server you are remotely administering, for example, \\ payroll . Any Net command that you type at this prompt executes on the server that you specify. For example, at the prompt, type:...
Page 185 This allows you to keep your password confidential, providing added security. If you forget to type a password with a command that requires one, the Advanced Server prompts you for it. Depending on the command that you type, the Advanced Server also may prompt you for other pertinent information such as your user name.
Page 186 Some Net commands require confirmation. The /yes and /no options help expedite Net commands. When Advanced Server reads one of these options, it does not pause to display the corresponding prompt. Instead, Advanced Server accepts the /yes or /no option as your response to the prompt.
Page 187 ( & ). When you are at the UNIX system command prompt typing a name with a special character in an Advanced Server command, you must use an escape character (the back slash [ \ ]) before each special character. If you are at a client computer, you can surround the string containing the special characters in double quotes.
Page 188 \\product\data 9.2.2 Understanding Command Syntax The commands that are used in Advanced Server will be easier to understand and use if you keep the following concepts in mind: When an option is enclosed in braces ( { } ), the option is a required item in the syntax statement.
Page 189 Administering Advanced Server at the Command Prompt 9.2.3 Getting Help on Net Commands On-line help is available for all of the Net commands that you can enter at the server command prompt. It provides command parameters, syntax, details about a command, and examples of the command in use.
Page 190 Displays the names of all files opened via the Advanced Server and the number of file locks, if any, on each file. This command also can be used to close files. When used without options, this command lists all of the open files at a server.
Page 191 Lists or disconnects sessions between a server and clients. When used without options, this command displays infor- mation about all of the sessions with the local server. This command also can be typed as net sessions. Creates, deletes, modifies, or displays shared resources.
Page 192 Advanced Server WINS computers, and with WINS for Windows NT systems. Advanced Server WINS is managed by the same Windows NT-based tool that is used to manage WINS for Windows NT. This allows both Advanced Server-based and Windows NT-based WINS servers to be managed from a single administrative tool on a single computer in the network.
Page 193 TCP/IP internetworks: Windows Internet Name Service (WINS) A computer can use WINS if at least one WINS server is available that contains a dynamic database that maps computer names to IP addresses. WINS can be used in conjunction with broadcast name resolution for an internetwork where other name resolution methods are inadequate.
Page 194 For more information about the LMHOSTS file, see Windows NT Help and the Microsoft Windows NT Resource Kit Networking Guide. On a computer running Advanced Server, a names.cfg file can be used in a way compa- rable to the LMHOSTS file, see section Advanced Server networking components never use HOSTS files for name resolution.
Page 195 The two most common node types for Windows client computers are h-node and b-node. For DHCP users, the node type is assigned by the DHCP server. When WINS servers are in place on the network, NetBT resolves names on a client computer by communicating with the WINS server.
Page 196 The h-node mode does more than change the order for using b-node and p-node. If the WINS server is down — making broadcast messages a necessity — the computer continues to poll the WINS server. When the WINS server can be reached again, the system returns to p-node.
Page 197 LMHOSTS file. If a b-node attempt fails, the system looks in LMHOSTS to find a name and then uses the associated address to cross the router. On computers running Advanced Server, this variation corresponds to the Siemens modified b-node where the mappings from a names.cfg file are used before or after the b-node attempt (section However, each computer must have these files which creates an administrative burden in maintaining and distributing the files.
Page 198 To allow browsing across routers without WINS, the network administrator must ensure that the users’ primary domain has Advanced Server, Windows NT Server, or Windows NT Workstation computers on both sides of the router to act as master browsers. These computers need correctly configured LMHOSTS / names.cfg files with entries for the domain...
Page 199 Subnet 1 Example of an Internetwork with WINS Servers The proxy communicates with the WINS server to resolve names and then caches the names for a certain time. The proxy serves as an intermediary either by communicating with the WINS server or supplying a name-to-IP address mapping from its cache.
Page 200 Client C may already have the requested information in cache. If so, Client C responds directly to Client A without going to the WINS server. Both examples assume that the requested information is available in the WINS database on the server. Product Manual...
Page 201 If WINS is enabled on the client: The name registration request is sent directly to the WINS server to be added to the database. A WINS server accepts or rejects a computer name registration depending on the current contents of its database, as follows: If the database contains a different address for that name, WINS challenges the current entry to determine whether that device still claims the name.
Page 202 An entry defined as static never expires. If the entry is owned by the local WINS server, the name is released at the specified time unless the client has renewed it. If the entry is owned by another WINS server, the entry is revalidated at the specified time.
Page 203 WINS server, which changes the state of the related database entry from active to released. If the entry remains released for a certain period of time, the WINS server marks it as extinct, updates the version number, and notifies other WINS servers of the change.
Page 204 5. Try DNS (Microsoft only) To find a particular computer, the client first checks its NetBIOS name cache (see above). If the name is not found, the computer queries its primary and / or secondary WINS server: Product Manual Name Resolution Services...
Page 205 Implementing WINS 1. In the following illustration, a client name query request is sent first to the WINS server. If the name is found in the WINS database, then the client can establish a session based on the address mapping received from the WINS server.
Page 206 WINS proxy queries a WINS server for the name-to-IP-address mapping. If a WINS server is not available on the local subnet, the WINS proxy can query a WINS server across a router. The WINS proxy caches (stores in memory) computer name-to-IP- address mappings it receives from the WINS server.
Page 207 Windows NT documentation. Dial-up Windows 95/98 and Windows NT computers that are configured to route TCP/IP and use WINS can access remotely their networks for services, including Advanced Server and Windows NT file and print sharing, electronic mail, scheduling, and database access.
Page 208 The number of WINS servers that an enterprise requires is based on the number of WINS client connections per server and the network topology. The number of users that can be supported per server varies according to usage patterns, data storage, and processing capabilities of the WINS server computer.
Page 209 WINS database. Any server (either NT Server or Advanced Server for UNIX) usually registers more NetBIOS names than other WINS-enabled clients. The name registration requests generated by a...
Page 210 IP address that is currently in its database for this name (Name Query packet, 92 bytes). When there is no reply, as can be expected in this case, the WINS server repeats the challenge two more times and then updates the name registration entry with the new IP address and a new version ID.
Page 211 The frequency of WINS database replication between WINS servers is a major planning issue. The WINS database should be replicated frequently enough that the down-time of any WINS server will not affect the reliability of the mapping information in the database of other WINS servers.
Page 212 10.2.2.1 Planning for Replication Convergence Time The time needed to replicate a new entry in a WINS database from the WINS server that owns the entry to all other WINS servers on the network is called convergence time. When planning for WINS servers, you need to decide the acceptable convergence time for your network.
Page 213 WAN. Another option is to set up a chain of WINS servers, where each server is both the push partner and pull partner with a nearby WINS server. In such a configuration, the two servers at the ends of the chain would be push and pull partners with each other.
Page 214 NBRFCWINSREG NBRFCPRELOAD 3. An Advanced Server running the WINS service (as well as every other WINS server) must be configured with static (not dynamic) IP addresses; they should not be DHCP clients. If your Advanced Server computer is a multihomed computer (a computer having more than one IP address), you have to decide which of the IP addresses shall be used by the WINS server.
Page 215 In an Advanced Server for UNIX networking environment, the availability of the WINS service can become an important aspect. Therefore, unlike other services within Advanced Server, the WINS Service is to some degree able to run independent of all other services, although there are some restrictions concerning administration.
Page 216 WINS service. In the contrary the net stop server command ends all other services except the WINS service. Without a running Server service the WINS service continues to work - with restrictions: it is no more manageable with the WINS manager, however it continues to support name registrations, name queries, etc.
Page 217 To use WINS Manager, both Advanced Server and WINS must be running. Use WINS Manager to view and change parameters for any WINS server on the network for which you have Administrator privileges. WINS Manager Help is organized to provide information for each of the specific administrative and configuration tasks that you need to perform to manage WINS servers.
Page 218 The WINS server adjusts the values specified by the administrator to keep the inconsistency between a WINS server and its partners as small as possible. The defaults for the four configurable timer values have been chosen with care and in general they should not be modified.
Page 219 Specifies that replication occurs only with configured WINS pull or push partners. If this option is not checked, an administrator can ask a WINS server to pull or push from or to a non-listed WINS server partner. By default, this option is checked.
Page 220 Replication is triggered when a WINS server polls another server to get replicated infor- mation. This can begin when the WINS server is started, and is repeated based on the configured update count or time interval, or by using WINS Manager to start immediate replication.
Page 221 WINS administrator using WINS Manager. A push partner is a WINS server that sends a message to its pull partners that the WINS database has changed. When the pull partners respond to the message with a replication request, the push partner sends a copy of its new WINS database entries to the pull partners.
Page 222 (which might not be capable of registering names with a WINS server) with a query to the WINS Server without having to resort to secondary resolution methods. Second, it prevents the WINS server from allowing another node to dynamically register the name.
Page 223 Implementing WINS Static NetBIOS name mappings can be any of the types listed in the following table. Type option Unique Group Domain Internet group Multihomed Product Manual Description A unique name that maps to a single IP address. Contrast with multihomed type. Also referred to as a “Normal Group.”...
Page 224 During the process of importing static mappings, WINS Manager first connects to the server (not WINS) and tries to create temporary files under the C$ share. The C$ share is the root ( / ) share. Generally, the root directory on the UNIX system is “read-only.”...
Page 225 By default, the Show Database dialog box shows all mappings for the WINS database on the currently selected WINS server. You can select a Sort Order option to sort by IP address, computer name, time stamp for the mapping, version ID, or type. To view only a range of mappings, choose the Set Filter button.
Page 226: Backing Up The Database
Help. In addition to the backups that occur automatically, you may wish to perform manual backups. You can back up the WINS server database using the Advanced Server winsadm command, regardless of whether the WINS service is running or not:...
Page 227 The local WINS database should be cleared periodically of released entries and old entries that were registered at another WINS server and replicated to the local WINS server, but for some reason did not get removed from the local WINS database.
Page 228 10.7.4 Compacting the WINS Database There is no built-in limit to the number of records that a WINS server can replicate or store. The size of the database is dependent on the number of WINS clients on the network. The WINS database grows over time as a result of clients starting and stopping on the network.
Page 229 Ê messages. Even if the WINS service is running (but the SERVER service is not), you may get a message like ”The Windows Internet Name Service is not running on the target machine or the target machine is not accessible”.
Page 230 Implementing WINS To discover why a WINS server cannot pull or push replications to another WINS server Use the ping utility to verify that each WINS server is running and is available to Ê establish a connection. Ensure that each server is correctly configured as both a pull or push partner: Ê...
Page 231: Troubleshooting
Administrators often can reduce the amount of time required to solve problems by observing the following guidelines: Be aware of and familiar with the tools and services that can be used for server trouble- shooting. Configure the available server utilities to gather the necessary data as a general practice.
Page 232 11.1.1.1 Event Viewer A number of events related to the daily operation of the server can be tracked using Event Viewer. These events are maintained in one of three event logs: system, security, and appli- cation. Administrators should develop and implement an event logging policy and include a review of event logs as a regular part of troubleshooting activities.
Page 233 Advanced Server command prompt. This command provides cumulative totals for a variety of server activities. Administrators who review the server statistics provided by using this command on a regular basis will find it easier to recognize and address changes in server operation.
Page 234 Closing Sessions An administrator can disconnect a user from the server at any time. Closing a user session does not prevent the user from reconnecting. To disconnect a user session from a Windows NT computer or from a Windows client Ê...
Page 235 An administrator should check these log files periodically to determine whether any such errors are occurring. The logs can be accessed from a client computer by linking to the PRINTLOG shared resource. The logs also can be accessed from the server. They are in the following directory: /var/opt/lanman/shares/printlog. 11.1.1.6...
Page 236 11.1.2.1 Alerter Service Advanced Server includes an Alerter service which can be used to notify specified users of the occurrence of a particular event. An administrator should use this service in order to make server problems known immediately. Prompt action to resolve server problems often can minimize their effect.
Page 237 The lmstat command interrogates the server’s shared memory image to gather a variety of data about the current state of the server. This command is especially useful when you want to determine which server process a client session is on.
Page 238 Troubleshooting How does the administrator know to which lmx.srv process a client is connected? Executing the lmstat -c command at the server prompt usually provides the answer. The system displays output similar to the following: Clients: BANANA~X (nwnum=0, vcnum=0) on 19916...
Page 239 11.1.3.6 srvconfig The srvconfig command is used to display the current default settings of all the server parameters in the lanman.ini file. (It also is a good way to check the location and spelling of any parameter you wish to modify.) The lanman.ini file contains several parameters that you can modify to change.
Page 240: Troubleshooting Procedures
The asxinfo command can be used to list information of relevance for the configuration and operation of Advanced Server for UNIX and NetBIOS. In contrast to asxcheck, no check is performed. The information is written to the text file $xASX/logs/asxinfo.<pid>.
Page 241 <name>. Reviewing all of the modules involved in the end-to-end connection between a client and Advanced Server, it is easy to see that isolating a problem is the first step for problem solving in a client-server networking environment.
Page 242 “see” each other from the perspective of a transport protocol. Most transport protocol applications include a connectivity test tool that can be used to verify connectivity at the transport level between a client and the server over the network.
Page 243 Operating system problems usually will affect all or most client computers connected to the server. Do not spend much time on this step if you are troubleshooting an individual client problem. Step 5: Isolating Problems on the Advanced Server If you determine that all of the underlying software is functioning properly, then you should check Advanced Server for problems.
Page 244 These are described in the following sections. Is the Server Running? It is worthwhile to verify that the server is actually running. You can do this easily by entering the following command at the system command prompt:...
Page 245 Depending on how your server is configured, there may be a core file located on your system. If the value of the CoreOk keyword is set to 1 (yes) in the Advanced Server Registry, then a core file is located somewhere on the system. The CoreOk value is in the following key:...
Page 246 Never attempt to delete or re-share these resources. If any of these resources are absent, the server will not function properly. If you detect that one of these resources is missing, stop and restart the server to determine whether they are shared at server startup. If they are not displayed, contact your service representative.
Page 247 Can the Server be Contacted From a Client? Attempt to log on to the server from a client computer. If the logon is successful, link a virtual drive ID to a shared resource. Then, view the contents of the linked drive.
Page 248 DOSUTIL and OS2UTIL shared directories. An Advanced Server is a computer that also is running the UNIX operating system. All of its files also are UNIX system files with their own set of UNIX system access permissions.
Page 249 Advanced Server access permissions grant access. For example, if a user has Advanced Server change permission for a file, then this file needs to have the UNIX system equivalent of change permission (RWX) in order for the user to perform all of the operations allowed by the Advanced Server change permission (read, write, create, and execute).
Page 250 If the protection of Advanced Server files provided by UNIX system permissions can be ignored, and if it is appropriate to rely solely on Advanced Server permissions to manage file access, you can set the IgnoreUnixPermissions keyword to 1 (ignore UNIX system permissions) in the Advanced Server Registry.
Page 251 Restricting access to others does not affect your own access to the files and directories. When a user attempts to access a file or directory, access to the server is allowed or denied depending on the permissions assigned to that user.
Page 252 Problem The display that results from executing a net view command from a LAN Manager server does not contain any of the Advanced Server computers that are in the domain. Product Manual...
Page 253 Troubleshooting Resolution Edit the Advanced Server Registry to change the value of the LmAnnounce keyword to 1 (yes). Advanced Server then will broadcast LAN Manager-style server announcements. The LmAnnounce keyword is in the following key: System\CurrentControlSet\Services\LanmanServer\Parameters The server must be stopped and re-started for the change to take effect.
Page 254 Problem There is no separator page. Resolution You cannot use Windows NT to create separator pages in Advanced Server. Use the net print command at the Advanced Server command prompt to create and modify separator pages. Product Manual Solving Printing Problems key.
Page 255 Troubleshooting Problem Print jobs in the queue are not printing. Resolution 1. Verify that the printer cable is connected according to the printer manufacturer’s instruc- tions. 2. Verify that the printer is turned on, selected (on-line), has paper, is not jammed, and has no other obvious problems.
Page 256 If you are using a file system other than those recognized by Advanced Server, it will be treated as an s5 file system. If you want all of your unknown file systems to be treated as a type other than s5, set the fsnosupport parameter in the [ fsi ] section of the lanman.ini file to the name of a recognized...
Page 257 AS/X uses a different character set following an update of LAN Manager/X V2.0 or V2.2 or Advanced Server for UNIX V3.51A10. As a result, Advanced Server for UNIX file and directory names can no longer be displayed by the client after an update. A utility is supplied with Advanced Server for UNIX which renames file and directory names containing umlauts such that these names correspond to the new character set.
Page 258 12 Advanced Server for UNIX - directories and files Following the installation of the network and server software, the following additional paths are created on your system: /var/opt/nbrfc /var/opt/lanman (contained in the environment variable $xASX) The following sections list the most important Advanced Server for UNIX files: Path: /etc/ init.d/asx...
Page 259 Advanced Server for UNIX - directories and files Path: /opt/ readme/asx.D/ readme/asx.GB/ Path: /usr/bin/ dos2unix euctosjis findbrow lmpaths lmshell midl nbrfc nbrfcdiag nbtstat sjistoeuc unix2dos uuidgen wins Path: /usr/include/ sys/nbrfc.h Product Manual Comment Readme/manual information (German) Readme/manual information (English) Comment...
Page 260 Advanced Server for UNIX - directories and files Path: /usr/lib/ libasu437.so libasu850.so libasulang.so libasusec.so libasusjis.so liblmx.so liblmxpsi.so libmsrpc.so libnbdns.so librpcapi.so libsam.so libtask.so msrpc/ip_tcp.so msrpc/np.so snmpd/lib/lmxext.so snmpd/mibs/lmxext.mib Path: /usr/share/ man/mrd/catman/asx/ Path: /var/opt/ prntfault Product Manual Comment Link to /var/opt/lanman/lib/libasu437.so Link to /var/opt/lanman/lib/libasu850.so Link to /var/opt/lanman/lib/libasulang.so...
Page 261 Advanced Server for UNIX - directories and files Path: /var/opt/lanman/ clipr/ customs/ debug/ domains/ include/ lanman.ini lanman.old mailslot/ msgfiles/ readme regfiles/ samsave/ sharefile.old spool/ timex/ wins/ Path: /var/opt/lanman/addon/ psaddon/lp_ops.so psaddon/xpr_ops.so Path: /var/opt/lanman/bin/ acladm addclipr asuconfig Product Manual Comment Directory for shared client printer...
Page 262 Sends messages about print jobs to workstations Administrator command for changing the server domain configuration Starts a program on the server at a particular time Program with the functionality of net helpmsg Script for setting internal environment variables Program with the functionality of net share...
Page 263 Used internally by the installation script Mapping of Advanced Server for UNIX users to UNIX users Microsoft Interface Definition Language Compiler for UNIX Not used by Siemens Advanced Server for UNIX Advanced Server for UNIX command interface Sends alerts Sends print alerts...
Page 264 Administration script for Spool 4.x interface Comment: Directory with Advanced Server for UNIX data Backup of the LAN Manager/X 2.x database LAN Manager/X 2.x database, not used by Advanced Server for UNIX ACL database of Advanced Server for UNIX (access control list)
Page 265 Product Manual Comment: Directory for additional Siemens files Administration program for saved permissions Created by accget Administration program for saving permissions Temporarily adds another servername Tool for checking installation / configuration of AS/X and NetBIOS...
Page 266 Product Manual Comment: Directory for additional Siemens files Administration program for saving users and groups Comment Link to /var/opt/lanman/bin/asx Only required if pre-installed at factory Start/stop script for the server Start/stop script for the WINS service...
Page 267 Daemon process for Netlogon service SNMP daemon program (in the asxsnmp package) Program for the Netrun service Program for the Net-View Alerter service (not supported by Siemens Advanced Server for UNIX) Program for the Replication service Program for the WINS service Comment:...
Page 268 Advanced Server for UNIX - directories and files Path: /var/opt/nbrfc/ addname cr_config delname get_config readme Path: /var/opt/nbrfc/bin/ Comment .nbrfc_autoconfig add_interfaces32 add_interfaces64 add_interfaces add_names addname addwins cr_interfaces del_names delname delwins findbrow get_config mv_names names2lm nbconfig nbrfc nbrfcdaemon nbrfcdiag32 nbrfcdiag64 Product Manual...
Page 269 Advanced Server for UNIX - directories and files Path: /var/opt/nbrfc/bin/ Comment nbrfcdiag nbtstat32 nbtstat64 nbtstat Path: /var/opt/nbrfc/conf/ interfaces.cfg names.cfg names.sam nbrfcdaemon.cfg wins.cfg wins.sam Path: /var/opt/nbrfc/lib/ libnbdns.so Product Manual Equivalent to nbrfcdiag32 or nbrfcdiag64, depending on the system NetBIOS status display (32-bit)
Page 270 Description of AS/U Administrator. Descriptions of the Advanced Server Registry keys and values. For information about the Advanced Server parameters that are stored in the lanman.ini file and how lanman.ini file parameters are mapped to Advanced Server Registry keys, see chapter “Lanman.ini...
Page 271 Advanced Server Registry 13.1 Advanced Server Registry Structure The Advanced Server Registry is a database organized in an hierarchical structure. It is composed of subtrees and their keys, and value entries. A key also can contain additional subkeys . The following table identifies and defines the Advanced Server Registry subtrees.
Page 272 For example, for the following value, the string %SystemRoot% will be replaced by the actual location of the directory containing the Advanced Server system files: File : REG_EXPAND_SZ : %SystemRoot%\file.exe A multiple string. Values that contain lists or multiple values in human readable text are usually this type.
Page 273 13.2 Using Registry Editor 13.2.1 Connecting to a Remote Registry To edit the Advanced Server Registry using the Windows NT Registry Editor, you must connect to Advanced Server from the Registry Editor of a remote Windows NT computer. To do so, use the Select Computer command in the Registry menu of the Registry Editor.
Page 274 Advanced Server Registry 13.2.2 Viewing the Registry Registry Editor displays the subtrees of the Registry. The hierarchical structure that appears in Registry Editor is similar to the hierarchical directory structures of Windows NT Explorer. Your ability to make changes to the registry using Registry Editor depends on your access permissions.
Page 275 Advanced Server Registry 13.2.2.1 Registry Editor Commands As shown in the following figure, Registry Editor displays data in two panes. The value entries in the right pane are associated with the selected key in the left pane. You can use the mouse or commands to manipulate the windows and panes in the Registry Editor in the same way as in the Windows NT Explorer.
Page 276 Collapse a branch of a selected registry key. Press 13.3 Using AS/U Administrator You can modify many of the values in the Advanced Server Registry using the AS/U Administrator. Using this tool allows you to modify specific keys in the registry which govern the performance of Advanced Server.
Page 277 Advanced Server Registry The following table lists the policies and their associated Advanced Server Registry keys that can be modified using AS/U Administrator. Policy Alerter Service Computer Browser (SYSTEM\CurrentControlSet\Services\Browser\Parameters) Service Connected Clients (SYSTEM\CurrentControlSet\Services\Netlogon\Parameters) File Name Space (SYSTEM\CurrentControlSet\Services\AdvancedServer\ Mapping Netlogon Service (SYSTEM\CurrentControlSet\Services\Netlogon\Parameters)
Page 278 Advanced Server Registry UNIX Account Mapping UNIX File System (SYSTEM\CurrentControlSet\Services\Advanced Server\ Integration UPS Service Users Alerts Product Manual (SYSTEM\CurrentControlSet\Services\AdvancedServer\ FileServiceParameters) CreateUnixUser FileServiceParameters) IgnoreUnixPermissions UnixDirectoryCheck UnixFilePerms UnixDirectoryPerms UseUnixLocks RootOwnsFilesCreatedOnNFS (SYSTEM\CurrentControlSet\Services\UPS\Parameters) IgnoreSIGPWR PowerFailAddress PowerFailMessage PowerMessageInterval (SYSTEM\CurrentControlSet\Services\AdvancedServer\ AlertParameters) AlertAdminOnLicenseOverFlow AlertUserOnLicenseOverFlow (SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters) AccessAlert ErrorAlert...
Page 279 You may want to modify these values directly using the AS/U Administrator or a registry editor. You do not need to be concerned with every key in the Advanced Server Registry; only those keys that you may have reason to change are described.
Page 280 Advanced Server Registry Registry Path: (where <logfile> is System, Application or Security) SYSTEM\CurrentControlSet\Services\EventLog\<logfile> \MaxSize \Retention Registry Path: SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters \SrvComment \SrvAnnounce \Hidden Registry Path: SYSTEM\CurrentControlSet\Services\Netlogon\Parameters \Pulse Registry Path: SYSTEM\CurrentControlSet\Services\Replicator\Parameters \ExportList \ExportPath \GuardTime \ImportList \ImportPath \Interval \Pulse \Replicate \UnixDirectoryGroup \UnixDirectoryOwner \UnixFileGroup \UnixFileOwner...
Page 281 You can change the value of this key using the AS/U Administrator. AlertUserOnLicenseOverflow Specifies whether the server sends a message to a client that tried to link but failed when the maximum allowable number of clients was exceeded. Default: 0 (message will not be sent) You can change the value of this key using the AS/U Administrator.
Page 282 Default: 10 13.5.2 File Service Parameters Entries The Registry path that contains entries for the Advanced Server file service is as follows: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \AdvancedServer\FileServiceParameters AclCacheSize Specifies the number of entries in ACL cache which keeps track of the results or recent access checks performed on Advanced Server resources.
Page 283 Default: 1 (create new access control list) ForceFileAcl Determines whether the Advanced Server will create an access control list for a newly- created file if an explicit access control list was not provided by the client computer. If an access control list is not created, one will be inherited automatically from its parent directory whenever it is needed.
Page 284 Some clients might get a timeout while Advanced Server is allocating the disk space. If a very large file is copied from an NT client to an Advanced Server share and the file sizes exceeds MaxZeroFillInKB, all of the disk space for that big file will not be allocated on the Advanced Server machine.
Page 285 The interval of time (in seconds) that the server waits for acknowledgment from a client of an "oplock" broken notification. Default: 30 ReadAheadCount The number of sequential file accesses by a client that the server must detect before it begins reading ahead. Default: 2 Product Manual...
Page 286 Determines whether the server will force changes to the access control list (ACL) file to be written to disk using an fsync(2) system call or whether the server will permit the operating system to write the changes to disk normally.
Page 287 The number of least-recently accessed open files that the server closes transparently to avoid reaching the UNIX system’s per-process limit. The server uses a technique called file descriptor multiplexing to allow clients to open far more files than the per- process limits would normally allow.
Page 288 Specifies whether the server tries to set UNIX system record locks in files as requested by clients. Record locks may not work on NFS files on a server running NFS. If the value of the UseUnixLocks key is 0, this feature has no effect on the server.
Page 289 (because the response is delayed), but the server can report disk full errors to clients. If UNIX system writes are performed after the response is sent, disk full errors during write SMBs are not reported to the client.
Page 290 Advanced Server Registry 13.5.3 Net Administration Parameters Entries The Registry path that contains entries for the Advanced Server Net Administration is as follows: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \AdvancedServer\NetAdminParameters NetAdminGroupName The UNIX system group name assigned to the net admin \\servername /c command. Default: DOS----...
Page 291 BigEndianLuidCompatibilityMode REG_DWORD 0 or 1 This keyword only applies to to big-endian Advanced Server implementations like Siemens Advanced Server for RM systems. When the value of this keyword is set to 0, big-endian Advanced Server return security privilege information to the client only in INTEL byte order.
Page 292 Default: De_DE.88591 MaxDirectoryBufferSize The maximum size of a buffer that the server will use for a getdents(2) system call to read the contents of a UNIX system directory. Because Advanced Server will attempt to allocate these buffers using the GC memory allocator, one should consider increasing the SizeGcBufferPoolInKB key if one increases this value.
Page 293 (IPC) between server processes. The server uses the read system call to receive IPC messages, but read does not always return the entire message. This key ensures that the server does not keep trying to get an IPC message at the expense of other activities the process could perform.
Page 294 The parameter is only evaluated if the configured spooler is "SPOOLV4". If the parameter is set to 1, Advanced Server submits the print jobs to the spooler under the user ID of the relevant UNIX user who is mapped to the Advanced Server user. For example, the Advanced Server administrator submits print jobs as the UNIX user "lmxadmin".
Page 295 MaxLockTimeInSeconds key elapses. Default: 10 milliseconds MaxLockTimeInSeconds The maximum interval in seconds that a server process waits for a shared memory lock to become available. Default: 300 seconds (5 minutes) MaxVCPerProc The maximum number of virtual circuits that each lmx.srv process should be able to...
Page 296 The minimum number of virtual circuits that each lmx.srv process should be able to handle. This limit normally is calculated on the fly by Advanced Server using the value of the VCDistribution Registry key and the value of the maxclients parameter in the lanman.ini file.
Page 297: Table Of Contents
This figure should be large because it limits the number of Windows NT clients that can contact the server. On a primary domain controller, it must be at least the number of servers and Windows NT clients in the domain.
Page 298 UNIX system. The server must decide if a new session should be handed off to an existing lmx.srv process or if a new process should be started. This key specifies the distribution of sessions over the lmx.srv processes.
Page 299 250-349 350-499 500-749 750-999 1000+ 13.5.6 RPC Parameters Entries The Registry path that contains entries for the Advanced Server RPC Parameters is as follows: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \AdvancedServer\RpcParameters BrowserMaxCalls The maximum number of open browser sessions that an lmx.srv process can support simultaneously.
Page 300: Reg_Dword
The maximum number of print sessions that an lmx.srv process can support simulta- neously. Default: 50 SrvsvcMaxCalls The maximum number of server sessions that an lmx.srv process can support simulta- neously. Default: 20 SvcctlMaxCalls The maximum number of service control sessions that an lmx.srv process can support simultaneously.
Page 301 Advanced Server user account created in the domain in which the server is a member. The value of this key must be set to 1 on every server on which UNIX system accounts are to be created. Note that new Advanced Server users are assigned to the UNIX system lmworld account, if the value of this key is set to 0.
Page 302: Reg_Dword
UNIX system user account with an equal or similar name, provided that the UNIX system user account is not specified in the exclude list.) GroupUpdateTime The interval in seconds at which the server checks the UNIX system file /etc/group for changes. Default: 3600 seconds (1 hour) NewUserShell The login shell for new user accounts.
Page 303: Infinity
UserRemark The comment string associated with the USERS shared directory. Default: Users Directory 13.6 Alerter Service Parameters The Registry path that contains entries for the Advanced Server Alerter service is as follows: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Alerter\Parameters AlertNames A list of the user accounts and computer names that should receive administrative alerts.
Page 304: Default: 120 Seconds (2 Minutes)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters BackupRecovery Specifies the period of time in seconds that must elapse before a server that has ceased being a backup browser can become a backup browser again. Default: 1800 seconds (30 minutes) You can change the value of this key using the AS/U Administrator.
Page 305 You can change the value of this key using the AS/U Administrator. WinsServer This key is obsolete in the Siemens Advanced Server for UNIX. 13.8 EventLog Service Entries The subkey for EventLog contains at least three subkeys for the three types of logs — Appli- cation, Security, and System.
Page 306 Specifies the number of categories supported. TypesSupported Specifies a bitmask of supported types. 13.9 Lanman Server Parameters The Registry path that contains entries for the Advanced Server LAN Manager service is as follows: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters AccessAlert Specifies the number of resource access violations that can occur before the server sends an alert to the alertnames list.
Page 307 CPU cycles on the client and server side. Default: 0 ErrorAlert REG_DWORD Specifies the number of errors that can occur before the server sends an alert to the alertnames list. Default: 5 You can change the value of this key using the AS/U Administrator.
Page 308 Default: none RequireSecuritySignature Specifies whether a server requires all of its clients to use SMB signing. If a client does not have security signatures enabled, it will not be able to connect to a server that requires security signatures.
Page 309 13.11 Net Logon Service Parameters The Registry path that contains entries for the Advanced Server Net Logon service is as follows: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters...
Page 310 RelogonDelay Specifies the interval in seconds that a client can wait before logging back on to the server after the server has been stopped and restarted. Default: 2 You can change the value of this key using the AS/U Administrator.
Page 311 Update REG_DWORD If this value is set, the server synchronizes the user accounts database with the primary domain controller every time it starts. This keyword applies only to a backup domain controller and is ignored by the primary domain controller. Note that full synchronization is a very time-consuming operation.
Page 312 These servers subsequently replicate from the export server. If no value is specified, the export server sends a notice to its domain. Separate multiple names with a semicolon (;). This value is ignored if the value of the Replicate key is 2 (Import).
Page 313 Advanced Server Registry ImportPath REG_SZ or REG_EXPAND_SZ Specifies the path on the import server to receive replicas from the export servers. This value is ignored if the value of the Replicate key is 1 (Export). Default: C:\var\opt\lanman\shares\asu\repl\import Interval REG_DWORD 1 to 60 Specifies how often in minutes an export server checks the replicated directories for changes.
Page 314 Advanced Server Registry TryUser REG_DWORD Specifies whether the import server should try to update directories when a user name is logged on locally. Default: 1 UnixDirectoryGroup Specifies the UNIX system group account name for replicated directories. Default: DOS---- UnixDirectoryOwner Specifies the UNIX system user account name for replicated directories.
Page 315 You can change the value of this key using the AS/U Administrator. PowerFailMessage The text of the message to be sent by the server when it receives a SIGPWR signal. Default: “The system has experienced a power failure. Please close all applications and files and log off immediately”.
Page 316 When a 1C name is pulled from this WINS partner, the addresses contained in it are given this precedence level. The value can be 0 (low) or 1 (high). Set this value to 1 if this WINS server is serving a geographic location that is nearby.
Page 317 Before attempting to change any of the parameters available in the lanman.ini file, it is useful to understand the relationship between the lanman.ini file entries and server defaults. Every server parameter has a default setting. To display and edit default settings, a utility program called srvconfig is provided in the /var/opt/lanman/bin directory.
Page 318 [ lmxserver ]. You then need to add a “parameter=value” pair to the appropriate section of the lanman.ini file. 3. After you edit the file, you must stop and restart the server in order for the new values to take effect.
Page 319 Values: any servername of 1-15 characters default: null Identifies the maximum number of simultaneous client sessions that the server must support. This number is set by default to 250. It can be increased to a number that is equal to the Advanced Server user licence.
Page 320 Product Manual Description, Values, and Default Setting The name of the domain that includes the server. To change the value of the listenname parameter, use the setdomainname command. For more information about this command, type man setdomainname at the Advanced Server command prompt.
Page 321 Japan Default: 001 The path to the directory containing message text files used by Advanced Server for UNIX system commands. To change the value of the listenname parameter, use the setlang command. For more information about this command, type man setlang at the Advanced Server command prompt.
Page 322 Description, Values, and Default Setting The extension that the UNIX system listener program, by default, applies to the name of the server computer. This parameter is ignored. Siemens does not use the UNIX listener. Values: 0-13 characters and a null value are acceptable.
Page 323 UNIX system’s LP subsystem. Default: /var/spool/lp/tmp/uname where uname is the server’s UNIX system name. Configures whether to use memory-mapped file opera- tions when accessing the Advanced Server Access Control List database. Values: yes, no; default: yes Configures whether to use memory-mapped file opera- tions when accessing the Advanced Server Change Log database.
Page 324 The location of the help file used by the net help command (relative to /var/opt/lanman/msgfiles). Default: /var/opt/lanman/msgfiles/001/net.hlp The interval, in seconds, that the server waits for a response when it sends a message that requires one. Values: 0 - unlimited; default: 30...
Page 325 Description, Values, and Default Setting The network device names and NetBIOS name- passing type for the network(s) the server should use. Values: sets of four items separated by commas, each set of four separated from the next by a space. The following four items are in each set: 1.
Page 326 Net command does not need to bind its own name, and this quickens the UNIX system’s Net access to the server. If this parameter is set to no, then each Net command will use its own unique name with somewhat slower performance resulting.
Page 327 Values: A path up to a maximum of 256 characters; default: lmfsiops.so The location of new file systems on the server. Values: A path up to a maximum of 256 characters; default: /usr/lib/fs File system type identifiers that map unknown file systems to known file system types.
Page 328 The listenname parameter is in the lanman.ini file as well as the Advanced Server Registry under \SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName. Product Manual Lanman.ini Parameter Mapping to Registry Keys Advanced Server Registry Key Name (\SYSTEM\CurrentControlSet\Services) LanmanServer\Parameters Alerter\Parameters...
Page 329 [Uidrules ] Section Parameter Mappings to Registry Keys Lanman.ini File Parameter exclude forceunique maxuid minuid usrcomment These values are not displayed by default but can be configured in the Advanced Server Registry. [Netlogon] Section Parameter Mappings to Registry Keys Lanman.ini File Parameter logonquery maxclisess maxquery maxsrvsess...
Page 330 Product Manual Lanman.ini Parameter Mapping to Registry Keys Advanced Server Registry Key Name (\SYSTEM\CurrentControlSet\Services) None (obsolete) None (obsolete) None (obsolete) None (obsolete) AdvancedServer\NetAdminParameters AdvancedServer\NetAdminParameters AdvancedServer\NetAdminParameters None (obsolete) None (obsolete) None (obsolete)
Page 331 Product Manual Lanman.ini Parameter Mapping to Registry Keys Advanced Server Registry Key Name (\SYSTEM\CurrentControlSet\Services) None (obsolete) None (obsolete) None (obsolete) AdvancedServer\UserServiceparameters AdvancedServer\FileServiceParameters AdvancedServer\FileServiceParameters Eventlog\System None (obsolete) AdvancedServer\FileServiceParameters AdvancedServer\FileServiceParameters AdvancedServer\FileServiceParameters...
Page 332 Product Manual Lanman.ini Parameter Mapping to Registry Keys Advanced Server Registry Key Name (\SYSTEM\CurrentControlSet\Services) None (obsolete) None (obsolete) AdvancedServer\ProcessParameters None (lanman.ini file) None (obsolete) None (obsolete) None (obsolete) None (obsolete) None (obsolete)
Page 333 Product Manual Lanman.ini Parameter Mapping to Registry Keys Advanced Server Registry Key Name (\SYSTEM\CurrentControlSet\Services) None (obsolete) None (obsolete) None (obsolete) None (obsolete) None (lanman.ini file) Alerter\Parameters None (lanman.ini file) None (lanman.ini file) None (lanman.ini file)
Page 334 Product Manual Lanman.ini Parameter Mapping to Registry Keys Advanced Server Registry Key Name (\SYSTEM\CurrentControlSet\Services) AdvancedServer\Parameters None (obsolete) AdvancedServer\FileServiceParameters (\SOFTWARE\Microsoft\LanmanServer CurrentVersion (and elsewhere)) (\SOFTWARE\Microsoft\LanmanServer CurrentVersion (and elsewhere)) None (obsolete) None (obsolete) None (obsolete)
Page 335 [vps] Section Parameter Mappings to Registry Keys Lanman.ini File Parameter poweraddr powermessage powertime Product Manual Lanman.ini Parameter Mapping to Registry Keys Advanced Server Registry Key Name (\SYSTEM\CurrentControlSet\Services) None (lanman.ini file) None (lanman.ini file) None (obsolete) AdvancedServer\ProcessParameters None (obsolete) None (obsolete)
Page 336 Product Manual Lanman.ini Parameter Mapping to Registry Keys Advanced Server Registry Key Name (\SYSTEM\CurrentControlSet\Services) Replicator\Parameters Replicator\Parameters Replicator\Parameters Replicator\Parameters Replicator\Parameters Replicator\Parameters Replicator None (obsolete) Replicator\Parameters Replicator\Parameters Replicator\Parameters Replicator\Parameters None (obsolete)
Page 337 None (lanman.ini file) None (lanman.ini file) None (lanman.ini file) None (obsolete) AdvancedServer\FileServiceParameters AdvancedServer\FileServiceParameters None (lanman.ini file) AdvancedServer\FileServiceParameters Advanced Server Registry Key Name Value Name None (obsolete) None (lanman.ini file) Advanced Server Registry Key Name None (obsolete) Value Name RootOwnsFilesCreated- OnNFS...
Page 338 [Browser] Section Parameter Mappings to Registry Keys Lanman.ini File Parameter backuprecovery backupupdate lmannounce masterupdate morelog Product Manual Lanman.ini Parameter Mapping to Registry Keys Advanced Server Registry Key Name (\SYSTEM\CurrentControlSet\Services) NetRun\Parameters NetRun\Parameters Advanced Server Registry Key Name (\SYSTEM\CurrentControlSet\Services) Browser\Parameters Browser\Parameters LanmanServer\Parameters Browser\Parameters...
Page 339 Using the programming interface of Advanced Server for UNIX, the application programs are given access to the services and shared resources of Advanced Server for UNIX. LM named pipes or mailslots can be accessed, for example, from application programs. Product Manual...
Page 340 A connection is set up if a client can access a shared resource of a server. A client can have several connections to a server. This is provided when a session is opened between a client and a server.
Page 341 IPC$ An administrative resource for controlling interprocess communication on servers. The IPC$ resource of a server must be shared before any of the following actions can be undertaken: displaying the shared resources of the server, use of the distributed applications on the server by the user.
Page 342 A server in a domain, which retains and uses a copy of the user account database of the domain but does not verify netlogon requests. This server role is not supported with Advanced Server for UNIX. In the case of an upgrade installation from LAN Manager/X, a member server receives the server role backup domain controller.
Page 343 With Trust Relationship, you can also access shared resources in other domains. See also Netlogon. netrun Netrun enables the execution of a UNIX program on the server from an OS/2 or an extended MS-DOS client. password A string used to access the network or one or more shared resources .
Page 344 A client can have several sessions set up to several servers. See also Netlogon. share If a resource on a server is available to users in a local network, it is “shared”. See also share level security A type of security by means of which access to each shared resource is dependent upon a password.
Page 345 Directories in the file system of the server, which are shared for use in the local network. Shared directories include the files contained in these directories and additional directories.
Page 346 Consists of all the information that defines a user to the Advanced Server. This includes items such as the user name and password required for the user to log on, the groups in which the user account has membership, and the rights and permissions the user has for using the system and accessing its resources.
Page 347 Windows Internet Name Service (WINS) for Advanced Server provides a Windows NT compatible, replicated, dynamic database for registering and querying NetBIOS computer name-to-IP address mappings in a routed network environment. Advanced Server WINS is designed to solve the problems that occur with name resolution in complex internetworks. workstation See client.
Page 348 HPFS ISDN LIPC Product Manual Access Control Entry Access Control List Application Programming Interface Advanced Server for UNIX Advanced Server for UNIX Backup Domain Controller Binary Large Object CD File System Communication Management under UNIX Distributed Computing Environment Dynamic Host Configuration Protocol...
Page 349 Product Manual Memory File System Management Information Base Microsoft Interface Definition Language Microsoft Microsoft Disk Operating System NetBIOS NetBIOS Name Server Network Basic Input Output System NetBIOS over TCP/IP Network File System NT File System Operating System /2 Open Systems Interconnection...
Page 350 VxFS WINS Product Manual Terminate and Stay Resident User Datagram Protocol UNIX File System User ID Uniform Naming Convention Uninterruptable Power Supply Veritas File System Windows Internet Name Service Wide Area Network Windows for Workgroups Abbreviations U7613-J-Z815-6-76...
Page 351: Related Publications
LAN Manager/X is included. Changes and extensions to the Siemens version are documented in this manual, “Overview and Installation”. Advanced Server for UNIX V4.0...
Page 352 Related publications The following manuals relate to the MS-DOS and MS OS/2 workstations: MS Network Client V2.2 Installation Guide for Clients Target group System administrators Contents Installation and configuration information for client software, information on incorporating the network driver, and information on the lanman.ini file on client systems. MS Network Client V2.2 User’s Guide for MS-DOS Clients Target group...
Page 353 Related publications MS Network Client V2.2 NetWare Connectivity Target group System administrators Contents The basics of “NetWare Connectivity”, installing and configuring NetWare Connectivity, troubleshooting, and differences in the administration of NetWare, Windows NT, and LAN Manager. Product Manual U7613-J-Z815-6-76...
Page 354 Related publications Other Siemens publications: SINIX V5.43 Network Administration System Administrator’s Guide SINIX V5.43 Tuning Guide System Administrator’s Guide SINIX V5.43 System Administration and Hardware Configuration Using SYSADM System Administrator’s Guide SINIX V5.43 Commands – Volume 1 and 2 Reference Manuals SINIX V5.43...
Page 355 User and Administrator Guide Xprint Reference Manual Xprint Menus User’s Guide SINIX OBSERVE User Guide SINIX V5.41 Logging V3.0 Target group: System administrators and programmers Ordering manuals You can order the specified publication through your local Siemens office. Product Manual Related publications U7613-J-Z815-6-76...
Page 356 158, 180 administration remote under Windows 25 administration shell 24, 339 administrator 4, 339 Advanced Server 339 Advanced Server for UNIX start 134 status display of the processes 137 terminate 135 AlertAdminOnLicenseOverflow 281 alerter 20, 236, 339 AlertNames 303...
Page 357 UNIX system 125 spool system 125 configure configuration files 137 lanman.ini file 137 configure lanman.ini file 137 configuring shared client printer 130 connecting Advanced Server for UNIX to Logging 120 connection 340 end 23 set up 23 ConnectTimeout 282 CoreOk 295...
Page 358 PC client software 86 procedure 47 sequence 55 SIreadmeM 55 software requirements 46 Windows NT Administrative Tools 169, 171 Windows NT Server Tools 172 with the default configuration 89 interface to the spool system keywords 125 interprocess communication (IPC$) 17, 341 Interval 313...
Page 359 MaxRawSize 293 Product Manual MaxRuns 311 MaxServiceWaitTime 293 MaxSize 305 maxspoolfds 323 MaxVCPerProc 295 MaxVCs 296 MaxZeroFillInKB 284 member server 342 upgrade installation of 48 MemberPrec 316 MemoryMapFiles 284 message POPUP 342 messenger 342 MinSmbWorkerTasks 296 MinVCPerProc 296 MixedCaseSupport 285...
Page 360 net group 190 net help 190 net helpmsg 190 net localgroup 190 net logoff 190 net logon 190 net password 190 net pause 190 net perms 190 Net POPUP 342 net print 190 net send 190 net session 191 net share 191 net sid 191 net start 191 net statistics 191...
Page 361 RefusePasswordChange 310 regcheck 181, 238 regconfig 181, 238 Registry 343 regload 181 RelogonDelay 310 remote administration under Windows 25 Remote Monitoring of Server 235 Remote Procedure Calls 26 remotemounts 327 repladm 181 Replicate 313 Replicator 21, 343 ReportNTFS 286 RequireSecuritySignature 308...
Page 362 SMB signing 307 SNMP service 22 software requirements 46 Sources 306 SpareServerTime 297 SPOOL V4.x name of spool server 127 names of printers and printer groups 128 setting up 126 spooler setting up shared client printer 130 spooler interface 139...
Page 363 WAN 304, 309 Windows Internet Naming Service 22 Windows NT Administrative Tools installation 171 Windows NT Adminstrative Tools installation 169 Windows NT Server Tools installation 172 WinregMaxCalls 300 WINS (Windows Internet Name Service) dial-up TCP/IP networking clients 207 names name query request packet 205...
Page 364 Siemens AG Information and Communication Products Computer Systems User Documentation UNIX QM4 33106 Paderborn Germany Fax: (++ 49) 52 51 8-1 52 48 DOCetc@pdb.siemens.de Submitted by Comments on Advanced Server UNIX V4.0 Overview and Installation U7613-J-Z815-6-76 Comments Suggestions Corrections...
Page 365 Fax: (++49) 89636-52003 The Siemens Training Center offers consulting for in-service training, courses and self-tuition media on almost all aspects of information technology, either on your premises or at a Training Center near you. Write to us for information and course programs.

This manual is also suitable for:

Advanced server unix v4.0

Siemens Unix V4.0 Overviews & Installation Instructions

Quick Links

Troubleshooting

Related Manuals for Siemens Unix V4.0

Summary of Contents for Siemens Unix V4.0

This manual is also suitable for:

Table of Contents