## MS BackOffice Unleashed

- System Requirements
  - SNA Server Requirements
    - LAN Network Protocol and Adapter
    - Memory Requirements
    - Hard Disk Requirements
    - SNA Communications Adapter
  - Client Requirements
    - SNA Server Clients for Windows NT
    - SNA Server Clients for Windows 95
    - SNA Server Clients for Windows Version 3.x
    - SNA Server Clients for MS-DOS
    - SNA Server Clients Running OS/2
    - SNA Server Clients on Macintosh Computers
- Planning
  - Filling Out Planning Forms
  - SNA Server Domains
  - Server Role
    - Primary Configuration Server
    - Backup Configuration Server
    - Member Server (No Configuration)
  - Security
  - Auditing
- Installation Procedure
  - Setup
  - Select Client-Server Protocols
  - Select Server Role
  - Install Link Services
  - Configure Link Services
    - DLC 802.2
    - SDLC
    - X.25
    - DFT
  - Finishing SNA Server Installation
  - Using Setup After Installation
    - Removing the SNA Server
    - Changing the SNA Server Role
    - Adding Link Services
    - Removing Link Services
    - Reconfiguring Link Services
    - Changing Client-Server Protocols
- Issues and Cautions
  - Backing Up Configuration Files
  - Server Name Change
  - Automatically Starting the SNA Server from the Control Panel
  - Windows NT Server Configuration
- Configuration Tasks After Setup Is Complete
  - Client Setup
    - Modifying A Client
- Verifying Successful SNA Server Installation
- Summary

#
— 39 —

##
Installing SNA Server

This chapter covers the step by step installation of SNA Server and clients, including the systems requirements and detailed setup and configuration of the DLC 802.2, SDLC, IBM X.25, and DFT link services, and clients on different host operating systems. A step by step guide to verifying a successful SNA Server installation through the use of the DEMO Link Services appears at the end of this chapter.

###
System Requirements

The following sections detail the system requirements for SNA Server and client installation.

####
SNA Server Requirements

The following sections explore the system requirements needed to install the SNA Server version 2.11.

#####
LAN Network Protocol and Adapter

The first requirement is one or more network adapters supported by Windows NT Advanced Server version 3.1 or Windows NT Server version 3.51 installed with support for one or more of the following network protocols:

- Microsoft networking (included with Windows NT)
- NWLink or equivalent IPX/SPX services
- Microsoft TCP/IP or equivalent Win32 Windows Sockets version 1.1
- Banyan Enterprise Client version 5.52 for Windows NT
- Services for Macintosh

#####
Memory Requirements

A minimum of 20M of total system RAM is required. This is 4M more than required by Windows NT Server. This extra memory is recommended to support optimal performance under peak loads.

#####
Hard Disk Requirements

A minimum of 11M free hard-disk space is required to install the SNA Server version 2.11.

#####
SNA Communications Adapter

The following is a partial list of SNA communications adapters supported:

- Any Windows NT NDIS-compliant Token Ring or Ethernet device driver, using Windows NT 802.2 DLC transport protocol
- Attachmate SDLC
- Barr Systems T1-SYNC (for SDLC)
- DCA IRMA (for DFT)
- DCA ISCA (for SDLC and X.25)
- Microgate MGx, Microgate DSA, Microgate USA (for SDLC and X.25)
- IBM SDLC
- IBM MCPA
- IBM MPA/A
- IBM DFT
- IBM 3270 Connection A,B
- IBM 3278/9 Advanced Emulation adapter
- Any driver developed through the SNADIS interface

####
Client Requirements

SNA Server supports clients running under Windows NT Server and Workstation, Windows 95, Windows 3.x, MS-DOS, OS/2, and Macintosh operating systems. The system requirements for each of these operating systems are detailed in this section.

#####
SNA Server Clients for Windows NT

The operating system versions, networking protocols, network adapters, memory, and hard disk requirements for a Windows NT client installation are detailed in this section.

######
Operating System

Operating systems required include Windows NT Advanced Server version 3.1, Windows NT version 3.1, Windows NT Server version 3.51, or Windows NT Workstation version 3.51.

######
LAN Network Protocol And Adapter

Another requirement is one or more network adapters, supported by Windows NT installed with support for one or more of the following network protocols:

- Microsoft networking (included with Windows NT)
- NWLink or equivalent IPX/SPX services
- Microsoft TCP/IP or equivalent Win32 Windows Sockets version 1.1
- Banyan Enterprise Client version 5.52 for Windows NT
- Services for Macintosh

######
Memory Requirements

A minimum of 14M of total system RAM is required. This is 2M more than the minimum required by Windows NT and Windows NT Workstation.

######
Hard Disk Requirements

A minimum of 7M free hard disk space is also required.

#####
SNA Server Clients for Windows 95

The operating system versions, networking protocols, network adapters, memory, and hard disk requirements for a Windows 95 client installation are detailed in this section.

######
Operating System

Operating systems required include Windows 95, Windows NT Server 3.51, or Windows NT Workstation 3.51.

######
LAN Network Protocol And Adapter

Another requirement is a network adapter supported by Windows 95, Windows NT Server version 3.51, or Windows NT Workstation 3.51, installed with support for one or more of the following network protocols:

- Microsoft networking (included with Windows NT and Windows 95)
- NWLink or equivalent IPX/SPX services
- Microsoft TCP/IP or equivalent Win32 Windows Sockets version 1.1
- Banyan Enterprise Client version 5.52

######
Memory Requirements

For Windows NT, a minimum of 14M of total system RAM is required. For Windows 95, a minimum of 8M of total system RAM is required.

######
Hard Disk Requirements

4 MB free hard-disk space.

#####
SNA Server Clients for Windows Version 3.x

The operating system versions, networking protocols, network adapters, memory, and hard disk requirements for a Windows version 3.x client installation are detailed in this section.

######
Operating System

Operating systems required include Windows for Workgroups or Windows 3.x.

######
LAN Network Protocol And Adapter

Another requirement is one or more network adapters supported by Windows for Workgroups or Windows 3.x, installed with support for one or more of the following network protocols:

- The network software included in Windows for Workgroups
- LAN Manager version 2.x
- Novell NetWare (IPX.COM) version 3.10 or later, or any ODI driver
- Microsoft TCP/IP or equivalent Windows Sockets version 1.1
- Banyan VINES version 5.52

######
Memory Requirements

A minimum of 4M of total system RAM is required. The following are the memory requirements of each of these applications:

Client Application | RAM Required
3270 Applet | 525K
5250 Applet | 490K
3270 and 5250 Applet both loaded simultaneously | 830K
Base support for ISV 5250 emulator | 185K
Base support for ISV 3270 emulator | 185K
Base support for APPC, CPI-C, LUA, or CSV application | 185K

The base support does not included the actual memory required by the emulation application.

######
Hard Disk Requirements

A minimum of 4M free hard disk space is also required.

#####
SNA Server Clients for MS-DOS

The operating system versions, networking protocols, network adapters, memory, and hard disk requirements for an MS-DOS client installation are detailed in this section.

######
Operating System

The MS-DOS operating system version 3.2 or later is required.

######
LAN Network Protocol And Adapter

Another requirement is a LAN Manager version 2.x, Novell NetWare (IPX.COM) version 3.10 or later, or Banyan VINES version 5.52 and supported network adapter.

######
Memory Required

A minimum of 640K RAM is required. Actual RAM occupancy is shown in the following table:

Client Application | RAM Required
Base support for IBM PC Support functions | 100K
Base support for ISV 3270 emulator | 50K
Base support for APPC, LUA-RUI, or CSV application | 50K

The base support does not included the actual memory required by the emulation application.

