Résumé du contenu de la page N° 1
Advanced Server UNIX V4.0
Overview and Installation
Edition April 1999
Résumé du contenu de la page N° 2
Comments… Suggestions… Corrections… The User Documentation Department would like to know your opinion on this manual. Your feedback helps us to optimize our documentation to suit your individual needs. Fax forms for sending us your comments are included at the back of the manual. 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 m
Résumé du contenu de la page N° 3
1Preface Advanced Server for UNIX can be used to integrate personal computers, which are ® operated under MS-DOS (also running MS Windows or MS Windows for Workgroups), ® ® MS OS/2 or OS/2 (referred to as OS/2 in this manual), Windows 95/98 and MS Windows ® NT operating systems, in local networks (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 m
Résumé du contenu de la page N° 4
Preface Target Group The “User's Guide for MS-DOS Clients” and “User's Guide for MS Windows Clients” are aimed at users of the MS-DOS or Windows clients. They provide information on starting up and closing down clients, and on shared directories and printers. They also provide refe- rences to the commands available for working with the client. The manuals “Installation Guide for Clients”, “MS Network Client V2.2”, and “MS Network Client V3.0” describe how to install these clients. The manual
Résumé du contenu de la page N° 5
Preface Summary of Contents 1.2 Summary of contents Information that became available after this manual went to print is contained in the i SIreadmeM package which is supplied with Advanced Server for UNIX. The chapter “Preface” provides users with an overview of the content and structure of this manual. The chapter “Introduction to Advanced Server for UNIX” contains information on the supple- ments and changes which you will require in addition to the information contained in the “Concepts
Résumé du contenu de la page N° 6
Preface Changes since the last version 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 “Compatibility” in the chapter “Introduction to Advanced Server for UNIX”. 1.4 Notational conventions The following notational conventions are used in this manual: Convention Usage Itali
Résumé du contenu de la page N° 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 “Concepts and Planning”. The following topics are dealt with: ● Shared resources and services ● Connection management ● Administration ● Application Programming Interface (API) The section on “Client-server architecture” contains a short description of the client-server architecture. The section entitled “Shared resou
Résumé du contenu de la page N° 8
Introduction to Advanced Server for UNIX Client-server architecture 2.1 Client-server architecture One or more server systems and several clients (workstations) are connected in a network (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 netw
Résumé du contenu de la page N° 9
Introduction to Advanced Server for UNIX Shared resources 2.2.1 Names in the network In the network, servers, domains, clients, users, and resources are assigned unique names. The following table describes briefly the various types of names in the network. Name Meaning System name Name of the UNIX system Computername, server name 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
Résumé du contenu de la page N° 10
Introduction to Advanced Server for UNIX Shared resources 2.2.1.1 System name Each UNIX system has a unique name in the network, which can be displayed using the command uname -n and set as the network node name using the SYSADM utility program. In order to avoid problems, it is strongly recommended that the system names you ! assign are unique throughout the network. While the same system name may appear several times in different DNS domains, even in the same network, Advanced Server for
Résumé du contenu de la page N° 11
Introduction to Advanced Server for UNIX Shared resources 2.2.1.3 Username Every user of a client is assigned a username by the administrator, which is unique throughout the network. Users are identified by their usernames in the network. The username consists of three to fifteen characters: letters, numbers, spaces and i special characters without / \ * ’ " ‘!. Use a maximum of eight characters to achieve unique mapping between UNIX names and Advanced Server for UNIX users. It is not rec
Résumé du contenu de la page N° 12
Introduction to Advanced Server for UNIX Shared resources 2.2.1.6 Domain name A domain gets its domain name during installation of the primary domain controller. The backup domain controllers are assigned during installation of a domain. The assignment of a client to a domain is defined while it is being installed; it can be reconfigured later or, on some clients, modified temporarily with the net logon command, for example. The trust relationship concept means that it is easier to manage and
Résumé du contenu de la page N° 13
Introduction to Advanced Server for UNIX Shared resources 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- butes a, r and h are mapped under UNIX: Permissions Owner Group Filename rw-rwsr-- lmx
Résumé du contenu de la page N° 14
Introduction to Advanced Server for UNIX Shared resources Existing configurations are not modified during an upgrade installation. You should therefore use either the Registry Editor or the regconfig command to set the value of the EAFilePrefix parameter in the registry to .EA@ under the key SYSTEM\CurrentControlSet\Services\AdvancedServer \FileServiceParameters. If you previously operated Advanced Server for UNIX V4.0A10 with the setting UseEAs=1, you will now have to rename all hidden shad
Résumé du contenu de la page N° 15
Introduction to Advanced Server for UNIX Shared resources 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. In this case, users work with the shared directory as they would with a local drive or directory on their clients. The security check is not taken into account in the following description in order to i avoid complexity. The administ
Résumé du contenu de la page N° 16
Introduction to Advanced Server for UNIX Shared resources Authorized users can assign this shared directory to their clients. The network name of the shared directory (in accordance with DOS naming conventions) \\server1\sf1 is linked on the client to a local drive letter, e.g. j:, using the command net use j : \\server1\sf1. The user may have to allow additional drive letters on the client in the configuration i file config.sys using the command lastdrive. The client user can then access t
Résumé du contenu de la page N° 17
Introduction to Advanced Server for UNIX Shared resources 2.2.5.2 Shared client printer It is also possible to route the output of the printer spooler to a printer which is connected to a client (shared client printer). For further information, please refer to the manuals entitled “MS Network Client V2.2” and “User's Guide for MS-DOS Clients”. 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. Window
Résumé du contenu de la page N° 18
Introduction to Advanced Server for UNIX Shared resources 2.2.6.1 LM named pipes Advanced Server for UNIX also provides LM named pipes. They are bidirectional commu- ® nication channels for interprocess communication in the network. They differ from UNIX named pipes. The following example describes the basic procedure for setting up and clearing down an 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
Résumé du contenu de la page N° 19
Introduction to Advanced Server for UNIX Shared resources 2.2.6.2 Mailslots 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. Example A reading process (on the server server1) creates a mailslot with the name ms. This program waits for me
Résumé du contenu de la page N° 20
Introduction to Advanced Server for UNIX Services 2.3 Services The following additional services can be configured in Advanced Server for UNIX: Service Comments Alerter configurable Auditing configurable Replicator configurable Netlogon configured when server is installed Timesource configurable SNMP Extension Daemon installed and configured with the asxsnmp package Netrun configurable Browser configured automatically Windows Internet Naming Service (WINS) configurable The following sections br
