advanced server manual.pdf

7/29/2019 advanced server manual.pdf

1/328

TotalNET Advanced Server 5.2Reference Manual

Sun Microsystems, Inc.

901 N. San Antonio RoadPalo Alto, CA 94303-4900

U.S.A.

Part No: 805-380810October 1998, Revision A


2/328

Copyright 1998 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved.

This product or document is protected by copyright and distributed und er licenses restricting its use, copying, distribution, anddecompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization ofSun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registeredtrademark in the U.S. and other countries, exclusively licensed through X/ Open Company, Ltd.

Sun, Sun Microsystems, the Sun logo, SunSoft, SunDocs, SunExpress, and Solaris are trademarks, registered trademarks, or service marksof Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registeredtrademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon anarchitecture developed by Sun Microsystems, Inc.

The OPEN LOOK and SunTM

Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sunacknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the

computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sunslicensees wh o imp lement OPEN LOOK GUIs and otherwise comply w ith Suns written license agreements.

RESTRICTED RIGHTS: Use, du plication, or disclosure by the U.S. Gov ernmen t is subject to restrictions of FAR 52.22714(g)(2)(6/ 87) andFAR 52.22719(6/ 87), or DFAR 252.2277015(b)(6/ 95) and DFAR 227.72023(a).

DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,INCLUD ING A NY IMPLIED WARRANTY OF MERCH AN TABILITY, FITNESS FOR A PARTICULAR PURPOSE ORNON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLYINVALID.

Copyright 1998 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, Ca lifornie 94303-4900 Etats-Unis. Tous droits rservs.

Ce produ it ou document est protg par un copyright et distribu avec d es licences qu i en restreignent lutilisation, la copie, ladistribution, et la dcompilation. Aucune partie de ce produit ou document ne peut tre reproduite sous aucune forme, par quelquemoyen que ce soit, sans lautorisation pralable et crite de Sun et de ses bailleurs de licence, sil y en a. Le logiciel dtenu par des tiers, etqui comprend la technologie relative aux p olices de caractres, est p rotg p ar u n copyright et licenci par des fournisseurs de Sun.

Des parties de ce produit pourront tre drives du systme Berkeley BSD licencis par lUniversit de Californie. UNIX est une marquedpose aux Etats-Unis et dans dautres p ays et licencie exclusivement p ar X/ Open Company, Ltd.

Sun, Sun Microsystems, le logo Sun, SunSoft, SunDocs, SunExpress, et Solaris sont des marques de fabrique ou des marques dposes, oumarques de service, de Sun Microsystems, Inc. aux Etats-Unis et dans dautres pays. Toutes les marques SPARC sont utilises sous licenceet sont d es marques de fabrique ou des m arques d poses d e SPARC International, Inc. aux Etats-Unis et dans dautres p ays. Les produitsportant les marques SPARC sont bass sur une architecture d veloppe par Sun Microsystems, Inc.

Linterface dutilisation graphique OPEN LOOK et SunTM

a t dveloppe par Sun Microsystems, Inc. pour ses utilisateurs et licencis.Sun reconnat les efforts de pionniers de Xerox pour la recherche et le dveloppement du concept des interfaces dutilisation visuelle ougraphique pour lindustrie de linformatique. Sun dtient une licence non exclusive de Xerox sur linterface dutilisation graphique Xerox,cette licence couvrant galement les licencis de Sun qui mettent en place linterface dutilisation graphique OPEN LOOK et qui en outrese conforment aux licences crites de Sun.

CETTE PUBLICATION EST FOURNIE EN LETAT ET AUCUNE GARANTIE, EXPRESSE OU IMPLICITE, NEST ACCORDEE, YCOMPRIS DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, LAPTITUDE DE LA PUBLICATION A REPONDRE A UNEUTILISATION PARTICULIERE, OU LE FAIT QUELLE NE SOIT PAS CONTREFAISANTE DE PRODUIT DE TIERS. CE DENI DEGARANTIE NE SAPPLIQUERAIT PAS, DA NS LA MESURE OU IL SERAIT TENU JURIDIQUEMENT N UL ET N ON AVENU.

PleaseRecycle


3/328


4/328

4. Configuring the NetWare Realm 12

5. Configuring the App leTalk Realm 14

6. Loading the Drivers and Starting the Server 15

3. TotalNET User Commands 17

General Utilities 17

t n cct 18

Location 18

U sa ge 18

O p tio n s 18

Examples 18

t n cm n a m es 19

Location 19

U sa ge 19

Example 19

tngettext 20

Location 20

U sa ge 20

O p tio n s 20

t n in fo 21

Location 21

U sa ge 21

O p tio n s 21

Examples 22

t nld 23

Location 24

U sa ge 24

O p tio n s 25

Examples 26

iv TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


5/328

t n m sg fm t 28

Location 29

U sa ge 30

O p tio n 30

N o te s 30

t n p as sw d 30

Location 30

U sa ge 30

Usage for TAS-DCE 30

O p tio n s 31

N o te s 31

Examples 32

t n st at 34

Location 34

U sa ge 34

O p tio n s 34

Examples 34

t nw h o 37

Location 38

U sa ge 38

O p tio n s 38

Examples 38

Realm-Specific Utilities 39

App leTalk Realm: 39

LM-NT-OS/ 2 Realm: 39

NetWare Realm: 40

a cp r in t 40

Location 40

Contents v


6/328

U sa ge 40

O p tio n s 40

Examples 41

acslist 41

Location 41

U sa ge 42

O p tio n s 42

Example 42

aczonelist 45

Location 45

U sa ge 45

O p tio n 45

Examples 45

a ta tt r 46

Location 46

U sa ge 46

O p tio n s 46

Example 47

atconvert 47

Location 48

U sa ge 48

O p tio n s 48

N o te s 49

Examples 49

d d p i nfo 50

Location 50

U sa ge 50

O p tio n s 51

vi TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


7/328

Examples 51

d esk 55

Location 55

U sa ge 55

O p tio n s 55

Example 56

m 2u 56

Location 56

U sa ge 56

O p tio n s 56

Examples 57

m a ccp 57

Location 57

U sa ge 57

O p tio n s 58

N ote 58

Examples 58

macfsck 59

Location 59

U sa ge 59

O p tio n s 59

N ote 60

Example 60

m acm d 60

Location 60

U sa ge 60

O p tio n s 61

Example 61

Contents vi i


8/328

m a cm v 61

Location 61

U sa ge 61

O p tio n s 62

Examples 62

m a cr d 63

Location 63

U sa ge 63

O p tio n s 63

Example 63

m a cr m 64

Location 64

U sa ge 64

O p tio n s 64

Examples 64

p fin fo 65

Location 65

U sa ge 65

O p tio n s 65

Examples 66

u 2m 66

Location 66

U sa ge 66

O p tio n s 67

Examples 67

nbmessage 67

Location 68

U sa ge 68

viii TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


9/328

O p tio n s 68

Examples 68

n bq 69

Location 69

U sa ge 69

O p tio n 70

Examples 70

n w m e ss ag e 70

Location 70

U sa ge 70

O p tio n s 71

Examples 71

n wq 72

Location 72

U sa ge 72

N o te s 72

Examples 72

Shadow File Utilities 73

t n ch g rp 73

Location 73

U sa ge 73

O p tio n s 74

Examples 74

t n ch m o d 75

Location 75

U sa ge 75

O p tio n s 75

Examples 76

Contents ix


10/328

t n ch o w n 77

Location 77

U sa ge 77

O p tio n s 77

Examples 77

t ncp 78

Location 78

U sa ge 78

O p tio n s 79

Examples 79

tndirck 80

Location 80

U sa ge 81

O p tio n s 81

Examples 81

t nm v 82

Location 82

U sa ge 82

O p tio n s 82

N o te 83

Examples 83

t nr m 83

Location 84

U sa ge 84

O p tio n s 84

Examples 84

tnvolck 85

Location 85

x TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


11/328

U sa ge 86

O p tio n s 86

Examples 86

Remote Utilities 87

Use of Wildcards 88

Remote LM-NT-OS/ 2 utilities 88

Remote NetWare utilities 88

r u at tr 89

Location 89

U sa ge 89

O p tio n s 89

N o te s 90

Examples 90

r u co p y 91