######
Hard Disk Requirements

A minimum of 2.2M free hard disk space is also required.

#####
SNA Server Clients Running OS/2

The operating system versions, networking protocols, network adapters, memory, and hard disk requirements for an OS/2 client installation are detailed in this section.

######
Operating System

An OS/2 operating system version 1.21 or later, with a network adapter installed, is required.

######
Memory Required

A minimum of 8M of total system RAM is recommended.

######
Hard Disk Requirements

A minimum of 1M free hard disk space is also required.

#####
SNA Server Clients on Macintosh Computers

The operating system versions, networking protocols, network adapters, memory, and hard disk requirements for a Macintosh client installation are detailed in this section.

######
Operating System

A System 6.0.2 or later and Finder version 6.0 or later is required (System 7.0 and Finder 7.0 can be used).

######
Networking Protocol

Another requirement is a standard Macintosh platform with AppleTalk access.

######
Other

A Macintosh terminal emulation software is required.

###
Planning

Before beginning the SNA Server installation, a few planning steps should be executed. A set of planning forms, provided with the SNA Server documentation, should be completed to assist in organizing your installation. The SNA Server domain configuration should be determined, and the role of this server should be selected. Other security and auditing issues should also be taken into account before installation. These planning issues are discussed in more detail in this section.

####
Filling Out Planning Forms

In the Microsoft SNA Server Version 2.11 Administration Guide, a set of planning forms are provided. These forms are useful for organizing the information necessary to install and configure SNA Server. Information from the host system administrator, LAN administrator, and client workstations is required to complete the planning forms. The planning forms are also available on the Microsoft Web Site at http://www.microsoft.com/sna/prepform.htm. The following forms are available:

- Server Resources Planning
- Server Information
- Initial Connections Settings
- 802.2 Settings
- SDLC Settings
- X.25 Settings
- Channel Settings
- 3270 RTM Settings
- Users and Groups
- 3270 LUs (Individual)
- 3270 LUs (Ranges)
- 3270 LU Pools
- Local APPC LUs
- Remote APPC LUs
- Mode Properties for LU-LU Pairs
- CPI-C Properties

####
SNA Server Domains

When planning an SNA Server installation, you need to decide whether the enterprise SNA Servers should be centralized in one location or distributed in branch offices. The necessary tools to effectively manage SNA Servers are provided for both configurations. The advantages of the centralized configuration are that all the SNA Servers are located in one place, easing administration. The advantages of the distributed configuration are that it uses smaller domains, which can be easier to configure, and requires smaller servers. A complete discussion of SNA Server Domain Configurations is provided in Chapter 38, "SNA Server Overview."

####
Server Role

The SNA Server can be designated to function in one of three different types of roles. This should be determined before installation begins.

#####
Primary Configuration Server

The Primary SNA Server contains the domain-wide configuration file. This configuration file contains the SNA Server resources for the domain, including SNA servers in the domain, link services, LUs, 3270 users, and so forth. Only one primary server can operate in a domain. The primary server is usually the first SNA Server installed.

#####
Backup Configuration Server

A Backup SNA Server is a server on which the configuration file is replicated by the Primary SNA Server. More than one backup server can be configured in a domain. If the Primary SNA Server cannot function, SNA Server will utilize the backup configuration file. Using the configuration file on the Backup Server, servers and connections can be started and stopped, but the configuration cannot be modified or saved. Up to 49 backup servers can be installed in a single domain.

#####
Member Server (No Configuration)

A Member Server does not have the configuration file or a backup of the configuration file. A Member Server applies the Primary Server’s configuration file as changes are made.

####
Security

To provide the highest level of security for Windows NT and SNA Servers in a domain, access to the SNA Server configuration file must be controlled. To control user access to files, SNA Server should be installed on a Windows NT File System (NTFS) partition. Only through utilizing NTFS can permissions can be assigned on a file-by-file basis. This is the most effective way to control access to the SNA Server configuration file.

Windows NT Server and SNA Server share the same user database. When a change is made to either user database, it is reflected in both. A user must successfully be logged into the Windows NT domain to gain access to SNA Server and its resources. A user or user group must be assigned to an LU to access host system resources.

####
Auditing

The Event Monitor in Windows NT Server enables various SNA Server events to be logged and monitored, creating an effective audit trail. Events to be monitored can be specified, and the date and time they occur will automatically be logged. The Event Viewer can filter out which events to view and specific dates and times. The event audit trail can be an effective security monitoring tool. Careful consideration of which events will be monitored should be taken. Event logging takes a small amount of system resources to accomplish, and if too many events are logged, the event log file can quickly become large.

###
Installation Procedure

Step-by-step procedures to install the SNA Server are detailed in this section, including the configuration of the DLC 802.2, SDLC, IBM X.25, and DFT link services.

####
Setup

The SNA Server Setup application is used to install the SNA Server. Because the SNA Server Setup requires the capability of accessing the Windows NT Registry, you need to be logged in as the Administrator before beginning.

From the File Manager, select the CD from which you are installing SNA Server. Then run the SETUP.BAT file located in the root directory of the SNA Server CD. The SETUP.BAT file will initiate the appropriate installation for the hardware platform you are using. You will need to wait a few moments while your system configuration is determined. As the setup application proceeds, a number of dialog boxes will be displayed.

A Welcome To SNA Server dialog box will be displayed. Click on the Continue button to begin the installation process or click on the Exit button to abort the installation process. You will then be asked to choose your licensing mode: Per-Server or Per-Seat. In the Per-Server licensing mode, each concurrent connection to the SNA Server requires a separate Client Access License. In the Per-Seat licensing mode each computer that accesses the SNA Server requires a separate Client Access License. After specifying the License mode, click on Continue to proceed with the installation. You then must agree to the Client Licensing mode you have selected to continue.

A standard Software Licensing dialog box is displayed. This dialog box is used to enter identifying information for you and your company. Enter your name, company name (optional), and product ID, which is located on the inside back cover of the installation guide. Click on Continue to proceed with the installation. After reviewing the information you have entered, you may click on on the Back button to return to editing your information, or the Ok button to proceed.

The Installation Path dialog is displayed next. The default installation path is C:\SNA. You may edit the installation. If you edit the installation path, be sure to use an empty directory so that the SNA Server will not accidentally write over any files required by another application. Click on the Continue button to proceed.

####
Select Client-Server Protocols

The system is then checked for available client-server networking protocols. If more than one client-server networking protocol is installed on the system, the Select Client/Server Protocols dialog box in Figure 39.1 is displayed; otherwise, the installation will proceed to the next step of selecting the SNA Server Role.

FIGURE 39.1. The Select Client/Server Protocols dialog box displays the available client-server networking protocols that have been automatically detected.

Only the protocols that are not grayed out are installed and available for selection. The protocols that have been detected will automatically be checked. You can select and deselect which protocols you wan the SNA Server to utilize.

> > For peak efficiency, select only one protocol for broadcasts between SNA servers. For peak efficiency in domains where SNA server adapters can use multiple protocols and broadcasts will not be routed over IP routers, for Server Broadcasts, select one (and only one) of the following protocols: IPX/SPX, Banyan VINES, or TCP/IP.

If you do not select the Microsoft Networking (Named Pipes) protocol, you must specify the name of the network domain in which your SNA Server will participate. The Network Domain Name dialog box in Figure 39.2 will be displayed. Enter the domain name and click on Continue to proceed.

FIGURE 39.2. The Network Domain Name dialog box is used to specify the domain in which the SNA Server will participate.

If the TCP/IP networking protocol is selected, the domain name can be specified in three ways:

- The domain name used in the Windows NT domain.
- The host name with the TCP domain name—for example, drwho.gallifrey.com. If this form is used, the Domain Name System (DNS) resolver must be configured to map the name to an IP address.
- The actual IP address—for example, 192.46.12.1.

If the BANYAN Vines protocol is selected, the StreetTalk Group Name dialog box is displayed. SNA Server Setup creates a StreetTalk name by combining information stored on the Banyan VINES network with information you type into the Setup dialog boxes. If you leave the Group Name entry blank, Setup uses the group name of the user currently logged on in the Banyan VINES network. You must ensure that the group name of the user logged on in the Banyan VINES network during installation of the SNA Server is always the same group name, regardless of whether client or server software is being installed.

####
Select Server Role

Once the client-server networking protocols have been selected, the role for the SNA Server must be designated. The Change SNA Server Role dialog box in Figure 39.3 is displayed. The SNA Server roles are described in the Planning And Things To Consider section earlier in this chapter.

FIGURE 39.3. The Change SNA Server Role dialog box designates the configuration role for the SNA Server.

By default, the Primary Configuration Server is selected. Click on the Backup or Member Server option if you want to change the server’s role. An SNA Server can be designated to only one role.

> > When a primary server or backup server is installed, the path of SNAROOT\SYSTEM\CONFIG (where SNAROOT is the installation directory specified) is automatically shared as \\servername\COMCFG. This enables the SNA Server to access the configuration file on the primary or backup servers.
> > To control user access to files, the SNA Server should be installed on a Windows NT File System (NTFS) partition. NTFS will allow permissions to be set on the SNA Server configuration files. If you are installing a primary server or backup server, it is important that NTFS be used. You can exit the SNA Server Setup and run the CONVERT utility to convert FAT or HPFS partitions to NTFS. See your Windows NT Server manuals for more information on the CONVERT utility.

Once the server role is designated, click on Continue to proceed. The Review Settings dialog box is displayed next. Click on the Review button to review and edit your installation directory and server role designations. To install the online documentation, click on the Install On-Line Documentation checkbox. Online documentation will require 14M additional free disk space. Click on continue to proceed with copying the appropriate SNA Server files. Once the application files have been installed, if online documentation was selected to be installed, the On-Line Documentation Destination Path dialog box appears. By default, the online documentation is installed in the help subdirectory of your initial installation path. Click on Continue to proceed with installing the online documentation.

####
Install Link Services

Link service define the protocols used to connect the SNA Server with the communications adapter. The Link Service Installation dialog box in Figure 39.4 displays Available Link Services. You may click on Continue to complete the SNA Server installation without installing any link services. You need to run the SNA Server Setup application to install a link service before connections can be configured.

FIGURE 39.4. The Link Service Installation dialog box displays the list of Available Link Services to install and configure.

Select the desired link service to install and configure from the list of Available Link Services. Click on the Install button to begin the link service configuration. A dialog box appropriate to the type of link service being installed will be displayed for configuration. The defaults can be accepted or modified for your needs. Click on the Continue button to begin copying the appropriate link service support files.

When installing different link service adapters, if more than one adapter is installed in the server, the extras must be configured to work together so that there are no interrupt, port address, or direct memory access (DMA) conflicts. When you install a new adapter in your computer, you may need to study the configuration of the new and old adapters to make sure there are no conflicts.

If the DLC 802.2 link service is selected for installation, the SNA Server Setup application checks to ensure that the DLC networking protocol has been installed through the Windows NT Server setup. The SNA Server Setup will assist you in the installation of the DLC protocol, but to do so it requires that you have the Windows NT Server setup disks available.

If a link service that you want to install is not listed in the Available Link Services list, the new link service can be installed using the link service installation disk. Clicking on the Other button requires that a path be specified for the new link services drivers. Once the new drivers are located, the link service configuration proceeds in a similar manner to any of the Available Link Services procedures.

####
Configure Link Services

Once a link service is selected, it must be configured. An installed and configured link service is required before configuration of the SNA Server can proceed. There are four basic types of link services. A detailed guide to installing and configuring these basic link services follows.

#####
DLC 802.2

To configure a DLC 802.2 link service, follow these steps:

1. Select the 802.2 DLC Link Service from the Available Link Services list. If the DLC protocol has not been installed by the Windows NT Server setup, you will be prompted to do so now. This will require the Windows NT Server Setup disks. Once the DLC protocol has been verified to be installed, the DLC 802.2 Link Service Setup dialog box in Figure 39.5 appears.

   FIGURE 39.5. The DLC 802.2 Link Service Setup dialog box.

2. The default title for the DLC 802.2 Link Service is displayed in the Title edit box. This title can be modified if desired; up to 40 characters can be used to specify the title.
3. The Adapter box is used to select the adapter card being used. The drop-down box displays the list of available adapter cards. Select the desired adapter card to configure for this link service.
4. The Local Service Access Point (SAP) box, contains the local SAP code, which is used in accessing certain services on an 802.2 connection in an SNA Network. The default SAP value for the SNA Server is 4; this number must be divisible by four and ranges from 4 through 252. The SAP value should be verified with the host administrator.
5. Click on the Continue button to copy the necessary Link Service files. Once complete, the Link Service Configuration dialog box in Figure 39.6 is displayed, showing the new Link Service.

   FIGURE 39.6. The Link Service Configuration dialog box, showing the newly configured DLC 802.2 link service.

6. Additional link services can be added by clicking on the Add button. The highlighted Link Service can be reconfigured by clicking on the Configure button or removed by clicking on the Remove button. (When removing a link service a Link Service Removal box will appear; click on Continue to remove the link service.)
7. To normally complete the SNA Server installation, click on the Continue button.

######
Installing SNA Servers On Ethernet LAN With Routers

If the SNA Server will communicate with remote hosts, peers, or downstream systems via routers, the FrameType entry may require adjustment in the Windows NT Registry. FrameType specifies the type of frames the DLC link service sends over the LAN. Thess frame types must match the frame type used by the routers. The FrameType entry is found in the registry at

    HKEY_LOCAL_MACHINE

    SYSTEM

     CurrentControlSet

     Services

     DLCLinkServiceName

     Parameters

     ExtraParameters

     FrameType

The values for FrameType and their corresponding effects are detailed in the following table.

Frame Type Value | Effect
0 | This is the default. Uses the frame type specified for the adapter in the registry entry for the DLC protocol: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DLC\Parameters\AdapterName\UseDixOverEthernet. The default for UseDixOverEthernet is 0, resulting in an 802.3 frame.
1 | Uses the frame type automatically determined by the DLC protocol during XID exchange.
2 | Uses standard 802.3 format.
3 | Uses 802.2 packets prefixed by DIX headers using EtherType value 0x80D5.

#####
SDLC

To configure an SDLC link service, follow these steps:

1. Select the SDLC Link Service you want to install and configure from the list of Available Link Services. Click on the Install button to proceed.
2. If one or more dialog boxes appear, asking you to enter information for IRQ, DMA, and other settings for the specific communications adapter you have selected, complete the dialog boxes and click on the Continue button to proceed. Once these dialog boxes have been completed, the SDLC Link Service Setup dialog box shown in Figure 39.7 will appear.

   FIGURE 39.7. The IBM SDLC Link Service Setup dialog box. The configuration for an IBM SDLC communications adapter is displayed.

3. The default title for the SDLC Link Service is displayed in the Title edit box. This title can be modified if desired; up to 40 characters can be used to specify the title.
4. Depending on the communications adapter selected, the Card Type drop-down box may appear. Select the communication adapter card you will be using from this list.

   > > If you are using an IBM SDLC adapter or an IBM MCPA adapter, and you need to use a transmission speed faster than 9600 baud, you must select half-duplex in the SNA Server Admin configuration. These adapter cards do not have a coprocessor and are unable to handle full-duplex at these higher baud rates.

