Chapter 4 TotalNET Maintenance Commands

This chapter lists TotalNET system maintenance commands, which reside in the TNHOME/usr/sbin directory. It covers the following topics:

• "Administration Utilities" -- Commands for administering basic server, realm, and service functions and generating information on the status of server operations.

• "Configuration Utilities" -- Commands for controlling and delimiting the various functions of TAS.

Realm Options

Use realm options for all TotalNET user and maintenance commands at and below the realm level. These options require a set of services on which to operate. You can only specify one of each of these options at a time. Since you use realm options to select objects on which to run commands, you do not need to use all three every time.

Option	Variable	Description
-r	realm	realm
-s	name:type	service
-t	type	service type

General Configuration Options

Most of the TotalNET utilities support the following options:

-L	list
-R	read
-A	add
-M	modify
-D	delete

You can specify only one of these options at a time. By default, a command without a specified option works the same as if you specify -L. Specifying -R returns all attributes for all applicable sections, including transports, realms, and service types.

Special Options

Special options apply to some TotalNET user and maintenance commands. They identify variables for TotalNET administration and configuration commands and attributes within these commands. The following table lists all special options applicable to the TAS user and maintenance commands:

Option	Variable	Description
-a	attribute	attribute flag    Follow -a with the appropriate attribute for the command. You can use multiple -a options. In the case of Read (-R) attributes, -a specifies keys. In the cases of Modify (-M) and Add (-A) attributes, -a specifies key value pairs separated by equals signs (=). Enclose attribute values containing spaces in quotes.
-b	product	license product
-c	client-context	client context
-d	service:type	advertisement
-i	interface	interface
-j	attach-point	attach point
-l	key	license key
-m	atmap	atmap
-n	transport	transport
-o	route	route
-p	printer	printer
-s	static-name	static NetBIOS name
-u	user	user
-v	volume	volume
-x	suffix	suffix
-z	flag	tracing flag

Administration Utilities

• "atdidck"

• "tnaccept"

• "tnck"

• "tncustom"

• "tnkill"

• "tnlicense"

• "tnreject"

• "tnshut"

• "tnstart"

atdidck

This command checks for problems in the database maintained by ATdidd, the AppleTalk directory ID daemon. It looks for invalid references within the database and for the presence of database entries that do not correspond to existing UNIX directories. The atdidck command only checks the database and reports potential errors in the database to ATdidd. ATdidd then verifies that the error exists and removes the corresponding entry from the database.

For systems that support fixed directory IDs, you must run the atdidck utility periodically. You should run this utility only when you have the AppleTalk file services enabled; that is, when TAS has the ATdidd daemon running.

Location

TNHOME/usr/sbin

Usage

atdidck [-d|-a][-p path]

Options

-d	Report all entry delete requests made to ATdidd.
-a	Report all interactions with ATdidd, including requests to delete entries from the database.
-p path	Control existence checks. When you specify the variable path, TAS assumes all paths with path as a prefix exist in the UNIX file system. Use this when you wish to suppress existence checks within the UNIX file system for database entries. For example, with a file system unmounted, TAS assumes any database entries that correspond to files on that system do not exist, and it removes them from the database.

Examples

1. Use the following command to check and report all entry "delete" requests:

   atdidck -d

2. Use the following command to check and report all interactions with ATdidd:

   atdidck -a

3. Use the following command to suppress checking of all files for their existence:

   atdidck -p /

4. Use the following command to suppress checking of all subdirectories in the documents and archive directories:

   atdidck -p /documents -p /archive

tnaccept

This command causes selected services to accept client connections. The tnstart command also executes this command.

Location

TNHOME/usr/sbin

Usage

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

Options

• "Realm Options"

Examples

1. Use the following command to enable new client connection attempts:

   tnaccept

2. Use the following command to enable new connections for services in the NetWare realm.

   tnaccept -r NW

3. Use the following command to enable new connections for file services:

   tnaccept -t file

4. Use the following command to enable new connections for the file service sparky:

   tnaccept -s sparky:file

tnck

This command checks and repairs the TAS lock information and runtime database. When it finds errors, it reports them on the command line and, if you so choose, corrects them. The runtime database stores information about running transports, programs, and connected clients.

Location

TNHOME/usr/sbin

Usage

tnck [-n] [-r realm] [-t type] [-s service]

Options

• "Realm Options"

(no options)	Check and repair the runtime database for all services in all realms.
-n	Check the runtime database for a file service, without repairing it.

Examples

1. Use the following command to check the runtime database of the file service spur without repairing the database:

   tnck -n -s spur:file

2. Use the following command to check and repair all file services in the LM-NT-OS/2 realm:

   tnck -r NB -t file

3. Use the following command to check and repair the runtime database of file service spock:

   tnck -s spock:file

tncustom

This command allows you to configure the environment of tnpasswd. You can use it to configure the prompts you want tnpasswd to expect from the UNIX password program. These include prompts for user name, old password, and new password.

You can also use this command to set the name of the UNIX password command. You can define the values used for the prompts as patterns, using shell-style, or glob-style, pattern-matching. For example, you can configure the old password prompt as *[Oo]ld*word:. This means it matches all of the following prompts:

Old password:
old password:
Enter your old password:

For further information on shell-style pattern matching, refer to the UNIX man pages for the Bourne shell.

Location

TNHOME/usr/sbin

Usage