Location 91

U sa ge 91

O p tio n s 92

Examples 93

r ud el 94

Location 94

U sa ge 94

O p tio n s 95

N ote 95

Examples 96

r ud ir 96

Location 96

U sa ge 96

O p tio n s 97

Contents xi


12/328

N o te 97

Examples 98

r um d 98

Location 98

U sa ge 98

O p tio n s 99

Examples 99

rumessage 100

Location 100

Usage 100

Options 100

Examples 100

r u p r in t 101

Location 101

Usage 101

Options 101

Examples 102

r u rd 106

Location 106

Usage 106

Options 106

Example 107

r u re n 107

Location 107

Usage 107

Options 107

Notes 108

Examples 108

xii TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


13/328

r u sh 109

Location 109

Usage 109

Options 109

N o te s 110

Examples 111

ruslist 115

Location 115

Usage 115

Options 116

Examples 116

r u t im e 117

Location 117

Usage 117

Options 117

N o te s 117

Examples 118

ncget 118

Location 118

Usage 118

Options 118

Examples 119

ncprint 120

Location 120

Usage 120

Options 120

Examples 121

n cp u t 121

Contents xiii


14/328

Location 122

Usage 122

Options 122

Examples 122

nctime 123

Location 123

Usage 123

Option 123

Example 123

ncslist 124

Location 124

Usage 124

Options 124

Examples 124

4. TotalNET Maintenance Commands 127

Realm Options 127

General Configuration Options 127

Special Options 128

Adm inistration Utilities 129

atdidck 130

Location 130

Usage 130

Options 130

Examples 130

tnaccept 131

Location 131

Usage 131

Options 131

xiv TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


15/328

Examples 131

t n ck 132

Location 132

Usage 132

Options 132

Examples 133

tncustom 133

Location 134

Usage 134

Options 134

Attributes 134

Examples 135

tnkill 136

Location 136

Usage 136

Options 136

N o te 137

Examples 137

tnlicense 138

Location 138

Usage 138

Options 138

N o te 139

Examples 139

tnreject 140

Location 140

Usage 140

Options 140

Contents xv


16/328

Examples 140

t n sh u t 141

Location 141

Usage 141

Options 141

Examples 142

tnstart 142

Location 143

Usage 143

Options 143

N o te 143

Examples 143

Configuration Utilities 144

atkprobe 145

Location 145

Usage 145

Options 145

Example 145

ipxprobe 146

Location 146

Usage 146

Options 146

Example 147

tnadvert 147

Location 148

Usage 148

Options 148

Attribute 148

xvi TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


17/328

Examples 148

tnatalk 149

Location 149

Usage 150

Options 150

N o te 150

Attribute 150

Examples 150

tnattach 151

Location 151

Usage 151

Options 151

Attributes 151

Examples 152

tniface 153

Location 153

Usage 153

Options 154

Attributes 154

Examples 159

tnnetmgr 160

Location 160

Usage 160

Options 161

Attributes 161

Examples 161

tnpref 163

Location 163

Contents xvii


18/328

Usage 163

Options 163

Examples 163

tnprinter 165

Location 165

Usage 165

Options 165

N o te 166

Attributes 166

Examples 167

tnrealm 168

Location 168

Usage 169

Options 169

Attributes 169

Examples 171

tnroute 172

Location 172

Usage 172

Options 172

Attribute 173

Examples 173

tnservice 174

Location 174

Usage 174

Options 174

Attributes 175

Examples 191

xviii TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


19/328

tnsname 194

Location 194

Usage 194

Options 194

Attribute 195

Examples 195

tnstype 197

Location 197

Usage 197

Options 197

N o te 197

Attributes 197

Examples 199

tnsuffix 200

Location 200

Usage 200

Options 200

Attributes 200

Examples 201

tnsystem 203

Location 203

Usage 204

Options 204

Attributes 204

Examples 206

tntransport 206

Location 207

Usage 207

Contents xix


20/328

Options 207

N o te 207

Attributes 207

Examples 216

t n u m ap 217

Location 217

Usage 217

Options 217

Examples 217

tnumapuser 218

Location 219

Usage 219

Options 219

Attribute 219

Examples 219

tnvolume 221

Location 222

Usage 222

Options 222

N o te 222

Attributes 222

Examples 227

tnvref 229

Location 230

Usage 230

Options 230

Notes 230

Examples 230

xx TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


21/328

5. Cl ie nt U ti li ti es 233

General Client Utilities: 233

NetWare Client Utilities: 233

SMB Client Utility: 234

u t yp e 234

Location 234

Usage 234

Option 234

Example 234

version 234

Location 235

Usage 235

Option 235

Example 235

attach 235

Location 235

Usage 235

Options 235

Example 236

capture 236

Location 236

Usage 236

Options 237

Examples 237

edscript 237

Location 238

Usage 238

Option 238

Contents xxi


22/328

Examples 238

login 239

Location 239

Usage 239

Options 239

Example 240

logout 240

Location 240

Usage 240

Options 240

Examples 240

m a p 241

Location 241

Usage 241

Options 241

Examples 241

slist 242

Location 242

Usage 242

Options 242

Examples 243

nettime 243

Location 243

Usage 243

Options 243

Examples 243

6. NetWare Login Scripts 245

Notational Conventions 245

xxii TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


23/328

Identifier Variables 246

Login Program 247

# 249

Usage 249

Options 249

Examples 249

attach 250

Usage 250

Options 250

Examples 250

break 250

Usage 251

Options 251

Examples 251

comspec 251

Usage 251

Option 252

Example 252

display 252

Usage 252

Options 252

Example 252

DOS break 252

Usage 253

Options 253

Examples 253

DOS verify 253

Usage 253

Contents xxiii


24/328

Options 254

Examples 254

d r iv e 254

Usage 254

Option 254

Example 254

exit 255

Usage 255

Option 255

Example 255

fire phasers 255

Usage 255

Option 256

Example 256

g ot o 256

Usage 256

Option 256

Example 256

if...then 257

Usage 257

Options 257

N o te 258

Example 258

include 258

Usage 259

Options 259

Example 259

machine 259

xxiv TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


25/328

Usage 259

Option 259

Example 260

m ap 260

Usage 260

Options 260

Examples 261

p a u se 262

Usage 262

Example 262

r em a r k 262

Usage 263

Options 263

Example 263

s et 263

Usage 263

Options 264

Example 264

shift 264

Usage 264

Option 264

Example 264

w r it e 265

Usage 265

Option 265

Example 265

7. Tro ub le sh oo ting 267

General Troubleshooting 267

Contents xxv


26/328

Initial Connection 268

LM-NT-OS/ 2 Connections 268

NetWare Connections 269

App leTalk Connections 270

Realm-Specific Error and Activity Logs 271

Error Logs 271

Activity Logs 272

Error Messages and Solutions 272

Access denied 273

Cannot access a directory 273

Cannot access network drive 273

Cannot create socket on server 274

Cannot log in to server as supervisor 274

Incorrect password 274

Incorrect response from network 274

Invalid connections in tninfo report 275

Invalid drive was specified 275

Network device type incorrect 276

Network path not found 276

No servers listed by slist 277

Remote compu ter not listening 277

Routing information database corrupted on large internetwork 278

Server not found 278

Too many redirections 279

Unknown board ID 279

Error Conditions and Solutions 279

App lication on UN IX server inaccessible 279

Compilation problems in DOS window 279

xxvi TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


27/328

Connection failure 280

Dead sessions not dropped 280

Disconnected clients still appear connected 280

DOS command s yield u nexpected results 280

File locking errors 281

Free disk space indicated incorrectly 281

NetBIOS does not start 281

Performance of network slow 281

Ping does not work 282

Printing problems 282

Contacting Sun Technical Sup port 283

8. To talN ET Co mman ds 285

a 285

d 285

i 286

m 286

n 286

p 287

r 287

t 287

u 289

9. Co mman d A ttribu te s 291

a 291

b 292

c 292

d 292

e 293

f 293

Contents xxvii


28/328

g 293

h 294

k 294

l 294

m 294

n 295

o 295

p 296

q 296

r 296

s 297

t 298

u 298

v 298

w 298

z 299

Index 301

xxviii TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


29/328

CHAPTER 1

Introduction

This chapter covers the following topics:

TotalNET Advanced Server on page 1

Whats New in This Release on page 2

About This Manual on page 3

Related Books on page 6

TotalNET Advanced ServerTotalNET Advanced Server (TAS) p rovides a unified networking solution for

multi-platform LAN and WAN environments. TAS enables LAN Manager, Windows

NT, Window s 95, Window s for Workgroups, Window s 3.x, OS/ 2, N etWare, and

App leTalk clients to share file, print, and terminal services transp arently across a

UNIX server, regardless of their choice of client software and network protocol.

Because TAS software u ses UN IX as the enterprise LAN server operating system, itcan operate with other UNIX processes. This interoperability allows youthe

adm inistratorto u se UNIXs mu lti-user scalability for ap plication, file, p rinter,

ATLW, terminal, NVT, mail, communications, and database services.

TAS includes three realms:

LM-NT-OS/ 2 realm The realm for LAN Manager, Windows NT, Windows 95,

and IBM OS/ 2 clients runn ing TCP/ IP or NetBEUI transports.

NetWare realm The realm for NetWare clients run ning the IPX/ SPX transport.

AppleTalk realm The realm for Macintosh clients running the AppleTalk

transport.

1


30/328

Whats New in This Release

TotalNET Administration SuiteTotalNET Adm inistration Suite (TNAS) allows you to configure the TotalNET

network through HTML menus and dialogue boxes, just as TotalAdmin did for

TotalNET Advanced Server (TAS) in previous releases of TAS. TotalAdminconstitutes one sphere of TNAS.

New TotalAdminThe presentation and arrangement of TotalAdmin menu items reflect the new,

intuitive TNAS framework.

File Name MappingThe way TAS hand les filename case now defaults to case-preservation, in w hich TAS

map s case to UNIX exactly as given by th e client, instead of to lower-case.

Improved Utility PerformanceThe TotalNET remote utilities, such as the ru- and nc- utilities, now support long file

names, the tnpasswd utility performs more efficiently, the CAP to MAC utility

works with TAS 5.0 file formats, the atconvert u tility allows you to convert from

Helios to TAS, and NetWare client utilities function more intuitively.

Enhanced TracingYou can now turn tracing on or off from all three realms and for all file services, and

you can do so more easily than in previous releases.

AppleTalk Printer Access from All RealmsThis feature allows you to print to AppleTalk printers through TAS. TAS extends

outbound and inbound support to the PAP driver.

2 TotalNET Advanced Server 5.2 Reference Manual October 1998, Revision A


31/328

About This ManualThis manual provides information for setting up, configuring, and administering TAS

from the UNIX command line after you install TAS using the instructions in the

TotalNET A dvanced Server Release N otes, which came with your packaging. It

assumes you have both an ad vanced u nderstanding of network administration and

network administration privileges in the system.After reading the rest of this introduction, perform initial setup as described in

Chapter 2. From there, you may administer TAS as using UNIX commands described

in Chapters 3 and 4.

This section covers the following topics:

Notational Conventions on page 3

Command Entry Format on page 4

Terminology on page 4

Overview of Chapters on page 5

Notational ConventionsThis table d escribes textual notations you will encounter:

courier A command, path, or part of a path.

italic A variable. You must replace each occurrence of this textwith a valid value for its variable. For the realm variable,

use NB, NW, or AT.

lo wer-case A com man d or file n am e th at d oes n ot req uire u p per -case.

U PPER-CA SE Ch ar acters yo u m u st su p ply in u p per -case.

[] Brackets around an op tional part of the command line.

{} Braces around two or more options, separated by pipes (| ),

from which you must choose.

| A pipe to separate choices enclosed in braces.

Introduction 3


32/328

() Parentheses to group the options they enclose.

... An ellipsis to indicate that you may include as manyspecifications as you wish for the p receding option.

The following example d emonstrates the use of courier, courier italic, brackets,

braces, pipes, and ellipses:

command [option]... {literal|variable}

The following example illustrates the addition of the value of the browse-master

attribute (kipper) to the file service atmoe:file in the AT realm:

tnservice -A -r AT -s atmoe:file -a browse-master=kipper

Command Entry FormatLists of command entries in alphabetical order appear in Chapter 3 and Chapter 4.

The command entries describe function, location, usage, examples, and attributes for

every command . Each command entry has the comm and name as the title, followed

by a description of its functionality and the following sections:

Location The path of the command s location.

Usage The format for UNIX command-line usage, including parameters and

options.

Options Descriptions of command and attribute variables and designations.

Attributes Command attributes that add to or modify the functionality of the

command . This section on ly app ears if attributes exist.

Notes Important properties and special requirements for the command. This

section only appears if these qualities exist.

Examp les Examples of u sage.

Terminology

$TNHOME The TotalNET home directory w here TAS files and programs reside,

located at /var/opt/totalnet.

attach points Aliases for directory paths in a volume. Users see attach points as

volumes and cannot move u p directory trees p ast them.

realms Domains in the TAS environment. TAS has the following three

realms, based on the three types of clients and transport protocols:



33/328

LM-NT-OS/ 2 realm The realm for LAN Manager, Window s N T,

Windows 95, and IBM OS/ 2 clients running NetBIOS-over-TCP/ IP

or NetBIOS-over-NetBEUI transports.

NetWare realm The realm for NetWare clients r unn ing the IPX/

SPX tran sport.

App leTalk realm The realm for Macintosh clients run ning the

App leTalk transport.

services File, print, and terminal services in the TotalNET environment.

TNAS TotalNET Adm inistration Suite, a task-oriented graphic

adm inistration and configuration interface for TotalNET product

administration, licensing, and system administration. TNAS

includes the TotalAdmin sphere for administering TAS. For more

information on TNAS, refer to TAS Administration Manual.

TotalNET s ystem

manager

The daemon that performs general management of the TotalNET

system. For more information, refer to TAS A dministration Manual.

transports Low-level networking protocol suites defined at the system level

and referenced from all realms. TAS provides services for eachrealm over the app ropriate tr ansport protocols: NetBIOS-over-TCP/

IP, NetBIOS-over-NetBEUI, IPX/ SPX, and AppleTalk.

volumes Short names for UNIX directory paths made known to TAS and its

clients. File services export volumes to clients. You mu st d efine a

volume and its corresponding directory path to make it accessible to

network clients. Include a reference to a volume for all the file

services you wish to enable for client access.

zone In the AppleTalk environment, a zone consists of a logical groupingof clients. It simplifies browsing the network for resources, such as

servers and printers, in similar domains. In a DNS (Domain Name

System) database, a zone consists of a subdirectory of the DNSdatabase. It serves as a DNS name server. This may contain a single

dom ain or several sub-dom ains. You can set up one or m ore name

servers for each zone.

zone list All of the zones associated with a particular network.

Overview of Chapters

You mu st complete Chapter 2 before you can p erform any tasks in Part II:

Administration.

Introduction 5


34/328

Part I: Initial Setup

Chapter 1 This chapter. Descriptions of new features; the u sage, terminology,

and chapters of this gu ide; related books; and TotalNET Advanced Server.

Chapter 2 Step-by-step instructions for performing initial configuration of TAS

from the UNIX command line.

Part II: Ad ministration

Chapter 3 Descriptions of the commands available to all users, including

general utilities, realm-specific utilities, shadow file utilities, and remote utilitiesfor SMB and NetWare clients.

Chapter 4 Descriptions of the commands for general administration and

configuration of TAS.

Chapter 5 Descriptions of the utilities for u se w ith DOS VLM/ NETX clients.

Chapter 6 Descriptions of N etWare login scripts for u se w ith N etWare clients.

Chapter 7 Instructions for general trou bleshooting, generating error and activity

logs, identifying error messages and conditions an d their solutions, generating

Customer Service Request (CSR) report system information, and contacting Syntax

Technical Support.

Related BooksTotalNET A dvanced Server Release Notes Instructions for installing TAS, included

with you r packaging. You m ust comp lete the appropriate steps in TotalNET A dvanced

Server Release N otes before using this TAS Reference Manual or TA S A dministration

M anual.

TAS Administration Manual On-line instructions for performing administrative

configuration of TAS from the TNAS interface.

TA S Quick Reference A sum mary of UNIX command s, included with your

packaging.



35/328