5. Depending on the SDLC communications adapter you have selected, the Details or Adapter Details button will be visible. Consult the documentation specific to your communications adapter for information regarding changing specific settings for your card. Clicking on the Details or Adapter Details button will display the specific settings.
6. In the Line Type group box, you may select one of four different options for the telecommunications line that will be connected:

   Line Type | Choose If
   Leased | If you are using a leased line, select this option.
   Switched: Server-Stored Number | If the communications adapter has a built-in serial (COM) port to which the synchronous modem attaches, select this option.
   Switched: Modem-Stored Number | If the communications adapter can store a phone number and pass it along to the synchronous modem when the Data Terminal Ready (DTR) is raised, select this option.
   Switched: Manual Dial | If the phone will be manually dialed when prompted by the SNA Server, select this option.

   ######
   Server-Stored Numbers

   If the Switched: Server-Stored Number line type is selected for the SDLC link service being installed, the synchronous modem must be set up so that the following are true:

   - It will not dial when the DTR signal is raised.
   - It will set Clear to Send (CTS) and Data Set Ready (DSR) to on when ready to accept dial commands.
   - It will set DSR to off after accepting a dial command.
   - It will set DSR to on again only when the dialed connection is made.
   - It will change to synchronous mode after the dial-up has completed.
   - It will change back to dial-command mode if Data Terminal Ready (DTR) is dropped and raised again.

   A dialing attempt by the SNA Server will be assumed to have failed if the DSR stays on after the dial string has been sent or the connection time-out expires before DSR comes on to indicate that the call is connected.

7. Click on the Constant RTS checkbox, if Constant Request To Send (RTS) is required. Constant RTS puts the SDLC adapter in a state in which it is constantly ready to send data. This is required if a full-duplex line will be used. It cannot be used in a multidrop configuration. If Constant RTS is not used, the SDLC adapter must raise the RTS signal and wait for the remote end to raise the CTS (Clear To Send) signal, before data can be sent. Keeping the RTS signal raised precludes this wait time.

   > > To achieve higher throughput, select the Constant RTS whenever possible. It is required on a full-duplex line. It cannot be selected in a multidrop configuration.

8. Depending on the SDLC communications adapter selected, other options may be displayed. Provide the necessary information by consulting the reference material provided with the SDLC adapter.
9. The Dialer Settings button may be displayed, depending on the SDLC communications adapter selected. If the Dialer Settings button is clicked the following configuration settings may be provided:
   COM Port: Select the COM port used by the SDLC adapter. If you are adding a new COM port, the Windows NT COM Port configuration dialog box is displayed. The range for the comport is None through 254. The default value is None.
   Baud Rate: Select the transmission baud rate for the SDLC adapter. The range is 75 through 115200, with the default 9600.
   Incoming String: Specify the string to be sent to the modem when an incoming call is detected. If the modem accepts standard AT commands, the default string AT&F&C1&S1&D3&Q1Q1S0=1 will be appropriate under most operating conditions.
   Outgoing String: Specify the string to be sent to the modem when an outgoing call is detected. If the modem accepts standard AT commands, the default string AT&F&C1&S1&D3&Q1Q1S0=0DT will be appropriate under most operating conditions.

   ######
   Modem Command Strings

   When the SNA Server prepares to send a dial string to the modem, it utilizes the outgoing command string configured in the Dialer Settings dialog box. It appends the phone number to be dialed to this string. If the standard AT command set is used, the default outgoing command string is AT&F&C1&S1&D3&Q1Q1S0=0DT. This string will be appropriate under most operating conditions. The components of the command strings are described as follows:

   AT: Standard modem command prefix

   &F: Resets the modem to the factory defaults

   &C1: Causes the modem to track the status of the Carrier Detect (CD) line

   &S1: Causes the modem to raise the Data Set Ready (DSR) line after it has dialed

   &D3: Causes the modem reset when the Data Transmit Ready (DTR) line drops

   &Q1: Causes the modem to come up in command mode and switch to synchronous mode when it has dialed (on some modems, this may be &M1 instead)

   Q1: Disables modem result codes

   S0=0: Disables auto-answer mode

   DT: Causes the number following it to be dialed, using tone dialing (substitute DP for pulse dialing)

   The incoming command string is used when an incoming call is detected. The default incoming command string is AT&F&C1&S1&D3&Q1Q1S0=1. The only difference from the default outgoing command string is the S0=1, which causes the modem to answer the phone after one ring.

10. Click on the Continue button to copy the necessary Link Service files. Once complete, the Link Service Configuration dialog box in Figure 39.8 is displayed, showing the new Link Service.

    FIGURE 39.8. The Link Service Configuration dialog box, showing the newly configured SDLC link service.

11. Additional link services can be added by clicking on the Add button. The highlighted Link Service can be reconfigured by clicking on the Configure button, or removed by clicking on the Remove button. (When removing a link service a Link Service Removal box will appear; click on Continue to remove the link service.)
12. To normally complete the SNA Server installation, click on the Continue button.

#####
X.25

To configure an X.25 link service, follow these steps:

1. Select the X.25 Link Service you want to install and configure from the list of Available Link Services. Click on the Install button to proceed. The X.25 Link Service Setup dialog box will be displayed; if the IBM X.25 link service is selected, the IBM X.25 Link Service Setup dialog box shown in Figure 39.9 will be displayed.

   FIGURE 39.9. The IBM X.25 Link Service Setup dialog box.

2. The default title for the IBM X.25 Link Service is displayed in the Title edit box. This title can be modified if desired; up to 40 characters can be used to specify the title.
3. Depending on the communications adapter selected, the Card Type drop-down box may appear. Select the communication adapter card you will be using from this list.

   > > If you are using an IBM SDLC adapter or an IBM MCPA adapter and you need to use a transmission speed faster than 9600 baud, you must select half-duplex in the SNA Server Admin configuration. These adapter cards do not have a coprocessor, and are unable to handle full-duplex at these higher baud rates.