tncustom [-L]
tncustom [-R [-u utility [{-a attribute}]]
tncustom (-A|-M) -u utility {-a attribute=value}
tncustom -D -u utility

Options

• "General Configuration Options"

• " Special Options"

-u utility

Specify the utility.

Attributes

• "command"

• "new-prompt"

• "old-prompt"

• "user-prompt"

command

This attribute names the UNIX command to run when changing a user's password, along with any command-line options. It defaults to passwd.

Usage:

tncustom -A -u tnpasswd -a command=value

new-prompt

This attribute designates the patterns to match the password program's prompt for the new password. You can define any number of patterns.

Usage:

tncustom -A -u tnpasswd -a new-prompt=string

old-prompt

This attribute designates the patterns to match the password program's prompt for the old password. You can define any number of patterns.

Usage:

tncustom -A -u tnpasswd -a old-prompt=string

user-prompt

This attribute designates the patterns to match the password program's prompt for a user name. You can define any number of patterns. Most UNIX password programs do not prompt for a user name, in which case you do not need to set this attribute.

Usage:

tncustom -A -u tnpasswd -a user-prompt=string

Examples

1. Use the following command to list all defined utilities:

   tncustom -L

2. Use the following command to add the command attribute of value /usr/bin/yppasswd to the tnpasswd utility:

   tncustom -A -u tnpasswd -a command="/usr/bin/yppasswd"

3. Use the following command to modify the tnpasswd utility's new-prompt attribute, of value *[Nn]ew*word::

   tncustom -M -u tnpasswd -a new-prompt="*[Nn]ew*word:"

4. Use the following command to delete the tnpasswd utility:

   tncustom -D -u tnpasswd

5. Use the following command to read the value of the user-prompt attribute for the tnpasswd utility:

   tncustom -R -u tnpasswd -a user-prompt

   output:

   Enter Your Password:

tnkill

This command disconnects one or more service clients. The client name, either the UNIX name of a connected user or the name of the client computer as reported by tnwho or tninfo, has case-sensitivity. You must specify at least one client. Precede each client name with a -u.

You can include the minutes until disconnection and an explanation for disconnection on the command line. This warns clients and gives them time to log off. A client's screen displays increasingly frequent warning messages as the shutdown time approaches. To display the messages, the client's network software must enable the receiver capability. You must include minutes when you give a reason.

Location

TNHOME/usr/sbin

Usage

tnkill [-C] [-f] [-r realm] [-t type] [-s service]
 	{-u user|-c client} [minutes... [reason...]]

Options

• "Realm Options"

-C	Cancel the tnkill command currently in progress.
-f	Terminate all TAS client connections immediately, without sending a default system-shutdown message to connected clients.
-u user	Specify the user to disconnect. You may specify user names or client network names and use multiple -u and -c options.
-c client	Specify the client to disconnect. You may specify user names or client network names and use multiple -u and -c options.
minutes	Specify the minutes before disconnection. You must define reason to use this option. This option defaults to 0 and has no upper limit.
reason	Give the reason for the disconnection. You must define minutes to use this option. Your explanation can contain any text of up to 60 characters. If the explanation includes any of the following characters, you may need to enclose it in quotes, depending on the UNIX shell you use:  # $ & * [ ' " ` ? \ |^ !

Note

Using this command to disconnect a client does not prevent the client from reconnecting.

Examples

1. Use the following command to terminate the connections for users peter, paul, and mary immediately, without stating a reason:

   tnkill -u peter -u paul -u mary

2. Use the following command to cancel all tnkill commands you have initiated:

   tnkill -C

3. Use the following command to terminate all TAS client connections immediately, without sending a default system shutdown message to connected clients:

   tnkill -f

4. Use the command below to terminate the connections for users scotty and spock in five minutes, in order to do system backups on the superserver. These users receive the message, "Superuser shutting down in 5 minutes - system backup."

   tnkill -u scotty -u spock 5 system backup -s superserver:file

tnlicense

This command displays information about TAS licensed products. Use it to administer TotalNET licenses.

Location

TNHOME/usr/sbin

Usage

tnlicense [-h] [-l] [-d product] [-p product] [-k key] [-a key] [-m key]

Options

(no options)	Display information about the licenses for all TAS realms.
-h	Display the system host ID of the TAS host.
-l	Display the product designations of installed licensed products.
-d product	Delete the license for a product.
-p product	Display the license attributes of a product. The designation for product should exactly match one of the designations output by the tnlicense -l command.
-k key	Verify and display the license information from the license keys, including the system ID, the product, the number of users, and the user and time limits. This allows you to examine an activation key before adding it to the TAS ID database. Enclose the key in quotes to prevent misinterpretation by the UNIX shell.
-akey	Install the license for a new product, using the specified key. Enclose the key in quotes to prevent misinterpretation by the UNIX shell.
-m key	Modify the license of an existing licensed product, using the specified key. Use this option for product upgrades. Enclose the key in quotes to prevent misinterpretation by the UNIX shell.

Note

The TAS ID database resides in the TNID file in the TAS home directory.

Examples

1. Use the following command to view license information for servers installed on this host, including, for each activation key, the system ID, product, number of users, and user and time limits:

   tnlicense

2. Use the following command to view the unique identifier for the TAS host system:

   tnlicense -h

3. Use the following command to list licensed products on this host:

   tnlicense -l

4. Use the following command to delete the license information for TotalNET Client from the TotalNET ID database file:

   tnlicense -d "TotalNET Client"

5. Use the following command to view TAS license information:

   tnlicense -p "TotalNET Advanced Server"

6. Use the following command to display the license information of license key MeE)-Q65f-<YGA-iHQ>-bI>t-(P<<:

   tnlicense -k "MeE)-Q65f-<YGA-iHQ>-bI>t-(P<<"

7. Use the following command to install the license QxE)-Q87a-GB<A-iHQ>-bI>t-(P<< for a new product:

   tnlicense -a "QxE)-Q87a-GB<A-iHQ>-bI>t-(P<<"

8. Use the following command to upgrade to the license OcQ)-*56y-PU<X-aNT>-eI>w-(T<< for a new product:

   tnlicense -m "OcQ)-*56y-PU<X-aNT>-eI>w-(T<<"

tnreject

This command rejects new client connections to selected file services.

Location

TNHOME/usr/sbin

Usage

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

Options

• "Realm Options"

Examples

1. Use the following command to reject all new client connection attempts to file services:

   tnreject

2. Use the following command to reject new connections for all services in the NetWare realm:

   tnreject -r NW

3. Use the following command to reject new connections to file services:

   tnreject -t file

4. Use the following command to reject new connections to file service spock:

   tnreject -s spock:file

tnshut

This command performs an orderly shutdown of the TAS system, realms, or services. It can send connected clients a sequence of warning messages first, including the number of minutes until disconnection and an explanation. To terminate connections for specific clients, use "tnkill". Use "tnstart" to restart the server.

Location

TNHOME/usr/sbin

Usage

tnshut [-f] [-r realm] [-t type] [-s service] [minutes [reason...]]
tnshut -C [-r realm] [-t type] [-s service]
tnshut [minutes [reason...]]

Options

• "Realm Options"

-f	Shut down all TAS realms and services immediately, without sending a message to connected clients.
-C	Cancel a shutdown in progress.
minutes	Specify the number of minutes before you want TAS to shut down. If you do not specify a time, minutes defaults to 0. When you specify minutes and reason, TAS accepts client connections until five minutes before shutdown.
reason	Indicate a brief message to send to connected service clients. The clients must have message-receipt capacity. The reason can include up to 60 characters. If the explanation includes any of the following characters, you may need to enclose it in quotes, depending on your UNIX shell:  # $ & * [ ' " ` ? \ |^ !  When you specify minutes and reason, TAS accepts client connections until five minutes before shutdown.

Examples

1. Use the following command to cancel a shutdown in progress:

   tnshut -C

2. Use the following command to provide a time until disconnection and a short message:

   tnshut 10 to back up system

3. Use the following command to shut down all TAS realms and services:

   tnshut

tnstart

This command starts file, print, and transport service processes and allows client connections. The tnstart command performs the following steps:

1. Determines the location and verifies the existence of the TAS and TAS home directories.

2. Checks the TAS file service connection database and lock file.

3. Starts transport daemons, such as NBUd and IPXd.

4. Starts TAS system level programs such as TNdiskfree, realm level daemons such as NBdaemon and NWdaemon, and realm-specific programs.

5. Starts services in each realm.

   If you enable the LM-NT-OS/2 realm, a short delay occurs before you can use TAS, while NBname checks the network for NetBIOS name conflicts.

Location

TNHOME/usr/sbin

Usage

tnstart [-r realm] [-t type] [-s service]
tnstart -B [-r realm]
tnstart -F

Options

• "Realm Options"

-B	Enable the base realm--the realm without the services, transports, and other options. When you use -r with -B, TAS enables the base system and the specified realm but none of the services in the realm.
-F	Refresh the system.

Note

You must restart TAS any time you restart the UNIX system.

Examples

1. Use the following command to start TAS:

   tnstart

2. Use the following command to start the nwspock file service in the NetWare realm:

   tnstart -r NW -s nwspock:file

3. Use the following command to start the base system in the LM-NT-OS/2 realm:

   tnstart -B -r NB

Configuration Utilities

• "atkprobe"

• "ipxprobe"

• "tnadvert"

• "tnatalk"

• "tnattach"

• "tniface"

• "tnnetmgr"

• "tnpref"

• "tnprinter"

• "tnrealm"

• "tnroute"

• "tnservice"

• "tnsname"

• "tnstype"

• "tnsuffix"

• "tnsystem"

• "tntransport"

• "tnumap"

• "tnumapuser"

• "tnvolume"

• "tnvref"

atkprobe

This command discovers information about the AppleTalk setup on the specified network interface, including the range of valid network numbers, a list of available AppleTalk zone names, and the default zone name.

Location

TNHOME/usr/bin

Usage

atkprobe devicename:ppa-number

Options

devicename	Specify the network interface name.
ppa-number	Specify the Physical Point Attachment number for the Data-Link Provider Interface (DLPI). For more information, refer to the DLPI specifications.

Example

Before running atkprobe, you must shut down the server. Telnet to the server and use the following command to shut down TAS:

tnshut

To run atkprobe, you must know the device names on your AppleTalk network. To find them, use the following command.

netstat -i

If netstat -i returns the network name le0, for example, you must enter the AppleTalk interface /dev/le:0 for the device variable. To display the configuration information on /dev/le:0, enter the following command:

atkprobe /dev/le:0

Information on the specified AppleTalk transport interface, such as network range, default AppleTalk zone name, and a list of available AppleTalk zones, appears.

Sample Output:

/dev/le:0	net-range	1000-1100
/dev/le:0	default-zone	MONOPOLY
/dev/le:0	zonelist	MONOPOLY MERCURY MELANCHOLY

Use the following command to restart the server:

tnstart

ipxprobe

This command discovers information about the IPX/SPX frame type and associated network numbers in use on the specified network interface.

Location

TNHOME/usr/bin

Usage

ipxprobe devicename:ppa-number

Options

devicename	Specify the network interface name.
ppa-number	Specify the Physical Point Attachment number for the Data-Link Provider Interface (DLPI). For more information, refer to the DLPI specifications.

Example

Before running ipxprobe from the command line, you must shut down the server. Telnet to the server and use the following command to shut down TAS:

tnshut

To run ipxprobe, you must know the device names on your NetWare network. To find them, use the following command:

netstat -i

If netstat -i returns the network name le0, for example, you must enter the AppleTalk interface /dev/le:0 for the device variable. To display the configuration information on /dev/le:0, enter the following command:

ipxprobe /dev/le:0

Information on the specified NetWare transport interface, such as frame types and IPX network numbers, appears.

Sample Output:

/dev/hme:0	ethernet_ii	00000100
/dev/hme:0	ethernet_802.3	00000101
/dev/hme:0	ethernet_802.2	00000102
/dev/hme:0	ethernet_snap	00000103

Use the following command to restart the server:

tnstart

tnadvert

This command gives you the ability to manage transport advertisements for the IPX/SPX transport. You can list, read the attribute values of, create, modify, and delete advertisements.

For special cases, the IPX/SPX transport tnipx allows you to specify a static set of services for the IPX Service Advertisement Protocol (SAP) to advertise, regardless of whether you have enabled or disabled the NetWare realm.

Advertisement names, similar to service names, consist of two parts separated by a colon (:). A valid service name for the NetWare realm precedes the colon. A hexadecimal number--made up of digits and lowercase letters a through f, with no leading zeroes--that specifies the physical service type follows the colon. It has the same meaning as the type attribute of a service type object (see "tnstype""tnstype).

Location

TNHOME/usr/sbin

Usage

tnadvert -L [-n transport]
tnadvert [-R [-n transport [-d service:type
 	[{-a attribute=value}]]]]
tnadvert [(-A|-M) -n transport -d service:type
 	{-a attribute=value}]
tnadvert [-D -n transport -d service:type]

Options

• "General Configuration Options"

-n transport	Specify the IPX/SPX transport.
-d service:type	Specify the advertisement.

Attribute

fixed-socket

This attribute designates the fixed-socket number for a service. It sets the IPX socket number for the service types requested. The value for fixed-socket consists of a hexadecimal number up to four digits long. It defaults to 0. Any other indicated value represents a protocol-dependent numeric socket designation.

Usage:

tnadvert -M -n transport -d service:type -a fixed-socket=number

Examples

1. Use one of the following commands to list all available advertisements for the tnipx transport:

   tnadvert tnadvert -L tnadvert -L -n tnipx

2. Use the following command to list the value of the fixed-socket attribute for the tnipx transport and advertisement service1:4:

   tnadvert -R -n tnipx -d service1:4 -a fixed-socket

3. Use the following command to modify the value of the fixed-socket attribute of the newservice:4 advertisement of the tnipx transport by changing it to 0x20:

   tnadvert -M -n tnipx -d newservice:4 -a fixed-socket=0x20

4. Use the following command to delete the tnipx advertisement newservice:4:

   tnadvert -D -n tnipx -d newservice:4

tnatalk

This command gives you the ability to manage AppleTalk maps. You can list, read attribute values of, create, modify, and delete AppleTalk maps.

An AppleTalk map, defined at the system level, represents a set of associations between Macintosh-style file attributes and UNIX file attributes. More than one file service can reference each AppleTalk map. You can define suffixes for each AppleTalk map (see "tnsuffix").

Location

TNHOME/usr/sbin 

Usage

tnatalk [-L] 
tnatalk [-R [-m atmap {-a attribute}]]
tnatalk [(-A|-M) -m atmap {-a attribute=value}]
tnatalk [-D -m atmap]

Options

• "General Configuration Options"

-m atmap

Specify the name of the AppleTalk map.

Note

You cannot delete an AppleTalk map from the system if a volume references it.

Attribute

template-only

This attribute creates the template. If you set it to on, the corresponding map becomes a template that does not affect the runtime behavior of the system.

Usage:

tnatalk -M -m atmap -a template-only={on|off}

Examples

1. Use one of the following commands to list all available AppleTalk maps:

   tnatalk tnatalk -L

2. Use the following command to list the value of the template-only attribute of the AppleTalk map atblark:

   tnatalk -R -m atblark -a template-only

3. Use the following command to change the template-only attribute value of the AppleTalk map atblark to on:

   tnatalk -M -m atblark -a template-only=on

4. Use the following command to delete AppleTalk map atblark:

   tnatalk -D -m atblark

tnattach

This command manages attach points to file services. You can list, read attribute values of, create, modify, and delete attach points. Attach points, aliases specified for internal directories in volumes, appear to users the same as volumes.

Location

TNHOME/usr/sbin

Usage

tnattach [-L [-r realm] [-s service]
tnattach [-R [-r realm] [-s service] [-j attach-point
 	[-a attribute]]]]]
tnattach [(-A|-M) -r realm -s service -j attach-point
 	{-a attribute=value}]
tnattach [-D -r realm -s service -j attach-point]

Options

• "Realm Options"

• "General Configuration Options"

-j attach-point

Specify an attach point.

Attributes

• "path"

• "volume"

path

This attribute designates the relative path to the volume.

Usage:

tnattach -M -r realm -s service -j attach-point -a path=pathname

volume

This attribute designates the volume within which the attach point resides.

Usage:

tnattach -M -r realm -s service -j attach-point -a volume=volumename

Examples

1. Use one of the following commands to list available attach points:

   tnattach tnattach -L

2. Use the following command to list available attach points for file service myhost in the LM-NT-OS/2 realm:

   tnattach -R -r NB -s myhost:file

3. Use the following command to read the value of the attribute volume for the attach point mybin in the file service myhost in the NetWare realm:

   tnattach -R -r NW -s myhost:file -j mybin -a volume

4. Use the following command to create a new attach point mybin in the file service myhost in the AppleTalk realm:

   tnattach -A -r AT -s atmyhost:file -j mybin -a volume=myvol -a path=/export/home

5. Use the following command to change the value of the attribute volume of attach point mybin in the file service myhost in the AppleTalk realm, to home:

   tnattach -M -r AT -s atmyhost:file -j mybin -a volume=home

6. Use the following command to delete the attach point mybin from the file service myhost in the LM-NT-OS/2 realm:

   tnattach -D -r NB -s myhost:file -j mybin

tniface

This command gives you the ability to manage transport interfaces. You can list, read attribute values of, create, modify, and delete transport interfaces. Transports contain sets of network interfaces over which they operate.

Location

TNHOME/usr/sbin

Usage

tniface [-L [-n transport]]
tniface [-R [-n transport [-i interface [{-a attribute}]]]
tniface [(-A|-M) -n transport -i interface
 	{-a attribute=value}]
tniface [-D -n transport -i interface]

Options

• "Realm Options"

-n transport	Specify the transport.
-i interface	Specify the interface.

Attributes

General attributes:

• "address"

• "broadcast"

• "netmask"

Attributes specific to the tnipx transport interface:

• "device"

• "frame-type"

• "mtusize"

• "net-number"

Attributes specific to the tnatk transport interface:

• "checksum"

• "default-zone"

• "device"

• "net-range"

• "zonelist"

Attribute specific to the tnnbu transport interface:

• "device""device

address

This attribute specifies the IP address, in dot notation, to associate with the transport interface. Separate multiple addresses with spaces.

Usage:

tniface -M -n transport -i interface -a address=IP-address

broadcast

This attribute designates the IP broadcast address, in dot notation, to associate with the transport interface.

Usage:

tniface -M -n transport -i interface -a broadcast=IP-address

netmask

This attribute designates the subnet mask, in dot notation, to associate with the transport interface.

Usage:

tniface -M -n transport -i interface -a netmask=IP-address

device

This attribute designates the device name for the transport interface. For example, the following serves as the device name for the Solaris system: /dev/le:0.

Usage:

tniface -M -n transport -i interface -a device=devicename

frame-type

This attribute designates the NetWare frame type.

Usage:

tniface -M -n transport -i interface -a frame-type=frametype

mtusize

This attribute designates the maximum transfer unit size. Do not change this attribute from the default.

Usage:

tniface -M -n transport -i interface -a mtusize=size

net-number

This attribute designates the IPX network number. To find the network number for the NetWare realm, refer to the instructions below for your NetWare server's version.

NetWare 4.x Server

1. At the server console, enter the following at the colon (:) prompt:

   load install

2. On the menu that appears, select Maintenance/Selective Install.

3. Press m.

4. Press Enter.

5. Select NCF Files Options.

6. Press n.

7. Press Enter.

8. Use a text editor to open AUTOEXEC.NCF.

9. Go to the section called bind IPX. If you find more than one bind IPX section, find the one that refers to the Ethernet frame type on that system.

10. On that line, note the value used for net=nnn, where nnn represents the hexadecimal network number up to eight digits long.

11. Write down the number.

12. Exit the program by pressing the Esc button three times and then Enter.

NetWare 3.x Server

1. At the server console, enter the following at the colon (:) prompt:

   load install

2. On the menu that appears, select System Options.

3. Press s.

4. Press Enter.

5. Select AUTOEXEC.NCF.

6. Press e.

7. Press Enter.

8. Go to the section called bind IPX. If you find more than one bind IPX section, find the one that refers to the Ethernet frame type on that system.

9. On that line, note the value used for net=nnn, where nnn represents the hexadecimal network number up to eight digits long.

10. Write down the number.

11. Exit the program by pressing the Esc button three times and then Enter.

NetWare 2.x Server

1. At a NetWare client PC, log in to the PLS as any user:

   login servername/username

2. Start the system configuration program:

   syscon

3. On the menu that appears, select File Server Information.

4. Press F.

5. Press Enter.

6. Select the PLS from the list of Known NetWare Servers.

7. Press the down arrow until you highlight the server name

8. Press Enter. The file server information appears, including the hexadecimal network number up to eight digits long.

9. Write down the number.

10. Exit the program by pressing the Esc button three times and then Enter.

Usage:

tniface -M -n transport -i interface -a net-number=network-number

checksum

This attribute designates the DDP checksum control. You can set DDP checksums on or off. This release of TAS does not implement this attribute.

Usage:

tniface -M -n transport -i interface -a checksum={on|off}

default-zone

This attribute designates the default AppleTalk zone in the zone list.

Usage:

tniface -M -n transport -i interface -a default-zone=zonename

device

This attribute designates the device name for the transport interface.

Usage:

tniface -M -n transport -i interface -a device=devicename

net-range

This attribute designates the range of network numbers.

Usage:

tniface -M -n transport -i interface -a net-range=network-range

zonelist

This attribute designates the list of AppleTalk zones available for the system.

Usage:

tniface -M -n transport -i interface -a zonelist=list

device

This attribute designates the device name for the specified transport interface.

Usage:

tniface -M -n transport -i interface -a device=devicename

Examples

1. Use one of the following commands to list all available transport interfaces:

   tniface tniface -L

   Sample Output:

   tcpip
   	204.242.9.83
   tnipx
   	internal
   	le0:ethernet_ii
   	le0:ethernet_802.3
   	le0:ethernet_802.2
   	le0:ethernet_snap
   tnnbu
   	le0
   tnatk
   	le0

2. Use the following command to list all transport interface information, including the values of all defined attributes:

   tniface -R

3. Use the following command to list the value of the attribute device for the interface iee0:ethernet_802.3 in a tnipx section:

   tniface -R -n tnipx -i iee0:ethernet_802.3 -a device

4. Use the following command to change the value of the attribute address for the interface 202.224.6.124 in a tcpip section to 204.242.8.167:

   tniface -M -n tcpip -i 202.224.6.124 -a address=204.242.8.167

5. Use the following command to delete the interface le:1 from a tnipx section:

   tniface -D -n tnipx -i le:1

tnnetmgr

This command allows you manage net managers added to specified realms. It can perform the following functions: list, read the attribute values of, create, modify, and delete net managers.

Net managers monitor the hub ability of the realm. Each net manager for the realm receives Simple Network Management Protocol (SNMP) traps whenever you enable or disable the realm.

Location

TNHOME/usr/sbin

Usage

tnnetmgr [-L [-r realm]]
tnnetmgr [-R [-r realm [-g net-manager [{-a attribute}]]]]
tnnetmgr [(-A|-M) -r realm -g net-manager
 	{-a attribute=value}]
tnnetmgr [-D -r realm -g net-manager]

Options

• "Realm Options"

• "General Configuration Options"

-g net-manager

Specify the net manager.

Attributes

• "address"

• "community"

address

This attribute designates the net manager's IP address. SNMP traps should go to this address.

Usage:

tnnetmgr -M -r realm -g net-manager -a address=IP-address

community

This attribute designates the name of the community to which the net manager and the agent belong.

Usage:

tnnetmgr -M -r realm -g net-manager -a community=name

Examples

1. Use one of the following commands to list all available net managers for all installed realms:

   tnnetmgr tnnetmgr -L

   Sample Output:

   NB
   	boxx-SNMP
   	SNMP1
   NW
   	SNMP6
   AT
   	starz-SNMP

2. Use the following command to list all attribute values for the net manager starz-SNMP in the NetWare realm:

   tnnetmgr -R -r NW -g starz-SNMP

   Sample Output:

   address=204.222.67.08 community=nbset

3. Use the following command to add the values of the attributes address and community for the net manager SNMP6 in the LM-NT-OS/2 realm:

   tnnetmgr -A -r NB -g SNMP6 -a address=204.242.58.23 -a community=Cisco

4. Use the following command to delete the net manager boxx-SNMP from the LM-NT-OS/2 realm:

   tnnetmgr -D -r NB -g boxx-SNMP

tnpref

This command allows you to manage printer references made to file services. It performs the following functions: list, read the attribute values of, create, and delete printer references.

Within TAS, each file service has a list of printers it exports. Since any number of distinct file services for distinct realms can export the same printer name, exported printers receive a list of printer references. The real printers and attributes have system-level definition (see "tnprinter"). AppleTalk file services do not use printer references, because AppleTalk uses independently configured print services.

Location

TNHOME/usr/sbin

Usage

tnpref [-L [-r realm [-s service]]]
tnpref [(-A|-D) [-r realm [-s service [-p printer]]]]

Options

• "Realm Options"

• "General Configuration Options"

-p printer

Specify a printer name.

Examples

1. Use either of the following commands to list all available printer references for all file services in all realms:

   tnpref tnpref -L

   Sample Output:

   NB
   	lmpac:file
   		blahprn
   	lmpacman:tty:term
   		blark:file
   NW
   	nwmyhost:file
   		lhpprn
   		blahprn
   	nwmyhost:term  nwmyhost:nvt

2. Use the following command to list all printer references for the file service test in the NetWare realm:

   tnpref -L -r NW -s test:file

   Sample Output:

   lhpprn blahprn

3. Use the following command to add the printer hpprn to the LM-NT-OS/2 realm file service myhost:

   tnpref -A r NB -s myhost:file -p hpprn

4. Use the following command to delete the printer reference hpprn from the file service nwmyhost in the NetWare realm:

   tnpref -D -r NW -s nwmyhost:file -p hpprn

tnprinter

This command manages printers in the TAS system. A printer, initially created as a system object, does not become available until a file service references it. Consequently, you must perform two operations to reference a printer: add a printer as a system object and reference a printer. This command lists, reads, adds, modifies, and deletes TAS printer configuration options.

You must reference printers from file services to allow connections to those services. A single file service may reference any number of printers. You must define printer names in lower case.

Because each TotalNET realm has its own case-mapping scheme, the naming conventions allow volume names to conform to the style of individual realm; however, one realm may allow a printer name that another realm does not.

Printers have three naming schemes:

• Each realm has its own set of characters for use in printer names. They do not include the null character ('\0'), upper case characters, and any other characters forbidden by the realm.

• All printer names must have at least one character, and at least one realm must allow all the characters in a name.

• Clients cannot access a printer with forbidden characters for a their realms. To make a printer accessible in all realms, you must create its name only from characters that all realms allow.

Location

TNHOME/usr/sbin

Usage

tnprinter [-L]
tnprinter [-R [-p printer [{-a attribute=value}]]]
tnprinter [(-A|-M) -p printer {-a attribute=value}]
tnprinter [-D -p printer]

Options

• "Realm Options"

• "Realm Options"

-p printer

Specify a printer.

Note

You cannot delete a printer from the system if a service references it.

Attributes

• "atalk-device-name"

• "description"

• "queue"

• "share-access"

• "share-passwd"

• "spooler-options"

• "template-only"

atalk-device-name

This attribute designates the printer's AppleTalk entity name. If defined, this attribute overrides the spooler and queue attributes defined under the system for the printer object. You must have the AppleTalk transports running, and the printer name must exist in the AppleTalk network.

Usage:

tnprinter -M -p printer -a atalk-device-name=name

description

This attribute designates a description of the printer. This attribute has no default.

Usage:

tnprinter -M -p printer -a description=string

queue

This attribute designates the UNIX queue name associated with the printer.

Usage:

tnprinter -M -p printer -a queue=queuename

share-access

This LM-NT-OS/2 realm attribute designates the printer mode, of value on or off. If you set this attribute to on, clients can access the printer through NB file services using share-level and user-level security. In this case, you can set a share password for the printer. If you set this attribute to off, clients can only access the printer through an NB file service using user-level security.

Usage:

tnprinter -M -p printer -a share-access={on|off}

share-passwd

This LM-NT-OS/2 realm attribute designates the share password for the printer. This attribute applies only if you set share-access to on. Use a plain-text string for the share password. If you do not specify this option, or if the string has no value, clients can access the printer without passwords through the NetBIOS file services using share-mode security.

Usage:

tnprinter -M -p printer -a share-passwd=password-string

spooler-options

This attribute designates options to pass to the UNIX printer spooler, such as lp.

Usage:

tnprinter -M -p printer -a spooler-options=option-strings

template-only

An attribute that, if set to on, causes the volume to behave only as a template, with no effect on TotalNET system performance.

Examples

1. Use one of the following commands to list all printers defined at the system level:

   tnprinter tnprinter -L

2. Use the following command to list the value of printer attribute queue for printer blahprn:

   tnprinter -R -p blahprn -a queue

3. Use the following command to change the value of the share-access attribute for the printer macprn to on:

   tnprinter -M -p macprn -a share-access=on

4. Use the following command to delete the printer blahprn as a printer option in the system:

   tnprinter -D -p blahprn

tnrealm

This command lists, reads, modifies, creates, and deletes TAS realms and realm configuration options. The TAS environment consists of collections of services provided over specified transports in three realms:

• LM-NT-OS/2 (NB) realm

• NetWare (NW) realm

• AppleTalk (AT) realm

Location

TNHOME/usr/sbin

Usage

tnrealm -L
tnrealm -R -r realm {-a attribute}
tnrealm (-A|-M) -r realm {-a attribute=value}
tnrealm -D -r realm

Options

• "Realm Options"

• "General Configuration Options"

Attributes

Attribute applicable to all realms:

• Failed Cross Reference Format

Attributes applicable to the LM-NT-OS/2 realm:

• "anninterval"

• "lm-domain"

• "wins-servers"

• "win95-logon-script-dflt"

Attribute applicable to the NetWare realm:

• "bindery-load"

transport

This attribute designates the name of the transport protocol for the specified realm. Separate transport names with commas. Available transports consist of tcpip and tnnbu for the LM-NT-OS/2 realm, tnipx for the NetWare realm, and tnatk for the AppleTalk realm.

Usage:

tnrealm -M -r realm -a transport={tcpip|tnnbu|tnipx|tnatk}

anninterval

This attribute designates the time interval in seconds between service announcements. This attribute defaults to 300--one broadcast every 5 minutes.

Usage:

tnrealm -M -r realm -a anninterval=seconds

lm-domain

This attribute designates the NetBIOS name for a LM-NT-OS/2 domain. Unless you set up clients to use a different name, use WORKGROUP as the value for this attribute.

Usage:

tnrealm -M -r NB -a lm-domain=domain-name

wins-servers

This attribute designates the list of IP addresses of WINS servers. For servers that use this attribute, each newly-claimed NetBIOS name registers with the WINS system by calling each server in turn, until it contacts one.

Usage:

tnrealm -M -r realm -a wins-servers=value

win95-logon-script-dflt

This attribute designates the name of a default logon script supplied to Windows-95 clients during the login process and serves as the default for users not known to the server and for known users who have a missing or null win95-logon-script attribute.

Usage:

tnrealm -M -r realm -a win95-login-script-dflt=value

bindery-load

This attribute pre-loads user names into the NetWare bindery. Specifying ALL instead of a list of user names causes all UNIX user names to pre-load.

Usage:

tnrealm -M -r NW -a bindery-load={username|ALL}

Examples

1. Use either of the following commands to list all available realms:

   tnrealm tnrealm -L

   Sample Output:

   NB NW AT

2. Use the following command to list all available realms and their attribute values:

   tnrealm -R

   Sample Output:

   NB
   	transport=tcpip, tnnbu
   	lm-domain=langroup
   	anninterval=300
   	state=enabled
   NW
   	transport=tnipx
   	bindery-load=all
   	state=enabled
   AT
   	transport=tnatk
   	state=enabled

3. Use the following command to modify the announcement interval in the LM-NT-OS/2 realm:

   tnrealm -M -r NB -a anninterval=600

4. Use the following command to delete the AppleTalk realm from the system:

   tnrealm -D -r AT

tnroute

This command allows you to configure static routes for the tnipx transport. You can list, read the attribute values of, create, modify, and delete static routes. Only the IPX/SPX (tnipx) transport offers the capability to specify a set of static routes that supplement the routes determined through the transport's dynamic routing protocols.

Location

TNHOME/usr/sbin

Usage

tnroute [-L -n transport]
tnroute [-R [-n transport [-o route [{-a attribute}]]]]
tnroute [(-A|-M) -n transport -o route {-a attribute=value}
tnroute [-D -n transport -o route]

Options

• "General Configuration Options"

-n transport	Specify a transport section.
-o route	Specify a static route to configure.

Attribute

gateway

This attribute designates the router address for reaching the target IPX network address.

Usage:

tnroute -M -n transport -o route -a gateway=gateway-address

Examples

1. Use one of the following commands to list all available static routes for the tnipx transport:

   tnroute tnroute -L tnroute -L -n tnipx

   Sample Output:

   ccf2080f

2. Use the following command to list the value of attribute gateway for static route ccf2080f:

   tnroute -R -n tnipx -o ccf2080f -a gateway

3. Use the following command to add the value of the gateway attribute at address 00000101:0000a517810 for static route ccf2080f:

   tnroute -A -n tnipx -o ccf2080f -a gateway=00000101:0000a517810

4. Use the following command to delete the static route ccf2080f:

   tnroute -D -n tnipx -o ccf2080f

tnservice

This command lists, adds, modifies, and deletes TAS service configuration options. The TAS environment includes file, printer, terminal, and NVT services. TAS provides services for each supported realm over each realm's transport protocols, unless restricted by the transport attribute of the service:

• LM-NT-OS/2 realm: file and term services

• NetWare realm: file, term, and NVT services

• AppleTalk realm: file and print services

Services share resources to clients. Each consists of a proper service name, a colon, and a service type string (file, term or nvt) and uses the following format:

servicename:servicetype

A system may have any number of services defined in each of its supported realms and service types. Each service consists of numerous attributes, volume references, printer references, attach points, and client contexts.

Location

TNHOME/usr/sbin

Usage

tnservice [-L [-r realm]]
tnservice [-R [-r realm [-s service [{-a attribute}]]]
tnservice [(-A|-M) -r realm -s service {-a attribute=value}]
tnservice [-D -r realm -s service]

Options

• "Realm Options"

• "General Configuration Options"

Attributes

Attributes for all services:

• "aliases"

• "command"

• "description"

• "home"

• "persistent"

• "plex"

• "template-only"

• "transport"

• "umask"

• "user"

Attributes for file services:

• "activity"

• "attdefault"

• "authent-proxy"

• "browse-election-bias"

• "browse-election-version"

• "browse-master"

• "browse-user"

• "cachesize"

• "chpass"

• "client-charset"

• "client-encryption"

• "commandpath"

• "db-update-interval"

• "dce-authentication"

• "dfreport"

• "guest"

• "keepalive"

• "lm-announce"

• "login-control"

• "machine"

• "max-conns"

• "netiosize"

• "nice"

• "no-login"

• "null-group"

• "null-passwd-login"

• "openfiles"

• "packet-burst"

• "passwdage"

• "prdefault"

• "prelip-rpktsize"

• "preserve-whitespace"

• "restrictdcm"

• "savepass"

• "searchcount"

• "share-mode"

• "share-user"

• "smb-protocol-level "

• "spooldir"

• "trace"

• "user-map"

• "windows95-logon "

aliases

This attribute designates a list of service names that alias the given service in the LM-NT-OS/2 realm. Clients access the service through the aliases and the base name. Aliases must adhere to all the rules for legal service names in the realm and have the same service type as the base service. Each service name and alias can occur only once in the network. An alias name must not conflict with any service name or any other alias of any service. This facility can define a single LM-NT-OS/2 file service available under an ordinary name and as the default CIFS service--the one accessed when the client specifies an IP address instead of a DNS name. Do this by specifying the alias *smbserver:file for the service.

Usage:

tnservice -M -r realm -s service -a aliases=value

command

This attribute designates the UNIX command line to execute when a client makes a connection to the defined service. The UNIX shell does not interpret the command, so you cannot use shell services like quoting, wildcards, and redirection. You may include any valid parameters for the UNIX command.

Usage:

tnservice -M -r realm -s service -a command=UNIX-command

description

This attribute designates a textual description of the service. No default exists. You may need to enclose text in quotes.

Usage:

tnservice -M -r realm -s service a description=string

home

This attribute designates the full, absolute path to the home directory of the service. Use this option only when you need to have the service's working directory differ from the realm's home directory.

Usage:

tnservice -M -r realm -s service -a home=path

persistent

This attribute designates the service control. If you mark a service as "persistent", the service starts when you enable it and runs autonomously thereafter. Non-persistent services start with each incoming connection. The NetWare realm can have persistent file or NVT services.

Usage:

tnservice -M -r realm -s service -a persistent={on|off}

plex

This attribute controls whether the network claims an LM-NT-OS/2 service name as a "unique" or "group" NetBIOS name. It defaults to unique, so the service name that this file defines occurs only once on the network. Specifying group indicates that other NetBIOS services of the same name may exist on the network.

Usage:

tnservice -M -r realm -s service -a plex={unique|group}

template-only

This attribute creates a template. If you mark an object as a template by setting this attribute to on, the system treats the object as a real object, but it has no effect on the system's runtime behavior. During installation, TAS creates templates with conventional names that reflect the objects. Templates define default values for the creation of new objects. When you set this attribute to off, the object becomes real.

Usage:

tnservice -M -r realm -s service -a template-only={on|off}

transport

This attribute designates the possible protocol stacks for the service. No default exists. LM-NT-OS/2 realm services use the tcpip and tnnbu transports. NetWare realm services use the tnipx transport. AppleTalk realm services use the tnatk transport.

Usage:

tnservice -M -r realm -s service a transport={tcpip|tnnbu|tnipx|tnatk}

umask

This attribute sets the file-creation mode mask for the service. Umask, a three-digit octal-number, represents the UNIX file-creation mode mask to use. It defines the access restrictions, called "permissions", to set for files and directories. The permissions define which users can read, write, and execute/access files or directories. The first digit of the octal-number indicates permissions for the owner of the file or directory. The second digit indicates permissions for users with the same group ID as the file's owner. The third digit sets permissions for the rest of the network's users.

You can define permissions by taking the values for the permissions you want to deny and adding them to 0. The value 7 denies all access rights, and the value 0 grants all access rights. The "read" permission has a value of 4, "write" has a value of 2, and "execute" has a value of 1--for directories, this equates to the "search" permission. The umask defaults to 077, indicating full permissions for the user and no permissions for anyone else.

The following table lists permission configurations:

Umask Number	File Permission	Directory Permission
0	rw-	rwx
1	rw-	rw-
2	r--	r-x
3	r--	r--
4	-w-	-wx
5	-w-	-w-
6	---	--x
7	---	---

For example, you might use the following directory permission for the umask:

Umask Number	File Permission	Directory Permission
033	-rwxr--r--	drwxr--r--

In this case, the owner can read, write, and execute files in that directory; the group can only read files in the directory; and everyone else can only read files in the directory.

DOS and Macintosh operating systems do not distinguish between reading and executing a file, so these systems ignore the "execute" permission. For directories, it still means "search" permission. If other DOS or Macintosh users need to run programs owned by the user, they need to have "read" permission. The Macintosh operating system determines the protection setting for new file folders.

You can set the umask for specific volumes by using the umask option of the volume command for that volume. For more information on the UNIX file-creation mode mask, refer to the UNIX man pages for umask and chmod.

Usage:

tnservice -M -r realm -s service -a umask=octal-number

user

This attribute designates the UNIX user identity you should assume when you execute the UNIX command line given in the command for the service. This attribute defaults to root. In addition to inheriting the specified user identity, the server process also inherits the appropriate group list for the specified user name.

Usage:

tnservice -M -r realm -s service -a user=username

activity

This attribute controls activity logging. It specifies whether the file service maintains an activity log. It defaults to off--no log. If set to on, this attribute causes the file service to record connection activity statistics in the activity log file that resides in the TotalNET home directory. This attribute applies only to file services.

Usage:

tnservice -M -r realm -s service -a activity={on|off}

attdefault

This attribute designates the default attach point for redirected drives in LM-NT-OS/2 file services. When a client redirects a drive to the defined file service without specifying a volume or an attach point, this attribute defines the default attach point. If you do not specify a default attach point, this attribute defaults to the first volume referenced in the file service configuration sections for the service to which the client connects. You can override this attribute by assigning a default attach point to a user's configuration file.

Usage:

tnservice -M -r realm -s service
 	-a attdefault={volumename|attachname}

authent-proxy

This attribute designates a list of proxy servers that can authenticate users for TAS in the LM-NT-OS/2 and NetWare realms. If you configure this attribute, all login requests go to the proxy for processing. A user receives resource access if the proxy server returns valid authentication, as long as the user name has validity on the host server as well. By default, the user's server authenticates logins.

The proxy does not need to reside on the same host or serve as a TAS service; however, the proxy should belong to the realm of the TAS host. For example, you should specify an SMB server to authenticate passwords for the LM-NT-OS/2 realm, a Novell NetWare server to authenticate passwords for the NetWare realm, and so on.

For this attribute, the service variable represents the name of the proxy service on another TAS host authenticating passwords. The service must have the same native protocol as the service for which it provides password authentication. If the service does not reside on a TAS host, then service represents the machine name for the service. For example, if the service resides on a TAS host server called server1, you would set up this service as an authentication proxy using the following command:

tnservice -A -r realm -s service -a authent-proxy=server1:file

You should always designate file as the service type for authent-proxy. This attribute does not work you set the value of share-mode to on. The client-encryption attribute does not work when you set authent-proxy, because session setups forward to the proxy server and incur local disregard.

Usage:

tnservice -M -r realm -s service -a authent-proxy=servicename:service-type

browse-election-bias

This attribute determines how hard the service should attempt to win the browse-master election in the LM-NT-OS/2 realm. It must have a value from 0 to 255. A value of 255 causes the service to try as hard as possible to win the election. A value of 0 prevents the service from participating in browse elections. Default values for potential browse-masters reflect the operating system of the host, as follows:

• Windows for Workgroups: 1

• Windows 95: 1

• NT Workstation: 16

• NT Server: 32

Usage:

tnservice -M -r realm -s service -a browse-election-bias=0-255

browse-election-version

This attribute tunes browser elections in the LM-NT-OS/2 realm, along with the browse-election-bias attribute. It must have a value from 0 to 65536. TAS uses this parameter in browse master elections to decide between two hosts with the same operating system. A value of 65535 causes the service to try as hard as possible to win the election. A value of 0 prevents the service from participating in browse elections. This attribute has no effect if you set the browse-master attribute to off.

Usage:

tnservice -M -r realm -s service -a browse-election-version=0-65535

browse-master

This attribute determines whether this service should participate in elections and attempt to become a browse master in the LM-NT-OS/2 realm. If you set this attribute to off, the service does not attempt to become browse master for its network segment. If you set this attribute to on, the service attempts to become browse master for its segment. If you set this attribute to domain, the service becomes the domain browse master; this means that it becomes browse master for its network segment by means of rigged elections. You may only configure one service in a domain as the domain browse master. This includes file services from all vendors, not just TotalNET file services. This attribute defaults to off.

Usage:

tnservice -M -r realm -s service -a browse-master={on|off|domain}

browse-user

This attribute designates the UNIX user identity for LM-NT-OS/2 realm clients who log in solely for browsing. This attribute defaults to the TotalNET administrator, the admin-user attribute of the system object, which prevents clients from logging in. This attribute has no effect if you set the browse-master attribute to off.

Usage:

tnservice -M [-r realm][-s service] a browse-user=username

cachesize

This attribute specifies the number of entries that the directory cache should maintain for the defined LM-NT-OS/2 file service. It defaults to 5.

Usage:

tnservice -M -r NB -s service -a cachesize=size

chpass

This attribute specifies whether clients can change their passwords through the AppleTalk file service. It defaults to off.

Usage:

tnservice -M -r AT -s service -a chpass={on|off}

client-charset

This attribute designates the name of the character set used by clients of the service. If you do not specify this, the file service process chooses a default based on the realm and the negotiated properties of the client.

Usage:

tnservice -M -r realm -s service -a client-charset=name

client-encryption

This attribute specifies whether the defined file service accepts encrypted client passwords. It defaults to off. If you leave this attribute off, TAS expects clear-text passwords. If you set this attribute to on, TAS uses password files on its host. Passwords sent by clients receive encryption according to the method appropriate to that realm. You can add passwords to the TotalNET password database using tnpasswd. TAS ignores this attribute if you define authent-proxy.

Usage:

tnservice -M -r realm -s service -a client-encryption={on|off}

clienttime

This attribute specifies whether TAS honors the client time stamp values as file modification times in the LM-NT-OS/2 and AppleTalk realms. This attribute defaults to off, so TAS uses the server's system time to set file modification time stamps for all files. When you set this attribute to on, TAS uses the client's system time. The client time setting in a user's configuration file can override this attribute.

Usage:

tnservice -M -r {NB|AT} -s service -a clienttime={on|off}

commandpath

This attribute has the same effect for remote command execution that the PATH environment variable has for ordinary UNIX shell commands. The path follows the form unixdir[:unixdir]..., where unixdir represents any valid directory on the server. UNIX does not check the current directory when searching for the program to execute. Enter a period (.) as a unixdir value to have the current directory checked. When you give more than one directory, separate them with colons (:). Do not use spaces. The path can contain no more than 256 characters. This attribute defaults to /usr/bin:/bin. A commandpath attribute in a user's configuration file can override this attribute.

Usage:

tnservice -M -r realm -s service -a commandpath=path

db-update-interval

This attribute specifies the frequency of client database and resource statistics updates. It defaults to 120. If you set this attribute to 0 or a negative number, TAS never updates the database.

Usage:

tnservice -M -r realm -s service -a db-update-interval=seconds

dce-authentication

If you define this attribute, the specified file service uses DCE security rather than the native UNIX password security, such as NIS. If you define a different authentication method--for example, if you set the client-encryption or share-mode attribute to on, or if you define authent-proxy--it takes precedence over DCE security. This attribute only works when you install the TAS-DCE package. This attribute does not control the acquisition of DCE credentials. DCE-enabled host systems always acquire appropriate DCE credentials, if possible.

Usage:

tnservice -M -r realm -s service -a dce-authentication={on|off}

dfreport

This attribute specifies the method for calculating free disk space. If you set it to all, the default, TAS reports all free disk space on all partitions to clients. Systems that do not support the UNIX statfs() system call or its equivalent do not support this options. If you set this attribute to root, TAS reports only the free disk space on the partition in which the virtual root of the client's connection resides. A freespace report attribute in a user's configuration file can override this attribute.

Usage:

tnservice -M -r realm -s service -a dfreport={all|root}

guest

This attribute provides a UNIX user name for guest logins to AppleTalk realm file services.

Usage:

tnservice -M -r realm -s service -a guest=username

keepalive

This attribute enables LM-NT-OS/2 and NetWare file service connection processes to detect and close incorrectly-terminated client sessions, such as when a user turns off a client PC with a session open. You do not need to use this attribute unless the transport protocol does not provide its own keepalive function. The number variable represents the time interval, in minutes, between checks for dead connections. This attribute defaults to 0, which means the server does not use keepalives.

Usage:

tnservice -M -r {NB|NW} -s service -a keepalive=number

lm-announce

This attribute supports browsing operations by old-fashioned LM-NT-OS/2 clients that do not attempt to contact a browse master. If such clients do not exist on the network, this attribute defaults to off.

Usage:

tnservice -M -r NB -s service -a lm-announce={on|off}

login-control

This attribute defines whether a list of users can access a file service. You may enter allow or deny, followed by a list of UNIX user names separated by commas. If you define allow, TAS grants only the defined users access to the file service. If you define deny, TAS denies only the defined users access to the file service. If you define neither of these attributes, TAS grants access to all UNIX users. In the LM-NT-OS/2 realm, this attribute also has no effect if you set the share-mode attribute to on.

If defined, this attribute takes precedence over the no-login attribute. If you define both the login-control and no-login attributes for a service, which you should not do, TAS ignores the no-login attribute. You should use this attribute for login control of file services, since future releases will not support the no-login attribute.

Usage:

tnservice -M -r realm -s service -a login-control={allow|deny} username...

machine

This attribute specifies the machine type for AppleTalk "GetServerInfo" responses. The field value string describes the server's hardware or operating system. This attribute reports a null string by default.

Usage:

tnservice -M -r realm -s service -a machine=string

max-conns

This attribute specifies the maximum number of simultaneous connections that the defined NetWare service should allow. It defaults to the licensed user limit.

Usage:

tnservice -M -r NW -s service -a max-conns=number

netiosize

This attribute restricts packet size negotiations with NetWare realm clients. By default, no restrictions occur. When you define a value for netiosize, that value becomes the maximum size of packets sent to the client.

Usage:

tnservice -M -r NW -s service -a netiosize=number

nice

This attribute determines the UNIX process priority for the defined service. Define a decimal integer from -20 to +19 to pass to the UNIX nice() system call. A positive number decreases the priority; a negative number increases it. This attribute defaults to -5, which gives the process a higher priority than the UNIX default. For example, a value to 5 causes the value to increase from the default value (-5) by a factor of 10. For more information on process priorities, see the UNIX man page for nice.

Usage:

tnservice -M -r realm -s service -a nice=number

no-login

If you define this attribute, TAS does not allow the listed UNIX users to connect. By default, this attribute has no definition. This attribute does not apply to LM-NT-OS/2 services with a share-mode=on setting.

Usage:

tnservice -M -r realm -s service -a no-login=username...

null-group

This attribute identifies a UNIX group that can replace a deleted group trustee--a user or group with special permissions regarding an entrusted file or directory--of a NetWare realm file service. By default, this attribute has no definition. If you do not identify a group trustee when you use this attribute, the file owner's UNIX group becomes the trustee.

Usage:

tnservice -M -r NW -s service -a null-group=groupid

null-passwd-login

This attribute determines whether users with "null" UNIX passwords can connect to the host through TAS using the defined file service. This attribute defaults to off, which denies users without passwords access to the server. You can use this attribute to provide access through a null password guest account. This attribute only applies to services with client-encryption set to off, and it does not work for share mode file services in the LM-NT-OS/2 realm. The file service checks this attribute before sending the password to an authentication proxy server, if you define authent-proxy.

Usage:

tnservice -M -r realm -s service -a null-passwd-login={on|off}

openfiles

This attribute specifies the maximum number of files that the TAS file service may have open simultaneously.

Usage:

tnservice -M -r realm -s service -a openfiles=number

packet-burst

This attribute specifies whether the NetWare realm file service allows packet burst mode. If you set this attribute to off, the NW file service does not allow packet burst mode. It defaults to on.

Usage:

tnservice -M -r realm -s service -a packet-burst={on|off}

passwdage

This attribute specifies whether TAS supports password aging. It only applies to systems that implement UNIX System V password aging. If you set this attribute to on, the system does not allow users with aged password entries. This attribute defaults to off, which causes TAS to ignore password aging.

Usage:

tnservice -M -r realm -s service -a passwdage={on|off}

prdefault

This attribute specifies the printer to receive print jobs by redirecting a printer port and without specifying a printer name. Define the printername variable as you would for a normal UNIX platform, specifying one of this file service's referenced printers. When a client connects to the server for print service with the command net use lpt1 \\servicename [username password], TAS routes the print jobs to printername at servername. A default printer attribute in a user's configuration file can override this attribute.

Usage:

tnservice -M -r realm -s service -a prdefault=printername

prelip-rpktsize

This attribute designates the packet size restrictions for old NetWare clients located behind a router. It defaults to 576, which means no packet size restrictions occur.

Usage:

tnservice -M -r NW -s service -a prelip-rpktsize=size

preserve-whitespace

When you activate this attribute, UNIX displays spaces and tabs in the service name. You can set this attribute to off when using a UNIX application that has difficulty with file names containing white spaces. It defaults to on.

Usage:

tnservice -M -r realm -s service -a preserve-whitespace={on|off}

restrictdcm

This attribute controls the handling of DOS compatibility mode file sharing. It defaults to off.

Usage:

tnservice -M -r realm -s service -a restrictdcm={on|off}

savepass

This attribute specifies the option for AppleTalk clients to save passwords locally for later use. It defaults to off.

Usage:

tnservice -M -r realm -s service -a savepass={on|off}

searchcount

This attribute controls the allocation of directory-search contexts in the LM-NT-OS/2 and NetWare realms. This attribute defaults to 100 in the LM-NT-OS/2 realm, which means no directory-search context control occurs. You should not change this attribute from its default value.

Usage:

tnservice -M -r realm -s service -a searchcount=value

share-mode

This attribute specifies the security mode of the defined LM-NT-OS/2 realm file service. This attribute defaults to off, which means TAS implements user-level security for the service. If you set this attribute to on, TAS uses share-level security mode for the defined LM-NT-OS/2 file service.

Usage:

tnservice -M -r realm -s service a share-mode={on|off}

share-user

This attribute specifies the UNIX user name for share-level security mode access to the defined volume. This attribute applies only if the service exists and only if you set the share-mode attribute for the service to on.

Usage:

tnservice -M -r realm -s service -a share-user=username

smb-protocol-level

The name of an SMB sub-protocol for negotiation with clients, in the LM-NT-OS/2 realm. Currently, you can use the following values: core, lanman1.0, lanman2.0, and lanman2.1. Future releases will support more values. The value of this attribute represents the highest protocol level that the server uses in negotiating protocols with a client. The client can choose any protocol level up to the one specified by this attribute. This attribute takes precedence over the coreonly attribute, which TAS no longer supports. You may achieve the same effect as coreonly on with smb-protocol-level core.

Usage:

tnservice -M -r NB -s service
 	-a smb-protocol-level={core|lanman 1.0|
 	lanman 2.0|lanman 2.1}

spooldir

This attribute specifies the directory path at which spooling occurs for LM-NT-OS/2 service print jobs. Give the full path name of a valid UNIX directory with permission mode 777 (see "umask""umask). This attribute defaults to /tmp. On some UNIX systems, you should not use /tmp, because a set sticky bit may prevent the system from deleting spooled files after printing.

Usage:

tnservice -M -r NB -s service -a spooldir=path

trace

This attribute controls operations tracing in programs.

Usage:

tnservice -M -r realm -s service -a trace=string

user-map

This attribute specifies the name of a file service user map for TAS to use when converting externally-supplied user names into internal ones. If you set authent-proxy to on, TAS authenticates the external name and then converts it to its corresponding internal name; otherwise, TAS authenticates the internal name as usual. If you set client-encryption to on, TAS treats the internal name as a TAS user. Otherwise, TAS treats the internal name as a UNIX user.

If you do not define this attribute, TAS does not use a user map. This means that TAS assumes clients supply internal names--UNIX user names or TAS user names--for user names.

Usage:

tnservice -M -r realm -s service -a user-map=name

windows95-logon

If you set this attribute to on, TAS becomes the Windows 95 logon master for its LM-NT-OS/2 realm domain. A domain can contain only one active logon master.

Usage:

tnservice -M -r NB -s service -a windows95-logon={on|off}

Examples

1. Use one of the following commands to list all available services for the entire system:

   tnservice tnservice -L

   Sample Output:

   NB
   	myhost:file
   	myhost:tty:term
   NW
   	nwmyhost:file
   	nwmyhost:term
   	nwmyhost:nvt

2. Use the following command to list the values of all attributes for all services in all realms:

   tnservice -R

   Sample Output:

   NB
   	myhost:file
   		command=/opt/TAS/tn/NB/LMfile
   		description=test server
   		plex=unique
   		persistent=off
   		template-only=off
   		state=enabled
   	myhost:tty:term
   		template-only=on
   		transport=tcpip,tnnbu
   		command=/opt/TAS/tn/NB/NBtty
   		state=disabled
   NW
   	nwmyhost:file
   		template-only=off
   		command=/opt/TAS/tn/NW/NWfile
   		persistent=on
   		activity=off
   		clienttime=off
   		dfreport=all
   		null-group=4095
   		null-passwd-login=off
   		state=enabled
   	nwmyhost:term
   		template-only=on
   		command=/opt/TAS/tn/NW/NWtty
   		state=disabled
   	nwmyhost:nvt
   		template-only=on
   		command=/opt/TAS/tn/NW/NWnvtd
   		persistent=on
   		state=disabled

3. Use the following command to list the value of the command attribute for the file service myhost in the LM-NT-OS/2 realm:

   tnservice -R -r NB -s myhost:file -a command

   Sample Output:

   command=/opt/TAS/tn/NB/LMfile

4. Use the following command to modify the activity attribute for the file service nwmyhost in the NetWare realm:

   tnservice -M -r NW -s nwmyhost:file -a activity=on

5. Use the command below to delete the terminal service nwmyhost from the NetWare realm. If you delete every service in a realm, you do not delete the realm itself.

   tnservice -D -r NW -s myhost:term

tnsname

This command allows you to configure a static set of NetBIOS names with associated network addresses for a transport. You can list, read attribute values of, create, modify, and delete the static names.

The TAS NetBIOS-over-TCP/IP transport offers the capability to specify a set of static NetBIOS names--with associated IP addresses--for sites that do not wish to use the dynamic mechanisms for translating remote NetBIOS names to IP addresses. These static names may supplement the dynamically-determined NetBIOS names. Currently, only TCP/IP transports support static names.

Location

TNHOME/usr/sbin

Usage

tnsname [-L -n transport]
tnsname [-R [-n transport [-s static_name [{-a attribute}]]]]
tnsname [(-A|-M) -n transport -s static_name [{-a attribute=value}]]
tnsname -D -n transport -s static_name

Options

• "Realm Options"

• "General Configuration Options"

-n transport

Specify the transport.

-s static-name

Static NetBIOS names, similar to service names, consist of two parts separated by a colon (:). A valid service name for the LM-NT-OS/2 realm precedes the colon. A hexadecimal number (made up of digits and lowercase letters a through f, with no leading zeroes) that gives the physical service type follows the colon. It has the same meaning as the type attribute of a service type object (refer to the "tnstype""tnstype command). TAS supports Static NetBIOS names only for the tcpip transport.

Attribute

address

This attribute specifies the address associated with the given static name. The tcpip transport uses an IP address. Other transports do not have static names.

Usage:

tnsname -R -n tcpip -s static_name -a address=IP-address

Examples

1. Use one of the commands below to list all available transports and static NetBIOS names. This returns a hexadecimal output of the type code for static names.

   tnsname tnsname -L

   Sample Output:

   tnipx
   tnnbu
   tcpip
   	mth:0x20

2. Use the following command to list static NetBIOS names for the tcpip transport:

   tnsname -L -n tcpip

   Sample Output:

   mth:0x20

3. Use the following command to list the value of the attribute address for the static name mth:32 of the tcpip transport:

   tnsname -R -n tcpip -s mth:32 -a address

   Sample Output:

   address=204.242.6.122

4. Use the following command to add the value of the attribute address=204.242.8.123 for the static NetBIOS name mth:32 to the tcpip transport:

   tnsname -A -n tcpip -s mth:32 -a address=204.242.8.123

5. Use the following command to delete the static NetBIOS name mth:32:

   tnsname -D -n tcpip -s mth:32

tnstype

This command allows you to specify service types that TAS services define. You can list, read the attribute values of, add, modify, and delete service types.

This release of TAS supports file, print, terminal, and NVT services. The LM-NT-OS/2 realm uses file and terminal services, the NetWare realm uses file, terminal, and NVT services, and the AppleTalk realm uses file and print services.

Location

TNHOME/usr/sbin

Usage

tnstype [-L [-r realm]]
tnstype [-R [-r realm [-t type [{-a attribute}]]]]
tnstype [(-A|-M) -r realm -t type {-a attribute=value}]
tnstype [-D -r realm -t type]

Options

• "Realm Options"

• "General Configuration Options"

Note

You cannot delete a service type from a realm if a service of that type exists in the realm.

Attributes

• "description"

• "fixed-socket"

• "protocol"

• "type"

description

This attribute describes the service. It has no default.

Usage:

tnstype -M -r realm -t type -a description="string"

fixed-socket

This attribute specifies the fixed socket number for the NetWare service configured to the IPX/SPX protocol. Currently, this attribute exists only for backward compatibility by service types developed before the existence of the generalized IPX SAP protocol. For example, the NetWare file service always has socket number 0x651.

Usage:

tnstype -M -r realm -t type -a fixed-socket=number

protocol

This attribute defines the protocol for the defined service type. Choose from the following:

• LM-NT-OS/2 realm: NB session

• NetWare realm: SPX, IPX, or TNIL

• AppleTalk realm: AFP or PAP

Usage:

tnstype -M -r realm -t type -a protocol=protocol

type

This attribute defines the physical type code for the service type of the LM-NT-OS/2 and NetWare realms, a 16-bit hexadecimal number. The AppleTalk realm has a code number string. This attribute has no default.

Usage:

tnstype -M -r realm -t type -a type=physical-type-code

Examples

1. Use one of the following commands to list service types available for the entire system:

   tnstype tnstype -L

   Sample Output:

   NB
   	file
   	term
   NW
   	term
   	nvt
   	file

2. Use the following command to list all services and their attribute values:

   tnstype -R

3. Use the following command to list the value of the attribute protocol, for terminal services in the NetWare realm:

   tnstype -R -r NW -t term -a protocol

4. Use the following command to add the file service type to the AppleTalk realm:

   tnstype -A -r AT -t file

5. Use the following command to delete the nvt service type from the NetWare realm:

   tnstype -D -r NW -t nvt

tnsuffix

This command allows you to manage AppleTalk map suffixes. You can list, read attribute values of, add, modify, and delete suffixes from the TotalNET AppleTalk map section. Suffixes handle file extensions in AppleTalk maps. AppleTalk maps represent associations between Macintosh-style file attributes and UNIX file suffixes. You can define more than one suffix for an AppleTalk map, and more than one file service can reference an AppleTalk map.

Location

TNHOME/usr/sbin

Usage

tnsuffix -L [-m atmap]]
tnsuffix -R [-m atmap [-x suffix [{-a attribute}]]]
tnsuffix (-A|-M) [-m atmap [-x suffix
 	{-a attribute=value}]]
tnsuffix -D -m atmap -x suffix

Options

• "General Configuration Options"

-m atmap	Specify an AppleTalk map.
-x suffix	Specify the suffix to add, modify, or delete.

Attributes

• "comment"

• "conversion"

• "creator"

• "type"

comment

This attribute specifies the comment to associate with UNIX files.

Usage:

tnsuffix -M -m atmap -x suffix -a comment=string

conversion

This attribute specifies the conversion discipline to associate with UNIX files with the given suffix.

Usage:

tnsuffix -M -m atmap -x suffix -a conversion={ascii|binary}

creator

This attribute specifies the four-character Macintosh creator code to associate with UNIX files with the given suffix.

Usage:

tnsuffix -M -m atmap -x suffix
 	-a creator=Macintosh-creator-code

type

This attribute specifies the four-character Macintosh type code to associate with UNIX files with the given suffix.

Usage:

tnsuffix -M -m atmap -x suffix
 	-a type=Macintosh-type-code

Examples

1. Use one of the following commands to list all available suffixes for the entire AppleTalk realm:

   tnsuffix tnsuffix -L

   Sample Output:

   atblahmap
   	.zip
   	.ppt
   	.doc
   nnnmap
   	.xls
   	.txt
   	.ps

2. Use the following command to list all suffixes available for the AppleTalk map nnnmap:

   tnsuffix -L -m nnnmap

   Sample Output:

   .xls .txt .ps

3. Use the following command to read the value of the attribute comment for the suffix .xls in the AppleTalk map atblahmap:

   tnsuffix -R -m atblahmap -x .xls -a comment

4. Use the following command to create the suffix .ps in the AppleTalk map nnnmap:

   tnsuffix -A -m nnnmap -x .ps -a type=PS -a comment="PostScripts"

5. Use the following command to modify the value of the comment attribute to read "Microsoft Word for Windows 95 version 7.0" for the suffix .doc in the AppleTalk map atblahmap:

   tnsuffix -M -m atblahmap -x .doc -a comment="Microsoft Word for Windows 95 version 7.0"

6. Use the following command to delete the suffix .xls from the AppleTalk map atblahmap:

   tnsuffix -D -m atblahmap -x .xls

tnsystem

This command allows you to specify TAS system configuration options. You can read the attribute values and add and modify system configuration options. During its installation, TAS installs and configures a basic system by setting default values for most system configuration options. The TAS administrator's user name defaults to totalnet. The host system name defaults to the host on which you installed TAS; you cannot change this attribute. This command supports only the "read" (-R) and "modify" (-M) general configuration options. It defaults to "read".

Location

TNHOME/usr/sbin

Usage

tnsystem
tnsystem -R [{-a attribute}]
tnsystem -M {-a attribute=value}

Options

• "General Configuration Options"

Attributes

• "admin-user"

• "dfinterval"

• "host-charset"

• "host-packaging"

• "spooler"

• "start-at-boot"

• "system-name"

admin-user

This attribute specifies the TAS administrator's user name. It defaults to totalnet. TAS gives ownership of certain processes and data files to the administrator, who must own the TAS home directory TNHOME.

Usage:

tnsystem -M -a admin-user=username

dfinterval

This attribute specifies the interval, in seconds, between determinations of free disk space on the server. It defaults to 600 seconds. File services in all realms use the free space information.

Usage:

tnsystem -M -a dfinterval=interval

host-charset

This attribute specifies the host's character set. It defaults to builtin-iso-latin-1, the TAS built-in version of the ISO-8859-1 character set, a superset of the ASCII character set. File services in all realms use this information.

Usage:

tnsystem -R -a host-charset=charset

host-packaging

This attribute specifies the host's character-packaging style. It defaults to default, which indicates that the packaging style depends on the host's character set: euc if host-charset contains multi-byte characters, single if not. Besides default, you may specify single, euc, or shift-jis. File services in all realms use this information.

Usage:

tnsystem -R
 	-a host-packaging={default|single|euc|shift-jis}

spooler

This attribute specifies the full path name of the UNIX print spooler, such as lp or lpr. File and print services in all realms use this information.

Usage:

tnsystem -M -a spooler=spoolername

start-at-boot

This attribute specifies whether the TAS system starts at each system reboot. Only the TAS boot-time start-up script queries this attribute.

Usage:

tnsystem -R -a start-at-boot={on|off}

system-name

This attribute specifies the name of the system, as returned by the UNIX host name or uname -n commands. The installation program sets system-name to the nodename[] string returned by the uname(2) system call. You cannot modify this attribute.

Examples

1. Use the following command to list all system configuration attributes of the TAS system:

   tnsystem -R

   Sample Output:

   system-name=sonpc admin-user=totalnet spooler=maxar dfinterval=60 state=enabled

2. Use the following command to list the value of the attribute admin-user:

   tnsystem -R -a admin-user

   Sample Output:

   admin-user=totalnet

3. Use the following command to set the value of the attribute dfinterval to 30:

   tnsystem -M -a dfinterval=30

tntransport

This command reads, lists, adds, modifies, and deletes TAS transport configuration options. The system defines transports--low-level networking protocols referenced from realms. In the current implementation, TAS provides services for each supported realm over the corresponding transport protocols:

• LM-NT-OS/2 realm: NetBIOS-over-TCP/IP (tcpip) and NetBIOS-over-NetBEUI (tnnbu)

• NetWare realm: NetWare-over-IPX (tnipx)

• AppleTalk realm: AppleTalk (tnatk)

Location

TNHOME/usr/sbin

Usage

tntransport [-L]
tntransport [-R [-n transport [{-a attribute}]]]
tntransport [(-A|-M) -n transport {-a attribute=value}]
tntransport [-D -n transport]

Options

"General Configuration Options"General Configuration Options

-n transport

Specify the transport.

Note

You cannot delete a transport from the system if a realm references it.

Attributes

Attribute for all transports:

• "template-only"

Attributes for the tcpip transport:

• "bcast-style"

• "NB-session-port"

• "NB-ensclient"

• "NB-ens-port"

• "NB-ensclient"

• "NB-name-port"

• "NB-nd-addr"

• "NB-nd-enable "

• "NB-nd-port"

• "NB-nokeep"

• "NB-scope"

• "NB-session-port"

• "recvbuf"

• "sendbuf"

Attributes for the tnipx transport:

• "rip-age-multiple "

• "rip-age-timeout "

• "rip-bcast-interval"

• "rip-ipg"

• "rip-max-entries"

• "rip-poll-base"

• "rip-xck-multiple"

• "rip-xck-prob"

• "rip-xck-prob"

• "router"

• "sap-age-timeout"

• "sap-age-timeout"

• "sap-answer-nearest"

• "sap-bcast-interval "

• "sap-ipg"

• "sap-max-entries"

• "spxmaxpacket"

Attributes for the tnatk transport:

• "local-zone"

• "router "

template-only

With TAS, you can mark transports as templates. When you set this attribute to on, TAS treats the defined object as a real object without affecting the system's runtime behavior. The TAS installation program creates templates with names that reflect their objects. You can assign default values to templates for the system to use when creating new objects. When you set the value of template-only to off, the defined object becomes real.

Usage:

tntransport -M -n transport -a template-only={on|off}

bcast-style

This attribute specifies the host part of broadcast addresses. It applies only to a small fraction of platforms, namely those TCP/IP platforms that do not support the "get broadcast address interface" IOCTLs, such as Berkeley's SIOCGIFCONF. This attribute defaults to 255.255.255.255.

Usage:

tntransport -M -n tcpip -a bcast-style=address

NB-ensclient

This attribute only applies if this host uses multiple network interfaces for NetBIOS-over-TCP/IP. Setting this attribute to on forces the host to register multiple IP addresses with the ENS agent as equivalent.

Usage:

tntransport -M -n tcpip -a NB-ensclient={on|off}

NB-ens-port

This attribute specifies the UDP port number at which the host makes ENS services available. If the network uses ENS, you should include this attribute on every LM-NT-OS/2 realm host server as an ENS client or ENS agent (ENSA). For the UDP-port-number variable, specify a number from 0 to 65535. It should not exceed 1023. It defaults to 228.

Usage:

tntransport -M -n tcpip -a NB-ensport=UDP-port-number

NB-name-port

NB-dgram-port

NB-session-port

These attributes specify the TCP/UDP port numbers at which NetBIOS services reside. By default, these attributes do not exist, which means the same as 137, 138, and 139, respectively. Since NetBIOS clients can rarely use non-standard port numbers, these attributes generally apply only during development or troubleshooting. Do not change these attributes from their default values.

Usage:

tntransport -M -n transport
 	-a {NB-name-port|NB-dgram-port|
 	NB-session-port}=value

NB-nd-addr

This attribute specifies a list of IP addresses, in Internet dotted numeric notation, at which the ENS Network Directory Agents (NDAs) reside. Separate addresses with commas. If you do not leave this list empty, the system acts as an ENSA. This attribute supports only one NDA.

Usage:

tntransport -M -n tcpip -a NB-nd-addr=IP-address

NB-nd-enable

This attribute causes the TAS host to act as the Network Directory Agent (NDA) for the enterprise-wide network. It defaults to off.

Usage:

tntransport -M -n tcpip -a NB-nd-enable={on|off}

NB-nd-port

This attribute specifies the UDP destination port number for transmitting data to the NDA. If the network uses ENS, you should include this command on every ENSA on the network if the default port number 227 does not work, and also on all systems where the NDA resides. For port-number, specify a number from 0 to 65535. It should not exceed 1023. The default value generally suffices.

Usage:

tntransport -M -n tcpip -a NB-nd-port=port-number

NB-nokeep

This attribute enables or disables TCP keepalives. It defaults to off. If you set the option it to on, the system does not enable TCP keepalives. If the underlying TCP implementation provides keepalives, NetBIOS TCP sessions normally enable TCP keepalives. TCP keepalives differ from NetBIOS keepalives, which have separate controls.

Usage:

tntransport -M -n tcpip -a NB-nokeep={on|off}

NB-scope

This attribute specifies the NetBIOS naming scope. It allows the unique NetBIOS name to expand for use in large or dispersed networks. This attribute limits the scope--also called the logical domain--of NetBIOS names. For example, the name JOE may have the scope ADMIN. End users cannot see the scope, but the name transmitted over the network contains both parts of the name, in the form JOE.ADMIN. The addition of the naming scope prevents confusion with other nodes called JOE on other network segments.

The scope applies over at least the local network segment and to all NetBIOS names in LM-NT-OS/2 realm. It consists of any ASCII string up to 256 characters. It defaults to no naming scope.

Usage:

tntransport -M -n tcpip -a NB-scope=scope-string

recvbuf

This attribute designates the "receive" buffer size to set in TCP. This attribute defaults to 0--no "receive" buffers.

Usage:

tntransport -M -n transport -a recvbuf=bufsize

sendbuf

This attribute designates the "send" buffer size to set in TCP. This attribute defaults to 0--no "send" buffers.

Usage:

tntransport -M -n transport -a sendbuf=bufsize

rip-age-multiple

rip-age-timeout

These attributes control IPX RIP aging. Measure the first rip-age-timeout in IPX RIP polling-timer ticks and the second in seconds. By default these attributes do not exist--they default to 2 and 180, respectively. Do not change these attributes from their default values.

Usage:

tntransport -M -n tnipx -a rip-age-multiple=2
tntransport -M -n tnipx -a rip-age-timeout=180

rip-bcast-interval

This attribute determines the frequency, in seconds, at which to send IPX RIP broadcasts. It defaults to 60. Do not change this attribute from its default value.

Usage:

tntransport -M -n tnipx -a rip-bcast-interval=60

rip-ipg

This attribute determines the inter-packet gap for IPX RIP, in milliseconds. Use this attribute when one network receives multiple IPX RIP packets in succession. This attribute defaults to 40. Do not change this attribute from its default value.

Usage:

tntransport -M -n tnipx -a rip-ipg=40

rip-max-entries

This attribute designates the maximum number of IPX RIP entries for each outgoing packet. For each interface, you may reduce the value to fit within the maximum data size available. This attribute defaults to 50, the value given by Novell. Do not change this attribute from its default value.

Usage:

tntransport -M -n tnipx -a rip-max-entries=50

rip-poll-base

This attribute determines the frequency, in seconds, of IPX RIP polling-timer ticks. This controls IPX RIP aging and cross-checking. This attribute defaults to 30. Do not change this attribute from its default value.

Usage:

tntransport -M -n tnipx -a rip-poll-base=30

rip-xck-fract

rip-xck-multiple

rip-xck-prob

These attributes control IPX RIP cross-checking. Measure the first in IPX RIP polling-timer ticks. The other values represent the fraction of the IPX RIP table to check and one of two ways to check it. By default these attributes do not exist--they default to 20, 6, and 6, respectively. Do not change these attributes from their default values.

Usage:

tntransport -M -n tnipx -a rip-xck-multiple=20
tntransport -M -n tnipx -a rip-xck-fract=6
tntransport -M -n tnipx -a rip-xck-prob=6

router

This attribute specifies whether IPX Routing Information Protocol (RIP) advertises the routing services. It defaults to on.

For tnatk, this attribute controls whether the system acts as an AppleTalk router or not. It defaults to auto, which means that the system acts as a router if you specify more than one tnatk interface.

Usage:

tntransport -M -n tnipx -a router={on|off}

sap-age-interval

sap-age-timeout

These attributes control IPX SAP aging in units of seconds. By default these attributes do not exist--they default to 60 and 180, respectively. Do not change these attributes from their default values.

Usage:

tntransport -M -n tnipx -a sap-age-interval=60
tntransport -M -n tnipx -a sap-age-timeout=180

sap-answer-nearest

This attribute specifies whether IPX SAP GetNearestServer queries receive responses. It defaults to on. Do not change this attribute from the default unless so directed by Syntax Technical Support.

Usage:

tntransport -M -n tnipx
 	-a sap-answer-nearest={on|off}

sap-bcast-interval

This attribute determines the frequency, in seconds, at which to send IPX SAP broadcasts. By default this attribute does not exist--it defaults to 60. Do not change this attribute from its default value.

Usage:

tntransport -M -n tnipx -a sap-bcast-interval=60

sap-ipg

This attribute determines the inter-packet gap for IPX SAP, expressed in milliseconds. It defaults to 40. Use this command when a network receives multiple IPX SAP packets in succession.

Usage:

tntransport -M -n tnipx -a sap-ipg=40

sap-max-entries

This attribute determines the maximum number of IPX SAP entries for each outgoing packet. It defaults to 7, the value given by Novell. For each interface, you may reduce the value to fit within the maximum data size available on that interface.

Usage:

tntransport -M -n tnipx -a sap-max-entries=7

spxmaxpacket

This attribute designates the SPX maximum packet size. It defaults to off--8192. Do not change this attribute from its default value.

Usage:

tntransport -M -n tnipx -a spxmaxpacket=8192

local-zone

This attribute specifies the system's AppleTalk zone.

Usage:

tntransport -M -n tnatk -a local-zone=zonename

router

This attribute controls whether TAS acts as an AppleTalk router. It defaults to auto, which means that TAS acts as a router if you configure more than one tnatk interface.

Usage:

tntransport -M -n tnatk -a router={auto|on|off}

Examples

1. Use one of the following commands to list all available transports:

   tntransport tntransport -L

   Sample Output:

   tcpip tnipx tnnbu tnatk

2. Use the following command to list all available transports and their attribute values:

   tntransport -R

3. Use the following command to list the value for NB-ens-port, for the tcpip transport:

   tntransport -R -n tcpip -a NB-ens-port

4. Use the following command to set the value of the template-only attribute for the tnatk transport to on:

   tntransport -M -n tnatk -a template-only=on

5. Use the following command to delete the tnatk transport:

   tntransport -D -n tnatk

tnumap

This command gives you the ability to manage file-service user maps. You can list, read the attribute values of, add, modify, and delete user maps. A file service can reference only one user map.

With a user map, a file service maps user names from an external name database--such as a set of pre-existing NetBIOS, NetWare, or AppleTalk user names--to an internal name database of UNIX user names or TAS user names. TAS defines user maps at the system level. More than one file service can reference a user map. Each user map consists of a set of associations between an internal file service user name--a UNIX user--and a list of external names to map to the internal name. To add these associations, refer to "tnumapuser".

For a file service to use a user map, you need to set its user-map attribute. To do so, refer to "tnservice""tnservice. Currently, user maps do not have any attributes. If you specify the -a option, tnumap ignores it.

Location

TNHOME/usr/sbin

Usage

tnumap [-L]
tnumap [-R [-m user-map [{-a attribute}]]]
tnumap [(-A|-M) -m user-map [{-a attribute=value}]]
tnumap [-D -m user-map]

Options

"General Configuration Options"General Configuration Options

-m user-map

Specify the user map.

Examples

1. Use one of the following commands to list all available user maps:

   tnumap tnumap -L

   Sample Output:

   marketmap worker supermap

2. In future releases of TAS, you can use the following command to list the values of all attributes for the user map worker:

   tnumap -R -m worker

   Sample Output:

   This command gives no output, since user maps do not have any attributes in the current release of TAS.

3. Use the following command to create the user map worker:

   tnumap -A -m worker

4. Use the following command to delete the user map worker:

   tnumap -D -m worker

tnumapuser

This command allows you to manage users added to specified user maps. You can list, read the attribute values of, add, modify, and delete user maps.

The users objects form associations between internal user names--TAS secure-authentication or UNIX user names--and a list of external names, such as a set of pre-existing NetBIOS, NetWare, or AppleTalk user names, to map to the internal name.

Before you can add any user object to a user map, you must create the user map. Refer to "tnumap" instructions on creating a user map. You can define more than one user object for a user map, and more than one file service can reference a user map.

Location

TNHOME/usr/sbin

Usage

tnumapuser [-L [-m user-map]]
tnumapuser [-R [-m user-map [-u internal-user
 	[{-a attribute}]]]]
tnumapuser [(-A|-M) -m user-map -u internal-user
 	{-a attribute=value}]
tnumapuser [-D -m user-map -u internal-user]

Options

"General Configuration Options"

-m user-map	Specify the user map.
-u internal-user	Specify the name of the internal user.

Attribute

external-users

This attribute specifies external user names that should map to the internal user names.

Usage:

tnumapuser (-A|-M) -m user-map -u internal-user
 	-a external-users=names

Examples

1. Use one of the following commands to list all available user objects for all user maps:

   tnumapuser tnumapuser -L

   Sample Output:

   supermap totalnet johndoe carolyn worker barryw wilson danielle

2. Use the following command to list all user objects available for the user map supermap:

   tnumapuser -L -m supermap

   Sample Output:

   totalnet johndoe carolyn

3. Use the following command to read the value of the attribute external-users for the user barryw in the user map worker:

   tnumapuser -R -m worker -u barryw -a external-users

   Sample Output:

   external-users=barry_will

4. Use the following command to add the value of the attribute external-users for the user johndoe in the user map supermap:

   tnumapuser -A -m supermap -u johndoe -a external-users=john_d

5. Use the following command to delete the user totalnet for the user map supermap:

   tnumapuser -D -m supermap -u totalnet

tnvolume

This command manages volumes, created as system objects, as system-level objects. A new volume does not become available until you reference it to a service. Volume referencing requires two separate operations: adding a volume as a system object and referencing a volume. You can list, read, add, modify, and delete TotalNET volumes and volume configuration options.

The TAS environment defines volumes as directories of the UNIX file system that file services can export. This command defines volumes at the system level, since file services in different realms may export the same volume, and a file service may reference any number of volumes. Supply volume names in lower-case.

Because each TotalNET realm has its own case-mapping scheme, the naming conventions allow volume names to conform to the style of the individual realm. However, a realm may allow volume names that other realms do not.

Volume have the following naming scheme:

• Each realm has its own set of characters for use in volume names. This does not include the null character ('\0'), upper case characters, or any other characters forbidden by the realm.

• Each volume name must have at least one character, and at least one realm must allow all the characters in the name.

• Clients in a realm cannot access volumes with characters forbidden in the realm. To make a volume accessible in all realms, form its name from characters accepted by all realms.

• For the LM-NT-OS/2 realm, volume names can contain up to 12 characters; NetWare realm volume names can contain up to 15 characters; and AppleTalk realm volume names can contain up to 27 characters. You can create names exceeding these maximums, but if you do, the clients whose limits such names exceed cannot see the names in their browse lists--except for the Windows client, which truncates the volume name after the first 12 characters.

Since attach point names have fewer limitations, you may use them to lax the restrictions on volume names. You can, for example, define realm-specific synonyms for a volume shared across all realms.

Location

TNHOME/usr/sbin

Usage

tnvolume [-L] 
tnvolume [-R [-v volume [{-a attribute}]]]
tnvolume [(-A|-M) -v volume {-a attribute=value}]
tnvolume [-D -v volume]

Options

"General Configuration Options"

-v volume

Specify a volume.

Note

You cannot delete a volume from the system if a service references it.

Attributes

• "atalk-map"

• "atalk-password"

• "atalk-per-session-dids"

• "atalk-text-conv"

• "description"

• "filename-case"

• "meter"

• "path"

• "protect"

• "share-access"

• "share-passwd"

• "template-only"

• "umask"

atalk-map

This attribute specifies the name the AppleTalk realm file service uses for the volume map, to map the UNIX file name suffixes in a volume to Macintosh types and owners. You must use a genuine AppleTalk map name, not an AppleTalk map template.

Usage:

tnvolume -M -v volume -a atalk-map=map-name

atalk-password

This attribute specifies the AppleTalk password of a volume. The password applies only to the AppleTalk realm. Enter the value for the atalk-password string in plain text. You may use the following values for AppleTalk passwords: #, "", and password--the actual password.

For the "read" (-R) option, this attribute indicates the status of the AppleTalk volume password. If you cannot determine the status of the password because of access restrictions, this attribute has the value "?". It has the value "x" if the volume has an AppleTalk password, "#" if the password denies all access, and ""--the null string--if the volume has no password.

For the "add" (-A) option, this attribute specifies the AppleTalk password to apply to the volume. The "#" value denies all access. If you do not specify this attribute, or if you specify the string as "null" or "", clients can access the volume without passwords.

For the "modify" (-M) option, this attribute allows you to remove the atalk-password attribute by setting it to null or "". The volume then becomes accessible to clients without passwords.

Usage:

tnvolume -M -v volume -a atalk-password=password

atalk-per-session-dids

This attribute determines AppleTalk directory ID persistence. If you set this attribute to off, the default, AppleTalk directory IDs persistently associate themselves with directories in the volume. If you set this attribute to on, each directory ID remains only for the duration of a single client session; subsequently, features that depend on persistent IDs, such as the Macintosh O/S alias facility, do not function across successive file service sessions.

The host system requires a modest amount of overhead to maintain and manage a permanent database of directory IDs. For some volumes, especially extremely large ones like those residing on "infinite" storage devices, this overhead becomes excessive.

Usage:

tnvolume -M -v volume
 	-a atalk-per-session-dids={on|off}

atalk-text-conv

This attribute applies text file mapping to files in the volume.

Usage:

tnvolume -M -v volume -a atalk-text-conv={on|off}

description

This attribute specifies a textual description of the volume. It has no default. If your description includes symbols, enclose it in quotes. If possible, the system shows this string to clients through browsing interfaces and to administrators through administrative interfaces.

Usage:

tnvolume -M -v volume -a description=string

filename-case

This attribute controls the way file services handle the distinction between upper- and lower-case letters in file names in the volume. If you set this attribute to lower, file services handle names by translating them internally to lower-case file names. This simplifies file searches by name and results in an efficient implementation of the case-insensitivity expected by clients. Clients see file names in mixed case, but can use either case for any letters when supplying file names themselves. This file name handling can cause problems for UNIX applications that expect files to have the mixed-case names as supplied by clients.

If you set this attribute to preserve, file services look up names in their standard form in a shadow-attribute file. This allows file services to store files under UNIX in the same case-pattern used by the client, and still provide true case-insensitivity with reasonable efficiency.

If you do not define this attribute, or if you set it to default, you achieve the same effect as if you set it to preserve.

Usage:

tnvolume -M -v volume
 	-a filename-case={lower|preserve|default}

meter

This attribute controls metering. If you set it to on, UNIX records, in an event log, user attachments to the volume in all realms. You can analyze this log to derive current and historical access statistics.

Usage:

tnvolume -M -v volume -a meter={on|off}

path

This attribute specifies the absolute path of the UNIX directory that serves as the virtual root of the volume. Choose from the following strings:

%USER%	The name of user.
%GROUP%	The user's primary group name.
%CLIENT%	The name of the NetBIOS client. For the NetWare and AppleTalk realms, %CLIENT% has the same meaning as %USER%.
%HOME%	The user's home directory.
%SYSTEM%	The system name.
%REALM%	The realm name (NW, NB, or AT).
%SERVICE%	The file service name.
%%	An actual percent sign.

One volume's directory may lie within another volume. A volume cannot, however, coincide with or lie within a protected volume (see the "protect""protect attribute). Since a volume generally reveals its path only when a file attaches to it, this limitation applies, in part, during attachment.

Usage:

tnvolume -M -v volume -a path=pathname

protect

This attribute specifies the number of clients that can simultaneously access the volume. It refuses access to additional clients. Attachments count cumulatively for all realms, and a count of 0 denies all access to the volume. If the volume lies within another volume, it appears empty when a client tries to access it through the volume in which it lies. No volumes may coincide with or lie within a protected volume. This attribute helps administrators comply with software licenses. It does not support escape sequences for its path.

Usage:

tnvolume -M -v volume -a protect=limit

share-access

This attribute determines share-mode access to the volume in the LM-NT-OS/2 realm. For share mode volumes, a separate, per-volume password, rather than the UNIX user identity, controls access. This attribute defaults to off, which means clients can only access the volume through user-level security mode services. With this attribute on, clients may access the volume through share-level security mode services.

Usage:

tnvolume -M -v volume -a share-access={on|off}

share-passwd

This attribute specifies the share-mode password for a volume in the LM-NT-OS/2 realm, if you set share-access to on. Enter the value for password-string in plain text. You may use the following values for AppleTalk passwords: # (special value to deny access), "" (password checked and access allowed), and password (the actual password).

For the "read" (-R) option, this attribute indicates the status of the share-mode password. If you cannot determine the status of the password because of access restrictions, this attribute has the value "?". It has the value "x" if the volume has an share-mode password, "#" if the password denies all access, and ""--the null string--if the volume has no password.

For the "add" (-A) option, this attribute specifies the share-mode password to apply to the volume, in plain text. The "#" value indicates that the password should deny access in share mode. If you do not specify this attribute, or if you specify the string as "null" or "", clients can access the volume in share mode without passwords.

For the "modify" (-M) option, this attribute allows you to remove the share-password attribute by setting it to null or "". The volume then becomes accessible in share mode to clients without passwords.

Usage:

tnvolume -M -v volume -a share-passwd=password-string

template-only

This attribute causes the volume to behave only as a template. If you set it to on, TAS treats the object as a real object, but it has no effect on the runtime behavior of the system. The TAS installation program creates templates with conventional names reflecting the objects. It assigns default values to templates for the creation of new objects. When you set this attribute to off, the object becomes real.

Usage:

tnvolume -M -v volume -a template-only={on|off}

umask

This attribute designates the UNIX umask value for accessing the volume. Without this attribute, UNIX uses the umask of the file service when accessing the volume and can potentially override umask entries in a user's personal profile, in $HOME/.profile.file.

Usage:

tnvolume -M -v volume -a umask=value

Examples

1. Use one of the following commands to list available volumes defined at the system level:

   tnvolume tnvolume -L

   Sample Output:

   sys home ccmail myvol

2. Use the following command to list the values of all available volumes and their corresponding attributes:

   tnvolume -R

   Sample Output:

   sys
   	template-only=off
   	path=/usr/tn/NW/sys
   	share-password=
   home
   	template-only=off
   	path=%HOME%
   	atalk-text-conv=off
   	share-access=off
   	share-password=
   ccmail
   	path=/home/ccmail
   	share-access=off
   	template-only=off
   	share-password=myvolume
   	atalk-text-conv=off
   myvol
   	path=/tmp
   	share-access=off
   	template-only=off
   	share-password=

3. Use the following command to list the value of the volume attribute path for the volume home:

   tnvolume -R -v home -a path

   Sample Output:

   path=%HOME%

4. Use the following command to change the value of the share-access attribute for the volume myvolume to on:

   tnvolume -M -v myvolume -a share-access=on

5. Use the following command to delete the volume ccmail:

   tnvolume -D -v ccmail

tnvref

This command allows you to manage volume references to specified file services. You can list, read attribute values of, add, and delete volume references defined for file services.

Within the TotalNET environment, an individual file service contains a list of volume references it exports. The volumes section defines the real volumes, and their attributes, at the system level.

Location

TNHOME/usr/sbin

Usage

tnvref [-L [-r realm [-s service]] -v volume]

tnvref [(-A|-D) -r realm -s service -v volume]

Options

"General Configuration Options""General Configuration Options

-v volume

Specify a volume.

Notes

1. You cannot delete a volume reference from a service if the reference serves as the volume attribute of an attach point in the service.

2. TAS NetWare and AppleTalk realms support up to 255 volumes for a single file service connection.

Examples

1. Use one of the following commands to list all volume references by all file services in all realms:

   tnvref tnvref -L

   Sample Output:

   NW
   	nwpacman:file
   		sys
   		tmp
   		home
   	nwpacman:term
   	nwpacman:nvt
   	dnwpacman:file
   		sys
   		tmp
   		home
   AT
   	atpacman:file
   		tmp
   	mspac:file
   		bally
   		barny

2. Use the following command to list all volume references for the file service myhost in the LM-NT-OS/2 realm:

   tnvref -L -r NB -s myhost:file

   Sample Output:

   sys tmp home

3. Use the following command to add a volume reference by defining the volume name ccmail for the file service myhost in the LM-NT-OS/2 realm:

   tnvref -A -r NB -s myhost:file -v ccmail

4. Use the following command to delete the volume reference ccmail from the file service nwmyhost in the NetWare realm:

   tnvref -D -r NW -s nwmyhost:file -v ccmail