Chapter 2 - Preparing to Install StreetTalk for Windows NT Software
During installation, StreetTalk for Windows NT base software is loaded on your server from CD-ROM or from a directory on your Windows NT Server or on another Windows NT Server on the Microsoft network. The base software consists of:
![]()
StreetTalk Naming service ![]()
StreetTalk Communications Protocols ![]()
StreetTalk Server Service ![]()
StreetTalk Security Service ![]()
StreetTalk Directory Assistance (STDA) service ![]()
StreetTalk File and Print
In addition to installing the base software, you can install all other components of the product or customize the installation. You can choose to install Backup Suite for StreetTalk, StreetTalk Intelligent Messaging, StreetTalk Network Management, and Server-to-Server UDP, or you can install this software after you install the base software. You can also install Banyan Enterprise Client for Windows NT, StreetTalk Explorer, and VINES Files client components.
To install Banyan StreetTalk for Windows NT software on your server, you must have the minimum hardware, software, and administrative requirements described in this section. You should also check the StreetTalk for Windows NT Release Notice for requirements added after this guide was completed.
You can install Banyan StreetTalk for Windows NT software only on Intel-based servers. You must have the following minimum hardware features on your computer:
![]()
An Intel-based computer with a minimum of 64 MB of memory. Windows NT 4.0 Server requires an Intel 486 processor and above. A minimum of 64 MB of memory is required if you run all types of services on your server. More memory may be required depending on the number and types of services that you install and run. ![]()
75 MB (minimum) free disk space available for StreetTalk for Windows NT, assuming you use one version of VINES Files. Each language version of VINES Files requires approximately 25 MB of disk space. This is in addition to the space required by the Windows NT operating system and by other software required on your system. Table 2-2 describes the approximate disk space requirements for StreetTalk for Windows NT components. ![]()
A CD-ROM drive. ![]()
An Ethernet, Token-Ring, or FDDI adapter with an NDIS-compliant driver installed and configured.
StreetTalk for Windows NT software supports multiprocessor Windows NT systems.
![]()
You can install StreetTalk for Windows NT on Windows NT Server version 4.0 only. Windows NT Server software is optimized to run services and supports more than one processor. ![]()
You must install Windows NT Service Pack 3 or Service Pack 4 to support StreetTalk for Windows NT on Windows NT Server 4.0. ![]()
StreetTalk for Windows NT software can be installed on an NTFS partition only. You cannot install any StreetTalk for Windows NT components on a FAT (DOS) or HPFS (OS/2) file partition. The root of a StreetTalk for Windows NT file service can be located on a FAT or HPFS file partition but the StreetTalk File software (STFILE.EXE) must reside on NTFS. NTFS provides the level of security needed to protect information in the StreetTalk for Windows NT databases. The NTFS partition can be any partition on your system. It does not have to be same partition on which Windows NT is installed. Before you begin the installation, format an NTFS partition if one on which you want to install StreetTalk for Windows NT does not exist. See the NTFS Partition section later in this chapter for more information.
![]()
To configure and manage StreetTalk for Windows NT file and print software, you must install the StreetTalk Explorer management tool on the StreetTalk for Windows NT server or on a Banyan Windows NT or Windows 95/98 client. The StreetTalk Explorer software is installed from the Banyan Client Components CD-ROM. Chapter 3 and the Client Components Suite CD-ROM Installation Guide explains how to install StreetTalk Explorer. ![]()
StreetTalk for Windows NT does not require a particular Windows NT domain model (for example, single domain, master domain, and so on). Since Windows NT Server software requires the configuration of a domain, you should configure domains to suit the needs of your Microsoft network. ![]()
Microsoft TCP/IP software must be installed and configured to support IP Client workstations or Server-to-Server UDP (S-to-S UDP) software or both. ![]()
If your server has S-to-S UDP software installed, you may need the hostnames, serial numbers, and IP addresses of all the StreetTalk for Windows NT servers that have S-to-S UDP software and that will communicate with your server.
Preparing to Install StreetTalk for Windows NT
Before you run the installation program, have available the information described in the next sections. A worksheet is provided at the end of the chapter to record the information you need when you run the installation program.
If you have any of the following installed on your system and you want to install StreetTalk for Windows NT software, you must first uninstall these:
![]()
A version of StreetTalk Access for Windows NT File and Print software ![]()
The Banyan Enterprise Client for Windows NT installed on a Windows NT server (not on a StreetTalk for Windows NT server) ![]()
The StreetTalk for Windows NT 7.x Client Workstation component of StreetTalk for Windows NT 7.x
Upgrading from StreetTalk Access Software
To uninstall StreetTalk Access:
1. Log in to the Banyan network as the administrator of the StreetTalk group in which the StreetTalk Access services reside.
2. Stop StreetTalk Access services on the Windows NT system. To stop StreetTalk Access services click on the StreetTalk Access Services icon, select, in turn, StreetTalk File and StreetTalk Print and click Stop.
3. Run the DUMPARL program to list the Access Rights Lists (ARLs) on the directories of the file service. Managing StreetTalk for Windows NT Services describes the DUMPARL program. You must do this to save information about any access rights configured when StreetTalk Access was configured. Uninstalling StreetTalk File removes the ARLs but leaves the data residing in the Windows NT directory unaffected.
4. Insert the StreetTalk Print diskette in the diskette drive.
Note: It is important that you remove StreetTalk Print before you remove StreetTalk File.
5. Select Run from the File menu. The Run dialog box appears.
6. Enter:
a:\uninstal
where a corresponds to the drive in which you inserted the diskette.
The StreetTalk Print software and the StreetTalk Print entries in the Windows NT Registry are removed from the Windows NT system.
7. Insert the StreetTalk File diskette in the diskette drive.
8. Select Run from the File menu. The Run dialog box appears.
9. Enter:
a:\uninstal
where a corresponds to the drive in which you inserted the diskette.
The StreetTalk File software, the StreetTalk names assigned to each NT directory, and the StreetTalk File entries in the Windows NT Registry are removed from the Windows NT system.
10. Delete the empty StreetTalk Access Program Group.
11. Uninstall the Banyan Enterprise Client for Windows NT software. To do this, insert the Banyan Client Components CD-ROM in the CD-ROM and enter:
d:\winnt\setup.exe /uninstall
where d is the CD-ROM drive on your system.
12. Reboot your system. The uninstall process is completed only when the system is rebooted.
13. If StreetTalk Access was installed on a FAT partition and you want to install StreetTalk for Windows NT on the same partition, convert the partition to NTFS. See NTFS Partition later in this chapter.
14. Follow the steps to prepare StreetTalk for Windows NT that are described in this chapter. Install StreetTalk for Windows NT as described in Chapter 3 and then recreate the ARL settings based on the DUMPARL listing.
If the Uninstall program runs while the StreetTalk Access user is logged in to the Banyan network, it deletes the PC-based StreetTalk Access File and Print services on the native VINES server on which the services were created. If the is user was not logged in, delete the services on the VINES server manually.
StreetTalk for Windows NT software will replace StreetTalk Access software with these results:
![]()
The partition on which the StreetTalk for Windows NT software will be installed is checked to see that it is an NTFS partition ![]()
All StreetTalk File data areas are unaffected ![]()
File and print services run as server-based rather than PC-based services. ![]()
The StreetTalk for Windows NT communications protocol stack replaces the Banyan Enterprise Client for Windows NT software.
Removing StreetTalk for Windows NT 7.x Client Workstation Component
If you installed the StreetTalk for Windows NT 7.x Client Workstation component on your StreetTalk for Windows NT 7.x server, you must remove it before installing StreetTalk for Windows NT 8.x. To do so, follow these steps:
1. Double-click the Uninstall icon in your StreetTalk for Windows NT program group (Windows NT 3.51) or select the program from your Windows NT Start menu (Windows NT 4.0).
2. Click Next until the Installed Components screen appears.
3. Select the StreetTalk Client Workstation component for removal and click Next.
4. At the Confirm Selection screen, check the selected component and click Next.
5. At the Uninstall Complete screen click Finish to reboot the server. You must reboot to complete the uninstallation procedure.
Removing Banyan Enterprise Client for Windows NT
If you have the Banyan Enterprise Client for Windows NT installed on your Windows NT server but do not have StreetTalk for Windows NT installed, and you want to install StreetTalk for Windows NT, you must first uninstall the Banyan Enterprise Client for Windows NT software:
1. . Insert the Banyan Client components CD-ROM in the CD-ROM and enter:
d:\winnt\setup.exe /uninstall
where d is the drive letter of your CD-ROM.
2. Reboot your system unless you are going to convert a FAT partition to an NTFS partition. If you convert a partition (see Step 3), you can reboot your system after the conversion.
3. If Enterprise Client for Windows NT software was installed on a FAT partition and you want to install StreetTalk for Windows NT on the same partition, convert the partition to NTFS. See the NTFS Partition section later in this chapter.
4. Follow the steps to prepare StreetTalk for Windows NT that are described in this chapter and then install StreetTalk for Windows NT as described in Chapter 3.
StreetTalk for Windows NT can be installed on an NTFS partition only. (The StreetTalk database is stored on an NTFS partition.) If you attempt to install StreetTalk for Windows NT software on a non- NTFS partition, an error message is displayed and the installation is terminated.
To convert a partition, for example, the C: drive, a FAT file partition, to NTFS, enter the following command at the system prompt:
convert c: /fs:ntfs /v
where /v displays all messages. If the partition is in use, the disk is converted to NTFS when you reboot the system. You must convert the partition before you install StreetTalk for Windows NT software.
Once the file volume is converted, you cannot go back to the original partition type without reinstalling Windows NT.
Even though StreetTalk for Windows NT software must be installed on an NTFS partition, a StreetTalk for Windows NT file service can share directories on any type of partition. For example, the VINES Files data directory can be either an NTFS or a FAT partition. See Managing StreetTalk for Windows NT Services for more information about StreetTalk file services.
TEMP Environmental Variable
If your Windows NT server has both an NTFS partition and a small non-NTFS partition that is less than 8 MB and your TEMP environment variable is set to a directory on the non-NTFS partition, the StreetTalk for Windows NT installation will fail if the smaller non-NTFS partition does not have enough disk space to store the temporary file that the StreetTalk for Windows NT installation program creates. Before you begin the installation, set the TEMP environmental variable to a directory on the NTFS partition.
To set these variables, click the System icon in the Control Panel. Set the variables in the User Variables section in the Environment tab of the System dialog box.
The installation program prompts you to enter the StreetTalk name of the computer on the Banyan network. A servername has a maximum of 15 characters that can include periods, commas, dashes, and spaces.
The servername becomes the second part of some StreetTalk names (for example, AdminList@STNT01@Servers, where STNT01 is a servername). The new server (and all other servers later added to the network) belongs to a default organization called Servers.
If you do not enter a servername, the default Microsoft computer name is used instead. Be aware of these considerations in naming your server:
![]()
Every StreetTalk for Windows NT server on your StreetTalk network must have a unique name. Once you set the StreetTalk for Windows NT servername, you cannot change it. If you have a large network, you should devise a server naming scheme before you install StreetTalk for Windows NT software. See Planning a Banyan Network. ![]()
If you select a name different from the Windows NT computer name for the StreetTalk for Windows NT servername, the server's StreetTalk for Windows NT users and the Windows NT users will use different names to refer to the same server. ![]()
If you did not enter a computer name when you installed Windows NT, the system's default name may not be unique if you have more than one Windows NT server in your network that uses the Windows NT default computer name.
Server Code and Server Enabler Code
Banyan StreetTalk for Windows NT software is serialized to prevent unauthorized use. A unique Server code and Server Enabler code must be entered when StreetTalk for Windows NT software is installed. The codes are on labels in your software product package. You can affix these labels to your server.
The StreetTalk for Windows NT server serial number is the server's StreetTalk address and becomes associated with the servername. The serial number is derived from the Server code and the Server Enabler code. The serial number must be unique. Therefore, never use the same Server Code and Server Enabler Code to install more than one server. Using the same codes on more than one server can seriously impair the operation of your network.
Note: Once you enter a servername and a Server code and a Server Enabler code, you cannot enter a different Server code to change the server's serial number. Changing a server serial number should only be done if you also change the servername.
In addition to creating a serial number, the Server Code and Server Enabler Code may create an expiration date for the software. If you get a new version of StreetTalk for Windows NT with new codes, you must uninstall the existing version and install the new version with the new codes and a new servername.
The Server code consists of a maximum of 16 numeric characters.
The Server Enabler code consists of 3 numeric characters and is related to the Server code.
If you do not install some of the StreetTalk for Windows NT software components when you do the initial installation, you do not have to re-enter the Server Code and Server Enabler Code on subsequent installations.
The server serial number is stored in the Windows NT Registry. The StreetTalk for Windows NT Administrator's Guide describes the StreetTalk for Windows NT entries in the Registry.
StreetTalk Administrator Password
The first time StreetTalk for Windows NT is installed, a user, Admin@servername@Servers, in the servername@Servers group is created. servername is the StreetTalk name of your StreetTalk for Windows NT server. This user is also placed on the AdminList@servername@Servers as the server administrator. This user has full system administrative privileges to set up other administrators, resources, and users on the new StreetTalk for Windows NT server.
The installation program prompts you for the password of the administrator.
Passwords cannot exceed 15 characters in length and are case sensitive.
Keep track of and protect your password. If you lose the password, you will not be able to administrate your StreetTalk for Windows NT server.
When you install the StreetTalk for Windows NT software, you must select destination directories for each of the following software components:
![]()
The default directory for the base software (StreetTalk Naming Service, Communications Protocols, Security Service, Server Service, and File and Print) is C:\Program Files\Banyan for server software. If the directory does not exist, it is created. The directory name can be a long filename and need not conform to the DOS 8.3 naming convention. The directory must be on an NTFS partition. ![]()
If you decide to install other components at a later time, you must use the same destination directory that you specified when you installed the base software components. ![]()
The default directory for VINES Files is the directory where you installed a previous version of VINES Files. Otherwise it is the same directory as the base software (C:\ProgramFiles\Banyan unless you choose to install the base software in a different directory). The installation program allows you to browse and select a directory other than the default. If your server has multiple fixed disks, it is recommended that you install VINES Files on a different disk to balance the load on your server. The VINES Files partition can be any type of partition.
The installation program prompts you to select one of the following types of installation;
![]()
Typical ![]()
Compact ![]()
Custom
Each installation consists of the following software:
Installation Type | Software | Notes |
Typical and Compact |
StreetTalk for Windows NT StreetTalk Communications Protocols StreetTalk Naming Service StreetTalk Security Service StreetTalk Server Service StreetTalk Directory Assistance Service StreetTalk File Service StreetTalk Print Service |
Installs all base components. VINES Files is on the CCCD. |
Custom |
StreetTalk for Windows NT StreetTalk Communications Protocols StreetTalk Naming Service StreetTalk Security Service StreetTalk Server Service StreetTalk Directory Assistance Service StreetTalk File service StreetTalk Print service StreetTalk Network Management Service * Backup Suite for StreetTalk * Server-to-Server UDP * StreetTalk Intelligent Messaging Mail Service * |
Installs base software and lets you select the other software that you want to install. If you intend to install Backup Suite for StreetTalk, you must have NetWorker 4.4 or 5.5 on your server. |
* - Must explicitly select these
to install. VINES Files is on the Client Components CD-ROM and you must separately install it. |
Estimating Disk Space Requirements
Before you install StreetTalk for Windows NT software, be certain that you have enough disk space available for the StreetTalk for Windows NT executable files and the data areas of StreetTalk for Windows NT services. The installation program allows you to display disk space available on your system' s fixed disk.
As shipped, the base StreetTalk for Windows NT services files are approximately 40 MB in size. To determine the disk space requirements of StreetTalk for Windows NT software, refer to Table 2-2. Note that the VINES Files directories are installed on the Windows NT system from the Client Components Suite CD-ROM shipped with the StreetTalk for Windows NT product.
Table 2-2 lists the approximate sizes of the StreetTalk for Windows NT products. Use this table for disk space planning purposes. The sizes of the products are approximate and are subject to change.
Component Description |
|
|
StreetTalk Naming Service StreetTalk Security Service StreetTalk Server Service StreetTalk Communications Protocol Stack STDA StreetTalk File StreetTalk Print |
|
|
StreetTalk Network Management |
|
|
StreetTalk Client Workstation Software |
|
|
Intelligent Messaging Mail |
|
|
Backup Suite for StreetTalk |
|
|
Server-to-Server UDP |
|
|
VINES Files 8.60 USA |
|
|
VINES Files 8.60 France |
|
|
VINES Files 8.60 Spain |
|
|
VINES Files 8.60 Germany |
|
|
VINES Files 8.60 Japan |
|
|
Banyan StreetTalk for Windows NT Total:1 |
|
|
1. Total is approximate for installing base software plus mail and one VINES Files language version. |
StreetTalk and STDA Disk Space Requirements
If your system has more than one disk partition, you can put the data areas for StreetTalk for Windows NT base services and the StreetTalk Directory Assistance service on a different partition. Specify the data areas when you create an STDA service.
Consider putting all data areas on a separate disk. You should also create other services on this separate disk. This allows you to more readily back up your StreetTalk for Windows NT data areas and services.
The base services data areas are variable in size and depend on the size of your network, particularly with respect to the StreetTalk database. StreetTalk can grow rapidly, particularly on a large network.
These requirements are shown in Table 2-3. See also Managing Users and StreetTalk for more information.
Component | Size | Size per Attribute | Attribute Size |
StreetTalk database resource | = 800 bytes | + 180 bytes per attribute | + The size of the attribute |
STDA back-end database entry | = 800 bytes | + 180 bytes per attribute | + The size of the attribute |
STDA front-end database entry | = 800 bytes for each resource you plan to display | + 800 bytes for each attribute you plan to display | + The size of each attribute you plan to display |
The StreetTalk for Windows NT data area requires a minimum of 10 MB for all services.
File and Print Disk Space Requirements
The StreetTalk for Windows NT file and print services are variable in size and depend on the types and numbers of files users create, the number of print services, and number of files waiting to be printed.
You can also put the data areas for file and print on other disks when you create these services. At creation time, the dialog prompts you to select a directory to install these data areas in.
USA (English),French, German, Japanese (for OADG DOS/V and NEC-98 client workstations), and Spanish language versions of VINES Files are included with the base product on the Client Components Suite CD-ROM. The language versions available vary according to client type. DOS, Windows 3.1, Windows 95, and Windows NT client workstations support all languages. OS/2 client workstations support English, German, French and Spanish.
It is not necessary to install both the English and the specific language versions. The installation program allows you to install only the language versions that you want on your system.
Loading any version of VINES Files is optional. However, you must have at least one VINES Files service running on your network to support DOS, Windows 3.1, Windows 95, Windows NT, or OS/2 clients.
DOS, Windows 3.1, and Windows NT client workstations are supported by DOS VINES Files. Windows 95 clients are supported by DOS and Win32 VINES Files. OS/2 client workstations are supported by OS2 VINES Files.
Keep these points in mind if you are installing one or more versions of VINES Files:
![]()
The installation program checks the available disk space before it starts the installation process. If it determines that the available space is insufficient for the new location software, the installation program quits. ![]()
If a previous version of VINES Files was installed on the server, the installation program does not take that into account when it calculates disk space. The installation program only checks for available disk space. You must make sure that the disk has enough space prior to the installation. ![]()
If you are upgrading an existing location (for example, USA VINES Files), users should not access that location until the installation is complete.
Workstation Configuration Options
A StreetTalk for Windows NT server allows you to log in to a Banyan network as a workstation user. To do so, you must install the Banyan Enterprise Client for Windows NT from the CCCD after you install StreetTalk for Windows NT. During the client installation, you can configure login options described in the next sections.
The Login Group Lists let you specify up to three StreetTalk groups that the login program appends to your username if you do not enter a complete StreetTalk username.
Enter the groups using this format:
group@organization
For example, if your StreetTalk name is Mary Smith@Sales@WCTUS and you enter Sales@WCTUS in your Login Group Search List, you only need to enter Mary Smith when you log in to the network. If your StreetTalk nickname is MaryS, you need only enter MaryS.
You can select the following workstation login options:
![]()
Load Banyan Workstation during System Start - Loads the Banyan Enterprise Client software each time your server boots. You can log in to the Banyan network whether or not you select this option because logging in causes the client workstation software to be automatically loaded. Selecting this option lets you log in more quickly. It is recommended that you enable this option if you will frequently log in to the Banyan network from this server. ![]()
Common Login - Lets you use your Windows NT username and password as a common login to the Banyan Network. If you want a common login, specify one or more StreetTalk groups to be searched for the name that you specify. Therefore, Banyan recommends that you do not enable common login. ![]()
Login Status Display Time - Lets you specify the length of time in seconds the Login Status dialog box remains on the screen after login processing has completed.
When you install the workstation client software, you can perform the following tasks after logging in to the Banyan network:
![]()
Send messages to other StreetTalk users. ![]()
Configure print queues for printing to StreetTalk print services. ![]()
Change your StreetTalk password.
You can select any NDIS-compliant Ethernet, Token-Ring, or FDDI adapter installed and configured in your Windows NT Server to transmit VINES IP packets.
This release of StreetTalk for Windows NT supports only one LAN adapter per server for VINES IP. The LAN adapter is configured explicitly for VINES IP when the installation program is run. You cannot prevent the adapter from using VINES IP. However, other protocols (for example, TCP/IP) can use this adapter. VINES IP does not use the adapter exclusively.
User Datagram Protocol (UDP) Client workstations and S-to-S UDP software are supported on all Windows NT LAN adapters configured to support TCP/IP. See "IP Client Workstations" in Chapter 1 for more information on UDP Client workstations. See "Server Configuration for Server-to-Server UDP" in the StreetTalk for Windows NT Administrator's Guide for more information on S-to-S UDP software.
To support StreetTalk for Windows NT, communications resources must be properly configured. You can configure these communications values:
![]()
The total size of the communications heap ![]()
The maximum number of StreetTalk sockets that processes can open simultaneously ![]()
The maximum number of Sequenced Packet Protocol (SPP) connections that processes (for example, services) can have in use at one time ![]()
SPP Maximum Transfer Unit (MTU) size.
Each communications parameter has a default, a minimum, and a maximum configurable limit as shown in Table 2-4.
The SPP MTU size parameter is described in the "Changing the Size of the SPP Maximum Transfer Unit (MTU)" section. Use this parameter to configure your StreetTalk for Windows NT Server as an IP Client server.
Parameter | Default | Minimum | Maximum |
Communications Heap Size (KB) | 1024 | 16 | 8192 |
Maximum Open Sockets | 300 | 10 | 8000 |
Maximum SPP Connections | 300 | 50 | 8000 |
SPP MTU Size (bytes) | 1450 | 100 | 1450 |
Enough memory must be available to meet the demands of each component. Otherwise, performance problems result. In general, an increase in the memory demands of one or more components decreases the amount of memory available for others. For example, if you make more memory available for communications heap, you decrease the amount of memory available for services.
StreetTalk for Windows NT programs and services use Sequenced Packet Protocol (SPP) connections and StreetTalk sockets.
Note: Exercise caution before you change communications settings. The default communications settings should be sufficient to get your StreetTalk for Windows NT software up and running. As you add services and users, use StreetTalk Explorer or the Performance Monitor (described in Chapter 4) to determine when the number of sockets, number of SPP connections, and the communications heap size need to be increased. Read the next sections and Chapter 4 before you change any default settings.
Configuring the Communications Heap
The communications heap size (memory for buffers and other communications data) must be large enough to handle the maximum number of open SPP connections and open sockets you want to assign. In addition, it must be able to handle the data transmitted by those connections and sockets. Otherwise, the StreetTalk server may not have enough communication heap space when these limits are approached or reached. How much you increase communications heap size is dependent on how much physical memory your server has and how heavily your StreetTalk for Windows NT software is being used. Chapter 4 describes how to estimate heap size increments.
The default setting is 1024 KB. The value can range from 16 to 8192.
A socket acts as an interface between a transport layer protocol, such as SPP, and a StreetTalk for Windows NT program. Whenever a program communicates with another program, at least one socket is open. Each open socket requires approximately 100 bytes of communications heap, plus space for the data being sent or received.
The default setting is 300. The value can range from 10 to 8000.
Some StreetTalk for Windows NT programs communicate using a Sequenced Packet Protocol (SPP) connection. SPP is a transport layer protocol that creates a virtual connection between two processes and acts as a data pipe between them. This section describes the StreetTalk for Windows NT programs that require SPP connections.
Each SPP connection requires 80 to 100 bytes of communications heap, plus space for the data being sent or received.
Set the Total SPP connections to the number of concurrent sessions connected to StreetTalk and other resources on the Windows NT system. Generally, there is one SPP connection for each drive that a workstation maps to a StreetTalk file service or for each workstation that maps a print queue to a StreetTalk print service. Each SPP connection requires 80 to 100 bytes of communications heap space to maintain the connection.
The default setting is 300, the value can range from 50 to 8000.
The following services use SPP to communicate with client workstations:
File - An SPP connection is established each time a user issues SETDRIVE from DOS to set a drive to a file volume or uses its UNC name in a path on a Windows NT client. The SPP connections are terminated for a variety of reasons including a user's logging out or a network problem, or an idle disconnect setting. Managing StreetTalk for Windows NT Services describes idle disconnect settings.
Keep in mind that SETDRIVE commands in the user profile do not establish SPP connections for sessions with the file service unless the /ROOT option is used. This improves login performance and prevents establishing an SPP connection that may not be used. For a drive that is set from the user profile, an SPP connection is established when the user performs an action on the drive, such as a read, write, CD, DIR, and so on. Although a user may have many drives set from the user profile, SPP connections for sessions with the specified file service may not always be established while the user is logged in to StreetTalk for Windows NT.
Print - Each time a job is spooled to a print service an SPP connection to the specified print service is established.
Security - When a user logs in, the Security Service establishes an SPP connection with the login client to deliver profile information. The connection terminates as soon as the delivery is complete.
STDA - The STDA service uses an SPP connection for a session with the STDA client.
Non-Banyan - Non-Banyan services integrated with the StreetTalk Naming service can also use SPP connections.
Refer to the application's documentation for information on assigning Computer Names.
Changing the Size of the SPP Maximum Transfer Unit (MTU)
The SPP MTU size is the maximum amount of SPP data in a VINES IP packet on an Ethernet, Token-Ring, or FDDI LAN or in a VINES IP packet encapsulated in UDP packets when Windows 95 and Windows NT clients communicate with a StreetTalk for Windows NT server.
The default (and maximum) MTU size is 1450 bytes. The minimum is 100 bytes. However, because packets sent and received by the IP Client require additional space for an IP, and possibly a UDP, header, you must reduce the size of the MTU on a StreetTalk for Windows NT server that is accessed by IP Clients. This parameter does not affect SPP data that is forwarded through the StreetTalk for Windows NT server and that originated elsewhere.
Modify this parameter to improve performance under these conditions:
![]()
Any type of IP Client - DOS and Windows 3.1 clients using IP, and Windows 95 and Windows NT clients using UDP - will access the StreetTalk for Windows NT server. ![]()
The StreetTalk for Windows NT server is not enabled for IP Client support but IP Clients forward packets to it from other servers that support IP Clients.
The maximum size of data StreetTalk for Windows NT software sends in a frame (1500 bytes) allows for 50 bytes of packet headers when the SPP MTU is 1450 bytes. In a VINES IP network, packet headers do not exceed the remaining 50 bytes, but an IP Client packet requires extra space to accommodate the IP and possibly the UDP header that is added during encapsulation. Since the size of the frame cannot be increased, adding the IP, and possibly the UDP, header reduces the number of bytes available for data. A single frame can no longer transport all the data that the original VINES IP packet contained.
As a result, the original VINES packet becomes fragmented into two separate IP packets, one carrying the maximum amount of data, and one carrying the minimal amount of data that can no longer fit within the first packet. Such fragmenting and subsequent reassembling of IP packets slows performance, particularly during file transfers.
You can prevent fragmentation by reducing the size of the SPP MTU. When you reduce the SPP MTU size, all SPP connections to the server use the reduced MTU size.
The recommended SPP MTU value are as follows:
![]()
1436 if packets originating from the server will be transmitted across the network using UDP encapsulation to another server or to a client. ![]()
1440 if packets originating from the server will be transmitted across the network using IP encapsulation (no UDP encapsulation) to another server or to a client. ![]()
1450 (the default) if packets originating from the server will be transmitted across the network using VINES IP encapsulation (no IP or UDP encapsulation) to another server or to a client. Note: References above to packets being transmitted using IP or UDP encapsulation do not mean that the server you are configuring must be using encapsulation. The server could be sending packets to another server that then encapsulates them.
If you install your StreetTalk for Windows NT server on a Token-Ring LAN, you may need to enable source-level routing for the Token-Ring card that connects the server to the LAN. Your server needs to have Source-Level Routing enabled for a Token-Ring LAN card when the Token-Ring LAN attached to the card connects your server to a Token-Ring bridge. This rule applies only if your server communicates across the bridge. Otherwise, source-level routing is not needed.
If a StreetTalk for Windows NT server or a VINES server on a ring has source-level routing enabled, all other servers on that ring (and over a bridge if one is present) must have source-level routing enabled to accept and respond to messages.
For more information on source-level routing, see Managing Communications
Advanced Communications Options
The StreetTalk for Windows NT Installation program lets you change certain communications parameters.
Caution: Change these parameters only if you have knowledge of network communications. Setting incorrect parameters can cause network communications to fail or can adversely affect server performance.
By default, the following options are disabled:
![]()
Accept All Multicast Addresses - This option might be required by certain applications or protocols, and is specific to Ethernet networks. ![]()
Accept All Functional Addresses - This option might be required by certain applications or protocols, and is specific to Token-Ring networks. ![]()
Reset Mac When No Traffic - This option automatically resets the MAC (Media Access Control) driver after a period of time of no traffic on the network. ![]()
Always Use Fragmentation - This option might be required by certain StreetTalk for Windows NT server drivers. ![]()
Routing Metric - By default, the routing metric is set to automatically determine the metric used to route information throughout the network. See the next section for more information. ![]()
Enable Client Routing Server - Enables or disables the StreetTalk for Windows NT server as a client workstation routing server. By default, a StreetTalk for Windows NT server is enabled to respond to client workstation routing requests. See "Disabling Client Workstation Routing" later in this chapter for more information.
StreetTalk for Windows NT supports configurable routing metrics for client workstations and servers connected with VINES IP. A routing metric is an estimated round-trip delay time measured in 200-millisecond units (ticks) associated with a route that a maximum size VINES IP packet takes to a destination server.
By default, a StreetTalk for Windows NT server is configured to automatically determine the metric to use for routing information throughout the network so you should not have to change the default setting. The metric is set on the Advanced Communications dialog box. The advanced communications parameters can be changed after installation but only if your support representative instructs you to do so.
The metric is set to a value based on the maximum speed of the server's network adapter as shown in Table 2-5.
Maximum Network Adapter Speed | Routing Metric |
100 Mbps or greater |
|
10 Mbps to 100 Mbps |
|
Less than 10 Mbps |
|
Later sections describe how to configure routing metrics for UDP client workstations and Server-to-Server UDP connections.
For more information see the StreetTalk for Windows NT Administrator's Guide.
Disabling Client Workstation Routing
When a user logs in at a StreetTalk client workstation, the Banyan client workstation software performs the following actions:
![]()
Finds a routing server ![]()
Announces its arrival to neighbors ![]()
Establishes a session with a VINES Files service
Workstations use the VINES Address Resolution Protocol (ARP) to find routing servers and obtain a VINES IP address when necessary. The routing server gives the workstation a VINES IP network layer address and provides it with routing support so that it can participate in the network.
After these actions are performed, the workstation periodically informs its neighbors of its presence on the LAN. The workstation also requests routing updates from its routing server when it has to communicate with servers that are not on its LAN.
By default, StreetTalk for Windows NT servers are enabled to perform client workstation routing.
Enabling or disabling client routing server support affects all interfaces on which client workstations are supported - LAN interfaces used by VINES IP and any interfaces used by UDP Client workstations.
If you change this parameter on the Advanced Communications dialog box, you must reboot the server for the change to take effect.
Guidelines
You can disable client routing if your StreetTalk for Windows NT server is being used as an applications server and there are other servers on the network. Turning off client routing can save server resources.
A server with client routing disabled does not assign addresses to workstations.
Do not disable client routing if the StreetTalk for Windows NT server is the only server on the network or if all other servers on the network have client routing disabled.
If you are using a third-party application that uses the Windows socket (Winsock) interface to VINES IP and that is integrated with StreetTalk, you must enter the application' s computer name during installation.
Winsock applications are server-based. StreetTalk for Windows NT is service-based. In order to map the server-based application to the StreetTalk for Windows NT service, you must enter the servername. The name that you enter is used to create a StreetTalk PC-based service that locates the servername. You can also enter groups that are searched to locate other computers on the network.
Refer to the third-party application's documentation for information on assigning Computer Names.
Server Configuration for IP Client Support
If Windows 95 or Windows NT client workstations with the User Datagram Protocol (UDP) will connect to the StreetTalk for Windows NT server as IP Client workstations, you must configure the server as an IP Client routing server.
For each IP Client routing server, you need to modify settings to support UDP communications. You will need to make the following configuration changes during or after installation of the base software:
![]()
Enable UDP support. ![]()
Change the size of the SPP Maximum Transfer Unit (MTU) as described earlier in the chapter. ![]()
Configure UDP metrics for links directly connected to your StreetTalk for Windows NT server and for remote networks that are not directly connected to your StreetTalk for Windows NT server.
For more information, see Installing Banyan Clients for Windows NT and Windows 95.
Server Configuration for Server-to-Server UDP
The StreetTalk for Windows NT Administrator's Guide describes how to configure Server-to-Server UDP (S-to-S UDP).
Before you configure Server-to-Server UDP software, record the following information for each server on the S-to-S UDP Worksheet in Figure 2-1.
The worksheet headings have the following meanings:
StreetTalk name of remote server - The StreetTalk name of the remote server your server will communicate with by means of the S-to-S UDP software.
Serial number - The remote server's serial number. The serial number of a StreetTalk for Windows NT server is displayed on the Network Communications dialog box (from the Network icon in Programs, StreetTalk for Windows NT, StreetTalk Server Configuration) after StreetTalk for Windows NT software is installed. The serial number is also referred to as the server's StreetTalk address or network ID.
IP hostname - The hostname of the remote server.
IP address - The remote server's IP address. The configuration program attempts to look this address up from the hostname, so you may not need to know this address.
Routing metric - The sum of the metrics of the links that intervene between your server and the remote server.
Increment - Metric added to compensate for encapsulation overhead.
For more information on S-to-S UDP software, see the StreetTalk for Windows NT Administrator's Guide.
StreetTalk for Windows NT Server as a DHCP Client
A StreetTalk for Windows NT server that is configured to be a Dynamic Host Configuration Protocol (DHCP) Client can affect the configuration of UDP Client and S-to-S UDP support.
As a DHCP Client, the server's IP addresses are not explicitly configured. Instead, another system that is a DHCP server dynamically assigns the StreetTalk for Windows NT server its IP addresses. As a consequence, the server's IP addresses can change. Also, the StreetTalk for Windows NT server may not be able to get IP addresses if a DHCP server is not available, or the StreetTalk for Windows NT server may have its IP addresses expire if it is not able to renew them.
For UDP Clients on directly connected networks, it is recommended that you do not configure the IP address of the server but instead let the client broadcast to find the server since the server's IP addresses can change.
For servers connected by S-to-S UDP, specify servers using their hostnames.
If the server reboots and is assigned different IP addresses, any UDP Clients that were connected to the server using the original IP addresses are unable to communicate with the server. S-to-S UDP connections are also broken. The UDP Clients must change the server IP address if configured and be rebooted to re-connect to the server. If servers connected by UDP and identified by their hostname are disconnected, select the connection on the Configure Server-to-Server UDP dialog box and click Modify. The software attempts to look up the hostname and re-establish the connection.
If the server IP address leases expire, StreetTalk for Windows NT software can no longer communicate with any UDP clients or other servers running S-to-S UDP software. If this occurs, the Event Viewer displays a System Log message similar to the following message:
The lease for IP address aaa.bbb.ccc.ddd has been terminated.
When StreetTalk for Windows NT is started and if the server has not been assigned IP addresses, the StreetTalk for Windows NT UDP Client or S-to-S UDP support cannot be enabled. The Event Viewer displays a System Log message similar to one of the following messages:
VNS: Invalid DHCP IP addr for UDP client.
VNS: Invalid DHCP IP addr for Server-to-Server UDP.
If the server gets its IP addresses assigned to it after StreetTalk for Windows NT has already started (for example, if the DHCP server was not available when the server booted but is now available), StreetTalk for Windows NT software is unable to start using the IP addresses to provide UDP Client or S-to-S UDP support. You must reboot to restart the StreetTalk for Windows NT software so it can use the IP addresses.
When the installation program runs, it performs the following tasks:
![]()
Checks your server for StreetTalk Access or Banyan Enterprise Client for Windows NT or a previously installed version of StreetTalk for Windows NT. ![]()
Checks that your destination installation directory is an NTFS file partition. ![]()
Checks that your server has enough disk space. ![]()
Prompts you to enter information described in the installation worksheet in Figure 2-2. ![]()
Copies program files to disk. ![]()
Configures the communications protocol stack and client workstation software. ![]()
Creates Windows NT Registry entries for the base software and the optional software you selected to install. ![]()
Creates Windows NT Service entries for StreetTalk for Windows NT services. ![]()
Creates a StreetTalk for Windows NT program group and program items in a new or existing program group.
Use this worksheet to record the information you will need to install StreetTalk for Windows NT software:
Description | Entry |
StreetTalk servername | |
Server code: | |
Server Enabler code: | |
Admin@servername@Servers password: | |
Type of installation: |
__ Typical or Compact __ Custom |
Installation directory: Base software __________________________________________ VINES Files __________________________________________ |
|
Software to install for Custom installation: |
__ Base Components __ Server-to-Server UDP __ StreetTalk Network Management __ StreetTalk Intelligent Messaging __ Backup Suite for StreetTalk |
VINES Files Clients: |
___DOS, Windows 3.1, Windows 95/98, and Windows NT ___OS/2 ___Win32 |
Language locations: |
DOS
OS/2
WIN32 USA ____ ____ ____ French ____ ____ ____ German ____ ____ ____ Japanese ____ N/A ____ NEC ____ N/A ____ Spanish ____ ____ ____ |
Program group to install icons in: | |
Banyan Enterprise Client for Windows NT Login search group: StreetTalk group 1: StreetTalk group 2: StreetTalk group 3: |
StreetTalk group names: ___________________________________ ___________________________________ ___________________________________ |
LAN adapter: | |
Enable source-level routing?: | |
Winsock application computer name: | |
Search groups for other computers: |
___________________________________ ___________________________________ |
Communications resource settings (default): | |
Communications heap size (1024) | |
Maximum sockets (100) | |
Maximum SPP connections (300) | |
SPP MTU size (1450) | |
Disable client workstation routing: | |
Enable UDP Support: | |
Support UDP Clients on directly connected networks | |
Metric increment for recognized network types (2): | |
Metric increment for recognized network types (10): | |
Support remote UDP clients: | |
Metric for remotely connected UDP clients (10): | |
Enable automatic Server-to-Server UDP support on directly connected networks: | |
Metric increment of recognized network types (2): | |
Metric for unrecognized network types (10): | |
Enable automatic Server-to-Server UDP support on remote networks | |
Metric for remotely connected UDP server (26): | |
Enable manual Server-to-Server UDP support: | |
Server serial number: | |
Server hostname: | |
Server host IP address: | |
Metric for remotely connected UDP server: |