4. Depending on the X.25 communications adapter you have selected, the Details or Adapter Details button will be visible. Consult the documentation specific to your communications adapter for information regarding changing specific settings for your card. Clicking on the Details or Adapter Details button will display the specific settings.
5. Enter the Local X.25 Address in the corresponding edit box. A Local X.25 Address contains 15 decimal digits, with no spaces separating the digits. The ending 3 digits of the address are used for routing between stations with the same 12-digit address. No default value is provided.
6. Enter the Default L3 Window Size in the corresponding edit box. The default L3 window size specifies the maximum number of packets that can be sent or received before an acknowledgment is required. The window size only applies to a switched virtual circuit (SVC). The range is 1 through 7. The default value is 2.
7. Enter the Default L3 Packet Size in the corresponding edit box. The default L3 packet size is the maximum size of the data packets that can be sent or received. This value can be overridden in the User Data or Facility Data fields in the X.25 Setup dialog box in the SNA Server Admin. Packet sizes allowed are 64, 125, 256, 512. The default value is 128.
8. Enter the L2 Window Size in the corresponding edit box. The L2 window size specifies the number of frames that the SNA Server can send without waiting for acknowledgment. The range is 1 through 7. The default value is 7.
9. Enter the T1 Timeout in tenths of a second in the corresponding edit box. The T1 timeout specifies the amount of time the SNA Server should wait for the receiving station to respond to a transmission before resending. A time greater than needed for relaying frames between the SNA Server and the remote system should be specified. The range is 1 through 100 tenths of a second. The default value is 30.
10. Enter the N2 Retry Limit in the corresponding edit box. The N2 retry limit specifies the number of times to attempt to resend data. The range is 1 through 100. The default value is 10.
11. Select the Accept Reverse Charge checkbox if the SNA Server should accept an incoming call, if a reverse charge (the receiving end is charged for the call) is specified in the call packet. This option is turned off by default.
12. Select the Select Standby checkbox if the modem standby line should be set to on. The standby line (commonly a switched line) is sometimes included on lease line modems. The standby line serves as a backup if the primary leased line fails. This option is turned off by default.
13. Select the Startup Restart checkbox if a restart is necessary every time the link is activated. This option is turned on by default.
14. Select the Incoming Filter checkbox if X.25 addresses should be filtered out if they are not local. This option is turned on by default.
15. Enter the Outgoing SVC channels in the corresponding edit box. The Outgoing SVC is the range of channels on the switched virtual circuit (SVC) that is used for outgoing calls. The range of Outgoing SVC channels must follow the channel number rules listed next, and be greater than any PVC, Incoming SVC, or Two-Way SVC channels specified for this link. No default value is provided.
    When entering channel numbers in the X.25 Link Service Configuration dialog box, remember these rules:
    - Channel numbers must be from 1 through 4096.
    - The format of channel numbers is n - n (0008 - 00012 is a valid entry, for example).
    - For a particular Switched Virtual Circuit (SVC) or Permanent Virtual Circuit (PVC), there is no requirement for the number of channels used, but the total number of channels must be greater than 1 but less than 16.
    - The range of channel numbers must be unique for each type of circuit. There cannot be any overlap of channel numbers.
    - At least an Incoming SVC or Two-Way SVC channel is required to answer incoming calls.
    - If more than one type of channel needs to be configured, channel numbers should be assigned in ascending order. PVCs are not required to start at channel 1, but they must have the lowest value. Outgoing SVCs are not required to end at 4096, but they must have the highest value.
    - Channel ranges must match the X.25 carrier configuration.
16. Enter the Two-Way SVC channels in the corresponding edit box. The Two-Way SVC is the range of channels on the switched virtual (SV) circuit that is used for both incoming and outgoing calls. The range of Two-Way SVC channels must follow the channel number rules listed previously, be greater than any Incoming SVC, and less than any Outgoing SVC channels specified for this link. The default value is 0001 - 0004.
17. Enter the Incoming SVC channels in the corresponding edit box. The Incoming SVC is the range of channels on the switched virtual circuit (SVC) that is used for incoming calls. The range of Incoming SVC channels must follow the channel number rules listed previously, be greater than any PVC, and less than any Two-Way SVC channels specified for this link. No default value is provided.
18. Enter PVC channels in the corresponding edit box. The PVC is the range of channels on the permanent virtual circuit (PVC) used by the server on the X.25 network. The range of PVC channels must follow the channel number rules listed previously and be less than any Incoming SVC, Two-way SVC, or Outgoing SVC channels specified for this link. No default value is provided.
19. Select the communications Data Rate in the corresponding selection box. This specifies the data rate between the modem and communications adapter if applicable. Select Low if low-quality data lines hamper communications.
20. Select the scheme for encoding when transmitting and receiving data. Both the local and remote system must use the same encoding scheme. Select NRC for NonReturn To Zero and NRZI for NonReturn to Zero Inverted.
21. In the Line Type group box, select one of four different options for the telecommunications line that will be connected:
    Leased. If you are using a leased line, select this option.
    Switched: Server-Stored Number.
    If the communications adapter has a built-in serial (COM) port to which the synchronous modem attaches, select this option. See the Server Stored numbers topic under the preceding Configuring the SDLC Link Adapter section for more information.
    Switched: Modem-Stored Number. If the communications adapter can store a phone number and pass it along to the synchronous modem when the Data Terminal Ready (DTR) is raised, select this option.
    Switched: Manual Dial. If the phone will be manually dialed when prompted by the SNA Server, select this option.
22. Depending on the X.25 communications adapter selected, other options may be displayed. Provide the necessary information by consulting the reference material provided with the X.25 adapter.
23. The Dialer Settings button may be displayed, depending on the SDLC communications adapter selected. If the Dialer Settings button is clicked, the following configuration settings may be provided:
    COM Port: Select the COM port used by the SDLC adapter. If you are adding a new COM port, the Windows NT COM Port configuration dialog box is displayed. The range for the comport is None through 254. The default value is None.
    Baud Rate: Select the transmission baud rate for the SDLC adapter. The range is 75 through 115200, with the default 9600.
    Incoming String: Specify the string to be sent to the modem when an incoming call is detected. If the modem accepts standard AT commands, the default string AT&F&C1&S1&D3&Q1Q1S0=1 will be appropriate under most operating conditions. See the Modem Command Strings section in the preceding Configure the SDLC Link Adapter section for more information.
    Outgoing String: Specify the string to be sent to the modem when an outgoing call is detected. If the modem accepts standard AT commands, the default string AT&F&C1&S1&D3&Q1Q1S0=0DT will be appropriate under most operating conditions. See the Modem Command Strings section in the preceding Configure the SDLC Link Adapter section for more information.
24. Click on the Continue button to copy the necessary Link Service files. Once complete, the Link Service Configuration dialog box in Figure 39.10 is displayed, showing the new Link Service.

    FIGURE 39.10. The Link Service Configuration dialog box, showing the newly configured X.25 link service.

25. Additional link services can be added by clicking on the Add button. The highlighted Link Service can be reconfigured by clicking on the Configure button or removed by clicking on the Remove button. (When removing a link service a Link Service Removal box will appear, click on Continue to remove the link service.)
26. To normally complete the SNA Server installation, click on the Continue button.

#####
DFT

To configure a DFT link service, follow these steps:

1. Select the DFT Link Service you want to install and configure from the list of Available Link Services. Click on the Install button to proceed. The DFT Link Service Setup dialog box will be displayed. If the IBM DFTlink service is selected, the IBM DFT Link Service Setup dialog box shown in Figure 39.11 will be displayed.

   FIGURE 39.11. The IBM DFT Link Service Configuration dialog box.

2. The default title for the IBM DFT Link Service is displayed. This title can be modified if desired; up to 40 characters can be used to specify the title by clicking on the Change button.
3. The default base address may be accepted. To change the default base address, click on the Configure button; the Adapter Base Address dialog box in Figure 39.12 will be displayed.
   Enter the new Base Address in the corresponding edit box and click on the Continue button to proceed. The address must be entered as a hexadecimal value, in the range A0000 to FF000.

   FIGURE 39.12. The Adapter Base Address dialog box.

4. To add additional DFT adapter cards, click on the Add button. The Adapter Base Address dialog box in Figure 39.12 will again be displayed. Enter the new base address and click on Continue to save the new adapter address. Up to four adapter cards can be specified.
5. To remove a DFT adapter card, highlight the adapter address you want to remove in the DFT adapter available list and click on the Remove button.
6. Click on the Continue button to copy the necessary Link Service files. Once complete, the Link Service Configuration dialog box in Figure 39.13 is displayed, showing the new Link Service.

   FIGURE 39.13. The Link Service Configuration dialog box, showing the newly configured DFT link service.

7. Additional link services can be added by clicking on the Add button. The highlighted Link Service can be reconfigured by clicking on the Configure button or removed by clicking on the Remove button. (When removing a link service a Link Service Removal box will appear, click on Continue to remove the link service.)
8. To normally complete the SNA Server installation, click on the Continue button.

####
Finishing SNA Server Installation

