Chapter 3 - Installing StreetTalk for Windows NT
This chapter describes how to install StreetTalk for Windows NT base and optional software components. You can install StreetTalk for Windows NT from:
![]()
A CD-ROM drive on your local Windows NT Server ![]()
A shared directory on another Windows NT Server on the Microsoft network ![]()
A CD-ROM drive on another Windows NT Server on the Microsoft network
To share a directory or CD-ROM drive, see your Microsoft documentation.
To let Banyan support personnel diagnose any problems that arise when StreetTalk for Windows NT software is installed, or after it is installed, every StreetTalk for Windows NT server must be configured to create debugging information files in the event your system experiences a fatal system (STOP) error. You can configure your system to create debugging information files for the Windows NT kernel, which includes StreetTalk Communications Protocols, and for StreetTalk for Windows NT services.
Debugging File for Communications Protocols
To save a debugging information file for StreetTalk Communications Protocols, follow these steps:
1. Display the Control Panel and double click the System icon.
2. Go to the Recovery section in the Startup/Shutdown tab (Windows NT 4.0).
3. Select the Write debugging information checkbox. Accept the default pathname (%SystemRoot%\MEMORY.DMP) for the debugging file or change it. Your system must have enough disk space to store the file in the event one is created. A debugging file requires a minimum of 32 MB of space and a maximum equal to your system's physical memory if more than 32 MB.
Do not select Overwrite any existing file checkbox. Save the debugging information file for study before overwriting it. If the system crashes and creates a debugging file, move the file to a new location after the system reboots.
Leave the select Automatically reboot checkbox blank unless necessary. Leaving this checkbox blank causes the system to display the system error screen and not reboot the system. Record the information in the system error screen before you reboot your system after a STOP error.
4. Reboot your system for the new settings to take effect.
It is also required that you configure Dr. Watson, the Windows NT application debugger, so that a StreetTalk for Windows NT service creates an error file if it crashes.
From the system prompt or in the Run menu, enter DRWTSN32.EXE to display the Dr. Watson user interface. Select the Create Crash Dump File checkbox, and either specify a filename for the crash dump file or accept the default. The default causes a service to create a USER.DMP file if it crashes.
Also, from the system prompt or in the File Run menu, run REGEDT32 and in the Registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Windows NT\CurrentVersion\AeDebug
make certain that these entries are set to the following values:
Auto: REG_SZ: 1
Debugger: REG_SZ: drwtsn32 -p %ld -e %ld -g
UserDebuggerHotKey: REG_DWORD: 0
Installing StreetTalk for Windows NT Base Software
During installation, StreetTalk for Windows NT base software is loaded on to your server from the CD-ROM or a shared directory. The base software consists of the StreetTalk Naming Service, StreetTalk Communications Protocols, the StreetTalk Security Service, the StreetTalk Server Service, StreetTalk Directory Assistance (STDA), StreetTalk File, and StreetTalk Print.
In addition to installing the base software, you can install optional product components. You can install StreetTalk Intelligent Messaging, StreetTalk Network Management, Backup Suite for StreetTalk, and Server-to-Server UDP when you install the base software or after you install the base software. Also after you install the base software, you can install VINES Files, the Enterprise Client for Windows NT, and StreetTalk Explorer, if you wish, from the Banyan Client Components CD-ROM included in the StreetTalk for Windows NT software package.
Before you begin the installation, it is recommended that you read Chapter 2 and complete the installation worksheet (Figure 2-2). If you are configuring Server-to-Server UDP software, complete the S-to-S UDP Worksheet (Figure 2-1).
If you have StreetTalk Access, the StreetTalk Client Workstation component of StreetTalk for Windows NT 7.x, or the Banyan Enterprise Client for Windows NT software installed on your Windows NT server, you must uninstall this software before installing StreetTalk for Windows NT software. See Chapter 2 for more information.
If you intend to install Backup Suite for StreetTalk, you must have NetWorker 4.4 installed on your server first.
If you have version 1.0 of LDAP for StreetTalk software on your server but you have not created an LDAP for StreetTalk service, the installation procedure will remove the LDAP for StreetTalk software.
Upgrading and Uninstalling
When upgrading from a previous version of StreetTalk for Windows NT or when uninstalling StreetTalk for Windows NT, you may see an error message stating that a particular StreetTalk for Windows NT service did not stop. In this case, exit the installation procedure and use the Task Manager to manually stop all StreetTalk for Windows NT processes before restarting the installation.
To stop the processes, press CTRL-ALT-DEL, click the Task Manager button (or right-click a blank area on the Task Bar and select Task Manager), and select the Processes tab. Find the process name of each running StreetTalk for Windows NT service (see the table below), select each StreetTalk for Windows NT process in the order shown, and click on the End Process button.
Table 3-1. StreetTalk for Windows NT Process Shutdown
Order | Service | Process in the Windows NT Task Manager |
1 | StreetTalk Server Service (Queries you to stop StreetTalk File and Print services.) | SS.EXE, STFILE.EXE, STPRINT.EXE |
2 | StreetTalk File (If Server Service not running.) | STFILE.EXE |
3 | StreetTalk Print (If Server Service not running.) | STPRINT.EXE |
4 | StreetTalk Network Management | SNM.EXE |
5 | StreetTalk LDAP Service | SLAPD.EXE, SADBSERVER.EXE |
6 | StreetTalk IMAP Service | IMAP4REVX.EXE (X is the revision, 1, 2, ...) |
7 | StreetTalk Intelligent Messaging | BMS.EXE, MTA.EXE |
8 | StreetTalk Directory Assistance and StreetTalk Name Collector | STDA.EXE, GETNAMES.EXE |
9 | StreetTalk Security | VS.EXE |
10 | StreetTalk | ST.EXE |
To verify that the services stop, see that the Task Manager no longer lists the StreetTalk for Windows NT processes.
Note: In the rare case that the Task Manager cannot stop a process, use this procedure:
1. Go into the Service Control Manager (SCM) (Start, Settings, Control Panel, Services) and make a record of which services have a Startup value other than Disabled and what the Startup values are.
2. Set the Startup value for all StreetTalk services to Disabled (select the service and click the Startup button).
3. Reboot the server and restart the upgrade or uninstallation procedure.
4. If you are upgrading rather than uninstalling, after you complete the upgrade but before rebooting again, go into the SCM and reset the StreetTalk services to their original Startup values as recorded in step 1.
When you install StreetTalk for Windows NT software from the software CD-ROM, refer to your installation worksheet (Figure 2-2) described in Chapter 2.
Note: If the file partition on which you intend to install StreetTalk for Windows NT is not an NTFS partition (for example, a FAT partition), an error message is displayed after you select the software components to be installed. You must exit the installation program and convert the partition to NTFS before proceeding. Chapter 2 describes how to convert your FAT partition to NTFS.
Follow these steps to install from CD-ROM:
1. Log on to your Windows NT server using a Windows NT username that is a member of the Windows NT administrator's group.
2. Insert the StreetTalk for Windows NT base software CD-ROM into the CD-ROM drive of your system.
On a Windows NT 4.0 system with the Autorun feature enabled, StreetTalk for Windows NT automatically prepares the installation and presents a dialog box to select the language version (location) to install.
If the Autorun feature is disabled, use this procedure:
a. Select Run from the Start menu of Windows NT 4.0. The Run dialog box appears.
b. Enter d:\Install\setup where d is the drive letter of your CD-ROM, or click Browse, go to the Install directory, open Setup.exe, and click OK.
3. Select the language version of the installation program by selecting it from the dropdown box and click OK.
Caution: Do not install a language version of StreetTalk for Windows NT that differs from the language version that is already present on your Windows NT server.
You can select English, French, German, Japanese, and Spanish language versions of the installation program.
The StreetTalk for Windows NT installation program prepares to install the software. This may take up to 30 seconds. It then displays the Welcome screen with information pertinent to installation.
4. Read the information and click Next. The Software License Agreement displays. Read the agreement carefully. Click Yes to accept the agreement. If this is a new installation, go to step 6.
Note: As the installation program proceeds, you can press F3 to exit whenever a dialog box displays.
5. If you previously installed a version of StreetTalk for Windows NT, you are prompted to replace the currently installed version. If you click Yes, the Information dialog box displays a list of StreetTalk services that are installed on the system. Click Next to proceed. The StreetTalk for Windows NT installation program automatically stops these services later in the installation process.
6. The Server Code dialog box displays as shown in Figure 3-1.
If this is an existing installation, the existing Server Code and Server Enabler Code display in the dialog box. The existing StreetTalk server name is dimmed because you cannot change the server name during installation.
If this is a new installation, enter the following information, which you obtain from the card that shipped with your software:
- The Server Code, which is a maximum of 16 numeric characters
- The Server Enabler Code, which consists of 3 numeric characters and is related to the Server Code.
- The StreetTalk for Windows NT server name. You supply the server name. If you have multiple StreetTalk for Windows NT servers, use a consistent naming scheme - see Planning a Banyan Network.
Click Next.
7. If this is a new installation, the StreetTalk Admin Account dialog box is displayed as shown in Figure 3-2.
If this is an existing installation, this dialog box is not displayed - go to step 8.
Enter and verify the password of the user that is created after the StreetTalk for Windows NT software is installed, Admin@servername@Servers. The password can be up to a maximum of 15 characters.
Keep a record of the password that you enter. If you lose the password, you cannot administrate the system.
Click Next. The Setup Type dialog box appears, Figure 3-3.
Figure 3-3. Setup Type Dialog Box 8. Select the type of installation that you prefer (Typical, Compact, or Custom) from the Setup Type dialog box. Each selection installs the following software:
Typical - The StreetTalk for Windows NT base software component (see above for a description) excluding the separately purchasable options. There is also a Compact selection that is identical to Typical.
Custom - Select from a list of software components. The StreetTalk for Windows NT base software component is checked to be installed by default. The separately purchasable options are not checked but you can select them individually.
Note: To install the Backup Suite for StreetTalk, you must have NetWorker 4.4 installed on the server.
The default destination directory is C:\Program Files\Banyan. Most server software components are installed in this directory and in subdirectories created under it. To select a directory other than the default, select Browse.
If this is an existing installation and you change the default destination directory, you must first uninstall the previous version of StreetTalk for Windows NT software. Changing the default destination causes the installation program to inform you that additional components must be installed in the same directory and returns you to the Setup Type dialog box.
9. Click Next. If you selected Typical or Compact, go to step 10.
If you selected Custom, the Select Installation Components dialog box displays as shown in Figure 3-4. Click on the checkboxes of the components that you want to select or deselect.
Notes: Backup Suite for StreetTalk appears only if NetWorker 4.4 or 5.5 exists on your server.
If you have Intranet Messaging Suite (IMS) on your server, you may not want to install the StreetTalk Intelligent Messaging component of StreetTalk for Windows NT 8.6 depending on which components of IMS you installed. This is because IMS includes an Intelligent Messaging component that supports IMAP and MAPI, and the Intelligent Messaging component of StreetTalk for Windows NT 8.6 does not support IMAP and MAPI. Refer to the StreetTalk for Windows NT 8.6 Release Notice for details.StreetTalk for Windows NT includes the StreetTalk Naming service, the StreetTalk Communications Protocol Stack, the StreetTalk Server Service, the StreetTalk Security Service, and StreetTalk File and Print, and these must be installed. They are always installed together no matter what type of installation you select. If you already installed StreetTalk for Windows NT and are now separately installing one or more of the optional components, you may deselect StreetTalk for Windows NT.
The disk space required for each component is also listed. Click Disk Space to check the amount available on the server. Click Back to change a selection or click Next if the settings are acceptable.
10. Select the program group to install StreetTalk icons in. The StreetTalk for Windows NT folder is the default group. Click Next.
11. The Confirm Selection dialog box displays. It lists the type of installation (Typical, Compact, or Custom) and the software components selected, the target directory, the program folder, the server name and the server serial number created from the Server Code and the Server Enabler Code, the expiration date of the software (if any), the above codes, and the software version.
Click Next to continue or click Back to make changes.
Note: If the number of days to expiration is 000, the software does not expire.
12. StreetTalk for Windows NT services previously installed are stopped if this is an existing installation; it may take a few minutes for all services to stop. New program files are copied from the CD-ROM.
13. After files are copied from the CD-ROM, the Network Communications dialog box displays as shown in Figure 3-5.
Note: After you install StreetTalk for Windows NT, you can display the Network Communications dialog box from Network icon of the StreetTalk server configuration selection in the StreetTalk for Windows NT program group.
The top of the dialog box displays the server serial number, which is derived from the Server Code and Server Enabler Code entered previously, and the network adapter that StreetTalk for Windows NT software will use.
To configure the server's LAN card for StreetTalk for Windows NT:
a. Select a network adapter from the drop-down list. The current adapter is highlighted.
b. Select any network adapter installed and configured for Windows NT. You can select only one adapter.
Do not enable UDP Client or S-to-S UDP support unless your server requires it. Enabling UDP Client or S-to-S UDP software consumes server resources and causes the StreetTalk Naming service to broadcast additional packets on your network that can impair its performance.
Note: If you select Server-to-Server UDP from the Select Installation Components dialog box (Figure 3-4), the Enable server-to-server UDP support checkbox is checked.
Select the Enable UDP client support checkbox to begin configuring UDP Client parameters. The UDP Setup dialog box automatically displays. Go to step 14.
A. Select the Enable server-to-server UDP support checkbox to begin configuring S-to-S UDP parameters. The Configure UDP Server-to-Server Communications dialog box automatically displays. Go to step 15.
B. Banyan suggests you use the default settings for Communications Heap Size, Number of Sockets, Total SPP Connections, and SPP MTU Size. These settings can be changed after the installation is complete. See Chapter 2 for more information about the meaning of these settings. Chapter 4 describes the conditions that might cause you to change them.
You can also choose to enable Source Level Routing (SLR) if your network adapter is a Token-Ring card and if both of the following conditions apply:
- Your workstation will send and receive data through Token-Ring bridges.
- The Token-Ring LAN to which your workstation is connected has no servers with Source-Level Routing enabled.
The Advanced button displays the Advanced Communications Options dialog box that allows you to change communications parameters. These advanced communications parameters can be changed after installation but only if your support representative instructs you to do so. Chapter 2 describes these parameters.
Click Continue to save your changes. Go to step 16.
Note: After you change any settings on the Network Communications dialog box, you must reboot your server for them to take effect.
14. From the UDP Setup dialog box, Figure 3-6, select Configure UDP clients on directly connected subnets checkbox to enable support for UDP clients on TCP/IP subnets that have been configured as part of the Windows NT configuration. They are directly connected to your StreetTalk for Windows NT server.
Change the default metric increment (2) for recognized network types and the metric (10) for unrecognized network types, if necessary.
Select the Configure UDP clients on remote subnets check box to enable support for UDP Clients from any TCP/IP subnet that is not directly connected to the StreetTalk for Windows NT server.
Change the remote UDP client default metric (10), if necessary.
If you do not support remote IP Clients, disable this support to prevent unintentional access to your server.
Click OK to save your changes and return to the Network Communications Dialog box (step 13 A).
15. From the Configure Server-to-Server UDP Communications dialog box (Figure 3-7), select the Enable automatic connectivity on directly connected subnets checkbox to enable support for servers on TCP/IP subnets that have been configured as part of the Windows NT configuration. They are directly connected to your StreetTalk for Windows NT server and their Server-to-Server UDP connectivity must be manually configured.
Change the default metric increment (2) for recognized network types and the default metric (10) for unrecognized network types, if necessary.
Click the Enable automatic connectivity on remote subnets checkbox to allow any StreetTalk for Windows NT server with Server-to-Server UDP software enabled on any TCP/IP subnet that is not directly connected to your server to connect to your server.
Caution: If you enable automatic connectivity, your server does not have any control over what servers attach to it. Therefore, you must carefully set up network security. Managing VINES Security describes configuring network security.
Change the default metric (26) for servers on remote networks, if necessary. If you leave the metric box blank or enter 0, the connection is assigned the default metric.
To manually configure a connection to a server, enter the serial number, hostname, host IP address, and metric of the StreetTalk for Windows NT or the VINES server you want your server to communicate with.
Click Enabled if you want your server to attempt to establish communication immediately with the server described in the entry. If you do not click Enabled, the configuration information is retained and can be enabled later.
Click Add to add the manually configured server entry. You are cautioned that the change cannot be undone and your server will be connected if Enabled is selected and the server is rebooted. (After a reboot, manual connections are added immediately if S-to-S UDP software was enabled since the last reboot.) When you add a connection, Enabled should be selected.
Click Default to restore the default metric settings for S-to-S UDP communications.
Click Cancel to exit the Server-to-Server UDP Configuration program. The original metrics for automatic connectivity are restored. The Network Communications dialog box is displayed. If you clicked Add, Delete, or Modify, the changes you entered are still in effect.
Click Continue to save your changes and return to the Network Communications Dialog box (step 13 B).
Click Help to display additional information about S-to-S UDP software.
Note: After you install S-to-S UDP software, whenever you enable or disable S-to-S UDP support or change metrics associated with automatic connectivity, you must reboot your server. If you change any settings on the Network Communications dialog box, reboot your server.
16. The Configure Network Workstation Name dialog box displays after you click Continue on the Network Communications dialog box. This dialog box lets you enter a name that the system uses for communication with third-party Winsock distributed applications. You can also enter the name of StreetTalk groups to be searched to locate other workstations on the network.
Note: After you install StreetTalk for Windows NT, you can display the Configure Network Workstation Name dialog box from Computer icon of the StreetTalk server configuration selection in the StreetTalk for Windows NT program group.
If you select the Name Workstation on Network checkbox and enter a computer name (for example, ST-NT-01), a PC-based service with the servername as the service's item name in the servername@Servers group (for example, ST-NT-01@ST-NT-01@servers) is created when the server is rebooted.
After StreetTalk for Windows NT software is installed, you can redisplay this dialog box and change these settings.
Leave this dialog box blank unless you are using a third-party Winsock application that uses Banyan protocols. Click Continue.
The Windows NT Bindings dialog box displays bindings messages as network protocols are bound to each other and the network adapter.
17. After all the StreetTalk for Windows NT files are copied and the network protocols are bound , the Setup Complete dialog box is displayed. Click Finish to complete the Setup and display the Readme file.
Note: If the Windows Explorer screen appears, click on the StreetTalk for Windows NT Installation in the background to see the Setup Complete dialog box.
18. The Installation Complete dialog box displays.
If you will not install the Banyan Enterprise Client, StreetTalk Explorer, or VINES Files on your server at this time, remove the CD-ROM from the drive, click Yes to restart now, and click Finish to reboot your system.
If you will install the Banyan Enterprise Client, StreetTalk Explorer, or VINES Files on your server, click No to restart later, click Finish, and go to "Installing VINES Files" or "Installing the Banyan Enterprise Client."
If you will install the Banyan Enterprise Client and you rebooted the server since the StreetTalk for Windows NT installation, install the Banyan Enterprise Client last and reboot after that installation. Otherwise, the operation of the StreetTalk for Windows NT software is adversely affected until you reboot.
Note: If you have an existing LDAP service, you must manually restart it after the server reboots.
You install the VINES Files on your StreetTalk for Windows NT server from the VFILES directory on the Banyan Client Components Suite CD-ROM.
Note: Before installing a new version of VINES Files, use StreetTalk Explorer to stop the existing VINES Files service unless you install VINES Files as part of installing StreetTalk for Windows NT, in which case that installation automatically stops all services.
Follow this procedure to install VINES Files on your StreetTalk for Windows NT server.
1. Insert the Banyan Client components CD-ROM in drive.
2. Select Run from the Start menu. The Run dialog box appears.
3. Enter D:\VFiles\Install\setup.exe or click Browse and go to the VFiles directory, open Setup.exe, and click OK. The Choose Setup Language screen appears.
Note: Do not run Install.exe from the VFiles directory. That program is for installing VINES Files on a native VINES server.
Figure 3-9. Choose Setup Language Screen
4. Select the language from the Choose Setup Language screen dropdown box. Choose the language that you used to install Windows NT server. This has no relation to the language versions of VINES Files.
Caution: Do not select a language version of StreetTalk for Windows NT that differs from the language version that is already present on your Windows NT server.
Setup prepares the InstallShield process.
5. The Welcome screen appears. Read the screen. If you have other Windows programs running, close them before continuing. You can press ALT-TAB to cycle through the programs. Click Next to continue.
Figure 3-10. Welcome Screen
6. The Software License Agreement appears. Read the agreement carefully. Click Yes to accept the agreement. If you click No, Setup exits.
7. If this is a new installation, the Specify StreetTalk VINES Files Destination Path screen appears. Accept the default or click Browse to install VINES Files in another directory. Click Next to continue.
If this is a new installation, you can change the installation directory; if it is not a new installation, you cannot change the installation directory. Go to step 8.
8. The Select StreetTalk VINES Files screen appears. Select the components and the languages you want to install on the server.
Figure 3-11. Select StreetTalk VINES Files Screen
The English language version of the DOS and Win32 components are selected by default. DOS is required to support DOS, Windows 95/98, and Windows NT clients. OS/2 is required to support OS/2 clients. Win32 is required to support Windows 95/98 clients.
Any language version of Win32 that you select automatically selects the corresponding language version of DOS and prevents you from deselecting the DOS language version. However, deselecting a Win32 language version does not automatically deselect the corresponding DOS language version. You must explicitly deselect the DOS language version if you do not want it.
When you finish selecting, click Next.
9. The Start Copying Files screen appears with the current setting for the default installation directory and the platform, and the DOS, OS/2, and Win32 VINES languages.
If the current settings are correct, click Next to start copying files. If you want to make changes, click Back.
Setup shows the progress of copying the files.
10. When the copy is complete, the Installation Complete screen appears reminding you to remove any diskettes from the diskette drive and to reboot the server. You must reboot to have access to VINES Files but do not reboot now if you will install from another language CCCD or if you will install other software such as StreetTalk Explorer or Enterprise Client for Windows NT. Read the screen and click Finish.
If you plan to install another language, such as Japanese, from the other CCCD, repeat this entire procedure with that CCCD.
Figure 3-13. Installation Complete Screen
11. Reboot the server unless you will install other StreetTalk for Windows NT software. Also, restart the VINES Files service after rebooting if you explicitly stopped the service before starting the VINES Files installation.
Installing the Banyan Enterprise Client
You install the Banyan Enterprise Client on your StreetTalk for Windows NT server from the WINNT directory on the Banyan Client Components Suite CD-ROM. The language will be the same as the language you selected when you installed StreetTalk for Windows NT.
1. Select Run from the Start menu (Windows NT 4.0). The Run dialog box appears.
2. Enter d:\winnt\setup where d is the drive letter of your CD-ROM or click Browse and go to the WINNT directory, open Setup.exe, and click OK. The Banyan Setup dialog box appears.
3. Click Install. The Install Directory dialog box appears with the Destination Directory. The default directory is C:\Program Files\Banyan\Vns or the Vns directory in wherever you installed StreetTalk for Windows NT, and cannot be changed. Click Continue. The Banyan Enterprise Client dialog box appears.
4. Specify a Login Group List. This feature lets you specify up to three StreetTalk groups that the login program searches when you enter only the first part of your three-part StreetTalk name or nickname. For more information, refer to Chapter 2 of this guide or Managing Workstations .
Enable or disable the following login options:
Load Banyan client software at system start - Loads the Banyan workstation software each time your workstation boots. You can log in to the Banyan network whether or not you select this option. Selecting this option lets you log in more quickly. It is recommended that you click this option if you will frequently log in to the Banyan network from this server. It is set by default.
Use Windows NT Login for Banyan Login (common login) - Enabling this option lets you use your Windows NT username and password as a common login to the Banyan network. This option passes the Windows NT login name together with the groups in the Login Group List and your password to the client for use in the Banyan login.You must wait until all StreetTalk for Windows NT services start before logging in to Windows NT if you enable common login. Therefore, Banyan recommends that you do not enable common login.
Timeout login status - Lets you specify the length of time in seconds the Login Status dialog box remains on the screen after login processing has completed. The default is 6 seconds.
Note: The Login Status timeout period does not start until after your client has located a VINES Files service. Depending on your network configuration, this may cause the Login Status dialog box to remain on the screen for much longer than the timeout period.
You can redisplay this dialog box and change these settings after the Banyan Enterprise Client for Windows NT software is installed.
5. Click Continue. The Banyan Desktop Configuration dialog box appears.
Enable or disable the following configuration options:
Create program group named - Enabling this option creates a program group that contains all the Banyan Client applications for Windows NT. You can specify the name of the program group. The default is VINES.
Change AUTOEXEC.NT to load the TSR - This option loads support for 16-bit Banyan DOS and Windows applications in a Windows NT environment. Enabling this option loads the TSR BANSVC.COM. If you do not enable this option, you must manually run the TSR before you can run Banyan Applications Toolkit DOS programs.
BANSVC.COM is needed to support 16-bit DOS applications on a Windows NT system because on Windows NT, DOS is only loaded as another process. Therefore, DOS has no direct knowledge of where local or network resources are located or how to access them. BANSVC.COM intercepts interrupt requests made by DOS applications and sends these requests to the Windows NT operating system.
Note: The Terminate and Stay Resident (TSR) program, BANSVC.COM, is installed in C:\Program Files\Banyan\Vns\apps.
6. Click Continue. The VINES Files Service Revision dialog box appears.
You can set a range of preferred revisions for your client workstation to connect to. The default range is 7.0 to the latest 8.0 version. You can also set an alternate range of revisions for your client workstation to connect to. The default range is 5.3 to the latest 8.0 version.
After you set or accept the ranges, click Continue. The installation process copies files to the server disk and creates the program group.
7. After all the Banyan Enterprise Client for Windows NT files are copied and the program group is created, the Setup Complete dialog box is displayed and you can restart your system. Click Restart Now to reboot your system.
Note: You must reboot your system in order to access the Banyan network. If you have an existing LDAP service, you must manually restart it after the server reboots.
After StreetTalk for Windows NT software is installed on Windows NT and the system is rebooted, a StreetTalk program group is installed in the Start menu Programs folder.
Table 3-2 describes the icons in the StreetTalk for Windows NT program group.
Icon | Click to... |
StreetTalk Server Configuration | Display Network and Computer selections of the StreetTalk Setup program group, which are described in Table 3-3. |
Uninstall | Uninstall StreetTalk for Windows NT software. |
StreetTalk Recover Browser | Provides you with a StreetTalk view of Banyan entities included on the server and allows you to recover and verify StreetTalk items. |
StreetTalk README | Read about StreetTalk for Windows NT. The printed StreetTalk for Windows NT Release Notice contains a complete listing of operational notes and known problems. |
Uninstall StreetTalk VINES Files | Uninstall VINES Files. Present only if you install VINES Files. |
Table 3-3 describes the icons in the Enterprise Client, or VINES, program group.
Icon Click to... Help See Enterprise Client for Windows NT Help. Login Log in to the Banyan networki. StreetTalk services must be completely started before you can log in to the Banyan network. Logout Log out of the Banyan network if you are logged in. You cannot log out if you have a network connection open. For example, if you open a DOS window and run a Banyan program from that window, you cannot log out until you close the program. Messages Read a message sent to you or send a message to StreetTalk users. Passwords Change your StreetTalk and Windows NT password. Send Send a message to StreetTalk users. Setup Configure the workstation, network communications, message receipt, VINES Files service revision, or access STDA. See Table 3-4. Release Notes Read about Banyan Enterprise Client for Windows NT. This Release Notice describes what is supported, describes fixes for this release, and contains a complete listing of operational notes and known problems. This icon is displayed only if you installed the StreetTalk client workstation software. Table 3-4 describes the icons displayed when you select the StreetTalk Server Configuration, or Setup, menu selection. The icons this program group displays depend on whether the client component software is installed.
By default, StreetTalk for Windows NT is installed in the directories shown in Figure 3-14. The Program Files\Banyan directory is configurable as is the location of VINES Files.
These directories contain the files described in Table 3-5:
Directory | Description |
BIN | StreetTalk for Windows NT executable files for users. |
DATA | Data areas for services including Intelligent Messaging, Server Service, StreetTalk, STDA, and the Security Service. |
FILE | StreetTalk File executable files if StreetTalk File was installed. |
StreetTalk Print executable files if StreetTalk Print was installed. | |
SBIN | Non-user executable files. |
SETUP | StreetTalk for Windows NT Setup files used for uninstalling StreetTalk for Windows NT. |
SUPPORT | Diagnostic programs. See Chapter 4 for more information. |
SYSERROR | English error (.err) and help (.hlp) files for StreetTalk for Windows NT services and administrative program accesses when VINES Files is not installed. |
VFILES | Drive Z client programs (VINES Files) if they were installed. |
VNS | StreetTalk for Windows NT communications protocol files. |
Additional StreetTalk for Windows NT files are installed in %systemroot%\system32 directory. These include Dynamic Link Library (DLL) files.
When you finish installing StreetTalk for Windows NT software and any other software, such as VINES Files and Banyan Enterprise client for Windows NT, and reboot the server, you should perform these tasks, which the following sections describe:
![]()
Log in as Admin@Servername@Servers. ![]()
Create StreetTalk Login Shortcut. ![]()
Configure the Remote Access Service. ![]()
Install StreetTalk Explorer if you installed Enterprise Client for Windows NT. ![]()
Create an emergency repair diskette. ![]()
Install additional StreetTalk for Windows NT components. ![]()
Install third-party software.
The sections that follow describe each of these topics.
The StreetTalk for Windows NT installation program creates an Adminlist@servername@Servers group with one member, Admin. This user was assigned a password when the software was installed.
Log in as this user either at a client workstation or at the server console if you installed Enterprise Client for Windows NT and add other users to the AdminList or click on the Password icon in the StreetTalk for Windows NT program group and change the password for this user, if necessary.
Note: StreetTalk for Windows NT services must be fully started before you can log in at the server console. If you have common login enabled, do not log in until all StreetTalk for Windows NT services have started.
Create a StreetTalk Login Shortcut
If you install Enterprise Client for Windows NT client software on your Windows NT Server, you can create a shortcut to log in to the network. An icon on your desktop represents the shortcut. Create a shortcut by dragging and dropping the Enterprise Client for Windows NT login icon to your desktop or by running the Windows NT shortcut wizard. To run the wizard on Windows NT 4.0, right-click on the desktop, select New, and select Shortcut. When the Create Shortcut dialog box is displayed, you must enter the path of the \VNS\Apps\Ban.exe program. For example, if you installed the Enterprise Client for Windows NT in the default installation directory, enter:
C:\Program Files\Banyan\VNS\Apps\Ban.exe
Do not enter Login.exe. If you enter Login.exe, your shortcut will not work properly. When you drag and drop to create the shortcut, the pathname of the shortcut is created correctly.
Configure the Remote Access Service (RAS) for Banyan Dial-in Support
To support StreetTalk for Windows NT software, it may be necessary for Banyan support personnel to dial-in to your server. Dial-in requires the configuration of the Windows NT Remote Access Service (RAS).
Before you configure RAS, you should have a modem supported by Windows NT connected to a COM port and the Microsoft TCP/IP stack configured on the Windows NT Server.
To configure the Windows NT Remote Access Service (RAS), follow these steps:
1. Log on to a Windows NT Server as an administrator of the server.
2. Create a user who belongs to the Administrator group specifically for dial-in use. This user's name and password must be given to Banyan support personnel before initiating a dial-in session.
3. Open the Control Panel and double-click the Network icon.
4. On Windows NT 4.0, click Start, select Programs, Administrative Tools, and then Remote Access Admin.
5. Select Remote Access Service from the drop-down list. If you are prompted for the Windows NT Server CD-ROM, insert it in to your CD-ROM drive. The RAS Setup files are copied to your server.
RAS displays the default COM port and detects the connected modem. If the information is correct, continue. If the information is not correct, you can manually select the modem type that is connected.
6. The RAS NetBEUI Configuration dialog box is displayed. You are prompted to allow remote NetBEUI clients to access the entire network or this computer.
7. The RAS TCP/IP Configuration dialog box is displayed. You are prompted to select the level of access for TCP/IP clients and to specify IP address assignments for RAS clients.
8. The network software is reconfigured and you are prompted to reboot your server to make these changes take effect. Once you reboot, a Remote Access Services program group is displayed on Windows NT 3.51.
9. Grant dial-in permission to the user who Banyan support personnel will log in as when they dial in to the Windows NT Server. From the Remote Access Service program group, select Users from the title bar and Permission from the drop-down menu. Select the user that you created and click Grant dialin permission to user.
10. To start RAS, select Server from the title bar of the Remote Access Service program group and click Start Remote Access Services from the drop-down menu. When RAS is started, the Windows NT Server is ready for dial-in.
For additional information on RAS, see your Windows NT documentation.
To install the StreetTalk Explorer management tool on your StreetTalk for Windows NT server, another Windows NT server, or a Banyan client Windows 95 workstation, insert the Client Components Suite CD-ROM in the CD-ROM drive and run:
\stexp\language\setup.exe
language is the same as the language version of the Banyan Enterprise Client for Windows NT, for example, usa.
The StreetTalk Explorer installation program also installs the StreetTalk OLE Automated Service. StreetTalk Explorer requires this service.
See the Banyan Client Components Suite Installation Guide and the StreetTalk Explorer online release notice for more information.
Create an Emergency Repair Diskette
It is strongly recommended that after you install StreetTalk for Windows NT that you update the repair information on your fixed disk or update your NT Emergency Repair diskette. To update repair information, to update a repair diskette, or to create a repair diskette, run the Windows NT RDISK.EXE utility.
Install Additional StreetTalk Software
You can re-run the installation program at a later time to install additional components. When you re-run the installation programs, you must use the same:
![]()
Servername ![]()
Data directory
The Server Code and Server Enabler Code must be the same unless the expiration date of your software changes and you are given a new Server Code and Server Enabler Code derived from your server serial number.
It is recommended that you use the same program group to specify the location of icons (for example, StreetTalk for Windows NT).
The installation program displays the information that you entered when you ran the program the first time.
Install StreetTalk-Integrated Applications
You can install software (for example, Microsoft SNA Server or Microsoft SQL Server) that is integrated with the StreetTalk Naming service. StreetTalk integration allows you to run these services along with other StreetTalk for windows NT services.
To install these services follow these steps:
1. Install the software on your StreetTalk for Windows NT server according to the vendor's instructions.
2. Create the service according to the vendor' s instructions. Add the service to a group on the local StreetTalk for Windows NT server.
3. When you create the service you must specify the user who will log in to the Windows NT server and run the service. You can create a special user for this purpose. To maximize security, create a blank profile for this user so the user does not have access to other network resources.
Backing Up StreetTalk for Windows NT
You can use the Windows NT backup utility to back up StreetTalk for Windows NT. However, this utility has these limitations:
![]()
You may not be able to completely restore a database (for example, StreetTalk and STDA) that was open at the time the backup was performed. ![]()
To restore a single file in a StreetTalk for Windows NT file service and restore the Access Rights List (ARL) associated with that file, it is necessary to restore the file service in which the file resides. ARL information is stored separately from the file data. See Managing StreetTalk for Windows NT Services for more information. ![]()
The Microsoft backup utility cannot distinguish between filenames that differ only in case. For example, if two files named file1.doc and File1.doc are in a file service, only one is restored. See the StreetTalk for Windows NT Release Notice for recommended backup utilities.
Removing StreetTalk for Windows NT Software
You can run the StreetTalk for Windows NT uninstall program to completely or partially remove the StreetTalk for Windows NT software from a server, for example, to return your system to its original state or to move StreetTalk for Windows NT software to another server. This procedure removes all or some of the services that you created on the server. Only use this procedure if you want to remove StreetTalk for Windows NT from a server.
The uninstall program does not delete file, print, or STDA services or the service that they depend on (for example, the StreetTalk Naming service) if they are running and recognized by StreetTalk when the uninstall program is invoked. For example, if you attempt to remove an STDA service that has not been stopped and deleted from StreetTalk, the following message is displayed:
Must remove STDA from StreetTalk before deinstalling.
Also, if VINES Files is running, use StreetTalk Explorer stop and delete the VINES Files service. Otherwise, VINES Files is recognized as a share of StreetTalk File and StreetTalk File cannot be deleted. For more information about VINES Files, see Managing StreetTalk for Windows NT Services.
Banyan Enterprise Clients for Windows 95 require DOS VINES and Win32 VINES. Removing DOS VINES can prevent Windows 95 workstations from accessing the network.
Uninstalling StreetTalk for Windows NT:
![]()
Checks for the existence of LDAP for StreetTalk, Banyan Intranet Messaging Suite (the IMAP service), and Banyan Enterprise Client. Also checks for Intelligent Messaging and STDA. If any one of these is present, the uninstall process displays an error message and stops. ![]()
Stops all StreetTalk for Windows NT services ![]()
Deletes StreetTalk for Windows NT software ![]()
Deletes all program and data files if located in the default installation directory (\Program Files\Banyan) ![]()
Removes StreetTalk entries from the Windows NT Registry ![]()
Removes the StreetTalk for Windows NT icons and folder
Uninstalling StreetTalk for Windows NT File does not delete data residing in StreetTalk for Windows NT file services in NT directories.
To remove StreetTalk for Windows NT from your server, follow these steps.
Note: If, during the uninstallation procedure, you see an error message stating that a particular StreetTalk for Windows NT service did not stop, see the Installation Notes section earlier in this chapter.
1. Run StreetTalk Explorer or another Banyan management tool to stop, and then delete any file (including VINES Files), print, Intelligent Messaging, IMAP, LDAP or STDA services that you created. Otherwise a message displays indicating that services that are still in StreetTalk cannot be deleted.
2. Uninstall Banyan Intranet Messaging Suite (IMS - the IMAP service) if it exists on your server. See the IMS documentation.
Note: Do not reboot the server until after uninstalling the Enterprise Client for Windows NT.
3. Uninstall VINES Files. See the section "Uninstalling VINES Files." You should have stopped the VINES Files service and deleted it from StreetTalk in step 1.
4. Uninstall LDAP for StreetTalk and Banyan Intranet Messaging Suite if they exist on your server. See the documentation accompanying these products.
5. Uninstall the Banyan Enterprise Client. See the earlier section "Uninstalling the Banyan Enterprise Client."
Reboot the server after uninstalling the Banyan Enterprise Client.
6. From the Start menu, select Programs, StreetTalk for Windows NT, Uninstall.
7. In the Confirm File Deletion window, click Yes to confirm the removal.
InstallShield removes the components of StreetTalk for Windows NT from the computer.
Note: If messages appear about deleting shared files, you can safely delete them.
8. When the uninstall successfully completes, click OK.
Note: If you see a message at the bottom of the screen related to some elements not being removed, click Details to determine what the elements are. You can manually delete them after you reboot.
9. Use the Add/Remove Programs icon in the Control Panel to remove StreetTalk Explorer; see the StreetTalk Explorer documentation.
Caution: You must not reinstall StreetTalk for Windows NT and enter a new server code or servername. The server code determines the StreetTalk address, which is associated with the servername. The servername and server code must be changed together by uninstalling the StreetTalk for Windows NT software. Proceeding any other way can cause serious network problems.
There is also an Uninstall icon in the StreetTalk for Windows NT program group that you can use to remove selected components, such as an option, from the server. The procedure for using the Uninstall icon is similar to the installation procedure in that the procedure presents you with a window where you can select individual components to remove.
Renaming a StreetTalk for Windows NT Server
To rename a StreetTalk for Windows NT server with your original Server Code and Server Enabler Code, you must uninstall StreetTalk for Windows NT software, wait a minimum of 96 hours until the old StreetTalk servername ages out of the StreetTalk database, and then reinstall StreetTalk for Windows NT software with a new StreetTalk servername. If you do not wait 96 hours, other servers on the network will not recognize your server until the old servername ages out of their StreetTalk databases.
The Server Code creates a StreetTalk address that is a associated with the original servername. The association between the servername and the Server Code lasts until the name disappears from the database.
Caution: Re-running the installation program and entering a different servername without waiting for the removal of the name from the StreetTalk database can impair the operation of your network.
Do not edit the Windows NT Registry to remove the StreetTalk servername.
You uninstall VINES Files using the Add/Remove Programs icon in the Control Panel. Follow this procedure:1. Log in to StreetTalk as a user on the server AdminList.
2. Use StreetTalk Explorer to stop the VINES Files service and delete it from StreetTalk.
Caution: If you do not stop and delete the VINES Files service and do not uninstall StreetTalk for Windows NT, and later you re-install VINES Files, the StreetTalk services may fail to start after rebooting the server.
3. Open Control Panel and double-click on the Add/Remove Programs icon.
4. From the Install/Uninstall tab, select StreetTalk VINES Files and click the Add/Remove button.
5. In the Confirm File Deletion window, click yes.
InstallShield removes the components of VINES Files from the computer.
6. When the uninstall successfully completes, click OK.
7. Click OK at the Add/Remove Properties window.
8. Manually delete the VINES Files directories if you did not install VINES Files on the same disk as the base software. The uninstall program does not remove the VINES Files directories unless they were installed under the Banyan default installation directory (\Program Files\Banyan).
Uninstalling the Banyan Enterprise Client
To uninstall StreetTalk for Windows NT software, you must first uninstall the Banyan Enterprise Client. To do this, you must have your Banyan Client Components Suite CD-ROM. Follow this procedure:
1. Insert the Banyan Client Components Suite CD-ROM in the CD-ROM drive.
2. From the Start menu, select Run and enter this command line:
D:\WINNT\Setup.exe -uninstall
D: represents the drive letter of the CD-ROM. If you click Browse to select the program name, you must manually enter the -uninstall switch.
3. Click OK on the Run dialog box.
The procedure stops the Banyan network services and removes the client program group without any intervention.
4. Shut down and restart the server.