StreetTalk for Windows NT Installation Guide
Chapter 1 - Installation Overview
The Banyan StreetTalk for Windows NT Installation Guide describes how to install Banyan® StreetTalk® for Windows NT® software on a Microsoft® Windows NT Server. StreetTalk for Windows NT software consists of the following base and optional software:
![]()
StreetTalk Naming Service ![]()
StreetTalk Security Service ![]()
StreetTalk Server Service ![]()
StreetTalk Communications Protocol Stack ![]()
StreetTalk Directory Assistance service ![]()
StreetTalk File ![]()
StreetTalk Print ![]()
Banyan Enterprise Client for Windows NT ![]()
VINES® Files ![]()
StreetTalk Explorer ![]()
Intelligent Messaging Mail (option) ![]()
Server-to-Server UDP (option) ![]()
StreetTalk Network Management (option) ![]()
Backup Suite for StreetTalk (option)
The Banyan StreetTalk for Windows NT Installation Guide is for administrators who will install Banyan software on Windows NT Server. If the Banyan administrator is not the same person as the Windows NT administrator, the Banyan administrator must work with the Windows NT administrator to install StreetTalk for Windows NT software and to administrate the system.
Prerequisites for this guide include:
![]()
Some experience with the Windows NT operating system ![]()
Basic understanding of local area networks (LANs)
This guide includes four chapters:
Chapter Description 1 Presents an overview of the product and its capabilities. 2 Describes the prerequisites and the information you must have on hand before you install the product. 3 Describes the installation steps. 4 Describes how to monitor StreetTalk for Windows NT software after if is installed.
Read Chapter 1 and Chapter 2, and the StreetTalk for Windows NT Release Notice before you install Banyan StreetTalk for Windows NT software.
If you are upgrading from StreetTalk Access for Windows NT File and Print software, you must uninstall that product before you install StreetTalk for Windows NT software. See Chapter 2 for more information.
To install StreetTalk for Windows NT on a Windows NT Server running the StreetTalk for Windows NT 7.x Client Workstation component on your StreetTalk for Windows NT 7.x server or the Banyan Enterprise Client for Windows NT workstation software on your Windows NT Server, you must uninstall these products before you install StreetTalk for Windows NT. See Chapter 2 for more information.
The StreetTalk for Windows NT package includes these components:
Component | Description |
StreetTalk for Windows NT 8.6 Installation Guide | Printed installation guide |
StreetTalk for Windows NT 8.6 Release Notice | Printed release notice |
Server Code and Server Enabler Code | Codes entered during installation to authenticate your software and create a StreetTalk for Windows NT server serial number. The serial number becomes associated with the servername. Not included on an upgrade. |
StreetTalk for Windows NT Product CD-ROM | StreetTalk for Windows NT software components that can be installed on the Windows NT Server. Also contains the Banyan NetWorker Recover Browser. |
Banyan Client Components Suite CD-ROM |
Client workstation software (VINES Files, Enterprise Client for Windows NT and Windows 95/98/98 software), the StreetTalk Explorer management tool, and Banyan GINA for Windows NT. There are two Banyan Client Components Suite CDs. One CD contains English (USA) and European (French, German, and Spanish) language versions of client workstation software and StreetTalk Explorer. The other contains English (USA) and Japanese versions of client workstation software and StreetTalk Explorer. Only one CD ships with the product depending on which language version of StreetTalk for Windows NT you purchase. The Banyan Client Components Suite CDs contain online documentation that describes how to install Banyan Enterprise Clients for Windows 95/98 and Windows NT. |
Banyan Books Online CD-ROM | Electronic information product containing Banyan network products documentation in HTML format. |
Software License Agreement | Printed software license agreement. |
Other components that you may receive if you purchase options are as follows:
Table 1-2. Components with Purchased Options
Component Description Option Code for StreetTalk Intelligent Messaging Code provided if you purchased the Intelligent Messaging Mail option. Option Code for Network Management Code provided if you purchased the Network Management option. Option Code for Server-to-Server UDP Code provided if you purchased the Server-to-Server UDP option (TCP/IP Server-to Server). Option Code for Backup Suite for StreetTalk Code provided if you purchased the Backup Suite for StreetTalk option. Banyan Networker 5.5 CD Banyan Networker backup and restore software. This is a separately purchasable option.
StreetTalk for Windows NT Software Components
StreetTalk for Windows NT consists of the following base and optional software components:
StreetTalk for Windows NT Base Software
StreetTalk Naming Service Maps StreetTalk names to resources on Windows NT and provides the administrative back-end service through which all directory management actions occur.
StreetTalk Directory Assistance Service (STDA) Provides a comprehensive directory of StreetTalk names with real-time searching capabilities.
StreetTalk Communications Protocols StreetTalk services use the VINES Internet Protocol (VIP). Banyan client workstations communicate with StreetTalk for Windows NT services by means of the VIP network protocol or VIP encapsulated in the User Datagram Protocol (UDP). (See the later sections "Client Workstations Supported" and "Server-to-Server UDP" for more information.)
StreetTalk Server Service General utility service that is created automatically on each StreetTalk for Windows NT server when the base StreetTalk for Windows NT software is installed. This service reports general server information, manages time, maintains the status of services on the server, and is responsible for creating, restarting, and destroying services. Chapter 4 describes how to configure Server Service to restart stopped services.
StreetTalk Security Service Authenticates and authorizes users and processes user profiles.
StreetTalk File Provides connections to Windows NT FAT, Windows NT NTFS, OS/2 HPFS file volumes on local or network disk drives, optical drives, or CD-ROM drives. With StreetTalk File, you provide Banyan client workstations with access to directories on Windows NT systems by assigning a StreetTalk name to Windows NT directories. Each Windows NT directory shared through StreetTalk runs as a Banyan file service on a StreetTalk for Windows NT server. StreetTalk File supports DOS, Windows 3.1, Windows 95/98, Windows NT, and OS/2 client workstations.
Just as in a Banyan network, the access rights to the Windows NT volume are determined by the rights extended to a given user.
StreetTalk File supports
![]()
Any size partition that Windows NT supports. ![]()
Long filenames and international filenames. ![]()
OS/2 extended attributes
StreetTalk Print Provides connections to Windows NT local or network printers. With StreetTalk Print, you assign a StreetTalk name to a printer attached to a Windows NT system to integrate Windows NT printers into the Banyan network. Each Windows NT printer shared through StreetTalk runs as a Banyan service on a Windows NT server. DOS, Windows 3.1, Windows 95/98, Windows NT, and OS/2 client workstations can print to a StreetTalk print service.
Print services support long filenames and international filenames.
The only component that must be installed is StreetTalk for Windows NT, which includes the StreetTalk Naming service, the StreetTalk Directory Assistance (STDA) service, the StreetTalk Communications Protocols, the StreetTalk Server Service, the StreetTalk Security Service, and the StreetTalk File and Print services. Installing all other components is optional.
StreetTalk for Windows NT Optional Software
StreetTalk Intelligent Messaging A full-function electronic messaging service available to all users of the network. As a messaging service, Intelligent Messaging provides message storage and message transport functions. A mail service provides mailboxes for individual users who can access their mailboxes from any workstation on the network. Mailbox service includes creating, deleting, sending, and organizing messages. Intelligent Messaging is a separately purchased option.
StreetTalk Server-to-Server UDP Allows a StreetTalk for Windows NT server to communicate with other StreetTalk for Windows NT servers and with native VINES servers through an IP (Internet Protocol) network. The Server-to-Server UDP software encapsulates VINES IP packets within UDP. The VINES packets appear as IP packets as they pass through the IP network. Server-to-Server UDP is a separately purchased option, and is also referred to as TCP/IP Server-to-Server.
StreetTalk Network Management Provides statistics about server performance, network traffic, server configuration, and StreetTalk communications interfaces if the option is installed. It is an informational tool for knowledgeable network designers or advanced administrators responsible for monitoring network performance and solving network problems. You access SNM through the Banyan management program, StreetTalk Explorer. For information on how to install and use the program, see Monitoring and Optimizing Servers. SNM is a separately purchased option.
Backup Suite for StreetTalk Allows you to individually restore certain components of StreetTalk for Windows NT, such as files and their ARLs, StreetTalk groups and their attributes, and mail services and user's mailboxes. Backup Suite for StreetTalk is a separately purchased option.
Client Component Software
Banyan Enterprise Client for Windows NT Software Allows an administrator to run PC-based services that have been integrated with the StreetTalk Naming Service (for example, SNA Server and SQL Server) and that are on the same system with other StreetTalk services. This feature also allows a user to log in to the Banyan network and access StreetTalk services. Installing this software is optional. See the later section "Logging in as a Client" for more information.
VINES Files Client programs that allow users to access and use network services. Installing VINES Files is optional. However, if your network is a single-server network and client workstations must access that server, you must install VINES Files.
The Client Components Suite CD-ROM includes VINES Files (drive Z) version 8.60. Language versions include English, French, German, Japanese, and Spanish. You can install more than one language version of VINES Files.
StreetTalk Explorer StreetTalk Explorer is a management tool modeled after the Windows 95/98 Explorer interface and designed to run in 32-bit mode on Banyan Enterprise Client for Windows 95/98 or Windows NT, or on a StreetTalk for Windows NT server with the Banyan Enterprise Client for Windows NT installed. StreetTalk Explorer incorporates most StreetTalk management tasks previously performed by the DOS-based M* utilities and the Windows 3.1-based ENS® MT program.
After StreetTalk for Windows NT software is installed, if you install the Banyan Enterprise Client for Windows NT, you can log in to the Banyan network as a client workstation user from the StreetTalk for Windows NT server and perform operations that an Enterprise Client for Windows NT workstation user can perform. These include:
![]()
Using the same username and password to log in to Windows NT and to the Banyan network ![]()
Editing Banyan user profiles ![]()
Sending messages to other StreetTalk users ![]()
Printing to Banyan print services ![]()
Running Banyan drive Z and Win32 applications ![]()
Accessing other Banyan file services ![]()
Using StreetTalk Explorer to manage the StreetTalk for Windows NT server and other Banyan servers
Banyan Enterprise Client for Windows NT software or StreetTalk for Windows NT 7.x Client Workstation component of StreetTalk for Windows NT 7.x must be removed from a Windows NT system before StreetTalk for Windows NT software is installed. See Chapter 2 for more information.
Using StreetTalk Explorer to Manage StreetTalk for Windows NT
If you install the Banyan Enterprise Client for Windows NT on your Using StreetTalk Explorer to manage the StreetTalk for Windows NT server, you can also install the Banyan StreetTalk Explorer management tool on your StreetTalk for Windows NT server so that you can monitor and manage the server and other servers from the server console rather than from a Banyan client workstation. See the StreetTalk Explorer documentation and help system for details.
Table 1-3 shows the types of Banyan client workstations that can connect to StreetTalk for Windows NT, the types of network protocols that are available for these connections, and the language versions supported:
Client Workstation | Network Protocol | Languages |
DOS | VINES IP | English, French, German, Spanish, and Japanese |
Windows 3.1 | VINES IP | English, French, German, Spanish, and Japanese |
Windows 95/98 | VINES IP or UDP | English, French, German, Spanish, and Japanese |
Windows NT | VINES IP or UDP | English, French, German, Spanish, and Japanese |
OS/2 | VINES IP | English, French, German, and Spanish |
The StreetTalk for Windows NT server can be an IP Client server for Windows 95/98 and Windows NT client workstations with the User Datagram Protocol (UDP) connected to the network. UDP is one of the TCP/IP suite of protocols and runs over the Internet Protocol (IP). Therefore, Banyan client workstations using UDP are referred to as IP Client workstations.
A Banyan Windows 95/98 client workstation with UDP and a Banyan Windows NT Client with UDP can communicate with a StreetTalk for Windows NT server using Microsoft TCP/IP software. Both the server and the workstations must have Microsoft TCP/IP software installed and configured for this communication to occur.
An IP Client Windows NT or Windows 95/98 workstation uses the UDP layer of the Microsoft TCP/IP software to transport VINES IP packets. VINES IP packets contain data that originate in a StreetTalk for Windows NT application, such as a file service. The IP Client passes these VINES IP packets to the TCP/IP software. The TCP/IP software adds a UDP header to the packet, thereby encapsulating the VINES IP packet in a UDP packet. The TCP/IP software then passes the packet out onto the network.
StreetTalk for Windows NT servers accept these UDP packets from the IP Client workstations, strip off the UDP headers, and route the packets to other Banyan servers as necessary. This allows the IP Client workstations to access a Banyan network that resides on the other side of a TCP/IP network as illustrated in Figure 1-1.
When the encapsulated packet arrives at its destination (another UDP workstation or a StreetTalk for Windows NT server), the destination node strips off the UDP header and passes the VINES IP packet to the appropriate StreetTalk for Windows NT service.
The IP Client can be connected to the same network as the StreetTalk for Windows NT server or the IP Client can be on a remote network. The IP Client is not limited to communicating only with the StreetTalk for Windows NT server. The StreetTalk for Windows NT server can forward packets between the IP Client and other servers on the Banyan network.
IP Client support can be configured when StreetTalk for Windows NT is installed or after it is installed. Chapter 2 describes the IP Client server configuration parameters.
Note: DOS, Windows 3.1, and OS/2 client workstations do not support using the UDP protocol. Therefore, a StreetTalk for Windows NT server cannot act as an IP Client server for DOS, Windows 3.1, or OS/2 workstations. These workstations must use VINES IP or they must communicate with a native VINES server that supports IP Clients. The native VINES server can forward packets between the IP Clients and the StreetTalk for Windows NT server.
For more information, see Installing Banyan Clients for Windows NT and Windows 95/98.
The StreetTalk for Windows NT Server-to-Server UDP (S-to-S UDP) option allows a StreetTalk for Windows NT server to communicate with another StreetTalk for Windows NT server or a native VINES Server through an IP network. UDP is a transport layer protocol used in the Internet suite of protocols. The S-to-S UDP software encapsulates VINES IP packets within UDP packets. The VINES packets appear as IP packets when they pass through the IP network.
A StreetTalk for Windows NT server can communicate with other StreetTalk for Windows NT servers and native VINES servers running the S-to-S UDP software. You can manually configure servers to communicate with one another or you can enable and disable automatic connectivity. Automatic connectivity allows servers to communicate with other servers without both servers manually specifying each other's serial number, hostname, and IP address. One of the servers must be manually configured and automatic connectivity can be enabled on the other server.
In Figure 1-2, the IP network appears to VINES IP as just another network type, such as Ethernet or Token-Ring, over which it must travel to reach a StreetTalk for Windows NT destination. With automatic connectivity enabled on Server 1, that server can connect to Server 2 and Server 3. The servername and IP address of Server 1 must be manually configured on Server 2 and Server 3.
Note: A StreetTalk for Windows NT server cannot communicate directly with a pre-8.0 native VINES server running the VINES TCP/IP Server-to-Server option, or with DOS or Windows 3.1 client workstations configured as IP clients.
Enabling Automatic Connectivity
Enabling automatic connectivity on a server with the Server-to-Server UDP option allows any server to configure and establish a connection to that server. When a server connects to your server, that server then has access to whatever hosts and gateways can be reached through your server. Therefore, you should carefully consider how enabling automatic connectivity will affect your network's security.
A StreetTalk for Windows NT server running the S-to-S UDP software can control the kinds of VINES traffic that enters its network from attached IP networks. Run the Banyan StreetTalk Explorer management tool and select the Restrict Access option to limit access to the server's resources. See Managing VINES Security for more information.
Automatic connectivity can also lead to inefficient use of server memory by allowing your routing table to accumulate host routes and expand.
For more information about S-to-S UDP software, see the StreetTalk for Windows NT Administrator's Guide. For more examples of server-to-server networks and the implications of using automatic connectivity, see Chapter 6 of the Banyan TCP/IP Guide.
You can install the S-to-S UDP software when you install other StreetTalk for Windows NT components. You can configure the S-to-S UDP software during or after StreetTalk for Windows NT software installation.
The S-to-S UDP software on a StreetTalk for Windows NT server has the following prerequisites:
![]()
StreetTalk for Windows NT base software. The S-to-S UDP software works only if StreetTalk communications software, the StreetTalk Naming service, and the StreetTalk Security Service are started. ![]()
TCP/IP. You must have installed Microsoft TCP/IP software included with your Windows NT software. You should be familiar with TCP/IP terminology and concepts and should be able to configure and manage TCP/IP on your Windows NT Server. ![]()
TCP/IP routing tables must be configured to correctly exchange UDP packets with other Windows NT Servers with which the StreetTalk for Windows NT server wants to exchange packets using the S-to-S UDP software. ![]()
If you manually connect your server to a StreetTalk for Windows NT server, you must know the hostname and the server serial number of the remote server, and the routing metric for the path to the remote server. If the Server-to-Server UDP software cannot look up the IP address of the remote server from its hostname, you need to know its IP address. If you know the IP address, you do not need to enter the hostname of the remote server.
For more information on Server-to-Server UDP, see the StreetTalk for Windows NT Administrator's Guide.
In a standalone environment, the time setting on the Windows NT operating system determines the time on a StreetTalk for Windows NT or VINES server. In a network that includes more than one StreetTalk for Windows NT server, servers can continuously share information to maintain a consistent network time. You can configure your network so that one or more StreetTalk for Windows NT or VINES servers control the time settings on the entire network.
StreetTalk for Windows NT servers and native VINES servers can communicate with one another to synchronize time across the network. Server Service on each server is responsible for coordinating time.
You can run StreetTalk Explorer to create a Trusted Source Time List to manage the exchange of time information among StreetTalk for Windows NT servers and native VINES servers on a network.
Server Service can keep a list of the servers from which it accepts broadcasts of time changes and a list of servers to which it broadcasts time changes. This is referred to as time synchronization.
You can control from what services a time synchronization is accepted and to what services a time synchronization is sent by creating lists of servers. Chapter 15 of the Banyan Server Operations Guide describes how to manage time on a StreetTalk for Windows NT server.
The following time-related tasks that affect time on a StreetTalk for Windows NT server are performed on the Windows NT operating system using Windows NT tools:
![]()
Setting or changing the time zone ![]()
Setting or changing the time and date ![]()
Scheduling an automatic dial-out to a reliable time service
See your Windows NT documentation for setting time on a Windows NT Server.
If your network has a native VINES server that is configured to dial out to the National Institute of Standards and Technology (NIST) Automated Computer Time Service (ACTS) of Boulder, Colorado (or any other time service that follows the NIST format) for accurate time, you can configure your StreetTalk for Windows NT server to accept time settings from that server.
The StreetTalk for Windows NT Network Management (SNM) optional service provides statistics about server performance, network traffic, server configuration, and VINES LAN interfaces. You access the service through StreetTalk Explorer or VNSM software such as MNET. It is an informational tool for knowledgeable network designers or advanced administrators responsible for monitoring network performance and solving network problems.
The SNM option lets your server communicate with a DOS, Windows, or OS/2 workstation from which you invoke StreetTalk Explorer or MNET. The server can then be monitored from any DOS, Windows, or OS/2 workstation in the network or from the server console of any VINES server, or from any StreetTalk for Windows NT server on which the Banyan Enterprise Client for Windows NT and STreetTalk Explorer are installed.
You cannot run the network monitoring software against a server that does not have the SNM option installed. Without SNM, you can only gather restricted statistics and configuration information about your server from its server console with programs such as STCOMMS and the Windows NT Performance Monitor.
The SNM option is useful in any network, but is especially recommended for large, multi-server networks. For instructions on how to use the program, see Monitoring and Optimizing Servers.
Managing StreetTalk for Windows NT File and Print Services
Managing StreetTalk for Windows NT file and print services requires that you install StreetTalk Explorer, a 32-bit graphical user interface management tool, on your Windows NT system. StreetTalk Explorer can also be installed on a Windows NT or Windows 95/98 client workstation.
StreetTalk Explorer lets you configure and manage StreetTalk file services (including VINES Files), and StreetTalk print services on Windows NT. StreetTalk Explorer is the only supported management tool that you can use to create and manage StreetTalk file and print services. You can use StreetTalk Explorer or other management tools (for example, MSERVICE) to manage other Banyan services (for example, STDA) running on a StreetTalk for Windows NT server or to manage your network.
You install StreetTalk Explorer from the Banyan Client Components Suite CD-ROM after you install StreetTalk for Windows NT software and the Banyan Enterprise Client for Windows NT.
StreetTalk for Windows NT on a Banyan Network
Figure 1-3 shows how running StreetTalk for Windows NT software lets you incorporate Windows NT servers, client workstations, and printers into a network. The network contains two separate networks connected by StreetTalk for Windows NT servers running S-to-S UDP software. One network consists of a StreetTalk for Windows NT server with an attached printer and three Banyan client workstations - Windows NT, Windows 95/98, and Windows 3.1. The Windows 95/98 and Windows 3.1 workstations use the VINES IP protocol to access the StreetTalk for Windows NT server. The Banyan Enterprise Client for Windows NT workstation accesses services on the StreetTalk for Windows NT server by means of UDP.
On the other segment are Banyan Enterprise IP Client for Windows 95/98 and Windows NT workstations. The Banyan Enterprise IP Client for Windows 95/98 accesses services by means of UDP. The Windows NT workstation uses the VINES IP protocol to access the StreetTalk for Windows NT server.
A StreetTalk Naming Service, StreetTalk Directory Assistance Service (STDA), StreetTalk Server Service, and StreetTalk Security Service run on the StreetTalk for Windows NT service. The STDA service can be configured to act as a master or a satellite to other STDA services. The service can be configured so client workstations look up names using that STDA service.
StreetTalk for Windows NT also maps a StreetTalk file service name (FS1@NT@Corporate) to a directory on the Windows NT server . The Banyan client workstations can map a network drive to this directory and use it as a StreetTalk file service. Windows NT users who log on to the Windows NT server (by means of other Windows NT-supported protocols) can store files in these same directories.
Similarly, the StreetTalk Print software installed on the Windows NT system assigns a StreetTalk name (Printer1@NT@Corporate) to the Windows NT local printer . All the Banyan client workstations can send print jobs to this print destination.
After StreetTalk for Windows NT software is installed and configured, StreetTalk security and Windows NT domains are independent of one another and are not synchronized. StreetTalk security and Windows NT domains can exist on the same network. See Managing StreetTalk for Windows NT Services for more information.
For more information on the topics discussed in this chapter, see the following documentation:
![]()
Managing StreetTalk for Windows NT Services ![]()
StreetTalk for Windows NT Administrator's Guide ![]()
StreetTalk for Windows NT Release Notice