After the SNA Server Setup is completed, the Finished dialog box in Figure 39.14 will appear. A number of configuration tasks still needs to be accomplished by using the SNA Server Admin application. The Admin application can be launched by clicking on the Admin button, or click on the Exit button to end the SNA Server Setup.

FIGURE 39.14. The Microsoft SNA Server Setup Finished dialog box.

####
Using Setup After Installation

After installation is complete, the Server Role can be changed, link services can be linked or removed, a link service configuration can be modified, client-server protocol selections can be modified, or the SNA Server can be removed by accessing the SNA Server Setup application from the Microsoft SNA Server Program Manager group.

> > Do not use the Network Option of the Windows NT Control Panel to remove Link Services drivers; this may cause unexpected system events. To correct such a situation, remove and reinstall the SNA Server, using SNA Server Setup.

#####
Removing the SNA Server

The SNA Server can be removed at any time. It must be stopped if it is running before it is removed.

To remove the SNA Server, follow these steps:

1. Stop all the SNA Server components.
2. Run the SNA Server Setup application.
3. Click on the Continue button to display the Setup Options dialog box.
4. Click on the Remove button and confirm the removal of the SNA Server.

#####
Changing the SNA Server Role

To change the server role, follow these steps:

1. Run the SNA Server Setup application.
2. Click on the Continue button to display the Setup Options dialog box.
3. Click on the Role button to display the SNA Server role dialog box. See the Server Role section earlier in the chapter for more information on changing the Server Role.

#####
Adding Link Services

To add a Link Service, follow these steps:

1. Run the SNA Server Setup application.
2. Click on the Continue button to display the Setup Options dialog box.
3. Click on the Link button to display the Link Configuration dialog box. See the Configure Link Services section earlier in the chapter for more information on configuring link services.

#####
Removing Link Services

To remove a Link Service, follow these steps:

1. Run the SNA Server Setup application.
2. Click on the Continue button to display the Setup Options dialog box.
3. Click on the Link button to display the Link Configuration dialog box. Highlight the link service to be removed and click on the Remove button. Confirm the Link Service Removal to complete the link removal.

#####
Reconfiguring Link Services

To reconfigure a Link Service, follow these steps:

1. Run the SNA Server Setup application.
2. Click on the Continue button to display the Setup Options dialog box.
3. Click on the Link button to display the Link Configuration dialog box. Highlight the link service to be reconfigured and click on the Reconfigure button. See the Configure Link Services section earlier in the chapter for more information on configuring link services.

#####
Changing Client-Server Protocols

To change client-server protocol selections, follow these steps:

1. Run the SNA Server Setup application.
2. Click on the Continue button to display the Setup Options dialog box.
3. Click on the Protocols button to display the Select Client Server Protocols dialog box. See the Select Client Server Protocols section earlier in the chapter for more information on changing the Client Server Protocols.

###
Issues and Cautions

Once SNA Server installation is complete, there are a few issues and cautions that should be considered. These include backing up your configuration files, what to do if you change the name of your server, how to automatically start the SNA Server at boot up, and how to maximize your Windows NT performance through configuration tuning. These issues are detailed in this section.

####
Backing Up Configuration File s

Once the SNA Server configuration is complete, and whenever a configuration change is made, the SNA Server configuration file should be backed up. The configuration file is stored on the Primary SNA Server. The configuration file COM.CFG is stored in the {SNAROOT}\SYSTEM\CONFIG (where {SNAROOT} is the installation directory specified) directory.

To back up the configuration file, in the SNA Admin application, choose the File menu option, and then choose Backup. All backup configuration files have an extension of SNA.

####
Server Name Change

If the name of the Windows NT Server that the SNA Server is running on is changed, the SNA Server configuration file must be updated to reflect this change. To update the Windows NT Server name, in the SNA Admin application, select File menu option, then Server Properties. After changing the server name, save the updated configuration file.

####
Automatically Starting the SNA Server from the Control Panel

To automatically start the SNA Server when the Windows NT system is started, the SNA Server service must be set to run automatically. Use the Service application to change the SNA Server startup method to Automatic.

####
Windows NT Server Configuration

To optimize performance of the SNA Server, the Windows NT Server should be set to maximize throughput for network applications. This should only be done if the server is not also used as a file server. From the Network applet in Control Panel, select Server from the Installed Network Software list, click on the Configure button, select Maximize Throughput For Network Applications, then Click on Ok to save the new system configuration.

###
Configuration Tasks After Setup Is Complete

This section presents step-by-step procedures for client setup and modification.

####
Client Setup

Before you begin to use the SNA Server, client emulators need to be configured. When installing the client emulators supplied with the SNA Server, you need to supply certain information:

- If the client workstation is in a local (the same domain as the SNA Server) or remote (a domain different from the SNA Server) domain. If the client is in a remote domain, one or two remote SNA Server names must be supplied.
- When installing an MS-DOS, the network card interrupt must be supplied.
- If the client is not using Named Pipes (Microsoft Networking), the domain name must be supplied. If the client is using Banyan VINES, the Banyan StreetTalk group name must be supplied.

Client installation can be performed over the network or by using floppy disks. To perform the client installation over the network, the client installation files should be placed in a shared directory on the server. To make the client installation files available on the network, follow these steps:

1. From the server you want to make the client installation files available from, create and share a directory. See your Windows NT Server documentation for more information on creating and sharing a directory.
2. If your SNA Server installation is on a CD, continue with the next step. If your SNA Server installation disks are floppies, create another subdirectory, in the directory that you just created, for each client you need to install:

   Client OS | Create This Subdirectory
   Windows NT | winnt
   Windows 95 | win95
   Windows 3.x | win3x
   MS-DOS | msdos
   OS/2 | os2

   Place your floppy disk in the appropriate drive. Type the corresponding command for the client you need to install (where d: is replaced with the appropriate floppy drive letter, servername is the name of your server, and sharename is the name of the directory you created in step 1). For each of the installation disks for that client, repeat the process of inserting the disk and typing the command:

   Client OS | Command
   Windows NT | xcopy d: \\servername\sharename\winnt /s /e
   Windows 95 | xcopy d: \\servername\sharename\win95 /s /e
   Windows 3.x | xcopy d: \\servername\sharename\win3x /s /e
   MS-DOS | xcopy d: \\servername\sharename\msdos /s /e
   OS/2 | xcopy d: \\servername\sharename\os2 /s /e

3. If your SNA Server installation disk is on a CD, at the command prompt, type the following command, where d: is replaced with the appropriate CD drive letter, servername is the name of your server, and sharename is the name of the directory you created in step 1:
   xcopy d:\clients \\servername\sharename /s /e

To create floppy installation disks from the SNA Server CD, follow these steps:

1. The correct number of formatted blank disks is required for each client:

   Client OS | Number Of Disks Required
   Windows NT | 3
   Windows 95 | 7
   Windows 3.x | 2
   MS-DOS | 2
   OS/2 | 1

2. Place the SNA Server CD into the CD-ROM drive.
3. From the File Manager or command prompt, change to the CD drive.
4. Change to the \I386\DISKS directory on the CD if you are installing the Windows NT, Windows 3.x, MS-DOS, or OS/2 client.
5. Insert a floppy disk into the appropriate drive.
6. Copy all files and subdirectories from the appropriate directory on the CD to the floppy disk:

   Client OS | Directories To Copy From
   Windows NT | DISK1
   Windows 3.x | WIN3X_1
   MS-DOS | MSDOS_1
   OS/2 | OS2

7. For the following clients, repeat this process until all directories have been copied onto separate floppies:
   Windows NT: DISK2 and DISK3 directories
   Windows 3.x: WIN3X_2 directory
   MS-DOS: MSDOS_2 directory