CHAPTER 2

Initial Setup Steps

This chapter provides instructions for initial configuration of TAS from the UN IX

command line. Configure TAS only after you complete all the appropriate

installation steps in the TotalNET Advanced Server Release Notes. You mu st p erform

initial configuration imm ediately after TAS installation to complete all system-level

configuration tasks.

1. Starting Initial SetupFollow these steps to begin initial setup:

1. Log in as root to the TAS host machine.

2. Change directory to the TotalN ET home di rectory $TNHOME/usr/sbin. For the

location of TNHOME on your platform, check the Solaris Server Intranet

Extensi on Inst al la t io n Library .

3. Enter the following command:

./tnsetup

The following script appears:

TotalNet Advanced Server

Press to continue. [OK]

7


36/328

4. Press Enter.


This script has attempted to discover default values for all of the

parameters required for minimum configuration of TotalNET Advanced Server.

You may modify any of the values on the following screens. If any are

displayed as a series of dashes (-), you will need to change them.

Otherwise, you may accept the defaults and these values will be used

to configure transports, realms, services, volumes and printers for

TotalNET Advanced Server.

Press to continue [OK]

2. Entering the License Key and GeneralTAS Settings1. Press Enter.

The following options appear:

General Configuration

1.License Key ---------

2.TotalNET administrator totalnet

3.TotalNET administrators group totalnet

4.Start configured services on reboot yes

Type:

a Accept all of the values as

shown.

c [ ...] Change specified item , or

all items.



37/328

h Help on item .

r Redraw menu

q Quit without changing

anything.

Option [r]

2. Enter c 1.

3. To use TAS in single-user mode, leave the license key field blank. To use TASwith multiple users, enter your TAS license key enclosed in quotes. Enter

letters in the key in the case provided by your Syntax representative. Each time

you start TAS and execute a server daemon, TAS verifies the identification

number of its host server, checks the licensed user limit, and, if applicable,checks the expiration date of the license. Contact your Syntax sales

representative to p urchase additional licenses.

4. To accept the user totalnet and the group totalnet as defaults for the TASadministrator and start configured services on reboot, continue to Step 5.

To change the name or group of the administrator or to disable the option to start

configured services on reboot, follow the approp riate instructions below. When

you finish, press Enter and continue to Step 5.

To change the name of the administrator: Enter c 2 and type the administrator

name you want.

To change the group name of the administrator: Enter c 3 and type the group

name you want.

To avoid starting your services wh en you complete configuration: Enter c 4,

then enter no.

5. Entera

to accept the values shown.The following script appears:

Checking user...


6. Press Enter.


Initial Setup Steps 9


38/328

Checking group...


7. Press Enter.


Checking license...


8. Press Enter.


Continue with these values? [yes]

9. Press Enter.

3. Configuring the LM-NT-OS/ 2 RealmThe options below appear. Options 4 and 5 do not appear if your system d oes not

supp ort NetBEUI.

LMserver Configuration

1. Enable LM-NT-OS/2 yes

2. LMserver server name hostname

3. LMserver workgroup name workgroup

4. Support for NetBEUI clients yes

5. Device for NetBEUI /dev/iee:0



39/328

Type:

a Accept all of the values as shown.

c [ ...] Change specified item or all

items.

h Help on item .

r Redraw menu

q Quit without changing anything.

Option [r]

1. To en able the LM-NT-OS/2 realm and accept all default values for file s ervice

name, workgroup name, NetBEUI services, and the NetBEUI interface name,continue to Step 2.

To d isable th e LM-NT-OS/ 2 realm or change the file service nam e, workgroup

name, NetBEUI services configuration, or NetBEUI interface nam e, follow theappropriate instructions below. When you finish, press Enter and continue to Step

2.

To disable the LM-NT-OS/ 2 realm: Enter c 1 and press Enter, then type no.

To change the file service name: Enter c 2 and press Enter, then type a service

name with 15 or fewer characters and no spaces.

To change the workgroup name: Enter c 3 and press Enter, then type the name

you want.

To disable NetBEUI client support: Enter c 4 and press Enter, then type no.

To change the NetBEUI interface name: Enter c 5 and press Enter, then type

the name you want.

2. Enter a to accept the values shown.The following options appear:

LMserver Configuration

1.Enable LM-NT-OS/2 yes

2.LMserver server name hostname



40/328

3.LMserver workgroup name workgroup

4.Support for NetBEUI clients yes

5.Device for NetBEUI /dev/iee:0


3. Press Enter.

4. Configuring the NetWare RealmThe following options appear:

NWserver Configuration

1. Enable NetWare Compatibility yes

2. NWserver name nwhostname

Type:


c [ ...] Change specified item , or all

items.

h Help on item .

r Redraw menu


1. To en able the N etWare realm and accept the def ault file service name, continue

to Step 2.



41/328

To disable the NetWare realm or change the file service name, follow the

appropriate instructions below. When you finish, press Enter and continue to Step

2.

To disable the NetWare realm: Enter c 1 and press Enter, then type no.



2. Enter a to accept the values show n.


NWserver Configuration

1. Enable NetWare Compatibility yes

2. NWserver name nwhostname


3. Press Enter.


TNIPX Configuration

Configure network numbers and Ethernet/

Token Ring frame types as defined by Novell.

If there are other NetWare or NetWare servers on the network, this script

can detect the values used and auto-

configure all of the interfaces. This is the recommended method.

1. Have the script auto-configure network interfaces to support all auto-

discovered frame types and network numbers.

2. Have the script ask you to specify options for each interface.

Option: [1]

4. To have the script auto-configure frame types and network numb ers fo r the

tnipx transport interface, enter 1. The following script appears:

This option should be selected only if there are other NetWare servers

running on the network.

Do you want to continue with option 1? [y]



42/328

To have the script prompt you for tnipx transport interface options, enter 2.

5. Enter yes (y).

5. Configu ring the Ap p leTalk RealmThe following options appear:

MACserver Configuration

1. Enable AppleTalk Compatibility yes

2. MACserver name athostname

3. AppleTalk interface /dev/le:0

Type:


c [ ...] Change specified item , or all

items.

h Help on item .

r Redraw menu.


Option [r]

1. To en able the Ap pleTalk realm and accept the default file service and i nterface

names, continue to Step 2.

To d isable th e Ap pleTalk realm or change the file service or interface name,

follow the appropriate instructions below. When you finish, press Enter and

continue to Step 2.

To disable the AppleTalk realm: Enter c 1 and press Enter, then type no.



43/328



To change the interface name: Enter c 4 and press Enter, then type the name

you want.

2. Enter a to accept the values show n.


MACserver Configuration

1. Enable AppleTalk Compatibility yes

2. MACserver name athostname

3. AppleTalk interface /dev/le:0


3. Press Enter.


The Default AppleTalk Zone is a character string specifying the logical

network this system belongs to. You must provide a value for it.

Default AppleTalk Zone [default-zonename]

4. Enter your AppleTalk zone name and press Enter.

6. Loading the Drivers an d Starting theServerThe following script appears:



44/328

Configure totalnet as the TotalNET Administrator

Enable server restart on reboot

Creating /etc/init.d/TAS

/etc/init.d/TAS created

Do NB realm setup

Adding driver tnnbu_nx...

Adding driver tnnbu_dg...

Adding driver tnnbu_ss...

Do NW realm setup

Adding driver tnipx_ex...

Adding driver tnipx...

Registering STREAMS modules tnspx and tnitp for autopush...Do AT realm setup

Adding driver tnddp...

Adding driver tnatp...

Adding driver tnasp...

Adding driver tnpap...

TAS setup completed.

You have successfully configured TAS!

For instructions on administering and configuring the server from the UNIX

command line, use the command s d escribed in Chapters 3 and 4.



45/328

CHAPTER 3

TotalNET User Commands

This chapter lists TAS user commands, which reside in the TNHOME/usr/bin

directory. The permissions of users, except for the superuser, determine the scope of

modifications the users can make w ith these commands.

This chapter contains the following sections:

General Utilities on page 17 Commands for generating information about

system components.Realm-Specific Utilities on page 39 Commands specific to the LM-NT-OS/ 2,

NetWare, and AppleTalk realms.

Shadow File Utilities on p age 73 Command s for adm inistering shad ow files

