Previous PageNext Page

Chapter 2 - Preparing to Install StreetTalk for Windows NT Software

Introduction

StreetTalk Naming service
StreetTalk Communications Protocols
StreetTalk Server Service
StreetTalk Security Service
StreetTalk Directory Assistance (STDA) service
StreetTalk File and Print

Prerequisites

Hardware Requirements

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.

Software Requirements

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

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

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.

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.

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

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

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.

NTFS Partition

convert c: /fs:ntfs /v

TEMP Environmental Variable

Select a Servername

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

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.

StreetTalk Administrator Password

Destination Directory

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.

Types of Installation

Typical
Compact
Custom

Table 2-1. Types of Installation

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

Table 2-2. Approximate Sizes of Banyan StreetTalk for Windows NT Products

Component Description

Approximate Size (MB)
StreetTalk Naming Service
StreetTalk Security Service
StreetTalk Server Service
StreetTalk Communications Protocol Stack
STDA
StreetTalk File
StreetTalk Print

 

 

16.5
StreetTalk Network Management

0.8
StreetTalk Client Workstation Software

7.2
Intelligent Messaging Mail

6.4
Backup Suite for StreetTalk

5.2
Server-to-Server UDP

0.003
VINES Files 8.60 USA

25.0
VINES Files 8.60 France

25.0
VINES Files 8.60 Spain

25.0
VINES Files 8.60 Germany

25.0
VINES Files 8.60 Japan

25.0
Banyan StreetTalk for Windows NT Total:1

47.9
1. Total is approximate for installing base software plus mail and one VINES Files language version.

StreetTalk and STDA Disk Space Requirements

Table 2-3. StreetTalk and STDA Disk Space Requirements

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

File and Print Disk Space Requirements

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

Login Search Group

group@organization

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.

Send messages to other StreetTalk users.
Configure print queues for printing to StreetTalk print services.
Change your StreetTalk password.

Network Adapter

Communications Resources

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.

Table 2-4. Communications Resource Limits

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

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

Specifying Maximum Sockets

Configuring SPP Connections

Changing the Size of the SPP Maximum Transfer Unit (MTU)

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.

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.

Source-Level-Routing

Advanced Communications Options

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.

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.

Routing Metrics Over VINES IP

Table 2-5. Metrics for Different Adapter Speeds

Maximum Network Adapter Speed Routing Metric
100 Mbps or greater

1
10 Mbps to 100 Mbps

2
Less than 10 Mbps

4

Disabling Client Workstation Routing

Finds a routing server
Announces its arrival to neighbors
Establishes a session with a VINES Files service

Guidelines

Windows Socket Applications

Server Configuration for IP Client Support

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.

Server Configuration for Server-to-Server UDP

S-to-S UDP Worksheet

Figure 2-1. Server-to-Server UDP Worksheet.

StreetTalk for Windows NT Server as a DHCP Client

The lease for IP address aaa.bbb.ccc.ddd has been terminated.

VNS: Invalid DHCP IP addr for UDP client.
VNS: Invalid DHCP IP addr for Server-to-Server UDP.

Installation Summary

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.

Information Requirements

Figure 2-2. Required Installation Information

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:  

Previous PageTop Of PageNext Page