To install the client applications on a Windows NT computer, follow these steps:

1. Access the shared client installation directory, or place the client installation floppy in the floppy drive. Then run the command d:\setup (if you are installing from a floppy drive) or d:\winnt\setup (if you are installing from a network share), where d: is the drive letter of the appropriate drive. An introductory Setup dialog box will appear.
2. Click on the Continue button to proceed. If you are installing from floppy disks, the Server/Client Selection dialog box will appear; click on the Client button.
3. Accept or modify the default installation path, then click on Continue to proceed.
4. If more than one client-server protocol is detected, select one or several of the checkboxes for Microsoft Networking, Novell Netware, Banyan VINES, and TCP/IP. Unavailable protocols will be grayed out. Otherwise, proceed to step 6.
5. If Microsoft Networking was not selected, the Network Domain Name dialog box will appear. Type the domain name and click on Continue to proceed.
6. If the TCP/IP networking protocol is selected, the domain name can be specified in three different ways:
   - The domain name used in the Windows NT domain.
   - The host name with the TCP domain name—for example, drwho.gallifrey.com. If this form is used, the Domain Name System (DNS) resolver must be configured to map the name to an IP address.
   - The actual IP address—for example, 192.46.12.1.
7. If the BANYAN Vines protocol is selected, the StreetTalk Group Name dialog box is displayed. SNA Client Setup creates a StreetTalk name by combining information stored on the Banyan VINES network with information you type into the Setup dialog boxes. If you leave the Group Name entry blank, Setup uses the group name of the user currently logged on in the Banyan VINES network. You must ensure that the group name of the user logged on in the Banyan VINES network during installation of the SNA Server is always the same group name, regardless of whether client or server software is being installed.
8. Specify the client mode:
   Local: If the client is located in the same network domain as the Primary SNA Server (the server that contains the configuration file), click on the Continue button.
   Remote: If the client is not located in the same domain as the Primary SNA Server, click on the Remote button and click on the Continue button. In the Remote SNA Server Names dialog box, type the name of the Primary SNA Server in the Primary edit box. Optionally, type the name of a Backup SNA Server in the Backup edit box. Once the client is connected to an SNA Server, it automatically learns the names of all the other servers in the domain. Click on Continue to proceed.
   The Optional Administration Program dialog box will be displayed.
9. If you don’t want to install the SNA Server Admin application, click on the Continue button. To install the SNA Server Admin application, select the Install Administration Program checkbox. Click on Continue to proceed.
10. The Review Settings dialog box will appear. Click on the Review button to review the configuration or the Continue button to begin file installation. If you are installing from floppy disks, insert the appropriate floppy disks as required.
11. When the Client Setup Finished dialog box appears, click on the Exit button to end.

To install the client applications on a Windows 95 computer, follow these steps:

1. Access the shared client installation directory, or place the client installation floppy in the floppy drive. Then run the command d:\setup (if you are installing from a floppy drive) or d:\winnt\setup (if you are installing from a network share), where d: is the drive letter of the appropriate drive. An introductory Setup dialog box will appear.
2. Click on the Continue button to proceed.
3. In the Name and Organization Information dialog box, enter your name and organization name. Click on Ok to proceed, and Ok again to confirm your name and organization name.
4. Click on Continue to accept the default folder for installation, or click on Change Folder to select a new folder for installation. Click on Ok to proceed.
5. Click on the Complete button to install all client components and applications, or click on the Customized button to select which components and applications you want to install. If you select Customized, place a checkmark by the components and applications you want to install, and then click on Continue to proceed.
6. Enter the name of the Program Group you want the applications to be installed into, or accept the default Program Group name.
7. Click on Yes to agree to the Licensing Agreement.
8. If more than one client-server protocol is detected, select one or several of the checkboxes for Microsoft Networking, Novell Netware, Banyan VINES, and TCP/IP. Unavailable protocols will be grayed out. Otherwise, proceed to step 10.
9. If Microsoft Networking was not selected, the Network Domain Name dialog box will appear. Type the domain name and click on Continue to proceed.
   If the TCP/IP networking protocol is selected, the domain name can be specified in three different ways:
   - The domain name used in the Windows NT domain.
   - The host name with the TCP domain name—for example, drwho.gallifrey.com. If this form is used, the Domain Name System (DNS) resolver must be configured to map the name to an IP address.
   - The actual IP address—for example, 192.46.12.1.
10. If the BANYAN Vines protocol is selected, the StreetTalk Group Name dialog box is displayed. SNA Server Setup creates a StreetTalk name by combining information stored on the Banyan VINES network with information you type into the Setup dialog boxes. If you leave the Group Name entry blank, Setup uses the group name of the user currently logged on in the Banyan VINES network. You must ensure that the group name of the user logged on in the Banyan VINES network during installation of the SNA Server is always the same group name, regardless of whether client or server software is being installed.
11. Specify the client mode:
    Local: If the client is located in the same network domain as the Primary SNA Server (the server that contains the configuration file), click on the Continue button.
    Remote: If the client is not located in the same domain as the Primary SNA Server, click on the Remote button and click on the Continue button. In the Remote SNA Server Names dialog box, type the name of the Primary SNA Server in the Primary edit box. Optionally, type the name of a Backup SNA Server in the Backup edit box. Once the client is connected to an SNA Server, it automatically learns the names of all the other servers in the domain. Click on Continue to proceed.
12. When the Windows 95 Client for the SNA Server Setup dialog box appears, click on the Ok button to end.

To install the client applications on a Windows 3.x computer, follow these steps:

1. Access the shared client installation directory, or place the client installation floppy in the floppy drive. Then run the command d:\setup (if you are installing from a floppy drive) or d:\winnt\setup (if you are installing from a network share), where d: is the drive letter of the appropriate drive. An introductory Setup dialog box will appear.
2. Accept or modify the default installation path, then click on Continue to proceed.
3. If more than one client-server protocol is detected, select one or several of the checkboxes for Microsoft Networking, Novell Netware, Banyan VINES, and TCP/IP. Unavailable protocols will be grayed out. Otherwise, proceed to step 6.
4. If Microsoft Networking was not selected, the Network Domain Name dialog box will appear. Type the domain name and click on Continue to proceed.
   If the TCP/IP networking protocol is selected, the domain name can be specified in three different ways:
   - The domain name used in the Windows NT domain.
   - The host name with the TCP domain name—for example, drwho.gallifrey.com. If this form is used, the Domain Name System (DNS) resolver must be configured to map the name to an IP address.
   - The actual IP address—for example, 192.46.12.1.
5. If the BANYAN Vines protocol is selected, the StreetTalk Group Name dialog box is displayed. SNA Server Setup creates a StreetTalk name by combining information stored on the Banyan VINES network with information you type into the Setup dialog boxes. If you leave the Group Name entry blank, Setup uses the group name of the user currently logged on in the Banyan VINES network. You must ensure that the group name of the user logged on in the Banyan VINES network during installation of the SNA Server is always the same group name, regardless of whether client or server software is being installed.
6. Specify the client mode:
   Local: If the client is located in the same network domain as the Primary SNA Server (the server that contains the configuration file), click on the Continue button.
   Remote: If the client is not located in the same domain as the Primary SNA Server, click on the Remote button and click on the Continue button. In the Remote SNA Server Names dialog box, type the name of the Primary SNA Server in the Primary edit box. Optionally, type the name of a Backup SNA Server in the Backup edit box. Once the client is connected to an SNA Server, it automatically learns the names of all the other servers in the domain. Click on Continue to proceed.