for name mapping.

Remote Utilities on page 87 Commands for administering remote system

objects.

General Utilitiestncct on page 18

tncmnames on page 19

tngettext on page 20

tninfo on page 21

tnld on page 23

tnmsgfmt on page 28

tnpasswd on page 30

tnstat on page 34

17


46/328

tnwho on p age 37

tncctThis comm and allows you to m anage client contexts for file services. It lists different

types of client context files for given realms and services and returns the UNIX pathnames of given client contexts for specified users, services, and realms.

For each file service in a realm, each user may have files whose contents have

meaning only for clients within the realm. These files must have appropriate names

and contain information clients can accept. A user can access any number of client

contexts for each service in each realm.

LocationTNHOME/usr/bin

Usagetncct -r realm -s service [-c client-context -u user]

Options

-r realm Specify a realm.

-s service Specify a service.

-c client-context Specify the client context file w hose UNX path name you

want to list.

-u user Specify the user whose client context file you want to list.

Examples1. Use the following command to list the type of client context files in the

NetWare realm for the file service myhost:

tncct -r NW -s myhost:file



47/328

2. Use the follow ing command to list the UNIX path name of the client context

file corduroy for the user schwip and the file service myhost in the

AppleTalk realm:

tncct -r AT -s myhost:file -c corduroy -u schwip

tncmnamesThis command displays a list of TotalNET character set map names.


Usagetncmnames

ExampleUse the following command to display the list of TotalNET character set map names

below:

tncmnames

Character Set Map Names

builtin-mac-roman

builtin-codepage-437

builtin-unicodebuiltin-iso-latin-1

iso-greek

codepage-850

shift-jis

euc-jp

TotalNET User Commands 19


48/328

tngettextThis command retrieves a translated text string corresponding to msgid from a

message file generated using the tnmsgfmt command. The message file name comes

from the domain argument, if present, or from the TEXTDOMAIN environment

variable. The domain text names a domain, like the message file name without the

.mo suffix. If you specify no d omain or if no correspond ing string exists, tngettextprints msgid.

This comm and looks for its message object in th e d irectory

TNHOME/usr/lib/locale/msgs/lang, where TNHOME represents the TotalNET

home directory /var/opt/totalnet. The lang variable represents the locale name.

The value of lang comes from the value of either the LC_MESSAGES or LANG

environment variables, checked in th at order; if neither of these variables exists,

tngettext prints msgid. If one or both exist, tngettext appends the value of the

LC_CHARSET environment variable to the path name. For example, message files

for the shift-jis character set reside in

TNHOME/usr/lib/locale/msgs/lang/shift-jis.

The tngettext command reads C escape sequences. Use \t for a tab and \\ for a

backslash. To set a message on a line of its own, either add \n at the end ofmsgid

or use tngettext in conjunction with the UNIX printf command . For more

information, refer to the UNIX printf(1) man page.


Usagetngettext [domain] msgid

Options

LAN G Sp ecify a local nam e.

LC_MESSAGES Specify a messaging locale. If specified, this overrides LANG for

messages.

LC_CHARSET Specify a messaging character set. If specified, this selects acharacter set directory to search for the message object file.



49/328

TEXTDO MAIN Spe cify the dom a in na m e of inte re st . The tngettext commanduses TEXTDOMAIN only if you omit tngettexts domain

argument.

TEXTDOMAINDIR Specify the path name to the message database. If present, thisreplaces TNHOME/usr/lib/locale/msgs .

tninfoThis comm and displays information abou t on e or more TotalNET client connections,

such as the connecting users, the times at which they initiate connections, and the

network addresses from which they connect. By default, the report gives the

following information about each clients connection: the users UN IX name, the file

service realm, the date and time of the connection, the number of transaction

requests serviced, and the servers network name.


Usage

tninfo [-r realm] [-t type] [-s service] [-f]

[-u user|-c client]

Options

-r realm Specify a realm.

-t type Specify a service type.

-s service Specify a service.

-f Receive com prehensive inform ation, includ ing the client

compu ters n etwork n ame, the clients n etwork ad dress,the directories to which the client has attached and their

corresponding volume names, the number of bytes readand written on each file and print service connection, and

the number of open files.



50/328

-u user Receive connection information on a user.

-c client Receive connection information about a client computer.

You can specify multiple options. The client variablerepresents the clients network name.

If you do not select a service, if no services match the conditions, or if the conditions

contradict, such as in -t file -s sparky:term, an error message appears.

Examples1. Use the foll owi ng command to get basic information about all connected TAS

clients:

tninfo

Sample Outp ut:

User Realm Startup Request Server N ame

spartacus NB Jan 19 10:390 lmspiffy:file

otto NB Jan 19 11:462 lmspock:file

2. Use the following command to get full information about user sallie:

tninfo -f -u sallie

Sample Outp ut:

User Realm Startup Request Servername

larry NB Jan 19 10:390 lmspiffy:file

Client name

X(00000101:00aa006834ba:4003)



51/328

Network address

X(00000101:00aa006834ba:4003)

3. Use the following command to get information about the user kathy:

tninfo -u kathy

Sample Ou tput:

User Realm Startup Request Server N ame

kathy NB Jan 19 10:390 lmnew:file

tnldThis comm and displays the contents of the TAS file service lock file

{TNHOME}/tndb/=flock.file in a readable format. Lock entries appear in any of

three forms: brief, long, and wide. If entries appear, a single header line

appears first, unless you use the -h option. In all of the forms, blank spaces separate

the fields in the output lines. If you specify no options, tnld uses the brief form to

display lock entries. The brief output format contains one line per lock entry. Each

line contains the following fields:



52/328

Inu m The inode num ber, a decimal string.

device A p air of decimal stringsmajor and minor d evice

numbersseparated with a comma.

lock sta te O ne of the follow ing one- to four -cha ra cter s tr ings:

C = DOS Compatibility

DN = Deny None

DNDR = Deny None and Deny Read

DNDW = Deny None and Deny Write

DR = Deny Read

DRDW = Deny Read and Deny Write

DW = Deny Write

DA = Deny All

number of clients A decimal string.

filename A UNIX file name path. It appears when you specify the -f or -soptions.

The following table shows an example of brief output format:

Inum device lock state

number of

clients filename

821 15,48 C 1 lions.doc

815 15,48 DW 2 tigers.doc

807 15,48 DRDW 2 bears.doc


Usagetnld [-h][-l] [-s] [-w] [-c client] [-f file]

[-i inode-number] [-u username]



53/328

Options

-h Supp ress the header line.

-l Use the long outpu t format. This format includes lock-entry lines

followed by client-info lines. Lock-entry lines contain t he followingorder of fields: inode num ber, device num ber, lock state, and, if

specified, file name. Each field appears as described above in th etnld d escription. Lock-entry lines begin with up to seven blank

spaces. Client-info lines give information about the file serviceclients that have the corresponding file open. Each client-info line

contains four fields, in the following order: process-id number,user n ame, realm, and service name. When a lock entry contains a

process-id num ber that does n ot m atch a current client object, theclient-info line only contains the process-id number and the string

(no client). Client-info lines begin with at least 27 blank spaces.

process-id num ber A decimal string.

user nam e A string w ith the special string (anon) for

anonymous connections.

realm One of the following strings: NB, NW, or AT.

service name A string as it would appear in the output of

tninfo -f.

-s Scan for file names. By default, lock information identifies lockedfiles by device and inode numbers, except when the -f option

selects t he file. The -s option causes tnld to scan file servicevolumes so it can d isplay the file names of locked files.

-w Use the wide output format. This format follows the long output

format, but it also includes the client name at the end of theclient-info lines. The client name, a string, appears in the output of

tninfo -f.

-c client Select entries locked by a specific file service client. Give the clientname as it appears in the outpu t of tninfo -f.

-f file Select entries for the specified file. For a non-directory file, tnld

selects entries for that file. For a directory file, tnld selects entriesfor all files in the selected directory.

-i inode-number Select entries for the specified inode number.

-u username Select entries locked by the specified UNIX user.



54/328

Examples1. Use the follow ing command to display the inode number, device number, lock

state, and number of clients:

tnld

Sample Outp ut:

Inum device state clients

229114 32,1 DN 1

2. Use one of the follow ing commands to display the inode number, device