7. Click on the Continue button to begin file installation. If you are installing from floppy disks, insert the appropriate floppy disks as required.
8. When the Client Setup Finished dialog box appears, click on the Exit button to end.

To install the client applications on an MS-DOS computer, follow these steps:

1. Access the shared client installation directory, or place the client installation floppy in the floppy drive. Then run the command d:\setup (if you are installing from a floppy drive) or d:\winnt\setup (if you are installing from a network share), where d: is the drive letter of the appropriate drive. An introductory screen will appear.
2. From the introductory screen, press Enter to proceed.
3. Accept or modify the Home Directory path and press Enter to proceed.
4. If more than one client-server protocol is detected, select one or several of the checkboxes for Microsoft Networking, Novell Netware, and Banyan VINES. Otherwise, proceed to step 6.
5. If the BANYAN Vines protocol is selected, the StreetTalk Group Name dialog box is displayed. SNA Server Setup creates a StreetTalk name by combining information stored on the Banyan VINES network with information you type into the Setup dialog boxes. If you leave the Group Name entry blank, Setup uses the group name of the user currently logged on in the Banyan VINES network. You must ensure that the group name of the user logged on in the Banyan VINES network during installation of the SNA Server is always the same group name, regardless of whether client or server software is being installed.
6. Specify the location of the SNA servers in the domain:
   No Remote Operation: If this client is located in the same network domain as the Primary SNA server, select No Remote Operation, and press Enter to proceed.
   Remote Operation: If this client is not located in the same domain as the Primary SNA server, select Remote Operation and press Enter. In the Primary Remote Server screen, enter the name of the first SNA Server the client should attempt to connect to and press Enter to proceed. Optionally, in the Backup Remote Server Name screen, type the name of the second SNA server that the client should attempt to connect to. Once a connection to a server is established, the client learns all the other servers in the domain. Press Enter to proceed.
7. The Operating Environment screen appears next. To install the MS-DOS client, press Enter. To install the MS-DOS client for a Windows 3.x system, select the MS-DOS Client on a Windows 3.x system option and press Enter to proceed. An MS-DOS–based client can run as an MS-DOS application or as a character application under Windows 3.x. If Windows 3.x Enhanced Mode is running, the Background option must be enabled.
8. The LAN Adapter Interrupt Level screen is displayed. Select the correct interrupt value from the available list.
9. The Number of SNA Servers screen is displayed. Modify or accept the number of SNA Servers. Connecting to fewer servers reduces memory utilization.
10. The Backup Extension screen is displayed. Specify the file extension to be used when the SNA Server makes backup copies of AUTOEXEC.BAT and of any other INI files that may be changed. Press Enter to accept the default extension OLD or correct the extension and press Enter.
11. The Confirm Setup Execution screen is displayed. To review your selections, press Enter; otherwise, select Execute Setup and press Enter to proceed with file installation.
12. When file installation is complete, the Setup Completed Successfully screen appears; press Enter to end the installation.
13. Reboot your computer to complete the installation.

> > If you are using a 5250 emulator on an APPC network, you may be required to install the SNA Server Router to allow the client to communicate through the SNA Server (using IPX/SPX, NetBEUI, or any other LAN/WAN protocol) instead of directly with the AS/400 (using DFT).

#####
Modifying A Client

Once a client has been installed, you may need to modify setup options. For example, you may need to change the server the client tries to connect to first, or change the client operation from local to remote. Run the Setup application accordingly for the client platform. The Setup application first determines whether any components are already installed. You will be walked through the installation process as usual, and will be able to make any necessary changes.

###
Verifying Successful SNA Server Installation

The SNA Server provides the capability of setting up a demonstration link, to test and evaluate the SNA Server without the need for a live host or a specialized communications adapter. The demo link setup can also be used to verify a successful SNA Server installation. To install a 3270 Continuous Demo Link, follow these steps.

1. Using the steps outlined in the Using Setup After Installation section, install a new Link Service. The Link Service Configuration dialog box will be displayed. Click on Add to install a new link service.
2. From the Link Service Installation dialog box (shown in Figure 39.15), select the DEMO SDLC Link Service link and click on Install to install and configure this link.

   FIGURE 39.15. The Link Service Configuration dialog box.

3. The DEMO SDLC Link Service Setup dialog box in Figure 39.16 will be displayed. Click on Add to install an additional link. Accept the default Service Title and make sure the script file 3270 Continuous Demo is selected in the script file combobox. This script will emulate the 3270 Flash test application. The Flash application continuously sends screens of data to the 3270 terminal emulator. Click on Continue to proceed with the Demo Link installation.

   FIGURE 39.16. The DEMO SDLC Link Service Setup dialog box.

4. The Link Service Installation dialog box will again be displayed; click on Continue, and click on Continue again to complete the Link Service setup.
5. Click on the Admin button or click on the Exit button, and from the Program Manager, select and run the SNA Server Admin application. The SNA Server Admin application in Figure 39.17 will be displayed.

   FIGURE 39.17. The SNA Server Admin Application.

6. Select the Servers and Connections window.
7. Select the SDLC1 service.
8. Select Services, then Properties.
9. The Connection Properties dialog box in Figure 39.18 will be displayed. The Link Service should be SnaDemo1, the Remote end should be Host System, and Activation should be On Demand.

   FIGURE 39.18. The Connection Properties dialog box.

10. Click on the Setup button to display the SDLC Setup dialog box. Click on Ok to close the SDLC Setup dialog box (these steps must be performed to configure the Demo Link) correctly.
11. Click on Ok to close the Connection Properties dialog box.
12. Select the Servers and Connections windows again. Select the Services, Assign LUs menu items. You should see the Insert LU dialog box in Figure 39.19.

    FIGURE 39.19. The Insert LU dialog box.

13. Select 3270 as the New Logical Unit. Click on Ok to proceed.
14. The New 3270 LU Properties dialog box in Figure 39.20 will be displayed.

    FIGURE 39.20. The New 3270 LU Properties dialog box.

15. The LU Number must be 2. Enter FLASH for the LU Name. Select Display for the LU Type. Select Model 2 as the Display Model type. Click on Ok to proceed.
16. Select the Users and Groups window.
17. Select the Users, New User menu items. The Add Users and Groups dialog box in Figure 39.21 will be displayed.

    FIGURE 39.21. The Add Users and Groups dialog box.

18. Select a user or group of users to assign rights to host LUs from this SNA Server—for example, select Everyone. Click on the Add button to Add the new user or group to the Add Names list. Click on Ok to save your selection and proceed.
19. Highlight the new user or group and select the Users, Assign LUs menu items. The Assign User/LU Pool Sessions dialog box in Figure 39.22 is displayed.

    FIGURE 39.22. The Assign User LU/Pool Sessions dialog box.

20. Select the available LU to assign to the selected user. Click on Ok to close the Assign User/LU Pool Sessions dialog box.
21. Select the Services and Connections window. Select the Service, Start Services menu items.
22. Start the 3270 Applet from the Microsoft SNA Server group window.
23. Select the Session, Session Configuration menu items. Choose the FLASH session and click on Ok to proceed.
24. Select the Session, Connect menu items. The host SSCP screen should appear. Type VM and press Enter. A host login screen will appear. Type USER for the userid and press the Tab key; type PASS for the password and press the Enter key. A VM ready prompt will be displayed; type FLASH and press Enter to begin the 3270 Continuous Demo.
25. Select the Session, Disconnect menu items to end the demo.

###
Summary

This chapter covered the planning and steps necessary to install the SNA Server and clients on multiple platforms. Once the SNA Server Setup is complete, the Admin application is used to configure Link Services, Connections, LUs and LU Pools, and Users. The Admin application is also used in the day-to-day management of the SNA Server.