number, lock state, number of clients, and file names:

tnld -f /home2/tmp/sh.date

tnld -s

Sample Outp ut:

Inum device state clients

229144 102,7 DN 1

filename

/home2/tmp/sh.date

3. Use the following command to display contents of the file service lock file in

long output format with lock-entry lines and without a file name:

tnld -l

Sample Outp ut:



55/328

Inum device state Pid user

229144 102,7 DN 9365 totalnet

realm service

NB spiffy:file

4. Use the following command to display the file service lock file in long output

format with lock-entry lines, and for a file name readodd.notes in the

directory /home2/tmp/:

tnld -l -f /home2/tmp/readodd.notes

Sample Ou tput:

Inum device state filename

298503 32.1 DN /home2/tmp/readodd.notes

Pid user realm service

9365 totalnet NB spiffy:file

5. Use the following command to display the file service lock file in long output

format with client-info lines for the file service client marcie:

tnld -l -c N(marcie/1/0)1901 marcie

Sample Ou tput:

Inum device state Pid user

229144 32,1 DN 9467 totalnet



56/328

realm service

NB plural:file

6. Use the following command to display the file service lock file in wide output

format with client-info lines:

tnld -w

Sample Outp ut:

Inum device state Pid user realm

229144 32,1 DN 9467 totalnet NB

service client

plural:file N(marcie/1/0)1901

tnmsgfmtThis comm and creates m essage object files from p ortable object filesthose with the

.xmsg extensionwithout changing th e portable object files. The .xmsg file contains

messages displayed to users by system command s or ap plication programs. You canedit these files and translate the messages to any language supported by the system.

All .xmsg files have the same format. Each file contains one or more lines, and each

line contains either a comment or a statement. A comment begins with a hash m ark

(#) and ends with a new-line character. The tnmsgfmt command ignores all

comments. Statements follow this format:

directive value



57/328

Each directive starts at the beginning of the line, and white spaceeither spaces or

tab charactersseparate it from value. The value variable consists of one or more

quoted strings separated by white space. Use any of the following types of directives:

domain domainname

msgid message_identifier

msgstr message_string

The value of domainname should correspond to the message file name; if you edit

messages for the tnnlc_lowutils domain, the directive should read domain

tnnlc_lowutils, and the output goes into the m essage file tnnlc_lowutils.mo.

The msgid directive specifies the value of a message identifier associated with the

directive that follows it. The message_identifier variable represents th e target string

to u se at retrieval time. Follow each msgid directive statement with a msgstr

directive statement. Do not change the msgid lines, since the code uses them as keys

to locate the translated strings defined by the msgstr lines that immed iately follow

msgid lines. Message strings m ay contain the following escape sequences:

\n new line

\t ta b

\v vertical tab

\b backspace

\r carriage return

\f form feed

\\ backslash

\ double quotes

\ddd octalbit pattern

\xDD hexadecimal bit pattern

Location

TNHOME/usr/bin



58/328

Usage

tnmsgfmt [-v] filename.xmsg

Option

-v List du plicate message identifiers in verbose format without re-definingmessage strings.

Notes1. Install mess age object files i n the directory

TNHOME/usr/lib/locale/msgs/lang[/charset/], where TNHOMErepresents the TotalNET home directory /var/opt/totalnet. The lang

variable represents the message language defined in LC_MESSAGES or in LANG,

and charset represents the message character set defined in LC_CHARSET.

2. Messages can have any length; however, each line in the .xmsg file can have

only MAX_INPUT (512) bytes. Installing message catalogs under the C locale

serves no purpose, since the command ignores them for the sake of efficiency.

tnpasswdThis comm and creates, mod ifies, and deletes TAS users passwords.

Location

TNHOME/usr/bin

Usagetnpasswd [-u username] [-r realm...] [-s script...]

tnpasswd -d username [-r realm...]

Usage for TAS-DCEYou mu st have th e TAS-DCE package installed on your system to use th is comm and:

tnpasswd [-u username] [-r realm...] [-s script...]

[-g DCE-adm-name] [-h DCE-adm-passwd]



59/328

Options

-u username Specify the name of the u ser. The superuser m ay u se thisoption to change any users password.

-r realm Specify the name of the realm.

-s script Specify a startup program for w hen a Window s 95 client

first logs on. This script must exist in a referenced volumeor an attach point nam ed netlogon in the LM-NT-OS/ 2realm.

-d username Specify the user name you want to delete or deny realm

access.

-g DCE-adm-name Specify the DCE privileged u sers nam e. You m ust usethis parameter wh en changing a DCE users password

using -r DCE.

-h DCE-adm-passwd Specify the DCE privileged u sers pa ssword . You m ustuse this parameter when changing a DCE users

password using -r DCE.

Notes

1. Any TAS us er can create a passw ord, but only the superuser root can delete

passwords. When the superuser deletes a users password for a realm, the user

does not have access to that realm. Only the superuser can reinstate a deleted

password for a realm.

2. Users can create or modify their own passw ords. If a user has different

passwords for different realms, an error message appears when the user tries to

change the password across all realms simultaneously.

3. When a user changes a password, the system prompts for the old password, thenew password, and re-entry of the new password. The system does not prompt

for the existing password when the superuser modifies or deletes the password

of a TAS user.

4. You can configure a nu ll p assword by entering a carriage return at the

password prompt.

5. When you set the client-encryption attribute to on, only users who have

entries in the TAS password file can access TAS realms. When you setclient-encryption to off, only users who have entries in the UNIX

password file can access TAS realms.



60/328

6. When you delete a TAS password, you do NOT delete the corresponding D CE

and UNIX passwords.

7. In D istributed Computing Environment (DCE), TAS regards DCE as a TotalNET

realm, along with NB, NW, AT, and UNIX. This provides a w ay of synchronizingthe passwords of all realms, including DCE if it exists on the server. When

changing a DCE users password, you should use one password for all

supported realmsNB, NW, AT, UNIX, and DCE. To change a DCE password

entry, you must use tnpasswd to define -r DCE. D efining -r DCE only

changes the DCE password. If you do not define the DCE realm, the TASsystem changes the password for all realms except DCE. You cannot create or

delete D CE user names and passwords with this command. Use the DCE

administration interface to administer D CE passwords externally.

Examples

1. Use the follow ing command to allow the superuser to create or modify the

password of user harold for all supported realms:

tnpasswd -u harold

The following prompts appear:

New password:

Re-enter new password:

2. Use the following command to create or modify the password of user haroldfor the LM-NT-OS/2 realm:

tnpasswd -u harold -r NB


Changing password for harold

New password:


3. Use the following command to delete the password of user harold and deny

harold access from all three realms:



61/328

tnpasswd -d harold

4. Use the following command to delete the password of user harold from the

NetWare realm:

tnpasswd -d harold -r NW

5. User harold can use the command below to change his password. He can use

either the -u option or no options.

tnpasswd [-u harold]


Changing password for harold

Old password:

New password:


6. Use the following command to specify the logon script win95.bat for the userharold in the LM-NT-OS/2 realm:

tnpasswd -u harold -r NB -s win95.bat

7. Use the following command to change the password of DCE user spiffy:

tnpasswd -u spiffy -r DCE


DCE privilege user account:

DCE privilege user password:

Log in as the DCE administrator. The following prompts appear:

Changing password for spiffy

Old password:

New password:




62/328

tnstatThis command displays operational status information about all realms. The output

includ es status of the TAS system an d services.


Usagetnstat [-r realm] [-t type] [-s service]

Options

-r realm Specify the realm. If you do not specify a realm, thereport contains the status of all realms.

-t type Specify the service type.

-s service Specify the service.

Examples1. Use the follow ing command to show basic TAS status information:

tnstat

Sample Outp ut:

TotalNET system is enabled.

Transports: tcpip tnipx tnatk

NBservices are up.

Transports used: tcpip

sparky:file is accepting new connects.



63/328

0 client(s) connected.

NWservices are up.

Transports used: tnipx

nwsparky:file is accepting new connects.


ATservices are up.

Transports used: tnatk

atsparky:file is accepting new connects.


2. Use the follow ing command to view the status of the N etWare realm:

tnstat -r NW

Sample Ou tput:


Transports: tcpip tnipx tnatk

NWservices are up.

Transports used: tnipx

nwmartin:file is accepting new connects.




64/328


65/328

atspatacux:file is accepting new

connects.


4. Use the following command to view the status of the file service ran in theLM-NT-OS/2 realm:

tnstat -r NB -s ran:file

Sample Ou tput:


Transports: tcpip

NBservices are up.

Transports used: tcpip

ran:file is accepting new connects.


tnwhoThis command lists the users that have current connections to the LM-NT-OS/ 2,

NetWare, or AppleTalk file or print services. The report resembles that of the UNIX

who command and includes the following information:

each users UN IX name

the file service realm

the machine name of the client

the date and time of connection started



66/328

The report normally shows only one connection per Ethernet address. A duplicate

may appear if TAS does not recognize a connection as terminated. An ungraceful

disconnection by the client, such as when the user turns off the PC or reboots

without logging out, usually causes this.


Usagetnwho [-r realm][-t type][-s service]

Options

-r realm Specify the realm.

-t type Specify the service type.

-s service Specify the service.

Examples1. Use the foll owi ng command to list users currently connected to TAS file

services:

tnwho

Sample Outp ut:

simon NB SIMONPC Jan 14 09:55

peter NB PETERPC Jan 15 10:23

2. Use the f ollowing command to list users currently connected to file services forthe LM-NT-OS/2 realm:

tnwho -r NB

3. Use the foll owi ng command to list users currently connected to the file service

spock in the LM-NT-OS/2 realm:



67/328

tnwho -r NB -s spock:file

Realm-Sp ecific UtilitiesWith the TAS 5.0 release, shad ow file utilities took over functions of several

realm-specific commands. If you cannot complete an activity as expected with a

realm-specific comman d, check Shadow File Utilities on page 73.

AppleTalk Realm:acprint on page 40

acslist on page 41

aczonelist on page 45

atattr on page 46atconvert on page 47

ddpinfo on page 50

desk on page 55

m2u on p age 56

maccp on page 57

macfsck on page 59

macmd on p age 60

macmv on page 61

macrd on page 63

macrm on p age 64

pfinfo on page 65

u2m on p age 66

LM-NT-OS/ 2 Realm:nbmessage on page 67

nbq on page 69



68/328

NetWare Realm:nwmessage on page 70

nwq on page 72

acprintThis command sends a print job to a remote AppleTalk realm printer, provided the

system contains an active AppleTalk transport, the AppleTalk ream has started, and

the remote printer supports the files format. For example, you must print PostScript

files to PostScript printers.

Location

TNHOME/usr/bin

UsageTo print a file to an AppleTalk realm printer with the given name:

acprint [-b] [-d] [-o] [-t] printername [file...]

To display the printers PAP status string:

acprint -s printername

Options

-b Remain attached to the terminal u ntil the job reaches the front of theprinters qu eue and the p rinter accepts all d ata. This option also reads

the standard input in an unbuffered mode to allow acprint to workinteractively. If you do not specify this option, the print job occurs in

the background.

-d Delete the files after they print.

-o Write output data from the printer to the standard output.

-t Turn off the default printer outpu t translation. When it displays printeroutput, acprint normally translates end-of-line markers CR an d

CR-LF to th e UNIX convention LF.



69/328

-s Acquire and display the printers PAP status string.

print ername Specify the n ame of the p rinter to receive the print job. Enter th eprinter name in the form name:type or name:type@zone . If the zone

does not exist or if you enter it as *, this command uses the hostservers local zone name. An AFP server h as the type AFPServer.

Print servers have the type LaserWriter.

file Specify the file to print.

Examples1. Use the following command to send the file rain.doc to the remote

AppleTalk realm printer atlwpr:LaserWriter@CINNEBAR and turn off the

default printer ou tput translation:

acprint -t atlwpr:LaserWriter@CINNEBAR rain.doc

2. Use the following command to send the file seattle.doc to the printer

atlwpr:LaserWriter@CINNEBAR and delete the file after it prints:

acprint -d atlwpr:LaserWriter@CINNEBAR seattle.doc

3. Use the following command to send the file northwest.doc to the printer

atlwpr:LaserWriter@CINNEBAR and write the output data from the printerto the standard output:

acprint -o atlwpr:LaserWriter@CINNEBAR northwest.doc

acslistThis comm and lists active services in the App leTalk realm.




70/328

Usageacslist [-m] [-s] [-q queries] [-w wait-secs] [pattern]

Options

-m Show multiple replies.

-s Show a single reply.

-q queries Specify the n umber of lookup queries for acslist to

send.

-w wait-secs Specify the n umber of seconds to w ait for replies toqueries.

pattern Specify a two- or three-part AppleTalk entity name, such

as AFPServer for file serv ices, or LaserWriter forprinter services.

Example1. Use the f ollowing command to list active services in the AppleTalk realm:

acslist

Sample Outp ut:

A(61443.86.150) newatkemppc:AFPServer@Cinnebar

A(61443.86.149) atkemppcd:AFPServer@Cinnebar

A(61443.86.148) atkemppc:AFPServer@Cinnebar

A(4100.246.128) SPIRO:AFPServer@*

A(11268.159.128) atNTPC:AFPServer@*

A(18948.244.128) atscorpio:AFPServer@*

A(64771.133.128) atjanepc:AFPServer@Cinnebar



71/328

A(12548.26.128) atmikhailpc:AFPServer@CINNEBAR

A(772.64.130) atspirogira:AFPServer@CINNEBAR

2. Use the command below to list active services in the AppleTalk zone

Cinnebar. AppleTalk uses = as a wild card.

acslist =:AFPServer@CINNEBAR

Sample Ou tput:

A(61443.86.150) newatkemppc:AFPServer@Cinnebar

A(61443.86.149) atkemppcd:AFPServer@Cinnebar

A(61443.86.148) atkemppc:AFPServer@Cinnebar

A(4100.246.128) SPIRO:AFPServer@*

A(11268.159.128) atNTPC:AFPServer@*

A(18948.244.128) atscorpio:AFPServer@*

A(64771.133.128) atjanepc:AFPServer@Cinnebar

A(12548.26.128) atmikhailpc:AFPServer@CINNEBAR

A(772.64.130) atspirogira:AFPServer@CINNEBAR

3. Use the follow ing command with the w ild card = to list all AppleTalkservices available in your local AppleTalk zone:

acslist =:=

Sample Ou tput:



72/328

A(77767.2.997) wallawalla:AFPServer@CINNEBAR

A(23238.1.132) simile:AFPServer@CINNEBAR

A(99977.1.131) datjunk:AFPServer@CINNEBAR

A(99977.1.130) datjunkr:LaserWriter@CINNEBAR

A(99977.1.129) junk:AFPServer@CINNEBAR

A(99977.1.128) bomb:AFPServer@CINNEBAR

A(99977.45.128) atsolx86:AFPServer@SYNTAX

A(2323.55.8) lc580:SNMP Agent@*

A(2323.55.4) lc580:Workstation@*

A(9876.55.252) powermac:Power Macintosh@*

A(9876.55.4) powermac:Workstation@*

A(6666.567.2) quadra:ARA - Client-Only@*

A(6666.567.252) quadra:Macintosh@*

A(6666.567.4) quadra:Workstation@*

A(12345.1.251) macbook:AFPServer@*

A(12345.1.252) macbook:PPCToolBox@*

A(12345.1.253) macbook:PowerBook 150@*

A(12345.6.4) macbook:Workstation@*

A(12345.6.8) NW410:SNMP Agent@*



73/328

aczonelistThis command displays a list of all zones in the AppleTalk network.


Usageaczonelist [-l]

Option

-l Display the local zone.

Examples1. Use the following command to display a list of all zones in the AppleTalk

network:

aczonelist

Sample Ou tput:

CINNEBAR

LTA 00000000

LTB 00000000

P2Ether1 A5178101

2. Use the following command to display the local zone:

aczonelist -l

Sample Ou tput:

Cinnebar



74/328

atattrThis command sets or modifies Macintosh file attributes.


Usageatattr [-C] [-V] [-v] [-u] [{+|-}bcdimrsw] filename...

Options

-C Display the program copyright message and execute thecommand.

-VDisplay the program version number and execute thecommand.

-v Execute the command in verbose form, listing files or

directories affected.

-u Display the program usage message only.

+bcdimrsw Add one or more of the attributes below.

-bcdimrsw Delete one or m ore of the attributes below.



75/328

(Attributes)

Although this command

accepts requests for adding anddeleting these attributes, it only

manipulates the c, i, and sattributes. TAS App leTalk file

services treat the otherattributes as read-only.

b Backup Required

c Copy Protect

d Delete Inhibit

i Inv isible

m Multi-User

r Rename Inhibit

s System

w Write Inhibit

filename The full or relative path to the file whose attributes you

want to change. You can n ame mu ltiple files on the samecommand line. Separate them with spaces.

Example

Use the following command to add the Invisible and Write Inhibit attributes to the

files private an d notes in the current directory, display the program version

number, and execute in written form:atattr -Vv +iw private notes

atconvertThis command converts the finder information .finderinfo and resource fork

.resource formats of p re-TAS 5.0 versions of the App leTalk realm file format, CAP

6.0, or H elios EtherShare into the TAS 5.2 shadow file structure. The d efault, if you

select no option, converts Macintosh files in pre-TAS 5.0 format to TAS 5.2 format.

The atconvert command converts Macintosh files recursively, d escending throughdirectory arguments.

CAP 6.0 stores the finder information and resource fork in the .finderinfo an d

.resource directories, respectively. The atconvert comm and converts the

information from the .finderinfo an d .resource directories into the new

structure and stores it in new shadow files. The command then deletes the

.finderinfo an d .resource directories.

Helios EtherShare stores the finder information and resource fork in a single file

directory under .rsrc. The atconvert command converts this information from

.rsrc into the new structure and stores it in new shadow files.



76/328

The atconvert command uses character set mapping when converting files

between Macintosh and TAS. With TAS installed, the server reads the host character

set value from the TAS configuration file. The client character set defaults to

builtin-mac-roman. The host character set defaults to builtin-iso-latin-1.

Location

TNHOME/usr/bin

Usageatconvert [-b] [-c] [-C charset] [-d] [-H] [-k]

directory...

Options

-b Convert Macintosh files in TAS 5.2 format to CAP 6.0

format. The -H option overrides this option.

-c Convert from CAP 6.0 format to TAS 5.2 format. The -H

option overrides this option.

-C charset Specify the client character set. If you do not specify this

option, the character set d efaults tobuiltin-mac-roman. Valid character sets include:

builtin-mac-roman

builtin-iso-latin-1

builtin-unicode

builtin-codepage-437

You can use additional character sets if you install TAS.

-d Convert Macintosh files with CAP binary compiled andUSE_MAC_DATES defined to TAS 5.2 format. The -H

option overrides this option.

-H Convert Macintosh files in Helios format to TAS 5.2

format. This op tion overrides the -b, -c, and -d options.



77/328

-k Keep the source finder information and resource fork. Ifyou do not specify this option, atconvert deletes the

original find er information and the resource fork aftercompleting the conversion. In pre-TAS 5.0 format or CAP

format, atconvert deletes all files in .finderinfo an d.resource. In Helios format, it deletes all files in .rsrc.

directory Specify the directories for file conversion.

Notes1. This command does not preserve the comment field in the finder information

when converting from Helios format to TAS format.

2. This command uses the UNIX creation/modification date of the files in allconversions except when converting CAP format to TAS format with CAP

binary compiled with USE_MAC_DATES.

3. The user who runs this command must have permission to read, write, andcreate all of the files under the directory.

4. This command preserves the original permission and ow nership of the file. Theshadow files and directories it creates have the same ownership and permission

as the parent directory. Back up the directory if you want to preserve theoriginal content.

5. Do not run the command from the root directory /.

Examples1. Use the follow ing command to convert the directory /home/totalnet and

every sub directory and fi le under it from pre-TAS 5.0 Macintosh file structure

to TAS 5.2 structure and delete the original pre-TAS 5.0 finder information and

resource fork:

atconvert /home/totalnet

2. Use the follo win g command to convert CAP directory /home/macdir to a TAS

directory, w ith USE_MAC_DATES defined when building CAP:

atconvert -c -d /home/macdir



78/328

3. Use the f ollowing command to convert Helios directory /home/heliodir to a

TAS directory:

atconvert -H /home/heliodir

ddpinfoThis command gives information about AppleTalk input and output packets and

packet errors.


Usageddpinfo [-i[x]] [-u[x]] [-r]



79/328

Options

-i Provide the interface, a list of hardware and AppleTalkaddresses, the number of input and output packets, and

the nu mber of p ackets that contained errors.

-x Give a detailed breakage of errors.

-u Provide user information broken down by protocol types,

number of input and output packets, and number of packets containing errors. The protocol types include:

RTMP Data and Response

Name Binding Protocol

App leTalk Transaction Protocol

App leTalk Echo Protocol

RTMP Requests

Zone Information Protocol

AppleTalk Data Stream Protocol

-r Provide network number and port number, or route and

router address, if applicable.

Examples1. Use one of the f ollowing commands to acquire information about an

AppleTalk interface:

ddpinfo

ddpinfo -i

Sample Ou tput:

Port 0:

name: 11c2:66

hw addr: 0800 6902 7a4e



80/328

appletalk addr: 1079/154 (0x437/0x9a)

ipkts/opkts 26579/2220, ierrs/oerrs 5/0

2. Use the foll owi ng command to receive a detailed breakdown of errors:

ddpinfo -x

Sample Outp ut:

Port 0:

name: 11c2:66

hw addr: 0800 6902 7a4e

appletalk addr: 1079/154 (0x437/0x9a)


Error breakdown:

fragment: 0

short packet: 0

too many hops: 0

indirect broadcast: 0

unreachable network: 1

inactive protocol type: 4

user queue closed: 0

no memory on input: 0

badly formatted aarp packet: 0



81/328

badly formatted ddp packet: 0

dropped due to full queue: 0

dropped due to full interface: 0

output data link: 0

interface unlinked: 0

no memory on output: 0

no output ddp stream: 0

no output aarp stream: 0

3. Use the follow ing command to acquire user information:

ddpinfo -u

Sample Ou tput:

Upper stream minor device 0:

Protocol type 6



Protocol type 3



Protocol type 1




82/328


Protocol type 2



Protocol type 4



Protocol type 0


4. Use the foll owi ng command to acquire the netw ork number and port number,or the route and router address:

ddpinfo -r

Sample Output:

Router route table entry:

range 1-1 (0x1-0x1), port number 0

router address 1000/66







83/328




range 410-410 (0x19a-0x19a), port number 0


Local route table entry:

range 1000-1100 (0x3e8-0x44c), port number 0

deskThis command lists the information in a volumes desktop database.


Usagedesk [-C][-u][-V][-{a|h|i}] volume

Options

-C Display the program copyright message and execute the

command.


-V Display the program version number and execute thecommand.



84/328

-a Display the .Adesktop file.

-h Display the header information.

-i Display the .Idesktop file.

volume Specify the relative or absolute p ath to the d irectory that

serves as the root of the Macintosh volume whose

desktop database you want to query.

Example

Use the following command to p rint the .Adesktop an d .Idesktop files for the

volume with root /usr/macvol:

desk -ai /usr/macvol

m 2uThis comm and converts all Macintosh carriage return s to UNIX linefeeds.


Usagem2u [-C][-u][-V][-v] filename...

Options

-C Display the program copyright message and execute thecommand.


-V Display the program version number and execute the

command.



85/328

-v Execute the command in verbose mode, listing all affectedfiles or directories.

filename Specify the relative or absolute path to the file requiring

conversion.

Examples

1. Use the following command to convert the files Fonts and Worklog in thecurrent directory:

m2u Fonts Worklog

2. Use the following command to convert all files ending in .doc in the directory

/usr/macvol/docs, display the program version number, and execute inverbose mode:

m2u -Vv /usr/macvol/docs/*.doc

maccpThis command has the same behavior as the tncp command. It exists for backward

compatibility only and may not appear in the next release of TAS. To copy files and

directories, use the tncp command.


Usagemaccp [-C] [-i] [-p] [-V] [-u] sourcefile targetfile

maccp [-C] [-i] [-p] [-V] [-u] sourcedir targetdir

maccp [-C] [-i

Documents

advanced server manual.pdf