SNA Server KnowledgeBase Articles (current as of 6/15/95)

This helpfile contains many of the SNA Server Microsoft KnowledgeBase articles which appear in Microsoft TechNet.  SNA Server 2.0 problems which have been fixed in 2.1 are not included. Some articles may not reflect the new features implemented in SNA Server 2.11.

Sample configurations

Common questions/problems

Operational issues

SNA Server or link activation problems

AS/400 or LU6.2 connection problems

3270 or 5250 session activation problems

SNA client problems

Third party issues

Programming issues

SNA Server internals

Server internals

Client internals

Tracing

Miscellaneous


Sample configurations

SNA Server sample VTAM/CICS parameters for independent LU6.2

Multiple connections to the same host over 802.2

Configuring SNA Server through a 3174 gateway via 802.2

Configuring for LU6.2 through a 3174 APPN Network Node

Configuring SNA Server to talk to AS/400 over 802.2

Configuring SNA Server to talk to AS/400 over SDLC

Connecting to a remote AS/400 connected via an APPN network

Multiple connections to same AS/400 are not supported


Common questions/problems

NOTE: All SNA Server 2.11 product documentation is available in helpfile format on the 2.11 CD-ROM, by running winhelp <2.11-cdrom>\sdk\help\sna.hlp.

Operational issues

SNA Server or link activation problems

AS/400 or LU6.2 connection problems

3270 or 5250 session activation problems

SNA client problems


Common problems/issues
Common questions/problems: Operational issues

Automatically starting SNA Server through Control Panel

SNA Server load balancing and hot backup

SNA Server and 3287 Host Print Emulation

Host printer emulation data flow through SNA Server

Running SNA Server Win16, MS-DOS and OS/2 apps on Windows NT

Changing the Windows NT computername on an SNA Server

Configuring a Windows NT user as an SNA Server Administrator

Maximizing IND$FILE 3270 host file transfer throughput

SNA Server doesn't include bundled support for HLLAPI

Different ways a Macintosh can connect through SNA Server

SNA Server connection to System/36 or /38 with "Coexistence PRPQ"


Common questions/problems: SNA Server or link activation problems
Common questions/problems: SNA Server or link activation

802.2 connection fails on SNA Server with two Token Ring NICs

Using SNA Server with SDLC multidrop leased lines

SDLC link failure due to invalid XID (Event 182)

SNA Server Error 23, SDLC outage code "2D"

Connecting SNA Server over X.25/QLLC

SNA Server X.25 PVC incoming calls

SNA Server service stays Inactive when started

SNA Server connection stays Inactive


Common questions/problems: AS/400 or LU6.2 connection activation

SNA Server 5250 session fails to OS/400 V3R1

Local and Remote Control Point Names can't be the same

SNA Server configurations that produce XID rejections

Event ID 49: Node ID from remote computer was rejected

AS/400 connection active, but no LU6.2 sessions negotiated

Ways to increase the number of SNA Server sessions to an AS/400

Auto-recovery of LU6.2 sessions when partner is restarted

SNA Server Event 18 may include sense data = 00320008

IBM 3174 Support C5.0 causes negative bind response

VTAM 3.4.2 PTF solves LU6.2 problem through 3172


Common questions/problems: 3270 or 5250 session activation

Running IBM PC Support on SNA Server

3270 LU's show Available, but no signon screen appears

Problems running SNA Server 5250 applet (autoconnect enabled)

Session error 2574 in 3270 applet


Common questions/problems: SNA Client

Automating the SNA Server Win 3.x client login process

SNA Server error 629 or 546 when using MS network client interface

WFW 3.11 error 546 connecting to SNA Server on Windows NT 3.5

SNA Server Windows client memory tuning

SNA Server Windows NT client loses session to server

Forcing Windows NT clients to use Non-Named Pipe LAN Transport

Running the SNA Win 3.x client on Windows NT causes 100% CPU

SNA Server Win 3.x client setup: No network installed

Connecting over TCP/IP to SNA Server with multiple net cards

Running IBM PC Support/400 on SNA Server

SNA Server Vines PC-based service doesn't get created

SNA Server Banyan client connection problem across TR Bridge

Novell WLIBSOCK.DLL dated 8/30/94 causes mailslot error 10066

Error 2139 - Could not create mailslot w/SNA Server client


Third party issues

Emulator issues

Wall Data Rumba 3270 user names appear as "Unknown" in SNA Admin

Wall Data Rumba for the AS/400 GP-faults in 5250 session

Using IBM PC/3270 Version 4.0 on SNA Server

DCA Irma for Macintosh client does not understand master domain model

Link service issues

Eicon WAN Services V3R2 problems with SNA Server

Attachmate SDLC support for SNA Server

Attachmate SDLC connection doesn't activate


Programming issues

CPIC/APPC program may hang opening a dependent APPC session

RECEIVE_ALLOCATE may return AP_UNEXPECTED_DOS_ERROR (F011)


SNA Server internals

Server internals

Client internals

Tracing


SNA Server internals
Server internals

How SNA Server communicates with other SNA Servers

SNA Server installation guidelines: on DC or Member server

SNA Server 802.2 connection activation process

SNA Server and 802.2 connection timers (t1, t2, ti)

TCP/IP socket numbers used by SNA Server

SNA Server password encryption support for LU6.2 sessions


SNA client internals
Client internals

Comparing SNA client TCP/IP named pipes vs sockets

Limits on OtherServers parameter in SNA Server

SNA client files for Windows 3.x and terminal emulators

Configuring Windows 3.x clients to use TCP/IP with SNA Server

Operator Information Area indicators for 3270 applet


SNA Server tracing

Enabling SNA Server Windows 3.x client traces

Remotely administering SNA Server tracing

"Messages Suppressed" in SDLC Level 2 tracing


Miscellaneous

SNA Server MCP Certification Exam

NCP Requirements for LU6.2

SNA Server client setup over Netware


Q107119: Local and Remote Control Point Names can't be the same.

Local and Remote Control Point Names Can't be the Same        [winnt]

ID: Q107119    CREATED: 15-NOV-1993   MODIFIED: 11-OCT-1994

2.00

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

----------------------------------------------------------------------

SUMMARY

=======

If you have difficulty making a connection with a link, confirm that the local and remote Control Point names are not the same. A common cause of connection difficulties with a new configuration is that the same names have been specified for both local and remote Control Point and Network names.

MORE INFORMATION

================

In SNA Server Admin, the local Control Point and Network names are set in a different dialog box than the remote Control Point and Network names. The local Control Point Name and Network Name apply to all connections, and are set in the Server Properties dialog box. The remote Control Point Name and Network Name for a particular connection are set in the Connection Properties dialog box.

 - The local network name and control point name (configured in the Server dialog) identify the SNA Server node to the SNA network.

 - The remote network name and remote control point name (configured in the connection dialog) identify the remote node name that you want to connect to.

 - These should never be set to the same value. If they are, the connection will show up as "Pending" and never activate (note that there are other causes for a Pending status besides this possible configuration problem).

To verify duplicate names use SNA Admin and do the following:

1. In the Servers and Connections window, choose Services.

2. Select Properties.

3. Make a note of the SNA Server Network Control Point Name.

If any other link service is using these names, change them so they are not the same as the Network Control Point Name.

Additional reference words: prodsna 2.00

KBCategory: kbnetwork

KBSubcategory: ntnetserv


Q107121: Operator Information Area indicators for 3270

Operator Information Area Indicators for 3270                 [winnt]

ID: Q107121    CREATED: 15-NOV-1993   MODIFIED: 09-DEC-1994

2.00

WINDOWS

PUBLIC | kbtool

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

----------------------------------------------------------------------

The Operator Information Area (OIA)is used to display the status of a 3270 screen session. The OIA is the last (bottom) line displayed in the terminal window of the 3270 session. Except for the initial three positions (system connection indicators), status line indicators only appear when they apply.

The following tables describe the OIA and explain each indicator. In the table, position refers to the column(s) that a specific indicator occupies on the OIA, where the left-most column of the OIA is position 1. In addition, the "female" symbol used for certain system connection and input inhibited indicators cannot be displayed in this table. In its place is the "^" symbol.

OIA INDICATOR (POSITION)

========================

Symbol     Meaning

--------------------------------------------------------------------------

System Connection (position 1):

Does not apply to the 3270 Applet.

System Connection (position 2):

B          Connection uses an SNA protocol.

A          Connection uses a non-SNA protocol.

System Connection (position 3):

b          Connected to a host application (LU-LU session).

^          Connected to host system services (SSCP-LU session).

?          Session is established, but is not connected to any host program

           (unknown).

Session ID (positions 4 - 7):

aaaa       First four characters of your configured long name session ID.

Input Inhibited messages (keyboard locked) (positions 9 - 17):

X COMMnnn  Communications error. See Communications Status (positions 19 - 26).

X MACHnnn  Computer check error.

X PROGnnn  Program check error. See Communications Status (positions 19   26).

X SYSTEM   Keyboard input is being processed by the host. Wait for the message to clear or press RESET.

X[]        The host requires more time to process your request. Wait for the indicator to clear or press RESET.

X -f       Function is not supported. Press RESET, and select a valid function.

X^>        More data was typed than the field allows or can accept. Press RESET, and re-enter the data.

X <-^->    Protected field; you cannot type data. Press RESET, and move the cursor to an unprotected field.

X -f^X     Function is not authorized. Press RESET, and select a valid function.

X^+?       Invalid accent/character combination typed. The accent is displayed in position 12. Press RESET, and type a valid combination.

Communications Status (positions 19 - 26):

COMM500    All the link services configured for use by the connection were inactive.

COMM504    Communications are not established with the host. This message disappears as soon as communication is established with the host. If this message does not disappear, check to ensure proper settings of the host network address, local node ID, or local SAP.

COMM505    The host terminated the connection used by your 3270 session.

COMM510    The host has deactivated the communications link. Report the message to your system administrator.

COMM518    A segment was out of sequence. Contact your system administrator.

COMM695    A communications error occurred.

COMM5nn    The communications link is still being established; the keyboard is locked. Wait for the message to clear; also check Input Inhibited messages.

PROG703    A session control, data flow control, or network control command is not supported. Press RESET, and try the operation again.

PROG705    A sequence number error has occurred. Press RESET, and try the operation again.

PROG706    A chaining error has occurred. Press RESET, and try the operation again.

PROG707    A bracket state error has occurred. Press RESET, and try the operation again.

PROG708    A data traffic reset state exists. Press RESET, and try the operation again.

PROG717    The support level requested is not valid. Press RESET, and try the operation again.

PROG723    The LU type requested is not valid. Press RESET, and try the operation again.

PROG724    The screen size requested is not valid. Press RESET, and try the operation again.

Screen Session LU Address (positions 79 - 80):

nn         The LU address of the currently displayed 3270 screen session.

ERROR 83: The LU selected is not valid for the logged on user. There is a configuration problem if this appears, because the emulator only presents the user with LUs they are allowed to use. Verify the user can use this LU.

ERROR 85: The primary reason for this error is the specific LU requested is already in use.

ERROR 87: There are several possibilities for this error:

    - All the LUs in the Pool requested are in use and will not be available until someone logs off.

    - One or more servers or connections are inactive, and need to be started before all the LUs in the Pool are available.

REFERENCES

==========

Microsoft SNA Server "3270/5250 Applet User's Guide," Appendix

Additional reference words: prodsna 2.00

KBCategory: kbtool

KBSubcategory: ntutil


Q107122: SDLC link failure due to Invalid XID

SDLC Link Failure Due to Invalid XIDs                         [winnt]

ID: Q107122    CREATED: 15-NOV-1993   MODIFIED: 11-OCT-1994

2.00

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

----------------------------------------------------------------------

SUMMARY

=======

If an invalid XID or an XID already in use is detected by the host when a dial-up (switched) SDLC connection is being established, the following error will be recorded in the Event Log under Application. The Event Detail will report the source SNA IBM SDLC Link. The description might read like this:

   Event: 182

   Connection failure, code=11

    Cause Data           = 3601 3401 3302 f035

    Link Role           = 00

    Remote Node Type      = 00

CAUSE

=====

Cause data is a list of the failure causes from the Failure subvector in the alert. Link role and remote node type are as described in the Link Connections Subsystem Configuration Data subvector in the alert. A connection failure can be due to a station outage, rather than a link outage. If it is due to a station outage--which can be recognized by outage code values of X'80' or higher--then message #183 will also be logged.

If this occurs and there are no other configuration issues that could be causing the link service to fail, this is more than likely the cause of the failure.

The SNA Server Reference Guide (Connection failure, code=11) corresponds to "Data Set Ready (DSR) failure". This occurs when the host drops the link when the Local Node ID (XID) sent by SNA Server is not recognized or not is use.

RESOLUTION

==========

Change the XID to a known XID, or an XID that is confirmed not to be in use. You can do this by doing the following:

1. From SNA Server Admin, select the link service you want to change.

2. Choose Services, and then choose Properties.

3. In the Connection Properties dialog box, choose Setup.

4. Change the Local Node ID by choosing the OK button, and then choosing the OK button again.

5. Save this configuration, and then restart SNA Server.

Additional reference words: prodsna 2.00

KBCategory: kbnetwork

KBSubcategory: ntnetserv


Q120036: SNA Server sample VTAM/CICS parameters for independent LU6.2

SNA Server Sample VTAM/CICS Parameters for Independent LU6.2  [winnt]

ID: Q120036    CREATED: 31-AUG-1994   MODIFIED: 11-MAY-1995

2.00

WINDOWS

PUBLIC | kbnetwork

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0, 2.1, 2.11

-----------------------------------------------------------------------

SUMMARY

=======

This article includes the following sections:

 - Sample VTAM and CICS Parameters for Independent LU 6.2

 - Sample VTAM Parameters for Use with LU 6.2

Sample VTAM and CICS Parameters for Independent LU 6.2.

The following sections show some sample VTAM and CICS configurations for independent LU 6.2. For more information, see the appropriate IBM manuals, or access the IBM APPC forum on CompuServe; to do this, at any ! prompt, type go appc. One document available through the IBM APPC forum is MPCONT.ZIP, a multi-platform LU 6.2 configuration guide containing information about CICS and VTAM.

NOTE: Information included in this article can also be found in Chapter 5 of the SNA Server 2.1 Admin Guide, pg 111-116

Sample VTAM Parameters for Use with LU 6.2.

The lists in this section show sample VTAM parameters that might be used for communication using independent LU 6.2. The underlined values correspond to values specified in SNA Server Admin.

SERVER1  PU    ADDR=09,                                X

               IDBLK=05D,                              X

               IDNUM=11111,                            X

               CPNAME=SNASERV,                         X

               ISTATUS=ACTIVE                          X

               DLOGMOD=D4C32782,                       X

               MODETAB=ISTINCLM,                       X

               MAXDATA=521,                            X

               MAXPATH=1,                              X

               PUTYPE=2,                               X

               SSCPFN=USSSCS,                          X

               MAXOUT=7,                               X

               PASSLIM=4,                              X

               PACING=0,                               X

               DISCNT=NO,                              X

               USSTAB=USSTAB

TRPATH    PATH DIALNO=2223331234567890,                X

               GRPNM=AAA01,                            X

               GID=2

LOCLU1    LU   LOCADDR=0,                              X

               ISTATUS=ACTIVE,DLOGMOD=APPCMODE,        X

               RESSCB=25,USSTAB=USSTAB,PACING=0,       X

               VPACING=0

Note that in the preceding example, the LOCADDR= value for the LOCLU1 is 0. This is the correct value to use with independent LU 6.2 Lus. The following table shows the SNA Server parameters and values that correspond to the preceding sample VTAM parameters:

SNA Server Parameter           Sample value    VTAM parameter

----------------------------------------------------------------------

Connection: Local Node ID,     05D             IDBLK in PU definition

first three digits

(block number)

Connection: Local Node ID,     11111           IDNUM in PU definition

last five digits

(block number)

Server: Control Point Name     SNASERV         CPNAME in PU definition

Connection: Max BTU Length     521             MAXDATA in the PU

                                               definition

Local APPC LU: LU Name         LOCLU1          Name in LU definition

LU 6.2 Partner LUs: Mode       APPCMODE        DLOGMOD in the LU

                                               definition

NOTE: The network name corresponds with the VTAM domain name (NETID).

The following list shows mode table entries for use with independent LU 6.2 Lus.

*********************************************************

*           LOGMODE TABLE ENTRY FOR RESOURCES           *

*          CAPABLE OF ACTING AS LU 6.2 DEVICES          *

*********************************************************

SNASVCMG MODEENT LOGMODE=SNASVCMG,FMPROF=X'13',          X

               TSPROF=X'07',PRIPROT=X'B0',               X

               SECPROT=X'B0',COMPROT=X'D0B1',            X

               RUSIZES=X'8585',ENCR=B'0000',             X

               PSERVIC=X'060200000000000000000300'

APPCMODE MODEENT LOGMODE=APPCMODE,                       X

               TYPE=0,                                   X

               FMPROF=X'13',                             X

               TSPROF=X'07',                             X

               PRIPROT=X'B0',                            X

               SECPROT=X'B0',                            X

               COMPROT=X'50B1',                          X

               PSNDPAC=X'03',                            X

               SRCVPAC=X'03',                            X

               RUSIZES=X'8585',                          X

               PSERVIC=X'060200000000000000002F00'

In the preceding list, the mode named APPCMODE is an example of a mode configured for use with LU 6.2. (Note that the mode named SNASVCMG is included in SNA Server, since it is required for parallel session support; it does not need to be configured in SNA Server

Admin.)

Sample CICS Configuration Screens for Use with LU 6.2

The following series of screens show how CICS could be configured for independent LU 6.2 through VTAM. In the first screen, the underlined values correspond to values specified in SNA Server Admin.

_________________________________________________________________

OVERTYPE TO MODIFY           CICS RELEASE = 0330

 CEDA  ALter

  Sessions       : LOCLU1

  Group          : VER3AAAA

  DEscription  ==> VERSION 3 LU 6.2 SESSION ENTRY

 SESSION IDENTIFIERS

  Connection   ==> CON1

  SESSName     ==>

  NETnameq     ==>

  MOdename     ==> APPCMODE

 SESSION PROPERTIES

  Protocol     ==> Appc                Appc | Lu61

  MAximum      ==> 250 , 125           0-999

  RECEIVEPfx   ==>

  RECEIVECount ==>                     1-999

  SENDPfx      ==>

  SENDCount    ==>                     1-999

  SENDSize     ==> 00521               1-30720

  RECEIVESize  ==> 00521               1-30720

                                            APPLID=CICSLU

PF 1 HELP 2 COM 3 END   6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

_________________________________________________________________

The following table shows the SNA Server parameters and values that

correspond to the preceding sample CICS parameters:

SNA Server Parameter        Sample value      CICS parameter

------------------------------------------------------------

LU Name for Local APPC LU    LOCLU1           Sessions

Mode name                    APPCMODE         MOdename

Parallel Session Limit       250              MAximum

in the mode

Partner Min Contention       125              Maximum

Winner Limit in the mode

Max Receive RU Size          00521            SENDSize

in the mode

Max Send RU Size             00521            RECEIVESize

in the mode

LU Name for Remote APPC LU   CICSLU           APPLID

In the sample CICS screen, the parameter called MAximum has two values, 250 and 125, separated by commas. The first value (250) is the parallel session limit. The second value (125) is the host minimum contention winner limit. On the SNA server, this corresponds

to Partner Min Contention Winner Limit in the mode. In addition, since the host is the contention winner on 125 sessions (out of a total of 250), then SNA Server should be configured as the contention winner on the remaining 125 sessions. In this case, the SNA Server mode would have the following values:

*     Parallel Session Limit 250

*     Minimum Contention Winner Limit 125

*     Partner Min Contention Winner Limit 125

*     Automatic Activation Limit 0

The remaining screens in this section show more information about how CICS could be configured for independent LU 6.2 through VTAM.

_________________________________________________________________

OVERTYPE TO MODIFY           CICS RELEASE = 0330

 CEDA  ALter

 SESSION PROPERTIES

  SESSPriority ==> 000                 0-255

  Transaction    :

 OPERATOR DEFAULTS

  OPERId         :

  OPERPriority   : 000                 0-255

  OPERRsl        : 0                   0-24,...

  OPERSecurity   : 1                   1-64,...

 PRESET SECURITY

  USERId       ==>

 OPERATIONAL PROPERTIES

  Autoconnect  ==> Yes                 No | Yes | All

  INservice      :                     No | Yes

  Buildchain   ==> Yes                 Yes | No

  USERArealen  ==> 000                 0-255

  IOarealen    ==> 00000 , 00000       0-32767

  RELreq       ==> No                  No | Yes

  DIscreq      ==> No                  No | Yes

  NEPclass     ==> 000                 0-255

 RECOVERY

  RECOVOption  ==> Sysdefault          Sysdefault | Clearconv

                                       | Releasesess | Uncondrel

                                       | None

  RECOVNotify  ==> None                None | Message | Transaction

                                            APPLID=CICSLU

PF 1 HELP 2 COM 3 END   6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

_________________________________________________________________

In the following screen, the underlined value corresponds to the LU Name of the local APPC LU in SNA Server.

_________________________________________________________________

OVERTYPE TO MODIFY                    CICS RELEASE = 0330

 CEDA  ALter

  Connection     : CON1

  Group          : VER3AAAA

  DEscription  ==> VERSION 3  LU 6.2 DEFINITION

 CONNECTION IDENTIFIERS

  Netname      ==> LOCLU1

  INDsys       ==>

 REMOTE ATTRIBUTES

  REMOTESystem ==>

  REMOTEName   ==>

 CONNECTION PROPERTIES

  ACcessmethod ==> Vtam                Vtam | IRc |INdirect | Xm

  Protocol     ==> Appc                Appc | Lu61

  SInglesess   ==> No                  No | Yes

  DAtastream   ==> User                User | 3270 | SCs|

                                       STrfield | Lms

  RECordformat ==> U                   U | Vb

 OPERATIONAL PROPERTIES

  AUtoconnect  ==> Yes                 No | Yes | All

  INService    ==> Yes                 Yes | No

 SECURITY

  SEcurityname ==>

  ATtachsec    ==> Verify              Local | Identify|

                                       Verify | Persistent|

                                       Mixidpe

  BINDPassword ==>                     PASSWORD SPECIFIED

  BINDSecurity ==> No                  No | Yes

                                            APPLID=CICSLU

PF 1 HELP 2 COM 3 END   6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

_________________________________________________________________

KBCategory: kbnetwork

KBSubcategory: ntnetserv

Additional reference words: prodsna 2.00


Q107192: Multiple connections to same host over 802.2

Multiple Connections to the Same Host Over 802.2              [winnt]

ID: Q107192    CREATED: 16-NOV-1993   MODIFIED: 20-APR-1995

2.00

WINDOWS

PUBLIC | kbnetwork

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

-------------------------------------------------------------------

SUMMARY

=======

SNA Server for Windows NT supports up to 250 connections (PUs) over a single SNA Server 802.2 link service, where each connection is communicating to a different IBM host, peer system (such as AS/400) or downstream (DSPU) device. However, to communicate to the same SNA destination, two SNA Server 802.2 link services and connections must be configured.

MORE INFORMATION

================

An SNA Server connection is equivalent to an IBM SNA Physical Unit Type 2.0 or 2.1. When communicating to different destinations (such as multiple 3745 and AS/400 computers), SNA Server supports up to 250 simultaneous connections over one 802.2 link service.

However, when communicating to the same destination (for example, to one 3745), two SNA Server 802.2 link services must be defined through the SNA Server Setup program (each with it's own SAP address), and a separate 802.2 connection must be defined through the SNA Server Admin program to use each 802.2 link service. Note that multiple SNA Server 802.2 link services can operate over a single 802.2 adapter, though

each link service must be configured with a unique SAP address.

To define two SNA Server 802.2 link services in the SNA Server Setup program, do the following:

1. From the Setup Option dialog box, Select Configure Link Services.

2. Select Add, then highlight SNA DLC 802.2 Link Service and choose Install.

3. Enter a title describing the link service (or leave the default title), then select the adapter the link service will use.

4. Leave the SAP default to 4

5. Repeat the previous steps to add the second 802.2 Link Service, except in step 4, set the SAP value to 8.

To exit Setup, choose Continue repeatedly until Setup displays an option to exit or start SNA Admin.

To define an SNA Server 802.2 link service in the SNA Server Admin program, do the following:

1. From the SNA Server Admin program, configure both connections with the appropriate Remote Network Address (which may be the same for both connections). Note that the Local Node ID will be unique for each connection, since each connection must refer to a unique PU at the host (where the Local Node ID must correspond with the IDBLK + IDNUM parameters on the PU definition in VTAM).

2. Add the required LUs (and optionally, LU pools) and save the configuration before restarting the SNA Server service.

SNA Server user/group records can be added after the SNA Server service has been started, though the configuration must be saved before these additions are available to the SNA Server client machine(s).

Additional reference words: prodsna 2.00 DLC 802.2

KBCategory: kbnetwork

KBSubcategory: ntnetserv


Q110390: Automatically starting SNA Server through control panel

Automatically Starting SNA Server Through Control Panel       [winnt]

ID: Q110390    CREATED: 20-JAN-1994   MODIFIED: 11-OCT-1994

2.00

WINDOWS

PUBLIC | kbenv

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

--------------------------------------------------------------------------

SUMMARY

=======

To automatically start SNA Server when you start your system, use the Services application to configure the SnaServer service startup method as Automatic. Also, if you are using NetView alerts and Run command, the NVAlert and NVRunCmd services should also be configured to start automatically.

All other SNA Server services are automatically started by SNA Server as needed, even though they are configured for manual start (this includes any SNA Server link services and SnaNetMn). In the case of SnaNetNm, this service displays an error message if the user attempts to start it through Control Panel.

MORE INFORMATION

================

Following is a description of each SNA Server service, and how each service is configured to start when SNA Server is installed:

SnaBase: Automatic startup. This service must be started before any other SNA Server service can run.

SnaServer: Manual startup. This can be changed to Automatic startup if desired. This may also be started/stopped using the SNA Server Admin program.

SNA Server link services (SnaDlc1, SnaSdlc1, and so on): Manual startup. SNA Server automatically starts the link services as needed. These services should NOT be configured to automatically start using Control Panel. Specifically, the SnaBase service starts these automatically. Also, the SnaServer service doesn't start unless all link services used by this server are running.

NVAlert, NVRunCmd: Manual startup. These services can be changed to Automatic startup if desired. SNA Server will not automatically start these services.

SnaNetMn: Manual startup. SNA Server will automatically start this service if NetView connectivity is configured on an SNA Server connection. This service should NOT be configured to automatically start using Control Panel, and fails with the following error message if the administrator tries to start it manually:

      SNA Server Error #0352

      Unable to open the configuration file, rc=618

Additional reference words: prodsna 2.00

KBCategory: kbenv

KBSubcategory: ntconfig


Q107567: Configuring SNA Server through 3174 gateway via 802.2

Configuring SNA Server through a 3174 Gateway via 802.2       [winnt]

ID: Q107567    CREATED: 23-NOV-1993   MODIFIED: 10-MAR-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT versions 2.0 and 2.1

--------------------------------------------------------------------------

SUMMARY

=======

This document provides the configuration parameters required on an IBM 3174 controller acting as an 802.2 gateway for SNA Server.

Note: SNA Server can connect through the 3174 gateway feature over either Token Ring or Ethernet. The 3174 can connect to the host over any supported link interface.

MORE INFORMATION

================

SNA Server can access a host system through an IBM 3174 controller, where the 3174 is configured to support a downstream PU 2.0 computer through the 3174 gateway feature.

In this configuration, SNA Server is configured with an 802.2 connection with "remote end=host" (as a secondary PU 2.0 node), where the 3174 provides the gateway function to a mainframe system.

On the SNA Server computer, do the following:

1. Run SNA Server Setup and add an 802.2 link service.

2. Run SNA Server Admin and configure the 802.2 connection (associated with the 802.2 link service) from the Servers And Connections dialog box, using the following properties:

    - Remote End: Host System

    - Activation: (as desired by the administrator--default for 802.2 connections is On Server Startup)

    - Allowed Directions: Outgoing Calls must be selected (Incoming optional)

3. Zoom on the Setup button, and set the following additional parameters:

    - Remote Network Address: Enter the network card interface address of the 3174. This is set in Response 900 in the 3174 customization program.

    - Local Node ID and Remote Node Name fields: not used--leave to defaults.

    - The Advanced settings can be left at the default settings.

4. Return to the main Servers And Connections dialog box. Focus on the 802.2 connection and create all required LUs off the connection (that is, 3270, LUA and/or dependent APPC LUs).

5. Optional: Configure pools of LUs through the LU Pools dialog box of SNA Server Admin.

6. Using the Users And Groups dialog box in SNA Server Admin, assign LUs and/or LU Pools to the appropriate users and groups.

On the IBM 3174 computer, do the following:

1. Using the 3174 configuration utility, configure downstream devices in Panel 940. Enter the SNA Server Token Ring network card (MAC) address in this panel. You can find the network card address of the SNA Server computer by entering "NET CONFIG WKSTA" from the command line of the Windows NT computer.

   When connecting over Ethernet, set the network card address in the 3174 Panel 940 to the bit-flipped version of the SNA Server local Ethernet address. The 3174 appears to bit-flip the incoming source address on the SNA Server XID message before matching against the addresses in the 940 screen. See below for instructions for determining the bit-flipped address.

   Most Windows NT adapters support overriding the network card address through the Windows NT network control panel. So, the SNA Server local network address could be set to match the address in Panel 940 on the 3174.

   The 3174 gateway feature recognizes the SNA Server computer by it's network card address only.  If the address in Panel 940 does not match (either the actual address if Token Ring, or the bit-flipped address if Ethernet), the SNA Server connection will stay "Pending" and the following error will be reported in the Windows NT application event log:

      Event: 230  Remote station not responding to XID commands

2. Set the T value in panel 940 to Controller and not Workstation. If it is set to Workstation, the connection (PU) will become active but the LUs defined in SNA Server Admin will remain inactive. To allow "Workstation" to work properly, the SNA Server connection must be configured to send a Format 0 XID (configurable within SNA Server Admin connection's setup / advanced dialog).

3. Complete the 3174 configuration and reload it according to 3174 procedures.

Determining a bit-flipped Ethernet address:

1. Separate the 12-digit hexadecimal address into a set of two digits. For example:

      40000A123456       ->   40 00 0A 12 34 56

2. Reverse the positions of the characters in each of the two-digit sets. For example:

      40 00 0A 12 34 56  ->   04 00 A0 21 43 65

3. Use the table below to bit-reverse each digit. For example:

      04 00 A0 21 43 65  ->   02 00 50 48 2C 6A

   Conversion Table

   ----------------

   Original  Converted

   Bit       Bit

   --------  ---------

   0          0

   1          8

   2          4

   3          C

   4          2

   5          A

   6          6

   7          E

   8          1

   9          9

   A          5

   B          D

   C          3

   D          B

   E          7

   F          F

4. After bit-reversing each digit, combine the six pairs into a 12-digit hexadecimal address. For example:

      020050482C6A

Additional reference words: prodsna 2.00 2.10 3174 gateway

KBCategory: kbnetwork

KBSubcategory: ntnetserv


Q107569: Configuring LU6.2 through 3174 APPN network node

Configuring  for LU 6.2 Through a 3174 APPN Network Node      [winnt]

ID: Q107569    CREATED: 23-NOV-1993   MODIFIED: 31-MAR-1995

2.00

WINDOWS

PUBLIC | kbenv kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

--------------------------------------------------------------------------

SUMMARY

=======

This document provides the configuration parameters required on an IBM 3174 controller acting as an APPN Network Node, supporting a downstream SNA Server (APPN LEN Node) over 802.2. The link between the 3174 and the host or peer system may be any link type supported by the 3174.

MORE INFORMATION

================

SNA Server can access a host or peer system through an IBM 3174 APPN Network Node. In this configuration, SNA Server is configured with an 802.2 connection (as a PU 2.1 LEN node), which may include independent APPC LU support, communicating through an adjacent IBM 3174 configured as an APPN Network Node.

On the SNA Server machine, do the following:

1. Run SNA Server Setup and add an 802.2 link service.

2. Run SNA Server Admin and configure the local SNA Server name:

    - Network Name: Must match parameter #501 in the 3174 configuration.

    - Control Point Name: Must match the CPNAME parameter (Node type #1), configured in the NETWORK RESOURCES and ASSOCIATED LUs in the 3174.

3. Off the server, add a Local APPC LU with the following options:

    - LU 6.2 type: Select Independent to support multiple (parallel) sessions.

    - LU Alias: Must match the Local LU name used by the Local APPC transaction program (refer to the product documentation).

    - Network Name: Must match parameter #501 in the 3174 configuration.

    - LU Name: In the 3174 configuration, this must match one of the 3174 LUNAMES that is configured off the CPNAME configured on behalf of SNA Server. The 3174 supports up to 4 LUNAMES (for LEN nodes) off one CPNAME.

    - Choose Enable Automatic Partnering if you want SNA Server to automatically partner this APPC LU with all remote APPC LUs in the SNA Server configuration.

    - Choose "Member of Default Outgoing Local APPC LU Pool" only if the local APPC transaction program does not specifies a local APPC LU, and you want this LU to be automatically used (this is not used by most programs).

4. Configure the 802.2 connection (associated with the 802.2 link service) from the Servers And Connections dialog box, using the following properties:

    - Remote End: Peer System

      NOTE: Remote End: Host system must be configured if the connection also supports 3270 devices. This setting forces SNA Server to have a secondary link role, while "Peer system" allows SNA Server to negotiate the link role to be either primary or secondary. Either role will support independent LU6.2 sessions.

    - Activation: (As desired by the administrator--default for 802.2 connections is On Server Startup.)

    - Allowed Directions: Outgoing and Incoming should be selected.

5. Zoom on the Setup button, and set the following additional parameters:

    - Remote Network Address: Enter the network card interface address of the 3174. This is set in Response 900 in the 3174 customization program.

    - Local Node ID: not used--leave to default.

    - Remote Node Name:

       - Network Name: Must match parameter #501 in the 3174 configuration (should appear as "SERVING NN" under the CPNAME.

       - Control Point Name: Must match parameter #511 in the 3174 configuration.

       - Remote Node ID: not needed--leave blank.

    - The Advanced settings can be left at the default settings (if remote SAP = 04).

6. Return to the main Servers And Connections window. Focus on the 802.2 connection and create all required LUs off the connection, which can include both 3270 LUs and remote APPC LUs. To configure a Remote APPC LU off the connection, enter the following information in the APPC Remote LU Properties dialog box:

    - LU Alias: Name used by the Local APPC transaction program (refer to product documentation).

    - Network Name: Remote VTAM NETID (which usually matches #501 in the 3174 configuration).

    - LU Name: Remote APPC LU name configured in VTAM (LU macro name in VTAM).

    - Uninterpreted LU Name: Usually the same as the LU Name.

    - Check Supports Parallel Sessions if you want to support multiple sessions.

    - Check Enable Automatic Partnering if you want SNA Server to automatically partner this APPC LU with all other Local LUs configured.

    - Implicit Incoming Mode: Not necessary.

7. Configure an APPC Mode, and partner the Local and Remote APPC LUs with the Mode:

    - In the Local or Remote APPC LU dialog box, zoom on the Partners button. If the Local and Remote LUs are not already partnered with the desired APPC mode name, zoom on the Modes button.

    - To create a new Mode, enter the new Mode name over an existing Mode. This Mode name must match the "DLOGMOD" entry in the Remote APPC LU macro in VTAM.

    - Partner your Local APPC LU and Remote APPC LU with this new mode, if they are not already partnered together.

8. Optional: Configure pools of LUs in the LU Pools dialog box of SNA Server Admin, if you want to create pools of 3270 LUs for your users.

9. Using the Users And Groups dialog box in SNA Server Admin, assign LUs and/or LU Pools to the appropriate users and groups. This is not necessary for APPC, though is required for user access to 3270 sessions.

10. Save the configuration, and then restart SNA Server.

On the IBM 3174 machine, do the following:

1. Using the 3174 configuration utility, configure downstream devices in Panel 940. Enter the SNA Server network card (MAC) address in this panel. (You can find the network card address of the SNA Server machine by entering "NET CONFIG WKSTA" from the command line of the Windows NT machine).

2. Configure the SNA Server control point name in the NETWORK RESOURCES option, as well as the Local APPC LU names as "LUNAMES" in the ASSOCIATED LUs section for the control point.

3. Complete the 3174 configuration and reload it according to 3174 procedures.

Additional reference words: prodsna 2.00

KBCategory: kbenv kbnetwork

KBSubcategory: ntconfig


Q107570: SNA Server and 3287 host print emulation

SNA Server and 3287 Host Print Emulation                      [winnt]

ID: Q107570    CREATED: 23-NOV-1993   MODIFIED: 11-OCT-1994

3.10

WINDOWS

PUBLIC | kbprint

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

--------------------------------------------------------------------------

SUMMARY

=======

The Microsoft SNA Server version 2.0 package does not include support for IBM 3287 host print emulation. However, several third-party companies do support printer emulation, which are listed in the ISV Companion Product Catalog that is included with SNA Server.

MORE INFORMATION

================

To support host print emulation (often referred to as 3287 print emulation) with SNA Server, a third-party product must be used, because the low-end 3270 emulator included with the product only supports display emulation.

To run the third-party print emulation package at the server, a 32-bit Windows host print emulation product must be used. Also, a third-party emulator could also run on any SNA Server client platform (that is, a Windows 3.x emulator runs on an SNA Server Windows 3.x client, and so on).

To support print emulation, the administrator must define 3270 printer Lus in the SNA Server configuration file (using SNA Admin), and assign these LUs to an SNA Server user or to a group account where the print emulator will be running. When users route print data to the printer LU supported by a printer emulation package, SNA Server routes the host print job to the print emulator, whether it resides on the server or an SNA Server client (that is, it does not flow to the 3270 display emulator user who initiated

the host print job).

Also, note that the Windows 16-bit and 32-bit 3270 applets that are shipped with SNA Server does include a local screen print capability, where screen data can be routed to a local printer, or redirected to a network printer.

Additional reference words: prodsna 2.00 3287 SNA print emulation

KBCategory: kbprint

KBSubcategory: ntprint


Q107571: Running SNA Server Win16, OS/2 or MS-DOS apps on Windows NT

Running SNA Server Win16, OS/2, or MS-DOS Applications        [winnt]

ID: Q107571    CREATED: 23-NOV-1993   MODIFIED: 08-MAY-1995

2.00 2.10 2.11

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0, 2.1, and 2.11

--------------------------------------------------------------------------

SUMMARY

=======

While Windows NT or Windows NT Advanced Server supports Windows 3.x, MS-DOS, and character-based OS/2 applications, SNA Server only supports 32-bit Windows SNA applications with the SNA Server Windows NT client software.

MORE INFORMATION

================

SNA Server Version 2.0

----------------------

SNA Server version 2.0 supports Windows NT, Windows 3.x, MS-DOS, and OS/2 clients. However, only 32-bit Windows SNA applications are designed to work with the SNA Server Windows NT client software. Any SNA application designed to run on these other client platforms are only supported on their native platform type. To summarize:

 - Windows 3.x., MS-DOS or OS/2-based SNA applications are not supported on the SNA Server Windows NT client.

 - Windows 3.x SNA applications are not supported with the SNA Server Windows 3.x  client software when run on a Windows NT machine.

 - OS/2 SNA applications are not supported with the SNA Server OS/2 client software when run from a Windows NT machine.

 - MS-DOS SNA applications are not supported with the SNA Server MS-DOS client software when run from a Windows NT machine.

SNA Server Version 2.1

----------------------

SNA Server version 2.1 supports Windows NT, Windows 3.x, MS-DOS, and OS/2 clients. Under Windows NT, you can install either the SNA Server Windows NT client or the SNA Server Windows 3.x client, but not both. Only 32-bit Windows SNA applications are designed to work with the SNA Server Windows NT client software. Any SNA application designed to run on other client platforms are supported only on their native platform type. To summarize:

 - Windows 3.x, MS-DOS, and OS/2-based SNA applications are not supported on the SNA Server Windows NT client.

 - Windows 3.x SNA applications are supported with the SNA Server Windows 3.x client software when run on a computer running Windows NT.

 - OS/2 SNA applications are not supported with the SNA Server OS/2 client software when run from a computer running Windows NT.

 - MS-DOS SNA applications are not supported with the SNA Server MS-DOS client software when run from a computer running Windows NT.

SNA Server Version 2.11

-----------------------

SNA Server 2.11, to be released during the summer of 1995, will support the "thunking" of many of the Windows 3.x SNA APIs on the SNA Server Windows NT client software. This applies to APPC, CPIC, CSV, LUA, and EHNAPPC interfaces. This will allow many Windows 3.x SNA applications to run on the SNA Server Windows NT client software. However, the SNA Server Windows 3.x Emulator Interface Specification (used by many 3270 emulation products) is not supported on the SNA Server 2.11 Windows NT client software.

Microsoft is interested in customer requests for such cross-platform SNA application support on Windows NT. Please let us know the specific SNA application (and platform it was written for) so that we can consider this in a future release.

KBCategory: kbnetwork

KBSubcategory: nt16ap ntdosap

Additional reference words: prodsna 2.00 2.10 2.11


Q130924 5250 emulation session fails to OS/400 V3R1

SNA Server 5250 Emulator Session Fails With AS/400 3.1        [winnt]

ID: Q130924    CREATED: 30-MAY-1995   MODIFIED: 12-JUN-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

-------------------------------------------------------------------------

SUMMARY

=======

When you attempt to establish a session from the SNA Server version 2.1 5250 emulator to an AS/400 version 3.1, the session attempt may stop responding (hang). This occurs in both Windows NT and Windows 3.x 5250 emulator applications. This occurs in both Windows NT and Windows 3.x 5250 emulator applications, as well as the SNA Server MS-DOS router (that is, the PC Support router replacement module).

RESOLUTION

==========

This problem is fixed in the 5250 applets and the SNA Server MS-DOS router included with SNA Server 2.11.

To correct this problem when using SNA Server 2.1, there are two possible solutions:

1. Install an update for OS/400 V3R1:

   A fix for this problem can be obtained from IBM by requesting PTF #SF23707 or APAR # SA43763. Once this update is applied, the original SNA Server 2.1 5250 applets work correctly.

2) Install the updated SNA Server 2.1 5250 applets or MS-DOS router:

   If you do not want to install the IBM OS/400 update described above, install the SNA Server 2.1 5250 applet update (5250UP.ZIP) located on the following electronic services:

    - On CompuServe, you can find 5250UP.ZIP in Library 4 of the MSSNA forum.

    - On the Internet, the file is located on the Microsoft anonymous ftp server, which you can reach by typing the following at the ">" prompt:

         ftp ftp.microsoft.com

      To download 5250UP.ZIP, change to the following directory:

         \bussys\winnt\sna-unsup-ed\fixes\5250up

   The 5250UP.ZIP file must be uncompressed using PKZIP 2.04g or later, using the following command:

      pkunzip -d 5250up.zip

A README file is included. It describes how to install the update.

The key modules which fix this specific problem are:

   SNASRV.EXE  - Update to the Windows NT and Windows 3.x 5250 applet

   INITRTR.EXE - Update to the SNA Server MS-DOS router

KBCategory: kbnetwork

KBSubcategory: ntinterop ntnetserv

Additional reference words: 2.00 2.10 prodsna


Q107866: Auto-recovery of LU6.2 sessions when partner is restarted

Auto-Recovery of APPC Sessions when Partner is Restarted      [winnt]

ID: Q107866    CREATED: 30-NOV-1993   MODIFIED: 11-NOV-1994

2.00

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

--------------------------------------------------------------------------

SUMMARY

=======

By default, SNA Server automatically recovers APPC sessions under most circumstances if the remote end (such as CICS or an AS/400) is stopped and restarted. However, if APPC sessions are still not being recovered, SNA Server supports more aggressive session recovery when the RENEGLIMITS parameter is added to the Windows NT Registry.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

MORE INFORMATION

================

To configure SNA Server 2.0 to support more aggressive APPC session recovery, do the following:

1. On the SNA Server machine, run REGEDT32.

2. Zoom on the following entries:

      HKEY_LOCAL_MACHINE

          SYSTEM

             CurrentControlSet

                  Services

                      SnaServr

                           Parameters

3. Add the following new parameter:

      RENEGLIMITS:REG_SZ:YES

4. Restart SNA Server.

This causes SNA Server to re-negotiate CNOS session limits following any negative response to an APPC application bind request.

BACKGROUND

==========

RENEGLIMITS and RETRYCNOS:

These variables only affect APPC LUs that support parallel sessions and determine SNA Server's behavior when an application BIND (non-CNOS BIND) fails.

By default, SNA Server performs CNOS negotiation:

 - At start of day (when the session limits are initially zero).

 - In response to an application issuing a CNOS verb.

Even after a connection outage, SNA Server does not reset session limits, so re-negotiation does not occur when the connection is reactivated.

The most likely reason for an application BIND to fail after a previously successful CNOS negotiation is that the partner LU has reset its session limits (perhaps because of a connection failure or being stopped and restarted) without SNA Server being informed by a request to re-negotiate the session limits.

If the remote application is now active, and there are no active sessions on the connection, performing CNOS re-negotiation solves this problem. If the CNOS re-negotiation fails, no further attempts are made to activate thesession until the connection is restarted or the SNA Server application retries.

The default settings for SNA Server are: RENEGLIMITS=NO and RETRYCNOS=YES. These settings attempt to detect the conditions where the remote application requires re-negotiation of session limits, and to avoid unnecessary re-negotiation.

Setting RENEGLIMITS=YES causes re-negotiation in all circumstances (provided there are no active sessions).

Setting RENEGLIMITS=NO and RETRYCNOS=NO provides backward compatibility with the default behavior of Comm Server 1.x.

RENEGLIMITS:REG_SZ:NO:

When this variable is set to YES, SNA Server performs CNOS re-negotiation whenever an application BIND fails, regardless of the sense code. Otherwise, SNA Server performs CNOS re-negotiation according to the setting of RETRYCNOS.

Note that when RENEGLIMITS is set to YES, it overrides any setting of RETRYCNOS.

RETRYCNOS:REG_SZ:YES:

When this variable is set to NO, SNA Server does not automatically re-negotiate LU 6.2 session limits when an application BIND fails. Otherwise, SNA Server performs CNOS re-negotiation whenever an application BIND is rejected by an UNBIND request or with a BIND negative response containing one of the following sense codes:

   Sense 1    Sense 2

   -------------------------------------------

   0x0806      0x3426 (Resource Unknown)

   0x0805      xxxxxx (Session Limit Exceeded)

   0x0801      xxxxxx (Resource Not Available)

If the variable RENEGLIMITS is set to YES, it overrides any setting of RETRYCNOS.

Note that the default value for this variable was NO in Comm Server 1.x.

Additional reference words: prodsna 2.00 SNA CNOS APPC LU6.2 recovery reneglimits retrycnos

KBCategory: kbnetwork

KBSubcategory: ntnetserv


Q110582: SNA Server service stays Inactive when started.

SNA Server Service Stays Inactive When Started                [winnt]

ID: Q110582    CREATED: 25-JAN-1994   MODIFIED: 11-OCT-1994

2.00

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

--------------------------------------------------------------------------

SYMPTOMS

========

If an SNA Server link service fails to start for any reason, the SNA Server service will not start. Using SNA Server Admin, the server switches from Pending to Inactive when it is started.

WORKAROUND

==========

To work around this problem, remove any SNA Server link services that depend on adapters that are not present, or determine why the SNA link service failed to start. Possible causes for link service initialization failures include, but are not limited to, the following:

 - Adapter not present in the machine.

 - Interrupt conflict with another device in the machine.

 - DLC driver not installed or bound to the network adapter.

MORE INFORMATION

================

When SNA Server is installed, the SNA Server service is configured to depend on all underlying link services to start. However, if an underlying link service fails to start for any reason, SNA Server fails to start and the following error will be logged in the Windows NT system log:

  Event ID: 7001

  Source:   Service Control Manager

  Type:     Error

  Description: The SnaServer service depends upon the <snalink> service which failed to start because of the following error: The dependency service or group failed to start.

Note that <snalink> is the name of the SNA Server link service specified during SNA Server setup (default names are SnaSdlc1, SnaDlc1, SnaDft1, SnaX251). This error occurs because the <snalink> service did not start. The reason for the failure should be present in a preceding error in the system event log, reported as Event ID #7000.

Additional reference words: prodsna 2.00 SNA service 7000 7001

KBCategory: kbnetwork

KBSubcategory: ntnetserv


Q112158: Configuring SNA Server to talk to AS/400 over 802.2

Configuring SNA Server to Talk to AS/400 Over 802.2           [winnt]

ID: Q112158    CREATED: 01-MAR-1994   MODIFIED: 07-OCT-1994

2.00

WINDOWS

PUBLIC | kbtool

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

--------------------------------------------------------------------------

SUMMARY

=======

This article describes how to configure SNA Server to communicate with an AS/400 over 802.2 (Token Ring or Ethernet), to support 5250 emulation. Both SNA Server and AS/400 configuration parameters are discussed.

NOTE: The end of this article includes sample AS/400 configuration screens.

MORE INFORMATION

================

These instructions assume all of the following:

 - The Windows NT DLC transport driver has been installed and is bound to the correct network adapter.

 - The SNA Server DLC link service has been installed using the SNA Server setup program.

 - The system has been restarted.

Configure the following entries using the SNA Server Admin program:

1. Zoom on the SNA Server service (which appears as the Windows NT machine name), located in the Servers and Connections window of Admin. Enter the following parameters:

   SNA Network Control Point Name

      Network Name =  APPN (or Remote Network ID, RMTNETID value on the AS/400).

      Control Point Name = This is the remote control point name (RMTCPNAME) value in the AS/400 APPC controller definition.  For simplicity, this should be set to the local Windows NT machine name.

   Choose OK.

2. Add a new Local APPC LU off the server service by choosing the Insert button and entering the following parameters:

      LU 6.2 Type  = Independent

      LU Alias     = For simplicity, this should be the same as the Local LU Name below.

      Network Name = APPN (same as network name above)

      LU Name      = This is the remote control point name in the AS/400 APPC controller description (RMTCPNAME).

      All other entries can remain at default values.

      NOTE: It is most efficient for all SNA Server users to use the same Local APPC LU. However, it is possible to create a unique LU for each user if desired, where the LU alias and LU name above could be replaced with the actual user name (though this requires additional administration to maintain).

   Choose OK.

3. Configure the SNA Server 802.2 connection by zooming on the connection name:

      Link Service = SnaDlc1 (or name specified during SNA setup)

      Remote End   = Peer System

      Activation   = If set to "On Server Startup" (default), then the Switched disconnect (SWTDSC) value on the AS/400 controller definition should be set to NO. This causes the underlying link to stay active even if there are no active sessions. Otherwise, if SWTDSC is YES, then SNA Server should be set to "On Demand" activation.

      Allowed Directions = Outgoing calls. Check Incoming Calls if you want the AS/400 to activate the link.

      Zoom on the Setup button:

      Remote Network Address = Set to the network adapter address of the AS/400 (ADPTADR), located in the AS/400 line description.

      Local Node ID = EXCHID value on the AS/400 controller description (if not specified on the AS/400, leave at default - 05D FFFFF).

      Remote Node Name:

      Network Name = APPN (or remote network ID RMTNETID value on the AS/400)

      Control Point Name = AS/400 local control point name, configured in the AS/400 Display Network Attributes screen.

      Remote Node ID = Not used (leave blank)

      Advanced options can be left at their default settings

      Choose OK.

4. Add a new Remote APPC LU off the connection by choosing the Insert button and enter the following parameters:

      LU Alias     = For simplicity, this should be the same as the Remote APPC LU Name below.

      Network Name = APPN (or remote network id RMTNETID value on the AS/400)

      LU Name      = Must be set to the AS/400 local control point name (set in the AS/400 Display Network Attributes screen).

      Uninterpreted LU Name = Not used (leave at default setting).

      Select Supports Parallel Sessions (required).

      Zoom on the Partners button.  The Remote APPC LU must be partnered with the Local APPC LU created above, using the QPCSUPP mode. Because Enable Automatic Partnering is enabled by default for APPC LU's, this pairing will already be added.

   Choose OK.

5. Save the SNA Server configuration file and restart the SNA Server service. Once the SNA Server service is Active, all connections configured to activate on server startup will go into a Pending state,then switch to Active.

   NOTE: If the connection stays in Pending mode and doesn't activate:

   a. Check the Windows NT application event log (using Event Viewer) to see the reason why the connection isn't activating. For example, if the AS/400 is not responding to TEST commands, then the remote network address may not be correct.

   b. Double check the configuration entries above with your AS/400 system administrator and make sure the AS/400 line is active. If all appears okay, check the SNA Server controller description on the AS/400. For LAN-based connections (such as Token Ring or Ethernet), the AS/400 defaults to auto configuration for new controllers, so manual generation on the AS/400 is not required.

   c. Check if the AS/400 is logging any errors when SNA Server attempts to establish the connection.

   d. If the connection activates but users are unable to open 5250 sessions, zoom on the Status button on the Local APPC LU, which should show the following (when working correctly):

     Partner LU           Mode            Connection     Sessions        Limit

     <remote LU>     SNASVCMG  <connection>    0                2

     <remote LU>     QPCSUPP      <connection>    0               64

     This means that up to 64 sessions are available for use, though no sessions are currently active.

At this point, a 5250 user can then open any valid APPC LU/LU pair supported by any SNA Server in the domain. However, in order to simplify 5250 user access through SNA Server, there are various options available to an SNA Server administrator and the 5250 user, including the following:

 - Default AS/400 session for a user: On the SNA Server user/group record, the administrator can define default local and remote APPC LU's. If defaults are configured, and the 5250 applet is used, this is the LU/LU pair the 5250 user will open when the 5250 applet local and partner APPC LU names are left blank.

 - If default APPC LU's are not preassigned to a user/group, here is how to configure pools of Local APPC LU's and Remote (partner) APPC LU's to simplify 5250 user access to one or more AS/400's supported by SNA Server:

   Local APPC LU pool: Define the Local APPC LU as a "Member of Default Outgoing Local APPC LU Pool". If a 5250 user does not enter a Local APPC LU when opening a session, the user will access one of the available Local LU's in this pool.

   Remote APPC LU pool: The Remote APPC LU pool is determined by the Remote LU's which are partnered with the Local APPC LU and the QPCSUPP mode. So, if a Local APPC LU is specified, but the Remote APPC LU is left blank, a 5250 session will be allocated from an available Remote APPC LU which it is partnered with.

SAMPLE AS/400 CONFIGURATION

===========================

The following AS/400 configuration screens are shown below, along with their corresponding configuration setting for SNA Server (see comments which are preceded with "****" below). This includes the AS/400 network attributes screen, Token Ring line description, APPC controller, and virtual device description. Many of the configuration settings are not relevant for communications to function, though are shown here for

completeness.

AS/400: Display Network Attributes

                             System:   OLYMPIA

 Current system name  . . . . . . . . . . . . . . :   OLYMPIA

   Pending system name  . . . . . . . . . . . . . :

 Local network ID . . . . . . . . . . . . . . . . :   APPN

**** must match the remote network name on the SNA Server connection.

 Local control point name . . . . . . . . . . . . :   OLYMPIA

**** must match the remote control point name on the SNA Server connection

 Default local location . . . . . . . . . . . . . :   OLYMPIA

 Default mode . . . . . . . . . . . . . . . . . . :   BLANK

 APPN node type . . . . . . . . . . . . . . . . . :   *ENDNODE

 Maximum number of intermediate sessions  . . . . :   200

 Route addition resistance  . . . . . . . . . . . :   128

 Server network ID/control point name . . . . . . :   APPN        REDHOOK

 Alert status . . . . . . . . . . . . . . . . . . :   *OFF

 Alert logging status . . . . . . . . . . . . . . :   *NONE

 Alert primary focal point  . . . . . . . . . . . :   *NO

 Alert default focal point  . . . . . . . . . . . :   *NO

 Alert backup focal point . . . . . . . . . . . . :

   Network ID . . . . . . . . . . . . . . . . . . :     *NONE

 Alert focal point to request . . . . . . . . . . :

   Network ID . . . . . . . . . . . . . . . . . . :     *NONE

 Alert controller description . . . . . . . . . . :   *NONE

 Alert hold count . . . . . . . . . . . . . . . . :   0

 Alert filter . . . . . . . . . . . . . . . . . . :   *NONE

   Library  . . . . . . . . . . . . . . . . . . . :

 Message queue  . . . . . . . . . . . . . . . . . :   QSYSOPR

   Library  . . . . . . . . . . . . . . . . . . . :     QSYS

 Output queue . . . . . . . . . . . . . . . . . . :   QPRINT

   Library  . . . . . . . . . . . . . . . . . . . :     QGPL

 Job action . . . . . . . . . . . . . . . . . . . :   *FILE

 Maximum hop count  . . . . . . . . . . . . . . . :   16

 DDM request access . . . . . . . . . . . . . . . :   *OBJAUT

 PC Support request access  . . . . . . . . . . . :   *OBJAUT

 Default ISDN network type  . . . . . . . . . . . :

 Default ISDN connection list . . . . . . . . . . :   QDCCNNLANY

AS/400: Change Line Desc (Token Ring) (CHGLINTRN)

Line description . . . . . . . . LIND         > LANLINE

 Resource name  . . . . . . . . . RSRCNAME       LIN031

 Online at IPL  . . . . . . . . . ONLINE         *YES

 Vary on wait . . . . . . . . . . VRYWAIT        *NOWAIT

 Maximum controllers  . . . . . . MAXCTL         64

 Line speed . . . . . . . . . . . LINESPEED      16M

 Maximum frame size . . . . . . . MAXFRAME       1033

 TRLAN manager logging level  . . TRNLOGLVL      *OFF

 TRLAN manager mode . . . . . . . TRNMGRMODE     *OBSERVING

 Log configuration changes  . . . LOGCFGCHG      *LOG

 Token Ring inform of beacon  . . TRNINFBCN      *YES

 Local adapter address  . . . . . ADPTADR        494061026052

**** Must match the remote network address on the SNA Server connection.

Also, the Local Adapter Address (ADPTADR) parameter on the line description (for Token Ring or Ethernet) has a default of *ADPT. AS/400 Administrators can choose to enter their own locally administered address or the *ADPT inserts the burned-in adapter card address. The following information includes advantages of both options.

Locally Administered Address:

   Advantages: The address is permanent and will not change. It is important to pick a unique address so that there are no network conflicts. This is the IBM recommended option.

*ADPT Address:

   Advantages: The adapter address is inserted into the line description when the line is varied on. Afterward, you can display the line description and see the adapter card address. This address is a unique address and you are insured there will be no duplicates on your network.

   Disadvantages: If the Adapter card has a hardware problem and is replaced, you need to have a new address when the line is varied on for the first time. All users who connect using the address will not be able to communicate unless they change their configuration accordingly. This can cause problems if you have many users because they all reference the same adapter address.

 Functional address . . . . . . . FCNADR         *SAME

                  + for more values

 SSAP list:                       SSAP

   Source Service Access Point  .                04

   SSAP maximum frame . . . . . .                *MAXFRAME

   SSAP type  . . . . . . . . . .                *SNA

                  + for more values

 Early token release  . . . . . . ELYTKNRLS      *YES

**** For 16 MB Token Ring, note the Early Token Release setting. This should match the early token release setting used on your local Windows NT network adapter (set using the Network applet in Control Panel).

 Error threshold level  . . . . . THRESHOLD      *OFF

 Link speed . . . . . . . . . . . LINKSPEED      16M

 Cost/connect time  . . . . . . . COSTCNN        0

 Cost/byte  . . . . . . . . . . . COSTBYTE       0

 Security for line  . . . . . . . SECURITY       *NONSECURE

 Propagation delay  . . . . . . . PRPDLY         *LAN

 User-defined 1 . . . . . . . . . USRDFN1        128

 User-defined 2 . . . . . . . . . USRDFN2        128

 User-defined 3 . . . . . . . . . USRDFN3        128

 Autocreate controller  . . . . . AUTOCRTCTL     *YES

**** This setting controls whether the APPC controller definition and virtual device definition (listed below) are automatically created by the AS/400 on this line. For Token Ring or Ethernet lines, this is the default. However, this is not the case for SDLC.

 Autodelete controller  . . . . . AUTODLTCTL     1440

 Recovery limits:                 CMNRCYLMT

   Count limit  . . . . . . . . .                2

   Time interval  . . . . . . . .                5

 Text 'description' . . . . . . . TEXT           'LAN Line description'

**** Note: If AUTOCRTCTL is YES (in the line description above), then the APPC controller and virtual device definitions below do not have to be generated. In this case, the SNA Server configuration settings noted below will cause these AS/400 configuration entries to be automatically generated.

AS/400: Change Ctl Desc (APPC) (CHGCTLAPPC)

Controller description . . . . . CTLD         > TRUTH00

 Online at IPL  . . . . . . . . . ONLINE         *NO

 APPN-capable . . . . . . . . . . APPN           *YES

 Switched line list . . . . . . . SWTLINLST      LANLINE

                  + for more values

 Character code . . . . . . . . . CODE           *EBCDIC

 Maximum frame size . . . . . . . MAXFRAME       16393

 Remote network identifier  . . . RMTNETID       APPN

**** Must match the network name configured on SNA Server (set using Admin when zooming on the server name), as well as the network name configured on the Local APPC LU.

 Remote control point . . . . . . RMTCPNAME      TRUTH

**** Must match the local control point name configured on SNA Server (set using Admin when zooming on the server name), as well as the LU name of the Local APPC LU.

Exchange identifier  . . . . . . . :   EXCHID      05600001

**** Must match the Local Node ID in the SNA Server connection

 SSCP identifier  . . . . . . . . SSCPID         *SAME

 Initial connection . . . . . . . INLCNN         *DIAL

 Dial initiation  . . . . . . . . DIALINIT       *LINKTYPE

 Switched disconnect  . . . . . . SWTDSC         *YES

**** If this is set to YES, the AS/400 drops the link when there are no active users, so the SNA Server connection should be configured to activate On Demand. Note that SNA Server 802.2 connections default to activate On Server Startup. If this is desired, the SWTDSC setting should be set to NO.

 Disconnect timer:                DSCTMR

   Minimum connect timer  . . . .                170

   Disconnection delay timer  . .                0

 LAN remote adapter address . . . ADPTADR        10005A38374C

**** This is the network adapter address of the network card being used on the SNA Server computer.

 LAN DSAP . . . . . . . . . . . . DSAP           04

**** This must match the SAP address on the SNA Server link service, configured using SNA Server setup. This is usually set to 04, so this rarely (if ever) changes.

 LAN SSAP . . . . . . . . . . . . SSAP           04

**** This is the SAP address of the destination AS/400 computer, and must match the SAP address on the SNA Server connection, configured using SNA Server Admin. Again, this rarely (if ever) changes.

 LAN frame retry  . . . . . . . . LANFRMRTY      *CALC

 LAN connection retry . . . . . . LANCNNRTY      *CALC

 LAN response timer . . . . . . . LANRSPTMR      *CALC

 LAN connection timer . . . . . . LANCNNTMR      *CALC

 LAN acknowledgment timer  . . .  LANACKTMR      *CALC

 LAN inactivity timer . . . . . . LANINACTMR     *CALC

 LAN acknowledgment frequency  .  LANACKFRQ      *CALC

 LAN max outstanding frames . . . LANMAXOUT      *CALC

 LAN access priority  . . . . . . LANACCPTY      *CALC

 LAN window step  . . . . . . . . LANWDWSTP      *NONE

 APPN CP session support  . . . . CPSSN          *YES

 APPN node type . . . . . . . . . NODETYPE       *CALC

 APPN transmission group number   TMSGRPNBR      *CALC

 APPN minimum switched status . . MINSWTSTS      *VRYONPND

 Autodelete device  . . . . . . . AUTODLTDEV     1440

 User-defined 1 . . . . . . . . . USRDFN1        *LIND

 User-defined 2 . . . . . . . . . USRDFN2        *LIND

 User-defined 3 . . . . . . . . . USRDFN3        *LIND

 Recovery limits:                 CMNRCYLMT

   Count limit  . . . . . . . . .                2

   Time interval  . . . . . . . .                5

 Model controller description . . MDLCTL         *NO

 Connection network network ID  . CNNNETID       *SAME

 Connection network CP  . . . . . CNNCPNAME      *SAME

 Control owner  . . . . . . . . . CTLOWN         *SAME

 Text 'description' . . . . . . . TEXT           'AUTOMATICALLY CREATED

 BY QLUS'

AS/400:  Change Device Desc (APPC) (CHGDEVAPPC)

Device description . . . . . . . DEVD         > TRUTH03

**** This device name corresponds with the SNA Server Local APPC LU name (in this case, TRUTH), plus a two-digit device number, generated by the AS/400 (but not configured in SNA Server).

 Online at IPL  . . . . . . . . . ONLINE         *NO

 Mode . . . . . . . . . . . . . . MODE           *NETATR

                  + for more values

 Message queue  . . . . . . . . . MSGQ           QSYSOPR

   Library  . . . . . . . . . . .                  *LIBL

 Local location address . . . . . LOCADR         00

 Single session:                  SNGSSN

   Single session capable . . . .                *NO

   Number of conversations  . . .

 Locally controlled session . . . LCLCTLSSN      *SAME

 Pre-established session  . . . . PREESTSSN      *SAME

 Text 'description' . . . . . . . TEXT           'AUTOMATICALLY CREATED

 BY QLUS'

 Mode description . . . . . . . . MODD         > QPCSUPP

**** This should not be changed; this is the default mode name for IBM PC Support clients (and SNA Server).

 Class-of-service . . . . . . . . COS            #CONNECT

 Maximum sessions . . . . . . . . MAXSSN         64

**** This is the number of sessions supported by the QPCSUPP mode, and should match the SNA Server session limit configured on the QPCSUPP mode entry, configured using the SNA Server setup program (zoom on Local or Remote LU, zoom on Partners button, then choose the Modes button).

 Maximum conversations  . . . . . MAXCNV         64

**** This should match the MAXSSN setting above.

 Locally controlled sessions  . . LCLCTLSSN      16

 Pre-established sessions . . . . PREESTSSN      0

 Inbound pacing value . . . . . . INPACING       7

 Outbound pacing value  . . . . . OUTPACING      7

 Maximum length of request unit   MAXLENRU       *CALC

 Text 'description' . . . . . . . TEXT           'created by <name>'

Additional reference words: prodsna 2.00 TR

KBCategory: kbtool

KBSubCategory: ntutil SNA


Q112159: Configuring SNA Server to talk to AS/400 over SDLC

Configuring SNA Server to Talk to AS/400 Over SDLC            [winnt]

ID: Q112159    CREATED: 01-MAR-1994   MODIFIED: 07-OCT-1994

2.00

WINDOWS

PUBLIC | kbtool

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

--------------------------------------------------------------------------

SUMMARY

=======

This article describes how to configure SNA Server to communicate with an AS/400 over an Synchronous Data Link Control (SDLC) switched (dial-up) line, to support 5250 emulation.

NOTE: The end of this article includes sample AS/400 configuration screens.

MORE INFORMATION

================

These instructions assume all of the following:

 - The SNA Server SDLC link service has been installed using the SNA Server setup program (and any interrupt conflicts have been resolved, per the SNA Server README.TXT file).

 - The system has been restarted.

 - AS/400 APPC controller and device description has been configured off the AS/400 SDLC line to be used (see below for sample AS/400 APPC controller and device descriptions).

Configure the following entries using the SNA Server Admin program:

1. Zoom on the SNA Server service (which appears as the Windows NT machine name), located in the Servers and Connections window of Admin. Enter the following parameters:

   SNA Network Control Point Name

      Network Name = APPN (or Remote Network ID, RMTNETID value on the AS/400).

     Control Point Name = This is the remote control point name (RMTCPNAME) value in the AS/400 APPC controller definition. For simplicity, this should be set to the local Windows NT machine name.

   Choose OK.

2. Add a new Local APPC LU off the server service by choosing the Insert button and entering the following parameters:

      LU 6.2 Type  = Independent

      LU Alias     = For simplicity, this should be the same as the Local LU Name below.

      Network Name = APPN (or Remote Network ID, RMTNETID value on the AS/400).

      LU Name      = This is the remote control point name in the AS/400 APPC controller description (RMTCPNAME).

      All other entries can remain at default values.

      NOTE: It is most efficient for all SNA Server users to use the same Local APPC LU. However, it is possible to create a unique LU for each user if desired, where the LU alias and LU name above could be replaced with the actual user name (though this requires additional administration to maintain).

   Choose OK.

3. Configure the SNA Server SDLC connection by zooming on the connection name:

      Link Service = SnaSdlc1 (or name specified during SNA setup)

      Remote End   = Peer System

      Activation   = If set to "On Demand" (default), then the Switched disconnect (SWTDSC) value on the AS/400 controller definition should be set to YES. This causes the underlying link to drop when there are no active sessions. Otherwise, if SWTDSC is set to NO, then SNA Server should be set to activate On Server Startup.

      Allowed Directions = Outgoing calls.

      Zoom on the Setup button:

      Dial data = Recommend to leave blank, and configure for modem-stored number dialing (assuming this is a dial-up link).

      Local Node ID =  EXCHID value on the AS/400 line description

      Remote Node Name:

      Network Name = APPN (or Remote Network ID, RMTNETID value on the AS/400).

      Control Point Name = AS/400 local control point name, configured in the AS/400 Display Network Attributes screen.

      Remote Node ID = Not used (leave blank)

      Zoom on Advanced options:

      XID Type = Format 3

      Encoding = (NRZ or NRZI). Must match the NRZI data encoding scheme (NRZI) configured on the AS/400 line description.

      Duplex = Must match the DUPLEX setting configured in the AS/400 line description.

      Poll Address = Must match the Station address (STNADR) setting on the AS/400 controller definition

      The remaining options can be left at the default

      Choose OK.

4. Add a new Remote APPC LU off the connection by choosing the Insert button and entering the following parameters:

      LU Alias     = For simplicity, this should be the same as the Remote APPC LU Name below.

      Network Name = APPN (or remote network id RMTNETID value on the AS/400)

      LU Name      = Must be set to the AS/400 local control point name (set in the AS/400 Display Network Attributes screen).

      Uninterpreted LU Name = Not used (leave at default).

      Select Supports Parallel Sessions (required).

      Zoom on the Partners button. The Remote APPC LU must be partnered with the Local APPC LU created above, using the QPCSUPP mode. Because Enable Automatic Partnering is enabled by default for APPC LUs, this pairing will already be added.

   Choose OK.

5. Save the SNA Server configuration file and restart the SNA Server service. Once the SNA Server service is Active, all connections configured to activate on server startup will go into a Pending state, then switch to Active.

   NOTE: If the connection stays in Pending mode and doesn't activate:

   a. Check the Windows NT application event log (using Event Viewer) to see the reason why the connection isn't activating. If the SDLC link service isn't activating, check the system event log for any entries logged by the IBMSYNC driver (indicating possible hardware conflicts), or the Service Control Manager (indicating why the link service was unable to start).

   b. Double check the configuration entries above with your AS/400 system administrator and make sure the AS/400 line is active. If all appears okay, check the SNA Server controller description on the AS/400.

   c. Check if the AS/400 is logging any errors when SNA Server attempts to establish the connection.

   d. If the connection activates but users are unable to open 5250 sessions, zoom on the Status button on the Local APPC LU, which should show the following (when working correctly):

     Partner LU           Mode            Connection     Sessions        Limit

     <remote LU>     SNASVCMG  <connection>    0               2

     <remote LU>     QPCSUPP      <connection>    0               64

     This means that up to 64 sessions are available for use, though no sessions are currently active.

At this point, a 5250 user can then open any valid APPC LU/LU pair supported by any SNA Server in the domain. However, to simplify 5250 user access through SNA Server, there are various options available to an SNA Server administrator and the 5250 user, including the following:

 - Default AS/400 session for a user: On the SNA Server user/group record,the administrator can define default local and remote APPC LUs. If defaults are configured, and the 5250 applet is used, this is the LU/LU pair the 5250 user opens when the 5250 applet local and partner APPC LU names are left blank.

 - If default APPC LUs are not preassigned to a user/group, here is how to configure pools of Local APPC LUs and Remote (partner) APPC LUs to simplify 5250 user access to one or more AS/400's supported by SNA Server:

   Local APPC LU pool: Define the Local APPC LU as a "Member of Default Outgoing Local APPC LU Pool". If a 5250 user does not enter a Local APPC LU when opening a session, the user accesses one of the available Local LUs in this pool.

   Remote APPC LU pool: The Remote APPC LU pool is determined by the Remote LUs which are partnered with the Local APPC LU and the QPCSUPP mode. So if a Local APPC LU is specified, but the Remote APPC LU is left blank, a 5250 session is allocated from an available Remote APPC LU that it is partnered with.

SAMPLE CONFIGURATION SETTINGS

=============================

The following AS/400 configuration screens are shown below, along with their corresponding configuration setting for SNA Server (see comments which are preceded with "****" below). This includes the AS/400 network attributes screen, SDLC (switched) line description, APPC controller, and virtual device description. Many of the configuration settings are not relevant for communications to function, though are shown here for completeness.

AS/400: Display Network Attributes                       System:   OLYMPIA

 Current system name  . . . . . . . . . . . . . . :   OLYMPIA

   Pending system name  . . . . . . . . . . . . . :

 Local network ID . . . . . . . . . . . . . . . . :   APPN

**** Must match the remote network name on the SNA Server connection.

 Local control point name . . . . . . . . . . . . :   OLYMPIA

**** Must match the remote control point name on the SNA Server connection.

 Default local location . . . . . . . . . . . . . :   OLYMPIA

 Default mode . . . . . . . . . . . . . . . . . . :   BLANK

 APPN node type . . . . . . . . . . . . . . . . . :   *ENDNODE

 Maximum number of intermediate sessions  . . . . :   200

 Route addition resistance  . . . . . . . . . . . :   128

 Server network ID/control point name . . . . . . :   APPN        REDHOOK

 Alert status . . . . . . . . . . . . . . . . . . :   *OFF

 Alert logging status . . . . . . . . . . . . . . :   *NONE

 Alert primary focal point  . . . . . . . . . . . :   *NO

 Alert default focal point  . . . . . . . . . . . :   *NO

 Alert backup focal point . . . . . . . . . . . . :

   Network ID . . . . . . . . . . . . . . . . . . :     *NONE

 Alert focal point to request . . . . . . . . . . :

   Network ID . . . . . . . . . . . . . . . . . . :     *NONE

 Alert controller description . . . . . . . . . . :   *NONE

 Alert hold count . . . . . . . . . . . . . . . . :   0

 Alert filter . . . . . . . . . . . . . . . . . . :   *NONE

   Library  . . . . . . . . . . . . . . . . . . . :

 Message queue  . . . . . . . . . . . . . . . . . :   QSYSOPR

   Library  . . . . . . . . . . . . . . . . . . . :     QSYS

 Output queue . . . . . . . . . . . . . . . . . . :   QPRINT

   Library  . . . . . . . . . . . . . . . . . . . :     QGPL

 Job action . . . . . . . . . . . . . . . . . . . :   *FILE

 Maximum hop count  . . . . . . . . . . . . . . . :   16

 DDM request access . . . . . . . . . . . . . . . :   *OBJAUT

 PC Support request access  . . . . . . . . . . . :   *OBJAUT

 Default ISDN network type  . . . . . . . . . . . :

 Default ISDN connection list . . . . . . . . . . :   QDCCNNLANY

AS/400: Change Line Desc (SDLC) (CHGLINSDLC)

Line description . . . . . . . . LIND         > NEWLINE

 Resource names . . . . . . . . . RSRCNAME     > LIN011

                  + for more values

 Online at IPL  . . . . . . . . . ONLINE       > *NO

 Data link role . . . . . . . . . ROLE         > *NEG

 Physical interface . . . . . . . INTERFACE    > *RS232V24

 Connection type  . . . . . . . . CNN          > *SWTPP

 Vary on wait . . . . . . . . . . VRYWAIT      > *NOWAIT

 Autocall unit  . . . . . . . . . AUTOCALL     > *NO

 Exchange identifier  . . . . . . EXCHID       > 05600001

**** Must match the Local Node ID configured in the SNA Server connection.

 NRZI data encoding . . . . . . . NRZI         > *YES

**** Must match the encoding setting configured in the SNA Server connection (located under the Advanced settings).

 Maximum controllers  . . . . . . MAXCTL       > 1

 Clocking . . . . . . . . . . . . CLOCK        > *MODEM

 Line speed . . . . . . . . . . . LINESPEED    > 9600

 Modem type supported . . . . . . MODEM        > *NORMAL

 Switched connection type . . . . SWTCNN       > *BOTH

 Autoanswer . . . . . . . . . . . AUTOANS      > *YES

**** With Autoanswer=YES, the AS/400 is answering the phone, so the SNA Server connection should be set to "Allowed directions = Outgoing." Also, SNA Server should be configured as "Remote end = Peer."

 Autodial . . . . . . . . . . . . AUTODIAL     > *NO

 Calling number . . . . . . . . . CALLNBR      > *NONE

 Station address  . . . . . . . . STNADR       > C1

Connect poll retry . . . . . . . CNNPOLLRTY   > 10

 Maximum frame size . . . . . . . MAXFRAME     > 521

Duplex . . . . . . . . . . . . . DUPLEX       > *HALF

**** Matches the SNA Server SDLC connection duplex setting (located under the advanced settings).

 Inactivity timer . . . . . . . . INACTTMR     > 300

 Poll response delay  . . . . . . POLLRSPDLY   > 0

 Nonproductive receive timer  . . NPRDRCVTMR   > 320

 Idle timer . . . . . . . . . . . IDLTMR       > 30

 Connect poll timer . . . . . . . CNNPOLLTMR   > 30

 Poll cycle pause . . . . . . . . POLLPAUSE    > 0

 Frame retry  . . . . . . . . . . FRAMERTY     > 7

 Data Set Ready drop timer  . . . DSRDRPTMR    > 20

**** During our testing, the AS/400 default was too short. This may have to be set to 20 or more, depending on the modem used.

 Autoanswer type  . . . . . . . . AUTOANSTYP   > *DTR

 Remote answer timer  . . . . . . RMTANSTMR    > 60

 Text 'description' . . . . . . . TEXT         > 'SHOW DEMO LINE -

DIAL IN LINE'

                   Additional Parameters

 Modem data rate select . . . . . MODEMRATE    > *FULL

 Error threshold level  . . . . . THRESHOLD    > *OFF

 Modulus  . . . . . . . . . . . . MODULUS      > 8

 Maximum outstanding frames . . . MAXOUT       > 7

 Clear To Send timer  . . . . . . CTSTMR       > 25

 Link speed . . . . . . . . . . . LINKSPEED    > 9600

 Cost/connect time  . . . . . . . COSTCNN      > 128

 Cost/byte  . . . . . . . . . . . COSTBYTE     > 128

 Security for line  . . . . . . . SECURITY     > *NONSECURE

 Propagation delay  . . . . . . . PRPDLY       > *TELEPHONE

 User-defined 1 . . . . . . . . . USRDFN1      > 128

 User-defined 2 . . . . . . . . . USRDFN2      > 128

 User-defined 3 . . . . . . . . . USRDFN3      > 128

 Recovery limits:                 CMNRCYLMT

   Count limit  . . . . . . . . .              > 2

   Time interval  . . . . . . . .              > 5

AS/400: Change Ctl Desc (APPC) (CHGCTLAPPC)

**** NOTE: the Exchange ID for the controller set in LINE definition above.

 Controller description . . . . . CTLD         > TRUTH

 Online at IPL  . . . . . . . . . ONLINE         *NO

 APPN-capable . . . . . . . . . . APPN           *YES

 Switched line list . . . . . . . SWTLINLST      SHOW

                  + for more values

 Character code . . . . . . . . . CODE           *EBCDIC

 Maximum frame size . . . . . . . MAXFRAME       521

**** Inherited from the SDLC line definition. For best performance, this setting should match the Max BTU Length setting on the SNA Server SDLC connection (located under the Advanced settings).

Remote network identifier  . . . RMTNETID       APPN

**** Must match the network name configured on SNA Server (set using Admin when zooming on the server name), as well as the network name configured on the Local APPC LU.

 Remote control point . . . . . . RMTCPNAME      TRUTH

**** Must match the local control point name configured on SNA Server (set using Admin when zooming on the server name), as well as the LU name of the Local APPC LU.

 SSCP identifier  . . . . . . . . SSCPID         *SAME

 Initial connection . . . . . . . INLCNN         *ANS

 Dial initiation  . . . . . . . . DIALINIT       *SAME

 Connection number  . . . . . . . CNNNBR         *SAME

 Predial delay  . . . . . . . . . PREDIALDLY     6

 Redial delay . . . . . . . . . . REDIALDLY      120

 Dial retry . . . . . . . . . . . DIALRTY        2

 Switched disconnect  . . . . . . SWTDSC         *YES

**** If this is YES, then the AS/400 will drop the link when there are no active APPC sessions, so the SNA Server connection should be configured to activate On Demand. Otherwise, if SWTDSC is set to NO, the SNA Server connection should be configured to activate On Server Startup.

 Disconnect timer:                DSCTMR

   Minimum connect timer  . . . .                600

**** AS/400 default is 170 sec. AS/400 drops the connection after this time-out when there are no active APPC sessions.

Disconnection delay timer  . .                0

 Station address  . . . . . . . . STNADR         C1

**** Inherited from the line description. Must match the poll address configured in the SNA Server connection (located in the Advanced dialog).

 SDLC poll priority . . . . . . . POLLPTY        *NO

 SDLC poll limit  . . . . . . . . POLLLMT        0

 SDLC out limit . . . . . . . . . OUTLMT         *POLLLMT

 SDLC connect poll retry  . . . . CNNPOLLRTY     7

 SDLC NDM poll timer  . . . . . . NDMPOLLTMR     *CALC

 APPN CP session support  . . . . CPSSN          *YES

 APPN node type . . . . . . . . . NODETYPE       *ENDNODE

 APPN transmission group number   TMSGRPNBR      1

 APPN minimum switched status . . MINSWTSTS      *VRYONPND

 Autodelete device  . . . . . . . AUTODLTDEV     1440

 User-defined 1 . . . . . . . . . USRDFN1        *LIND

 User-defined 2 . . . . . . . . . USRDFN2        *LIND

 User-defined 3 . . . . . . . . . USRDFN3        *LIND

 Recovery limits:                 CMNRCYLMT

   Count limit  . . . . . . . . .                2

   Time interval  . . . . . . . .                5

 Text 'description' . . . . . . . TEXT           'Show controller for Demo

                                                 dial-in.'

AS/400: Change Device Desc (APPC) (CHGDEVAPPC)

Device description . . . . . . . DEVD         > TRUTH03

**** This device name corresponds with the SNA Server Local APPC LU name (in this case, TRUTH), plus a two-digit device number, generated by the AS/400 (but not configured in SNA Server).

 Online at IPL  . . . . . . . . . ONLINE         *NO

 Mode . . . . . . . . . . . . . . MODE           *NETATR

                  + for more values

 Message queue  . . . . . . . . . MSGQ           QSYSOPR

   Library  . . . . . . . . . . .                  *LIBL

 Local location address . . . . . LOCADR         00

 Single session:                  SNGSSN

   Single session capable . . . .                *NO

   Number of conversations  . . .

 Locally controlled session . . . LCLCTLSSN      *SAME

 Pre-established session  . . . . PREESTSSN      *SAME

 Text 'description' . . . . . . . TEXT           'AUTOMATICALLY CREATED

                                                 BY QLUS'

 Mode description . . . . . . . . MODD         > QPCSUPP

**** This should not be changed; this is the default mode name for IBM PC Support clients (and SNA Server).

 Class-of-service . . . . . . . . COS            #CONNECT

 Maximum sessions . . . . . . . . MAXSSN         64

**** This is the number of sessions supported by the QPCSUPP mode, and should match the SNA Server session limit configured on the QPCSUPP mode entry, configured using the SNA Server setup program (zoom on Local or Remote LU, zoom on Partners button, then select the Modes button).

 Maximum conversations  . . . . . MAXCNV         64

**** This should match the MAXSSN setting above.

 Locally controlled sessions  . . LCLCTLSSN      16

 Pre-established sessions . . . . PREESTSSN      0

 Inbound pacing value . . . . . . INPACING       7

 Outbound pacing value  . . . . . OUTPACING      7

 Maximum length of request unit   MAXLENRU       *CALC

 Text 'description' . . . . . . . TEXT           'created by <name>'

Additional reference words: prodsna 2.00

KBCategory: kbtool

KBSubCategory: ntutil SNA


Q131624: Connecting to a remote AS/400 connected via an APPN network

Connecting to a remote AS/400 connected via an APPN network   [winnt]

ID: Q131624    CREATED: 14-JUN-1995   MODIFIED: 14-JUN-1995

2.00 2.10

WINDOWS

PUBLIC |

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

------------------------------------------------------------------------

SUMMARY

=======

This article describes how to configure SNA Server to talk to a remote AS/400, connected as follows:

  SNA Server <--->  AS/400  <- (appn) ->  AS/400

  (SNASERV)        (AS400A)              (AS400B)

For users to connect to AS400B through SNA Server, SNA Server should be configured with two Remote APPC LU's (AS400A and AS400B) off a single 802.2 connection to AS400A.  Users can then open sessions to AS400B by requesting the AS400B remote LU name.

Refer to Q112158 or Q112159 for complete configuration examples showing how SNA Server can be configured to communicate with an AS/400.

NOTE: SNA Server should only be configured with a single 802.2 connection to an AS/400.  SNA Server dual connections to the same AS/400 will not work, since the AS/400 only supports a single APPC controller definition per control point, and SNA Server (acting as a LEN node) can only be configured with a single local control point name.

MORE INFORMATION

================

In some network configurations, it may not be practical for SNA Server to have a direct SNA link to an AS/400.  In cases where a remote AS/400 is accessible through a locally accessible AS/400 acting as an APPN network node, SNA Server can be configured to access the remote AS/400.

Referring to the diagram above, here is how SNA Server could be configured to support user access to both AS/400's.  Using an 802.2 connection as an example:

Server Properties

  Local network name        = APPN

  Local control point name  = SNASERV

Local APPC LU Properties: SNASERV

  LU 6.2 type = Independent

  LU alias            = SNASERV

  network name        = APPN

  LU name             = SNASERV

Connection Properties:  TOKEN1

  Remote end = peer system

  Remote network address    = < address of AS400A >

  Remote network name       = APPN

  Remote control point name = AS400A

Remote APPC LU Properties: AS400A   (used to access AS400A)

  LU alias            = AS400A

  network name        = APPN

  LU name             = AS400A

  Supports parallel sessions

  Partners:

  Partner LU = SNASERV, Mode = QPCSUPP, Connection: TOKEN1

Remote APPC LU Properties: AS400B   (used to access AS400B)

  LU alias            = AS400B

  network name        = APPN

  LU name             = AS400B

  Supports parallel sessions

  Partners:

  Partner LU = SNASERV, Mode = QPCSUPP, Connection: TOKEN1

To open a session to AS400B, the SNA Server user should request Local LU alias of SNASERV, and a remote LU alias of AS400B.

KBCategory: kbnetwork kbusage

KBSubcategory: ntnetserv   ntconfig nthowto

Additional reference words: prodsna 2.00 2.10 3.50


Q131625: Multiple connections to same AS/400 are not supported

Multiple Connections to the Same AS/400 Are Not Supported     [winnt]

ID: Q131625    CREATED: 14-JUN-1995   MODIFIED: 15-JUN-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

------------------------------------------------------------------------

SUMMARY

=======

While SNA Server does support one or more connections to the same host system (see Q107192), the AS/400 doesn't support more than one concurrent connection from SNA Server (acting as a LEN node), over any link type (802.2 Token Ring, Ethernet, SDLC, or X.25).

To increase the number of sessions from SNA Server to an AS/400, multiple local APPC LU's can be defined and partnered with the AS/400's remote APPC LU, or the QPCSUPP mode's session limit can be increased in both SNA Server and the AS/400. For more information on this, see Q126395.

MORE INFORMATION

================

For SNA Server to connect to an AS/400, an APPC controller definition must exist for SNA Server's local control point name. The APPC controller may be autocreated by the AS/400, or manually created by the AS/400 administrator.

The AS/400 allows only a single APPC controller, with a given control point name, over any line it supports. If two connections are defined in SNA Server to the same AS/400 (i.e. two 802.2 connections, or one 802.2 and one SDLC, etc.), the AS/400 rejects the second connection request unless the first APPC controller definition is deleted.

SNA Server 2.x can only be configured with one local control point name (configured in SNA Admin from the Session Properties dialog box).

For 802.2 connections, the AS/400 allows only a single APPC controller to have a specific network adapter address. So, if an SNA Server connects to an AS/400 with one local control point name configured (over an 802.2 connection), and the local control point name is later changed, the AS/400 will refuse the connection attempt with the new name since an APPC controller definition already exists with the same network adapter address.

KBCategory: kbnetwork

KBSubcategory: ntnetserv ntconfig

Additional reference words: prodsna 2.00 2.10


Q112635: Over-the-network installation of SNA client over Netware

SNA Server NetWare Client Setup                               [winnt]

ID: Q112635    CREATED: 15-MAR-1994   MODIFIED: 11-OCT-1994

2.00

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

--------------------------------------------------------------------------

You can install SNA Server client files on a Novell NetWare workstation by doing one of the following:

 - Install from the SNA Server client disks.

   -or-

 - Install from a NetWare file server.

To set up the SNA Server client files on a Novell NetWare file server:

1. Map a Novell client workstation drive on the NetWare server.

2. Tree copy (XCOPY A:\*.* <net drive>:*.* /S) all the SNA Server client files from the SNA Server client disks to the mapped drive on the NetWare server.

Use this mapped drive for any further NetWare client installations.

The Novell product included here is manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional reference words: prodsna 2.00

KBCategory: kbnetwork

KBSubcategory: ntnetserv


Q113349: Client files for Windows 3.x and Terminal Emulators

Client Files for Windows 3.x and Terminal Emulators           [winnt]

ID: Q113349    CREATED: 03-APR-1994   MODIFIED: 28-FEB-1995

2.00

WINDOWS

PUBLIC | kb3rdparty

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT version 2.0

----------------------------------------------------------------------

Specific files and WIN.INI settings are required when you use independent vendor Windows-based terminal emulators with SNA Server for Windows NT.

MORE INFORMATION

================

The following executable files should be located in the <snaroot> directory (where <snaroot> means the directory where your SNA Server for Windows NT client software is installed). Verify the <snaroot> directory is in the path statement in your AUTOEXEC.BAT file or put the files in a directory that is in the path.

   WNAP.EXE     - SNA Windows client.

   WPOPUP.EXE   - Displays popup messages if errors occur.

   SNAVER.EXE   - Displays the version of SNA Server client components (optional).

   WSHOWMEM.EXE - Displays the internal memory tables and settings for diagnostic purposes (optional).

The following dynamic-link library (DLL) files should be located in the <winroot>\system directory (where <winroot> means the directory where your Windows 3.x, or Windows for Workgroups 3.xx software is installed).

DLL's for a Novell Netware Network

----------------------------------

   NWCLI.DLL    - SNA client interface for Netware.

   NWNETAPI.DLL - Netware Application Programming Interface (API).

   NWIPXSPX.DLL - Netware IPX/SPX interface.

DLL's for a LAN Manager or Windows for Workgroups Network

---------------------------------------------------------

   LMCLI.DLL    - SNA client interface for LAN Manager/WFW.

Other DLL's

-----------

   WDMOD.DLL    - SNA client interface used by WNAP, SNA API's and third-party vendors using the Emulator Interface Specification (EIS).

   WLOGTR.DLL   - Required for logging and trace formatting.

   TOOLHELP.DLL - Used by WNAP to determine if an SNA Server client application has ended.

   WINTRC.DLL   - For message tracing when debugging (optional).

   CTL3D.DLL    - For 3D support. Required by SNAVER.EXE and by SNA Server for Windows NT 3270 and 5250 applets.

   YMGR.DLL     - Yield manager. Required for applications using the DCA/Microsoft Communications Server APPC API.

DLL's for 5250 Terminal Emulation

---------------------------------

   WINAPPC.DLL  - APPC API support for transaction verbs (see Chapter 4 of the "APPC Programmer's Guide").

   WINCSV.DLL   - Common Service Verbs API support.

DLL's for SNA API Support

-------------------------

NOTE: Specific DLL files are required for SNA applications which use specific API's.

   WINSLI.DLL   - LUA Session Level Interface API support.

   WINRUI.DLL   - LUA Request Unit Interface API support.

   WINCPIC.DLL  - CPI-C API support.

   WINMGT.DLL   - APPC Management Verb API support (see Chapter 3 of the "APPC Programmers Guide").

You also need to verify that the following entries are in the [Wnap] section of the client's WIN.INI file:

   WBinPath=<snaroot>

   Remote= [ <Netware domain name> | <SNA Server computer name>]

      For a Netware network, this must be set to the domain name where the SNA Server for Windows NT computer is running.

      -or-

      For a LAN Manager or Windows for Workgroups network, this entry is optional unless the client is located in a different domain than the SNA Server for Windows NT server. If this is the case, it must be set to the SNA Server for Windows NT computer name.

   NosType= [ LANMAN | NETWARE ] (Type of Network)

   NosSetup= [ LANMAN | WFW | NETWARE ] (Type of client)

   NetSetup=NO

This is an example of a [Wnap] section of the WIN.INI file for Windows for Workgroups client on a LAN Manager network in the same domain as the SNA Server for Windows NT server:

   [Wnap]

   WBinPath=C:\SNA

   Remote=

   NosType=LANMAN

   NosSetup=WFW

   NetSetup=NO

The Novell Netware products included here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional reference words: wfw wfwg prodsna 2.00

KBCategory: kb3rdparty

KBSubcategory: ntutil


Q118365: Host printer emulation data flow through SNA Server

Host Printer Emulation Data Flow Through SNA Server           [winnt]

ID: Q118365    CREATED: 17-JUL-1994   MODIFIED: 02-NOV-1994

2.00

WINDOWS

PUBLIC | kbprint kbnetwork

---------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

---------------------------------------------------------------------------

SUMMARY

=======

The Microsoft SNA Server version 2.0 package supports Logical Unit (LU) types 1 and 3, though it does not include a host print emulator. However, several third-party companies do support print emulation that works through SNA Server; these products are listed in the Companion Product Catalog included with the SNA Server product. This article describes how host print data flows through SNA Server when these third-party products are being used.

NOTE: The latest companion product catalog can be found on Lib #2 of the MSSNA forum on CompuServe, or on the Microsoft Internet server (ftp.microsoft.com) under the BUSSYS/SNASRVR/DOCS directory.

MORE INFORMATION

================

Before describing how host print data flows between the host, SNA Server, and print emulator, the following components must be configured:

 - VTAM (host) is configured with printer Logical Units (LU) off a physical unit (PU) definition. Also, users are defined at the host to have access to print host application data/files to this printer LU.

 - SNA Server is configured with a connection to the host, emulating this PU and 3270 LUs (including a printer LU). A local area network (LAN)-based user is assigned access to the printer LU in the SNA Server Admin program.

 - A third-party print emulator is run under the user context of the LAN user who has been assigned access to the printer LU. Also, the third-party emulator is configured to route the print data to a PC printer (for example, LPT1, or redirected LPT1 to a Windows NT print queue, which may be configured to print to a LAN-attached printer through Windows NT Print Manager).

Here's how the host print data flows:

 - A host user, using his host application on a 3270 terminal (or 3270 emulator), sends a host print job to the printer LU.

 - The host sends the print data to the printer LU, which flows to SNA Server over the SNA Server link. SNA Server then sends the data to the third-party print emulator (which is emulating a host printer -- the third-party emulator already has activated the printer LU session). The print emulator may be running on the same computer as SNA Server, or on any SNA Server client computer that is communicating through the server (over any client/server LAN connection type supported by SNA Server).

 - The third-party host print emulator converts the host print data (and performs any additional formatting, as supported by the emulator), and sends the data to the PC print destination (that is, redirected LPT1 port). Using print redirection, this printer destination can be a Windows NT print queue, as supported by the underlying network software.

 - The Windows NT print queue sends the print job to the printer, which can be a network-attached printer as supported by Windows NT Print Manager.

Additional reference words: prodsna 2.00 3287 SNA print emulation

KBCategory: kbprint kbnetwork

KBSubcategory: ntprint


Q118498: Session error 2574 in 3270 applet

Session Error 2574 in 3270 Applet                             [winnt]

ID: Q118498    CREATED: 20-JUL-1994   MODIFIED: 07-OCT-1994

2.00

WINDOWS

PUBLIC | kbtool

---------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

---------------------------------------------------------------------------

SYMPTOMS

========

The SNA Server applet generates a Session Error 2574 when you attempt to establish a connection with an SNA Server.

CAUSE

=====

This error may occur if the 3270 applet is trying to connect to an LU Pool that is defined on the SNA Server and that LU Pool doesn't have any Lus assigned to it. If you start SNA Server Admin and put the focus on the LU Pools windows, a "No Assigned LUs" message may be in the right side of the window.

RESOLUTION

==========

To correct this error, add LUs to the LU Pool that the 3270 Applet is trying to establish a connection to. Also, changing an LU Pool definition requires that all affected SNA Servers be restarted to pick up the configuration change. In SNA Server Admin, all affected servers will appear as "Active [Out of Date]" to indicate that the server needs to be restarted for the configuration change to take effect.

Additional reference words: prodsna 2.00

KBCategory: kbtool

KBSubCategory: ntutil


Q118965: Wall Data Rumba for the AS/400 GP fault in 5250 session

Wall Data Rumba for the AS/400 GP Faults in 5250 Session      [winnt]

ID: Q118965    CREATED: 03-AUG-1994   MODIFIED: 14-JAN-1995

2.00

WINDOWS

PUBLIC | kb3rdparty

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

-----------------------------------------------------------------------

SYMPTOMS

========

When you attempt to launch a 5250 session in Wall Data Rumba for the AS/400, an "Interface not found" message appears followed by a general protection (GP) fault in the SNASRV.EXE module.

CAUSE

=====

This problem occurs when the WDMICOMM.EXE file in Wall Data Rumba doesn't wait long enough for the SNA Server Windows client (WNAP.EXE) to initialize.

STATUS

======

Wall Data has confirmed this to be a problem with Rumba. For more information, please call Wall Data Technical at (800) 927-8622.

Wall Data Rumba is manufactured by Wall Data, Inc., a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional reference words: prodsna 2.00 third-party 3rdparty thirdparty gpf

KBCategory: kb3rdparty

KBSubcategory: nt16ap


Q119653: VTAM 3.4.2 PTF UY97878 solves LU6.2 problem

VTAM 3.4.2 PTF UY97878 Solves LU6.2 Problem                   [winnt]

ID: Q119653    CREATED: 20-AUG-1994   MODIFIED: 07-OCT-1994

2.00

WINDOWS

PUBLIC | KBhw

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

----------------------------------------------------------------------

SYMPTOMS

========

When you activate and use independent LU6.2 sessions through an IBM 3172 interconnect controller (configured as an external adapter) attached to VTAM version 3.4.2, the LU6.2 session may hang or APPC allocation errors may occur.

SNA Server does not encounter these problems when communicating through an IBM 37x5 front end processor, to VTAM 3.4.2.

RESOLUTION

==========

This problem is solved when you apply IBM PTF #UY97878, which includes an update to VTAM 3.4.2, when VTAM is implementing a boundary function. Contact IBM to request this update.

The IBM product discussed here is manufactured by International Business Machines Corp. (IBM), a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

MORE INFORMATION

================

This customer reporting the failure was connecting SNA Server over Token Ring through an IBM 3172 interconnect controller, attached to VTAM v3.4.2. When attempting to activate independent LU6.2 sessions between SNA Server and the host (for use with the Micro Decisionware DB2 Database Gateway), the host would fail to respond to the SNA Server Attach message during SNASVCMG mode bind processing (where the SNASVCMG mode pacing window is set to 1 by default).

An SNA trace shows that the host fails to provide pacing responses to SNA Server. Once SNA Server has exhausted our send window size (as negotiated in the bind), the host fails to provide an Isolated Pacing Response (IPR) so SNA Server is unable to send any further data on the LU6.2 application session.

Configuring both ends with an LU6.2 pacing window of 0 (both on the SNASVCMG mode and the application mode) may temporarily solve the problem, though is not recommended.

Additional reference words: prodsna 3.10

KBCategory: KBhw

KBSubCategory: nthw


Q121420: IBM 3174 Support C 5.0 causes negative bind response

IBM 3174 Support C - Rel. 5.0 Causes Negative Bind Response   [winnt]

ID: Q121420    CREATED: 04-OCT-1994   MODIFIED: 13-OCT-1994

2.00 2.10

WINDOWS

PUBLIC |

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

----------------------------------------------------------------------

SYMPTOMS

========

In the event that the Customer Information Control System (CICS) region goes down, CICS will attempt to renegotiate the LU 6.2 SNASVCMG mode sessions as the first step in getting the connection back to an active state. It does this by sending down bind requests to SNA Server. When talking through a 3174 Establishment Controller running Configuration Support C - Release 5.0, SNA Server may reject these bind requests which will cause the sessions, and therefor the connection, to stay in a pending state.

RESOLUTION

==========

Downgrade to 3174 Establishment Controller Configuration Support C - Release 3.0. There may be other resolutions that also correct this problem. Release 3.0 corrected one customer's case.

Additional reference words: 2.1 2.0 prodsna

KBCategory: kbnetwork

KBSubcategory: ntnetserv


Q121614: SNA Server Banyan client not connecting over TR bridge

SNA Server Banyan Clients from Connecting Across TR Bridge    [winnt]

ID: Q121614    CREATED: 12-OCT-1994   MODIFIED: 05-DEC-1994

2.10

WINDOWS

MSONLY | kbnetwork kb3rdparty

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1.

----------------------------------------------------------------------

SYMPTOMS

========

When you attempt to start WNAP.EXE on a Banyan Vines client to an SNA Server running the Banyan Vines redirector, the client may receive return code 177. This only occurs when there is a Token Ring bridge between the client and the SNA Server computer. Moving the client onto the same ring as the SNA Server corrects the problem, though this is not a feasible solution in most cases. Return Code 177 is a Banyan Vines message that translates to the following:

   177 - BYRDISC: VINES SPP terminates an SPP virtual connection. Causes

   can involve LAN failures, lack of sufficient communications buffers, or

   an insufficient limit on the number of concurrent SPP connections.

CAUSE

=====

Banyan Vines has confirmed this problem to occur with one of the following configurations:

 - Windows NT version 3.5 running the Banyan Vines Early Release Program (EAP) redirector (DAYTONA3.ZIP).

   NOTE: The Banyan redirector EAP (Early Access Program) for Daytona is an unreleased product.

   -or-

 - Windows NT version 3.1 running the shipping version of the Banyan Vines redirector for Windows NT 3.1 without applying the NTSLR.ZIP patch file from Banyan.

RESOLUTION

==========

The respective resolutions for the above causes are:

 - Wait for DAYTONA4.ZIP and apply it to Windows NT version 3.5 using the instructions included. It will be posted to the BOA BBS in the near future.

   -or-

 - Apply NTSLR.ZIP to Windows NT 3.1. It can also be found on the BOA BBS.

The BOA BBS number is (508) 836-1834. To get to the Daytona section, from the main menu, choose (S)cripts, and then (D)ownload.

The Banyan products discussed here are manufactured by Banyan Systems, Inc., a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional reference words: ntprotocol prodsna 2.1

KBCategory: kbnetwork kb3rdparty

KBSubcategory: ntdistrib


Q121615: NCP Requirements for LU6.2

NCP Requirements for LU 6.2                                   [winnt]

ID: Q121615    CREATED: 12-OCT-1994   MODIFIED: 14-OCT-1994

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0 and 2.1

----------------------------------------------------------------------

The SNA Server 2.1 Data Sheet (<CD-ROM ROOT>\COLLATRL\GENERAL\DATASHET.DOC) lists the following system requirement for Network Control Program (NCP):

   NCP version 5 release 2.1 or later

This requirement is only relevant for mainframe LU 6.2 configurations. There are no known NCP version requirements for host 3270 configurations.

Additional reference words: prodsna 2.00 2.10

KBCategory: kbnetwork

KBSubCategory: ntdistrib


Q130854: Automating the SNA Server Win 3.x client login process

Automating the SNA Server Win 3.x Client Login Process        [winnt]

ID: Q130854    CREATED: 30-MAY-1995   MODIFIED: 02-JUN-1995

2.10 2.11

WINDOWS

PARTNER | kbnetwork kbsetup kbinterop

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.1 and 2.11

--------------------------------------------------------------------------

SUMMARY

=======

When the SNA Server Windows 3.x client software is configured to use TCP/IP sockets, Netware IPX/SPX, or Banyan IP (any client-server transport except named pipes), the SNA client software (WNAP) uses a separate user login to the Windows NT servers running SNA Server to ensure security is maintained. This article describes ways to automate this client login process using SNA Server versions 2.1 and 2.11.

SNA Server 2.1

--------------

When you log into Windows NT Server using TCP/IP, Netware IPX/SPX or Banyan IP from Windows 3.x clients, the two WNAP command lines noted below can be used to remove the Domain Login dialog box when starting WNAP manually.

Add an icon in the Windows Startup group for WNAP.EXE (the SNA Windows 3.x client process) that has the following command line option. This causes WNAP to start automatically when Windows is started:

   WNAP /USER: /PWD:

NOTE: The must be no space after the semi-colon (:).

This command lets the user login to the Windows NT Server using the guest account (provided that the guest account is enabled and has no password).

The next command requires that the user have a valid account in the Windows NT/SNA Server domain:

   WNAP /USER:<userid> /PWD:<password>

SNA Server 2.11

---------------

The following additional options are available under SNA 2.11:

1) The following two new options can be added to the [WNAP] section of the WIN.INI file:

      LogonUserName=<USERID>

      LogonPassword=<PASSWORD>

   WNAP will parse these entries and use them when a  application is first started, reducing the need for starting WNAP manually with command line parameters.

   Also, to use the guest account using the parameters in WIN.INI, add the entries as such:

      LogonUserName=guest

      LogonPassword=

NOTE: The must be no space after the equals sign (=).

2) Automated use of Windows for Workgroups 3.11 cached domain password.

If the above WIN.INI entries are not present on a Windows for Workgroups 3.11 client, and if the user is using the cached domain password feature of Windows for Workgroups (enabled in the network Control Panel Startup dialog box by selecting "Log On to Windows NT or LAN Manager Domain"), the user password is automatically retrieved from Windows for Workgroups.

WNAP will start automatically when an SNA Server application (3270, 5250, or an application written to the SNA Server APIs is started), or when Windows is started (if a WNAP icon is added to the Startup group). If the cached domain password method is used, WNAP retrieves the username when WNAP is started. If the Windows for Workgroups user logs off and on, WNAP is still running under the previous user context.

To resolve this problem, WNAP can be configured to terminate automatically when the last SNA application ends by adding AutoTerminate=Yes  to the [WNAP] section of the WIN.INI file. By default, WNAP remains running even if the Windows for Workgroups user logs off and then logs back on. The user should quite all SNA applications before logging off in Windows for Workgroups. This ensures that WNAP will quit so that it will be restarted again when the new Windows for Workgroups user logs in and starts an SNA

application.

To enable the AutoTerminate feature:

1. Add AutoTerminate=Yes to the [WNAP] section of the WIN.INI file.

2. Start WNAP automatically by starting an SNA application. If WNAP is started manually, WNAP will not unload, even if AutoTerminate is set to Yes.

With some emulators the WNAP will quit when the last connection is disconnected. With other emulators you need to exit from the emulator. This behavior depends on how the emulator is implemented. With the SNA Server applets the WNAP won't unload before you exit from the applet.

Windows for Workgroups Domain Password Expiration

-------------------------------------------------

If the Windows for Workgroups user's domain password expires, or if user is required to change their domain password on the next domain login attempt, the SNA client login dialog will fail with Error 546. To solve this problem, the Windows for Workgroups user must login and change their domain password first. The user may then need to update their SNA client configuration to reflect their new password. There is no additional user interaction required when using the Windows for Workgroups cached domain password.

KBCategory: kbnetwork kbsetup kbinterop

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.1 2.11


Q122552: SNA Server Error 629 or 546 when using Network Client Interface

SNA Server Error 629 or 546 when using Network Client Interface[winnt]

ID: Q122552    CREATED: 07-NOV-1994   MODIFIED: 12-JUN-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

----------------------------------------------------------------------

SYMPTOMS

========

When you use the SNA Server Windows 3.x client software configured to use the SNA Server Microsoft Networking (Named Pipes) Interface, the SNA client component (WNAP.EXE) may fail to start and the following error messages may appear (using both the 5250 emulator and 3270 emulator):

Using 5250 Emulator

-------------------

   SNA Server Error: 629  No SNA Server configuration broadcast received

   -or-

   SNA Server Error: 546  Cannot establish connection with SNA Server

   <servername>.

Using 3270 Emulator

-------------------

   SNA Server Error: 629  No SNA Server configuration broadcast received

   -or-

   SNA Server Error: 546  Cannot establish connection with SNA Server

   <servername>.

   Error: The NAP is not started.

NOTE: When these error messages appear, the SNA Server client icon (WNAP.EXE) is gray when it loads at the bottom of the screen, and it disappears when the error messages appear.

CAUSE

=====

Error 629 occurs when the client cannot find an SNA Server in the local domain.

Each of the following can cause error 546:

 - You are using Windows for Workgroups 3.11 and the computer is configured to use Microsoft IPX/SPX compatible transport (the default).

 - The client cannot open a session to the server.

 - You do not have access rights on the Windows NT server.

Using Windows for Workgroups 3.11 and Microsoft IPX/SPX Compatible Transport to Access a Windows NT Server

------------------------------------------------------------------

For for complete details about the problem using Windows for Workgroups 3.11 and IPX/SPX compatible transport to access a Windows NT 3.5 server, query on the following words in the Microsoft Knowledge Base (to find Q123255):

   SNA and 546 and NWLINK

Client Cannot Open a Session to the Server

------------------------------------------

If you select the Remote Domain option while installing the SNA Server client, you are prompted to enter the primary or backup SNA Server name. If the client cannot open a session to one of these SNA Servers (for example, if the server name was not entered correctly, or if an underlying network connection problem exists), the SNA client displays error 546.

The Client Does Not Find an SNA Server in the Domain

----------------------------------------------------

When the SNA Server client software is configured to use the Local Domain option, the client software sends a NetBIOS broadcast message to the domain and listens for a broadcast response from any server in the domain. If the client's workgroup name and/or domain name is different than the domain name of the SNA Server, the server will not see this message. On a Windows for Workgroups client, ensure that the Enterprise Network option to Log on to Windows NT or LAN Manager Domain is selected in the Networks option in Control Panel, and that the Domain name is correct. In addition, if the client and server are separated by a router, and this router does not pass NetBIOS broadcasts (such as with an IP router), this will also fail.

The User Does Not Have Access Rights on the Windows NT Server

-------------------------------------------------------------

Once the client computer locates the server, the SNA Server client software attempts to open a named pipe session with the server. If the user does not have rights to open a session to the server, the open request fails.

NOTE: The cause of the error messages above is different when the system runs on NetWare IPX/SPX, Banyan IP, or TCP/IP. Refer to the appropriate documentation describing possible causes of this error when you are using these other SNA Server client connection options.

RESOLUTION

==========

To correct this problem, do the following:

 - If the client does not find an SNA Server in the local domain, run the SNA Server client setup program and configure the client for the Remote Domain option, and provide the name of an SNA Server in the domain you want to connect to.

   NOTE: When connecting over TCP/IP and there is a router separating the SNA Server and the client, the Windows for Workgroups computer requires a method of resolving NetBIOS names to an IP address. If you are using the real mode TCP/IP stack, an LMHOSTS file or a WINS server may be used. (To use the WINS server with the real mode stack, you must be using the real mode TCP/IP stack shipped with Windows NT version 3.5.)

 - If the user does not have access rights on the Windows NT server, grant the user access to the Windows NT computer where SNA Server is running. You can do this either through a specific user account or by enabling the Guest account.

 - If Windows for Workgroups 3.11 is being used and the Microsoft IPX/SPX compatible transport is installed, add "Directhost=no" (without the quotation marks) to the [network] section of SYSTEM.INI file on the Windows for Workgroups 3.11 client computer, and then reboot the computer.

The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional reference words: wfw wfwg prodsna 2.00 2.10

KBCategory: kbnetwork

KBSubcategory: ntconfig ntinterop


Q123004: Remotely administering SNA Server traces

Remotely Administering SNA Server Tracing                     [winnt]

ID: Q123004    CREATED: 17-NOV-1994   MODIFIED: 22-NOV-1994

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

----------------------------------------------------------------------

SUMMARY

=======

Microsoft SNA Server includes an SNATRACE tool (Win32 utility), installed into the Microsoft SNA Server (Common) program group, to allow an administrator to dynamically turn off/on all types of server-side (and Win32 SNA application-side) SNA Server tracing.

This article describes how to remotely control SNA Server tracing using the SNA Server version 2.1 SNATRACE program. This program will also work with SNA Server version 2.0. However, if this program isn't available, qualified SNA Server support personnel can assist in remotely controlling SNA Server tracing using REGEDT32.

MORE INFORMATION

================

Under SNA Server version 2.1, the SNATRACE program accepts a \\servername command line parameter to remotely control tracing. For example

   SNATRACE \\servername

allows an authorized administrator to remotely control SNA Server tracing on \\servername.

Under SNA Server version 2.0, the SNATRACE program must be run on the local server machine to generate traces. However, tracing can be remotely enabled/disabled by changing SNA Server Registry settings on the remote machine using REGEDT32, though this should only be used with the assistance of qualified support personnel.

In either case, SNA Server trace files (*.TRC) are still generated on the remote server machine, stored in the <SNAROOT>\TRACES directory.

Under SNA Server, REGEDT32 can be used to control tracing by remotely updating SNA Server registry settings on the remote server.

Here are the registry trace settings along with how they can be set manually using REGEDT32:

Under HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services:

 SnaServr/Parameters   (controls SNA Server tracing)

 DLCTraceState: REG_SZ: OFF/ON -- if ON, enables data link control tracing between the SNA Server service and the SNA link service (includes all SNA traffic as well).

 SNATraceState: REG_SZ: OFF/ON -- if ON, enables SNA Format tracing between SNA Server and all remote SNA systems it's communicating with.

 FMITraceState: REG_SZ: OFF/ON -- if ON, enables 3270 message tracing between all clients and the server.

 PVITraceState: REG_SZ: OFF/ON -- if ON, enables LU6.2 message tracing between all clients and the server.

 InternalTraceLevel: REG_DWORD: 0-0x14 -- If 0, full internal tracing is enabled.  If 0x14, internal tracing is disabled.

 FlipLength: REG_DWORD: 500000 default (decimal).  This controls how large (in bytes) each SNA Server trace file can grow. By default, SNA Server traces wrap between two trace files so the hard disk isn't filled up.  Increasing the FlipLength can be helpful to increase the amount of trace data that's saved at any one time, to extend the amount of time the administrator has to turn off tracing, so that important trace information isn't overwritten when the trace file wraps.

NOTE: The FlipLength parameter can be set on any SNA service, not just on the SNAServr service.

 InternalTraceFile1: REG_SZ: <snaroot>\TRACES\NODEINT1.TRC

 InternalTraceFile1: REG_SZ: <snaroot>\TRACES\NODEINT2.TRC

    SNA Server service internal trace file names. Trace files will grow to the FlipLength size before wrapping to the second file (and vice versa).

 MessageTraceFile1: REG_SZ: <snaroot>\TRACES\NODEMSG1.TRC

 MessageTraceFile2: REG_SZ: <snaroot>\TRACES\NODEMSG2.TRC

    SNA Server message trace files (DLC, 3270, PVI, Admin tracing). Trace files will grow to the FlipLength size before wrapping to the second file (and vice versa).

 SnaBase/Parameters    (controls SnaBase service tracing)

 InternalTraceLevel: 0-0x14 -- If 0, full internal tracing on SnaBase is enabled. If 0x14, internal tracing is disabled.

 FMITraceState: REG_SZ: OFF/ON -- if ON, enables 3270 message tracing between the SnaBase and the SNA Server service.

 PVITraceState: REG_SZ: OFF/ON -- if ON, enables LU6.2 message tracing between the SnaBase and the SNA Server server.

 InternalTraceFile1: REG_SZ: <snaroot>\TRACES\NAPINT1.TRC

 InternalTraceFile1: REG_SZ: <snaroot>\TRACES\NAPINT2.TRC

    Internal trace file names. Trace files will grow to the FlipLength size before wrapping to the second file (and vice versa).

 MessageTraceFile1: REG_SZ: <snaroot>\TRACES\NAPMSG1.TRC

 MessageTraceFile2: REG_SZ: <snaroot>\TRACES\NAPMSG2.TRC

    SNABase message trace files (FMI, PVI tracing). Trace files will grow to the FlipLength size before wrapping to the second file (and vice versa).

 <SNA link service name>/Parameters  (controls SNA Server link service tracing -- can be set on any SNA Server link service, such as SnaDlc1, SnaSdlc1, SnaX251, etc).

 InternalTraceLevel: 0-0x14 -- If 0, full internal tracing on the link service is enabled. If 0x14, internal tracing is disabled.

 ConnectionTraceState: OFF/ON -- If ON, enables Level 2 tracing on the link service.

 DLCTraceState: REG_SZ: OFF/ON -- if ON, enables data link control tracing between the SNA Server service and the SNA link service (includes all SNA traffic as well).

 InternalTraceFile1: REG_SZ: <snaroot>\TRACES\LINKINT1.TRC

 InternalTraceFile1: REG_SZ: <snaroot>\TRACES\LINKINT2.TRC

    Internal trace file names. Trace files will grow to the FlipLength size before wrapping to the second file (and vice versa).

 MessageTraceFile1: REG_SZ: <snaroot>\TRACES\LINKMSG1.TRC

 MessageTraceFile2: REG_SZ: <snaroot>\TRACES\LINKMSG2.TRC

    SNA link service DLC message trace files. Trace files will grow to the FlipLength size before wrapping to the second file (and vice versa).

 ConnectionTraceFile1: REG_SZ: <snaroot>\TRACES\CONNECT1.TRC

 ConnectionTraceFile2: REG_SZ: <snaroot>\TRACES\CONNECT2.TRC

    SNA link service Level 2 connection trace files. Trace files will grow to the FlipLength size before wrapping to the second file (and vice versa).

 SnaBase/Parameters/Client  (controls SNA application traces)

 InternalTraceLevel: 0-0x14 -- If 0, enables full internal tracing on any Win32 SNA Applications running on the server.

 APPCTraceState: OFF/ON -- If ON, enables APPC API tracing on any Win32 SNA Applications running on the server.

 CPICTraceState: OFF/ON -- If ON, enables CPIC API tracing on any Win32 SNA Applications running on the server.

 CSVTraceState: OFF/ON -- If ON, enables Common Service Verb API tracing on any Win32 SNA Applications running on the server.

 RUITraceState: OFF/ON -- If ON, enables LUA Request Unit Interface API tracing on any Win32 SNA Applications running on the server.

 SLITraceState: OFF/ON -- If ON, enables LUA Session Level Interface API tracing on any Win32 SNA Applications running on the server.

 SnamanagTraceLevel: 0-0x14 -- If set to 0, enables full internal tracing on the SNA Server Administration program. This traces the internal code execution of the Admin program.  If set to 0x14,SNA Server Admin full internal tracing is disabled.

 FMITraceState: REG_SZ: OFF/ON -- if ON, enables 3270 message tracing between the SNA Application and the SNA Server service.

 PVITraceState: REG_SZ: OFF/ON -- if ON, enables LU6.2 message tracing between the SNA Application and the SNA Server server.

 InternalTraceFile1: REG_SZ: <snaroot>\TRACES\CLIENT1.TRC

 InternalTraceFile1: REG_SZ: <snaroot>\TRACES\CLIENT2.TRC

    SNA Application internal trace file names. Trace files will grow to the FlipLength size before wrapping to the second file (and vice versa).

 MessageTraceFile1: REG_SZ: <snaroot>\TRACES\CLIMSG1.TRC

 MessageTraceFile2: REG_SZ: <snaroot>\TRACES\CLIMSG2.TRC

    SNA Application message trace files (FMI, PVI tracing). Trace files will grow to the FlipLength size before wrapping to the second file (and vice versa).

 APITraceFile1: REG_SZ: <snaroot>\TRACES\API1.TRC

 APITraceFile2: REG_SZ: <snaroot>\TRACES\API2.TRC

    SNA Application API trace files (all API's). Trace files will grow to the FlipLength size before wrapping to the second file (and vice versa).

Additional reference words: prodsna 2.00 2.10

KBCategory: kbnetwork

KBSubcategory: ntdistrib


Q123178: Rumba 3270 user names appear as "Unknown" in SNA Admin

Rumba 3270 User Names Appear as "Unknown" in SNA Admin        [winnt]

ID: Q123178    CREATED: 23-NOV-1994   MODIFIED: 01-DEC-1994

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

----------------------------------------------------------------------

SYMPTOMS

========

When you run the Wall Data Rumba Office version 1.0 3270 emulator on an SNA Server Windows version 3.x client computer, the SNA Server Administration program may display the user name as "Unknown."

If you start the SNA Server Windows version 3.x client ahead of time (by starting WNAP.EXE manually, or by adding WNAP.EXE icon to the Windows Startup group), the user name appears correctly.

CAUSE

=====

Due to an initialization problem, the Rumba 3270 emulator was not properly initializing the underlying SNA Server client software before opening a 3270 session, causing the user name to appear as "Unknown" in the SNA Server Administration program.

RESOLUTION

==========

To obtain a fix for this problem, call Wall Data technical support at (206) 814-9255.

The Rumba product discussed here is manufactured by Wall Data Incorporated, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional reference words: prodsna 2.00 2.10

KBCategory: kbnetwork

KBSubcategory: ntdistrib


Q123255: WFW 3.11 fails to connect to SNA Server on Windows NT 3.5

WFW 3.11 Fails to Connect to SNA Server on Windows NT 3.5     [winnt]

ID: Q123255    CREATED: 28-NOV-1994   MODIFIED: 03-MAR-1995

3.50 2.00 2.10

WINDOWS

PUBLIC | kbnetwork kbinterop kbbug3.50

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

----------------------------------------------------------------------

SYMPTOMS

========

After upgrading an SNA Server computer from Microsoft Windows NT version 3.1 to Windows NT version 3.5, Microsoft Windows for Workgroups version 3.11 client computers fail to connect to SNA Server:

   SNA Server Error: 546

   Cannot establish connection with SNA Server <server name>.

CAUSE

=====

The Microsoft IPX/SPX compatible transport (NWLink) is installed by default with Microsoft Windows for Workgroups 3.11. When you configure the SNA Server client to use the "MS Network Client (named pipes)" interface, the NWLink transport is automatically used. This works fine with a Windows NT 3.1 server.

Under Windows NT 3.5, a new feature, direct hosting, was added to improve performance. This allows a Windows for Workgroups client to communicate directly with the server over IPX/SPX, rather than over NetBIOS. However, applications which use named pipes do not work correctly over direct-hosted IPX/SPX connections.

WORKAROUND

==========

To resolve this problem, add the following entry to the [network] section of SYSTEM.INI on the Windows for Workgroups 3.11 client computer:

   [network]

   DirectHost=NO

The client workstation must be rebooted for this change to take effect.

Microsoft provides updated Windows for Workgroups 3.11 client modules on the Windows NT 3.5 CD-ROM, though the updated modules do not solve the direct hosting problem. However, other named pipes applications (such as SQL Server) work fine with these updates.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5. We are researching this problem and will post new information here as it becomes available.

KBCategory: kbnetwork kbinterop kbbug3.50

KBSubcategory: ntdistrib ntnetserv

Additional reference words: wfw wfwg prodsna 2.00 2.10 nwlink DirectHost

3.50


Q123256: Enabling SNA Server Windows 3.x client traces

Enabling SNA Server Windows 3.x Client Traces                 [winnt]

ID: Q123256    CREATED: 28-NOV-1994   MODIFIED: 05-DEC-1994

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

----------------------------------------------------------------------

Microsoft SNA Server provides extensive tracing capabilities at both the server and client side to help diagnose problems. On the server side, you can use the SNATRACE tool to trace SNA Server and Win32 application activity. You can enable Windows 3.x client tracing by following the steps in the Enabling SNA Server Client Tracing section below. Client tracing is useful in diagnosing client-to-server connection problems or Windows 3.x SNA Server application problems. Note that client tracing cannot be used to capture server-to-host SNA Server or link level traffic; these types of traces must be captured at the server.

SNA SERVER CLIENT TRACING TYPES

===============================

Following are descriptions of the types of client tracing provided by SNA Server, along with a descriptions of each associated WIN.INI entry:

Internal Tracing

----------------

Internal tracing traces code execution of SNA Server components and is intended for SNA Server development. This type of tracing is useful to diagnose:

 - Client connection failures in communication (546 errors for example) over any client-server transport supported by SNA Server. If the SNA Server client software encounters an underlying network or operating system error, the error code is logged in the internal trace file.

 - Problems automatically loading a invokable transaction program (auto-started APPC or CPIC invokable TP).

 - Abnormal terminations of clients (general protection (GP) faults or application exceptions).

WIN.INI Entries Used To Control Internal Tracing:

   InternalTraceLevel: [0-8] Level of detail. The most detailed level is 0.

   InternalTraceFile1, InternalTraceFile2: ASCII files that store internal trace information. If only InternalTraceFile1 is specified, the trace file will grow indefinitely. If both trace files are listed, each file will grow to the FlipLength (see below) before wrapping to the next file.

   TraceFlushing: [OFF/ON] Controls whether or not trace information is immediately flushed to the trace file. When debugging a problem involving a hang condition, this entry should be set to ON to ensure that the most recent trace event is logged to the trace file.

   FlipLength: [size in bytes] Controls how large each SNA Server trace file can grow (default: 250,000). If two trace file names are specified, SNA Server traces wrap between two trace files so the hard disk doesn't fill up.

API Tracing

-----------

API tracing traces application program interfaces (APIs) supported by SNA Server, in call/return format. You can analyze these traces using the appropriate SNA Server API programmer's guide. This type of tracing is useful in diagnosing:

 - User-written applications which use the SNA Server APIs.

 - 5250 emulation problems (which use APPC).

SNA Server Trace Entries Used To Control API Tracing:

APPCTraceState: [OFF/ON] Enables APPC API tracing.

CPICTraceState: [OFF/ON] Enables CPIC API tracing.

CSVTraceState: [OFF/ON] Enables Common Service Verb API tracing.

RUITraceState: [OFF/ON] Enables LUA/RUI API tracing.

SLITraceState: [OFF/ON] Enables LUA/SLI API tracing.

APITraceFile1, APITraceFile2: ASCII files that store API trace information. If only APITraceFile1 is specified, the trace file will grow indefinitely. If both trace files are listed, each file will grow to the FlipLength (see Internal Tracing section above) before wrapping to the next file.

Message Tracing

---------------

Message tracing traces the internal message flow between the SNA Server client and the server. This type of trace is used by SNA Server development to diagnose:

 - 3270 emulator problems communicating with the server.

 - APPC or CPIC application problems communicating with the server.

SNA Server Trace Entries Used To Control Message Tracing:

FMITraceState: [OFF/ON] Controls 3270 Emulator Interface (EIS) message tracing, used by 3270 emulators.

PVITraceState: [OFF/ON] Controls LU6.2 message tracing which flows between the client and server.

MessageTraceFile1, MessageTraceFile2: ASCII files to store message trace information. If only MessageTraceFile1 is specified, the trace file will grow indefinitely. If both trace files are listed, each file will grow to the FlipLength (see Internal Tracing section above) before wrapping to the next file.

ENABLING SNA SERVER CLIENT TRACING

==================================

To enable SNA Server client tracing on a Windows 3.x client computer:

1. Stop the SNA Server for Windows client software.

2. Make backup copies of the following files on your client workstation:

      <snaroot>\WNAP.EXE -> WNAP.ORG

      <winroot>\SYSTEM\WDMOD.DLL -> WDMOD.ORG

      <winroot>\SYSTEM\LMCLI.DLL -> LMCLI.ORG (MS network/named pipes)

      <winroot>\SYSTEM\NWCLI.DLL -> NWCLI.ORG (Netware ipx/spx)

      <winroot>\SYSTEM\BVCLI.DLL -> BVCLI.ORG (Banyan IP)

      <winroot>\SYSTEM\IPCLI.DLL -> IPCLI.ORG (TCP/IP sockets)

3. Copy the following traced versions of the client components from your SNA Server CD-ROM to your client workstation:

      \clients\win3x\trace\WNAP.EXE  -> <snaroot>\WNAP.EXE

      \clients\win3x\trace\WDMOD.DLL -> <winroot>\SYSTEM\WDMOD.DLL

      \clients\win3x\trace\LMCLI.DLL -> <winroot>\SYSTEM\LMCLI.DLL

      \clients\win3x\trace\NWCLI.DLL -> <winroot>\SYSTEM\NWCLI.DLL

      \clients\win3x\trace\BVCLI.DLL -> <winroot>\SYSTEM\BVCLI.DLL

      \clients\win3x\trace\IPCLI.DLL -> <winroot>\SYSTEM\IPCLI.DLL

4. Add the following entries to your <winroot>\WIN.INI file, under the [WNAP] section. Any combination of tracing is supported. Not all entries need to be present in WIN.INI, only those necessary to capture the desired traces.

      [WNAP]

      ; Entries which control Internal tracing:

      InternalMessageTraceState=ON

      InternalTraceFile1=C:\NAPINT1.TRC

      InternalTraceFile2=C:\NAPINT2.TRC

      InternalTraceLevel=2

      ; Entries that control API tracing:

      APPCTraceState=ON

      CPICTraceState=ON

      CSVTraceState=ON

      RUITraceState=ON

      SLITraceState=ON

      APITraceFile1=C:\API1.TRC

      APITraceFile2=C:\API2.TRC

      ; Entries that control message tracing:

      FMITraceState=ON

      PVITraceState=ON

      MessageTraceFile1=C:\NAPMSG1.TRC

      MessageTraceFile2=C:\NAPMSG2.TRC

      ; Other general tracing entries:

      FlipLength=250000

      TraceFlushing=ON

5. Restart WNAP.EXE by choosing Run from the File menu of Program Manager.

6. Once the problem occurs, stop the SNA application and close the SNA Server client icon (WNAP.EXE).

Be sure to rename the client files to the original versions to disable tracing. There is no need to remove the WIN.INI entries if you use the original client files; they will be ignored.

KBCategory: kbnetwork

KBSubcategory: nthowto

Additional reference words: prodsna 2.00 2.10


Q123257: TCP/IP socket numbers used by SNA Server 2.1

TCP/IP Socket Numbers Used by SNA Server 2.1                  [winnt]

ID: Q123257    CREATED: 28-NOV-1994   MODIFIED: 31-JAN-1995

2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

----------------------------------------------------------------------

SNA Server uses the following socket numbers to support SNA Server clients over TCP/IP (over Windows Sockets):

0x05C5 - Socket used to receive SNA application traffic (3270, APPC). This is the socket used to communicate to the SNA Server service.

0x05C6 - Socket used to support SNA Server client "sponsor sessions". This is the socket used to communicate to the Snabase service over which the client workstation receives a list of other SNA Servers running in the domain.

The SNA Server client socket number is allocated dynamically through the Windows Sockets interface.

In addition to TCP/IP protocol over Windows Sockets, Microsoft SNA Server version 2.1 clients use the following to communicate with the server:

 - Named pipes (over any local area network [LAN] transport supported by the Microsoft network redirector included with Windows for Workgroups, Windows NT, or LAN Manager)

 - NetWare IPX/SPX

 - Banyan IP (over Banyan Vines)

 - AppleTalk

The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional reference words: wfw wfwg prodsna 2.10

KBCategory: kbnetwork

KBSubcategory: ntdistrib


Q130595: SNA Server password encryption support for LU6.2 sessions

SNA Server Password Encryption Support for LU 6.2 Sessions    [winnt]

ID: Q130595    CREATED: 23-MAY-1995   MODIFIED: 02-JUN-1995

3.10 3.50

WINDOWS

MSONLY | kbnetwork

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.11

-------------------------------------------------------------------------

SUMMARY

=======

When SNA Server 2.11 ships it will support a new feature called Password Substitution. This is a security feature supported by the latest version of OS/400 operating system (V3R1) which encrypts any password which flows between two nodes on an ATTACH message. A password flows on an ATTACH whenever someone invokes an APPC Transaction Program (TP) specifying a user ID and password. Forexample, this happens whenever anyone logs onto an AS/400.

The two nodes negotiate whether or not they support this feature in the BIND exchange. SNA Server 2.11 will set a bit in the BIND, and also adds some random data on the BIND for encryption. This bit had been reserved with previous versions of SNA Server. If the remote node supports password substitution, it sets the same bit in the BIND Response, and adds some (different) random data for decryption.

Note: It is illegal for the remote node to set the bit specifying password substitution, but not to add the random data.

According to IBM, there are implementations of LU 6.2 Password Substitution that do not support password substitution but do echo the password substitution bit back to SNA Server, without specifying any random data. When they do this, SNA Server will UNBIND the session with the sense code 1006 0006.

This sense code means:

 1006 = Required field or parameter missing

 0006 = A required subfield of a control vector was omitted

SNA Server should also log an Event 17 (APPC session activation failure: BIND negative response sent).

The correct solution is for the failing implementation to be fixed. However, as a short-term workaround, the following SNA Server service registry setting may be set:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your

own risk.

Hkey_local_machine\system\CurrentControlSet\Services\snaservr\parameters

NOPWDSUB: REG_SZ: YES  - when this is specified in the registry SNA Server's Password Substitution support will be disabled.

KBCategory: kbnetwork

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.11


Q123326: SNA Server MCP certification exam

SNA Server Certification Exam                                 [winnt]

ID: Q123326    CREATED: 29-NOV-1994   MODIFIED: 05-DEC-1994

2.00 2.10

WINDOWS

PUBLIC | kbother

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

----------------------------------------------------------------------

The Microsoft SNA Server Exam (70-12) is available worldwide. Registration and testing was started on November 7, 1994. This is an new exam. It is an additional elective for the Microsoft Certified Systems Engineer certification.

Customers can get the Exam Preparation Guidelines from the Microsoft Education and Certification Roadmap. The Roadmap is available from:

 - Microsoft at 800-636-7544, ask for the "Roadmap", part #098-56980

 - CompuServe (Go MSEDCERT, Library #5), E&CMAP.ZIP

 - ftp.microsoft.com (/Services/MSEdCert/CERTIFIC), E&CMAP.ZIP

KBCategory: kbother

KBSubcategory: ntgeneral

Additional reference words: prodsna 2.00 2.10 mcp exam


Q123336: "Messages Suppressed" in SDLC Level 2 tracing

"Messages Suppressed" in SNA Server Level 2 Tracing.          [winnt]

ID: Q123336    CREATED: 29-NOV-1994   MODIFIED: 05-DEC-1994

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

 The information in this article applies to:

 - Microsoft SNA Server versions 2.0 and 2.1

----------------------------------------------------------------------

SUMMARY

=======

The output of an SNA Server level 2 trace may include the following line:

   ...

   |000000a5.000000a1 SDLC   --------------------------------08:17:36.79

   |000000a5.000000a1 SDLC   ***** 63965  messages suppressed ****

   ...

This indicates that the message that is passing between the SNA Server Link service and the actual driver is the same as the message that was just logged in the trace file. The message suppressing function was added to level 2 tracing to keep SDLC trace files manageable and not let them get too large. It uses the following algorithm:

1. Each time the trace code is asked to trace an SDLC message, it compares it with the two previous messages that it received.

2. If either message matches, it increments the count of messages suppressed, traces nothing, and updates the buffer of the last two messages received.

3. If there is no match, it checks to see if it was suppressing messages. If it was, it traces the XXXX messages suppressed line, then traces the message and updates the buffer of the last two messages received.

By doing this, an active SDLC line which has the following activity:

   Tx RR

   Rx RR

   Tx RR

   Rx RR

   Tx RR

   Rx RR

   ...

will only take 3 lines in a trace file, no matter how many times the same message repeats. The result, in a simple form, will look like the following:

   Tx RR

   Rx RR

   X messages suppressed.

KBCategory: kbnetwork

KBSubcategory: ntui

Additional reference words: prodsna 2.00 2.10


Q123337: How SNA Server communicates with other SNA Servers

How SNA Server Communicates with Other SNA Servers            [winnt]

ID: Q123337    CREATED: 29-NOV-1994   MODIFIED: 05-DEC-1994

2.00 2.10

WINDOWS

MSONLY | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server versions 2.0 and 2.1

----------------------------------------------------------------------

SUMMARY

=======

SNA Server uses broadcasts to propagate its Service Table updates to other SNA Servers in the domain. This is necessary to keep all SNA Servers abreast of any configuration change that is made or any action that is being taken in the SNA Server domain. SNA Server 2.1 has provided choices that allows an Administrator of an SNA Server network to optimize the way this Service Table propagation occurs. This article should be read as a supplement to the Server Broadcasts dialog box helpfile that can be launched from within the Server Broadcasts dialog box.

MORE INFORMATION

================

SNA Server 2.0

--------------

By default SNA Server 2.0 will send broadcasts using the following method:

- WriteFile API call:

SNA Server will use a WriteFile API call, to send broadcasts to other SNA Servers in the domain. It does this by submitting a WriteFile API call, that will in turn be sent over all network protocols that the Workstation Service is bound to. For instance, if the Workstation Service was bound to Netbeui, TCP/IP and NWLink Netbios, SNA Server would send mailslot broadcasts over all three of these protocols. Sending mailslot broadcasts over all transports is a function of the WriteFile API call. This may cause unnecessary network traffic, however. In SNA Server 2.0 there is no way to disable this other than to remove unnecessary protocols from the Network applet in Control Panel.

- IPX Sockets if NWLink is Installed:

If NWlink is installed SNA Server 2.0 will send a mailslot broadcast over NWlink Netbios as described above using the WriteFile API AND over a well-known IPX socket.

- TCP/IP MailSlots:

If the SNA Servers are divided by TCP/IP routers, then enable the following registry parameter:

\Hkey_local_machine\system\current_control_set\services\snabase\parameters\

: EnableIPMailSlots:REG_SZ:YES

With this value enabled, SNA Server will only send mailslot broadcasts to domain controllers in the domain using TCP/IP only, even though other protocols may be installed. If the SNA Server machines do not reside on a domain controller with this option chosen, no SNA Server will listen for these mailslots.

- For Comm Server Support:

By default SNA Server 2.0 has turned on support for Comm Server Gateways, sending specific mailslot broadcasts that they can recognize. If there are no Comm Server Machines in the domain, add the following value to \Hkey_local_machine\system\current_control_set\services\snabase\parameters\

: CommServerSupport:REG_SZ:NO

Setting this value to NO will reduce the broadcast traffic by nearly one-half.

SNA Server 2.1

--------------

SNA Server 2.1 Admin enables the user to choose how two or more SNA Server will communicate with each other through the Server Broadcasts dialog box under the Options menu in SNA Server Amin. This dialog box includes the following choices:

   Microsoft Networking

   Novell Netware (IPX/SPX)

   Banyan Vines/IP

   Windows Sockets (TCP/IP)

   Router Server Broadcasts over IP routers

   SNA Server 2.0 servers in the same domain

   DCA/Microsoft Comm Server Client Support

- Microsoft Networking:

When selecting the "Microsoft Networking" option only, SNA Server 2.1 will send mailslot broadcasts using the WriteFile API, just like SNA Server 2.0 does by default. It does this by submitting a WriteFile API call, that will in turn be sent over all network protocols that the Workstation Service is bound to. For instance, if the Workstation Service was bound to Netbeui, TCP/IP and NWLink Netbios, SNA Server would send mailslot broadcasts over all three of these protocols. Sending mailslot broadcasts over all transports is a function of the WriteFile API call. This may cause unnecessary network traffic, however.

- Native Transport Interface:

Unlike 2.0, SNA Server 2.1 has options that enable the user to choose to send over selected native transports instead of using the WriteFile API call. These other choices are:

Novell Netware (IPX/SPX), Banyan Vines/IP, Windows Sockets (TCP/IP)

For instance, if TCP/IP was installed on all SNA Server machines, then the user would want to deselect "Microsoft Networking" and select Windows Sockets (TCP/IP). This would cut down on the number of mailslot broadcasts by only sending over one transport - TCP/IP in this case.

- Comm Server Support:

If there are no DCA/Microsoft Comm Server clients or servers, disable the Comm Server Support options: "SNA Server 2.0 servers in the same domain" AND "DCA/Microsoft Comm Server Client Support".

Deselecting these values will reduce the broadcast traffic by nearly one-half.

- TCP/IP MailSlots:

When SNA Servers are separated by TCP/IP routers. Select "Route Server Broadcasts over IP routers" when their is an IP router separating SNA Server machines. This is equivalent to setting EnableIPMailslots to YES under 2.0. Just like in 2.0, SNA Server will only send mailslot broadcasts to domain controllers in the domain using TCP/IP only, even though other protocols may be installed. If the SNA Server machines do not reside on a domain controller with this option chosen, no SNA Server will listen for these mailslots. Note: This option can only be chosen if "Microsoft Networking" is chosen.

Additional reference words: prodsna 2.00 2.10

KBCategory: kbnetwork

KBSubcategory: ntnetserv


Q123748: SNA Server Event 23, Outage "2D"

SNA Server Err Msg: Event 23, Outage Code "2D" (Abnormal Resp.)[winnt]

ID: Q123748    CREATED: 08-DEC-1994   MODIFIED: 08-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0, 2.1

----------------------------------------------------------------------

SYMPTOMS

========

If the Microsoft SNA Server Synchronous Data Link Control (SDLC) connection is configured with the Maximum BTU Size set to a value less than the maximum frame size of the remote system (set using the PU macro MAXDATA parameter in VTAM), the following SNA Server connection failure may be logged in the Windows NT application event log:

   Event 23, Outage code "2D" (abnormal response)

CAUSE

=====

The abnormal response error occurs if the host banner screen (that is, the USSTAB message 10 screen) exceeds the Maximum BTU size set in SNA Server. Because the maximum frame size is not negotiated until a BIND takes place, the SNA Server's maximum frame size can be exceeded.

RESOLUTION

==========

To correct this problem, change the SNA Server Maximum BTU size to match the value used on the remote system.

NOTE: If an IBM SDLC adapter or MicroGate adapter is being used with SNA Server 2.0 or 2.1, the maximum frame size supported by Microsoft SNA Server is 521. Other SDLC adapters do not have this restriction.

Additional reference words: ntprotocol prodsna 2.10 2.00 configured

KBCategory: kbnetwork

KBSubcategory: ntnetserv


Q123779: Changing the Windows NT computername on an SNA Server

Changing the Windows NT Computer Name on an SNA Server        [winnt]

ID: Q123779    CREATED: 11-DEC-1994   MODIFIED: 08-FEB-1995

2.10

WINDOWS

PUBLIC | kbnetwork ntdistrib

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

 - Microsoft SNA Workstation for Windows NT, version 2.1

----------------------------------------------------------------------

SUMMARY

=======

If the Windows NT computer name is changed on a machine running SNA Server or SNA Workstation, the SNA Server configuration file continues to reflect the old computer name. As a result, the SNA Server fails to start.

You can run the SNA Admin program to update the SNA Server service name to the new computer name. To do so, you must login with local administrator authority.

NOTE: You may introduce additional problems with any AS/400 connections if the local control point name is also changed.

MORE INFORMATION

================

To update the SNA Server configuration file with the new server name, run the SNA Admin program as follows

   snaadmin <config file>

where <Config File> is the fully qualified path to the SNA Server configuration file. For example:

   snaadmin c:\sna\system\config\com.cfg

When you open the configuration file you can change the SNA Server service name through the server properties dialog box. After you change the server name, choose Save from the File menu to save the configuration.

If the SNA Server machine is supporting connections to one or more AS/400 computers, and the Local Control Point Name is changed to reflect the new server name, the AS/400 connections fail to activate. This problem occurs because the SNA Server local control point name corresponds to the APPC controller description name on the AS/400, and the old entry still points to the SNA Server's adapter address (for 802.2 Token Ring or Ethernet connections) or to the poll address (for SDLC connections).

To correct this problem, create a new APPC controller on the AS/400 associated with the new SNA Server control point name. To do so, delete the old entry and add a new entry. The new entry is added automatically on Token Ring or Ethernet if the auto-create controller option is enabled. For SDLC you have to add the new entry manually.

Additional reference words: prodsna 2.10 computername servername

KBCategory: kbnetwork

KBSubcategory: ntdistrib


Q123791: SNA Server 802.2 remote discovery process

SNA Server Remote Station Discovery Process                   [winnt]

ID: Q123791    CREATED: 11-DEC-1994   MODIFIED: 08-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork ntdistrib

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0,  2.1

----------------------------------------------------------------------

SUMMARY

=======

When SNA Server starts an 802.2 connection, it submits, by default, an unlimited number of Open(Link) requests to the 802.2 link service. If an SNA Server 802.2 connection is configured to activate OnServer Startup or By Administrator, the server will try indefinitely to activate the connection.

The DLC protocol then sends logical link control (LLC) test frames to test link station-to-link station connectivity. These test frames are the first frames that are sent by SNA Server (through DLC) and are used to discover the remote station. To ensure the best chance of remote station discovery, the DLC protocol then submits various types of MAC level frames to the NDIS (Network Device Interface Specification) interface. The types submitted depend on the media access method DLC is bound to.

THE SNA SERVER LINK LEVEL OPEN(LINK) REQUEST

==========================================

SNA Server's link level requests can be adjusted in SNA Server Admin by choosing the Retry Timers button in the Connection Properties dialog box. The two values are:

 - Maximum number of attempts

   This value represents the number of link level Open (link) requests made by the SNA Server service to the SNA Server 802.2 link service. It does not represent the number of test frames that will be submitted by the DLC protocol to NDIS. The valid range is from 1 to No Limit; the default is No Limit.

-  Delay after failed attempts

   This value represents the number of seconds that the SNA Server service will wait after a failed attempt before submitting another request 802.2 link service. The valid range is from 5 seconds through 255 seconds (in multiples of 5); the default is 10 seconds.

DLC MAC level Framing

=====================

Ethernet

--------

On Ethernet there are two frame formats: IEEE 802.3 and the older DIX (Digital Intel Xerox). With DIX format, SNAP message headers are used to identify the protocol as DLC because various other MAC level protocols can flow on Ethernet such as TCP/IP, NetBEUI, IPX, and so forth.

SNA Server tells the DLC stack which sort of framing to use:

   HKEY_LOCAL_MACHINE\SYSTEM

   CurrentControlSet\Services\DLCLinkServiceName\Parameters\ExtraParameters

   Frametype:REG_DWORD:number

This specifies the type of frames for DLC to send over an Ethernet local area network (LAN). The variable need be set only if the LAN is Ethernet and only if the SNA server communicates with remote host, peer, or downstream systems via routers (not MAC layer bridges). If the SNA server communicates over Ethernet via routers, check with the local network support staff to determine what types of frames the routers pass. The frames can be either standard 802.3 format or 802.2 packets prefixed by DIX headers using EtherType value 0x80D5.

Specify the number in FrameType as follows:

Value   Effect

-----------------------------------------------------------------------

  0     Use the frame type specified for this adapter in the

        registry entry for the DLC protocol stack:

           HKEY_LOCAL_MACHINE\SYSTEM

           \CurrentControlSet\Services\DLC\Parameters\AdapterName

             \UseDixOverEthernet

        The default for UseDixOverEthernet is 0, resulting in 802.3 format.

  1     Use the frame type automatically determined by the DLC stack during XID exchange.

  2     Use standard 802.3 format.

  3     Use 802.2 packets prefixed by DIX headers using EtherType value 0x80D5.

If FrameType is not set it defaults to 0.

When you run DLC applications on Ethernet LANs, where the DLC traffic may need to pass over an Ethernet-Token Ring bridge (such as IBM 8209), the destination adapter address may need to be sent in bit-flipped order to accommodate the address change that such a bridge performs.

SNA Server handles this by sending TEST and XID frames to both the configured remote network address and the bit-flipped address (for Ethernet 802.2 connections), in both DIX and 802.3 formats.

Some stations may send bits in little-endian order (least significant bit first), while others send them big-endian (most significant bit first). As a result, some remote stations won't recognize their own addresses unless the local station reverses the order of bits in the MAC address on every frame.  One common problem occurs when an older LAN bridge flips the bits as the frames pass through it. As a result, remote systems do not recognize their own address, even when the sending and receiving stations are using the same bit ordering. Because of this, DLC sends both bit flipped and non-bit flipped frames to ensure that the remote system recognizes its address even when passing through one of these bridges.

In summary, on each connection, the originating station starts an 802.2 session by sending an LLC TEST frame. By default, DLC sends this frame using both 802.3 and DIX framing with both bit orderings of the MAC header. This can create as many as four TEST frames on the wire per request from the SNA Server 802.2 link service. The answering station's LAN adapter is only listening to one bit ordering of its MAC address, but it may be enabled for both 802.3 and DIX framing; the receiving station responds with either one or, at most, two TEST frames - one for each framing. The bit ordering is now established. DLC at the originating station hears both responses, and chooses one for the 802.2 session.

Token Ring

----------

On token ring LANs, there is only one framing format, as specified by IEEE standard 802.5. Bit-flipping is not necessary.

In Windows NT 3.1, DLC's automatic frame type detection did not work correctly; it could not establish a session with DIX framing, though it could via 802.3.

In Windows NT 3.5, a filtering algorithm was added to avoid unnecessary duplication of the initial messages. This filtering avoids handing the client software (SNA Server) a duplicate message received with both framing formats. This cuts down on the superfluous messages exchanged during XID negotiation.

To Bit-flip:

1. Separate the 12-digit hexadecimal address into a set of two digits; for example:

      40 00 0A 12 34 56

2. Reverse the positions of the characters in each of the two-digit sets:

      40 00 0A 12 34 56  ->   04 00 A0 21 43 65

3. Use the table below to bit-reverse each digit. For example:

      04 00 A0 21 43 65  ->   02 00 50 48 2C 6A

   Conversion Table

   ----------------

   Original  Converted

   Bit       Bit

   --------  ---------

   0          0

   1          8

   2          4

   3          C

   4          2

   5          A

   6          6

   7          E

   8          1

   9          9

   A          5

   B          D

   C          3

   D          B

   E          7

   F          F

4. After bit-reversing each digit, combine the six pairs into a 12-digit hexadecimal address. For example:

      020050482C6A

Additional reference words: ntprotocol prodsna 2.00 2.10

KBCategory: kbnetwork

KBSubcategory: ntdistrib


Q129601: Connection fails on SNA Server with two Token Ring NICs

Connection Fails on SNA Server with Two Token Ring NICs       [winnt]

ID: Q129601    CREATED: 30-APR-1995   MODIFIED: 02-JUN-1995

3.10 3.50

WINDOWS

PUBLIC | kbinterop kbbug3.10 kbbug3.50

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Server version 3.5

 - Microsoft SNA Server versions 2.0 and 2.1

----------------------------------------------------------------------

SYMPTOMS

========

If an SNA Server has two token ring network interface cards (NIC) and multiple SNA Server link services and connections (PU's) defined over each NIC, one or more SNA Server connections may fail to activate when the connections are started, if the remote system is located across a source routing bridge.

When an SNA Server connection is activated, SNA Server sends a TEST frame to the remote address, specifying the local network first. If no response is received, the TEST frame is resent with the "all routes" bit set. However, when this problem occurs, the second TEST frame (specifying the source routing bit) is never sent for a given connection.

CAUSE

=====

This problem occurs when the Windows NT DLC protocol does not handle multiple token ring NICs properly.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5. A fix to this problem is in development, but has not been regression-tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix.

RESOLUTION

==========

This problem is fixed in Windwos NT Server version 3.51.

To correct this problem in Windows NT Server version 3.5, apply the fix.

To correct this problem in Windows NT Advanced Server version 3.1, upgrade to Windows NT Server version 3.51, or upgrade to Windows NT 3.5 and apply the fix.

KBCategory: kbinterop kbbug3.10 kbbug3.50

KBSubcategory: ntprotocol ntinterop

Additional reference words: prodnt 3.10 3.50 2.00 2.10 dlc sna


Q123832: Using SNA Server with SDLC multidrop leased lines

Using SNA Server with SDLC Multidrop Leased Lines             [winnt]

ID: Q123832    CREATED: 13-DEC-1994   MODIFIED: 08-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork ntdistrib

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0, 2.1

----------------------------------------------------------------------

SUMMARY

=======

When you use SNA Server on an SDLC multidrop leased line, you should use the

following configuration:

 - Disabled the Constant RTS checkbox in the SNA Server 2.1 link service (configured in SNA Server Setup). NOTE: In SNA Server 2.0, this option appears as Constant Carrier.

 - Duplex: Select Half in the SNA Server SDLC connection Advanced Setup dialog box (configured in SNA Server Admin).

MORE INFORMATION

================

If either Constant RTS or Full Duplex is selected, SNA Server always raises the Request to Send (RTS) flag high and creates a point-to-point connection. As a result, other stations on the multidrop line are not able to send data on the line and operations through a multiplexor may fail.

If Half Duplex is selected, SNA Server only raises RTS when it has data to send to the remote system.

This setting should not be confused with half-duplex or full-duplex data transfer. In SNA Server, this setting simply controls SNA Server's use of the RTS signal and should be set to full-duplex to improve performance on an SDLC point-to-point line.

NOTE: The remote system can still be configured to use full-duplex, even though SNA Server is configured as half-duplex.

Additional reference words: prodsna 2.00 2.10 leased sdlc multidrop mux

KBCategory: kbnetwork

KBSubcategory: ntdistrib


Q123833: Connecting SNA Server over X.25/QLLC

Connecting SNA Server over X.25/QLLC                          [winnt]

ID: Q123833    CREATED: 13-DEC-1994   MODIFIED: 08-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork ntdistrib

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0, 2.1

----------------------------------------------------------------------

SUMMARY

=======

SNA Server supports SNA connections over X.25/QLLC using any SDLC adapter supported by SNA Server, or through special X.25 link services available from several third-party vendors listed in the SNA Server product companion catalog included with the product.

For SNA Server configuration information, see the SNA Server Admin program's Online Help, the SNA Server "Administrator's Guide," and/or the appropriate third-party vendor's documentation.

MORE INFORMATION

================

If the connection still fails to activate after you follow the configuration information and you're connecting to a host system, the following settings should also be checked in the SNA Server Admin Advanced Setup dialog box for the SNA Server X.25 connection:

- XID Format

  For 3270 communication to a host system over X.25/QLLC, some host systems require Format 0.

- User Data

  Host systems require that C3 is configured here to indicate that X.25/QLLC protocol is being requested.

Additional reference words: prodsna 2.00 2.10 x.25 eicon qllc

KBCategory: kbnetwork

KBSubcategory: ntdistrib


Q124211: Using IBM PC/3270 Version 4.0 on SNA Server

Using IBM PC/3270 Version 4.0 on SNA Server                   [winnt]

ID: Q124211    CREATED: 21-DEC-1994   MODIFIED: 31-JAN-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0

 - Microsoft SNA Server for Windows NT, version 2.1

----------------------------------------------------------------------

SUMMARY

=======

IBM Personal Communications/3270 WorkStation Program (IBM PC/3270) version 4.0 supports the SNA Server Windows client interface.

MORE INFORMATION

================

To run this application on top of an SNA Server Windows client computer:

1. The SNA Server Windows client software must first be installed on the Windows or Windows for Workgroups computer. Any SNA Server client-server connection method can be selected.

   NOTE: To run on a Windows NT computer, the SNA Server 2.1 Win3x client software must be installed on Windows NT. However, the Win3x client software will not run directly on SNA Server because the Win32 SNA client software is installed there by default.

2. 3270 LUs must be assigned to the user or group (or Everyone user) within the Users and Groups window of SNA Server Admin.

3. Configure PC/3270 to use this interface:

    - Run the Personal Communications "Start/Configure Sessions" icon

    - Choose the Communication/Configure dialog. Set:

         Adapter:   LAN

         Attachment:   FMI  Windows NT - client

    - Choose the Configure button. This will automatically retrieve the 3270 LUs assigned to the user/group within the SNA Server configuration file. Select an LU from the list.

The IBM PC/3270 is manufactured by International Business Machines Corporation, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional reference words: wfw wfwg prodsna 2.00 2.10

KBCategory: kbnetwork

KBSubcategory: ntdistrib


Q125024: Attachmate SDLC adapter support for SNA Server

Attachmate SDLC Adapter Support for SNA Server                [winnt]

ID: Q125024    CREATED: 19-JAN-1995   MODIFIED: 20-JAN-1995

2.10

WINDOWS

PUBLIC | kb3rdparty

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

 - Microsoft SNA Workstation for Windows NT, version 2.1

----------------------------------------------------------------------

SUMMARY

=======

SNA Server version 2.1 driver support for the Attachmate SDLC adapter and Attachmate Advanced SDLC adapter is available from Attachmate. Drivers are included with the adapter itself, or available from the Attachmate Customer Support BBS number at (206) 649-6660.

MORE INFORMATION

================

The correct driver must be used for the appropriate adapter. The following self-extracting files are available on the Attachmate BBS:

  SDLCNT21.EXE : Attachmate SDLC driver, for SNA Server 2.1

  ADSDLC21.EXE : Attachmate Advanced SDLC driver, for SNA Server 2.1

Once these files are extracted, they may be installed through SNA Server Setup by choosing the Add Link Service option and choosing the Other button which prompts for the location of the third-party driver setup files.

The Attachmate SDLC adapter is a 1/2-length card and has a switch pack with only 5 dip switches on it. The Attachmate Advanced SDLC adapter is a 2/3-length card and has 8 dip switches on the switch pack.

The Attachmate products discussed here are manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional reference words: prodsna 2.10 attachmate sdlc

KBCategory: kb3rdparty

KBSubcategory: nthw


Q125025: Attachmate SDLC connection doesn't activate

Attachmate SDLC Connection Doesn't Activate                   [winnt]

ID: Q125025    CREATED: 19-JAN-1995   MODIFIED: 20-JAN-1995

2.10

WINDOWS

MSONLY | kb3rdparty

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

 - Microsoft SNA Workstation for Windows NT, version 2.1

----------------------------------------------------------------------

SYMPTOMS

========

Due to a problem in early versions of the Attachmate SDLC setup script for SNA Server, a Registry setting doesn't get set properly during link service installation on a machine running Windows NT version 3.5 and SNA Server version 2.1.

This setup problem causes the SDLC connection to fail to activate (the connection will stay Inactive or On Demand, even though the SNA Server service activates OK).

To determine if this problem is occurring, the following event will be logged in the Windows NT application event log:

  169  Failed to open device driver \Device\, Windows NT

       rc = C0000033

  (C0000033 = object name invalid)

If this error is present, the setup process failed to configure a registry setting for the SDLC link service. To correct this problem, run REGEDT32 and set the following registry entry:

  HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/[...]

    /ATMSDLC1/Parameters/Extra Parameters  (Attachmate SDLC)

  or

    /ADVSDLC1/Parameters/Extra Parameters  (Advanced SDLC)

  DeviceName: REG_SZ: <value>

If no value was configured for DeviceName, set the device name to ATMSYNC if the Attachmate SDLC adapter is being used, or to ADVSYNC if the Attachmate Advanced SDLC adapter is being used.

RESOLUTION

==========

This problem doesn't occur when using more recent versions of the Attachmate SDLC driver support available on the Attachmate Customer Support BBS number at (206) 649-6660.

The correct driver must be used for the appropriate adapter. The following self-extracting files are available on the Attachmate BBS:

  SDLCNT21.EXE : Attachmate SDLC driver, for SNA Server 2.1

  ADSDLC21.EXE : Attachmate Advanced SDLC driver, for SNA Server 2.1

The Attachmate SDLC adapter is a 1/2-length card and has a switch pack with only 5 dip switches on it. The Attachmate Advanced SDLC adapter is a 2/3-length card and has 8 dip switches on the switch pack.

The Attachmate products discussed here are manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional reference words: prodsna 2.10 attachmate sdlc 169

KBCategory: kb3rdparty

KBSubcategory: nthw


Q125881: Maximizing IND$FILE 3270 host file transfer throughput

Maximizing IND$FILE 3270 Host File Transfer Throughput        [winnt]

ID: Q125881    CREATED: 07-FEB-1995   MODIFIED: 13-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbtool kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT versions 2.0 and 2.1

----------------------------------------------------------------------

SUMMARY

=======

Windows NT SNA Server 3270 and other third-party 3270 emulators support host file transfer using the host IND$FILE interface. There are three ways you can improve performance:

 - Choosing a Fast SNA Link Interface to the Host

 - Maximizing the SNA Link Frame Size

 - Maximizing the 3270 Structured Field RU Size

Choosing a Fast SNA Link Interface to the Host

----------------------------------------------

The fastest link type supported by SNA Server is a 16 megabits per second (Mbps) Token Ring network. An 802.2 connection to the host should be used if one is available. Note: SNA Server 2.1 supports channel connections when third-party driver support is available. (Not currently available as of 2/8/95.)

Maximizing the SNA Link Frame Size

----------------------------------

The maximum frame size supported by SNA Server and the host varies depending on the link type. The host frame size is configured in the MAXDATA= parameter in the PU definition in VTAM. This setting should match the "Max BTU size" in the SNA Server Connection setup/advanced dialog in SNA Administrator.

Here are the maximum frame sizes supported (in bytes):

   802.2 Token Ring connection (16 Mbps):      16393

   802.2 Token Ring connection (4 Mbps):        4096

   802.2 Ethernet connection:                   1493

   IBM SDLC/MPAA adapter or Microgate adapter:   521

The maximum frame size provided by third-party SNA Server link support depends on the third-party interface being used.

Maximizing the 3270 Structured Field RU Size

--------------------------------------------

Maximizing the SNA RU size reduces end-to-end acknowledgments at the 3270 application level. An RU is split into multiple messages if the frame size is smaller.

First, the query bit on the LU definition at the host must be enabled in order to support structured field file transfer. This is enabled in bit 0 (the high order bit) on byte 1 in the PSERVIC parameter which you can configure in the MODEENT on the 3270 LU's DLOGMODE mode entry:

  PSERVIC=X'0280xxxx...

  Byte 0 is the LU type (02 in this example)

  Byte 1 is used by VSCS and needs to be set as follows:

  80 - Device supports extended data stream capability. It supports write structured field (WSF) and read partition query (Query) structured field.

Otherwise, screen-mode transfer is used, limiting the data RU size to 1920 bytes.

The RU size supported by the host is configured in the RUSIZES=LU mode entry (MODEENT). Here are common values used:

   8787 = 1024

   8888 = 2048

   8989 = 4096

   8A8A = 8192

   8B8B = 16384

   8C8C = 32768

The RU size is computed as follows:  RUSIZES = MNMN, where the RU size = M*2^N. This specifies the maximum length of data (request units) in bytes that the primary or secondary can send to each other. The leftmost two digits apply to the secondary (SNA Server) logical unit, and the rightmost two digits apply to the primary (host) logical unit. If set to 00, then the default size (no limit on the RU size) is used.

Within the 3270 emulator, the structured field file transfer RU size must be specified in the file transfer configuration. Within SNA Server 3270, this is set in the Packet Size field within the 3270 File Transfer dialog box. The maximum value is 32767.

MORE INFORMATION

================

While the SNA link interface and frame size are often not adjustable, maximizing the 3270 structured field file transfer RU size can provide dramatic performance improvements.

However, IND$FILE is not an efficient file transfer method. For higher throughput host file transfer, an LU 6.2-based file transfer product should be considered. See the latest SNA Server third-party companion product catalog, ISVCAT.EXE, for a list of available products:

 - Library 1 of the MSSNA CompuServe Forum

 - ftp.microsoft.com in /BUSSYS/WINNT/SNA-PUBLIC

KBCategory: kbtool kbnetwork

KBSubcategory: ntutil

Additional reference words: prodsna 2.10 2.00 ind$file 3270 file transfer


Q125882: SNA Server connection stays inactive

SNA Server Connection Stays Inactive                          [winnt]

ID: Q125882    CREATED: 07-FEB-1995   MODIFIED: 08-FEB-1995

2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT versions 2.0 and 2.1

----------------------------------------------------------------------

SUMMARY

=======

An SNA Server connection may remain inactive. You cannot reactivate the connection using SNA Administrator. Here are some possible causes and resolutions:

The SNA Server Service Owning the Connection Is Inactive

--------------------------------------------------------

Start the SNA Server service using SNA Administrator. If the server fails to start, check the Windows NT system and application logs. In order for the SNA Server service to start, all SNA Server link services installed by SNA Setup must also start successfully.

SNA Server Shows [Out of Date]

------------------------------

If a new connection is defined in SNA Server Administrator when SNA Server is running, the server status appears as "Active [Out of Date]." This indicates that the SNA Server service must be restarted to enable the configuration changes. When a new connection is created, the SNA Server service must be stopped and restarted to enable the change.

The SNA Server Backup Server Had an Old Configuration File

----------------------------------------------------------

The SNABase service running on the SNA Server primary and backup configuration servers automatically handles the replication of the SNA Server configuration file. However, if security is enabled on the COMCFG share point, or NTFS file permissions restrict access to the configuration file, <SNAROOT>\SYSTEM\CONFIG\COM.CFG, the configuration file on the backup configuration server may be out of date. To test this, copy the configuration file from the primary to the backup server:

   copy \\<primary>\comcfg\com.cfg \\<backup>\comcfg\com.cfg

where <primary> is the SNA Server primary configuration server and <backup> is the SNA Server backup server. After you copy the configuration file, you'll need to restart the SNA Server service on any backup servers.

By default, the SNABase service runs under the Windows NT Local System context. If the Everyone group does not have Read access to the COMCFG share point on the primary server, or Full Control access on the backup server, the replication to the backup server will fail.

See Chapter 12, "Setting Up Security with SNA Server," in the SNA Server 2.1 Administrator's Guide for a full discussion on limiting user access to the SNA Server configuration file.

Additional reference words: prodsna 2.10 2.00 inactive connection

KBCategory: kbnetwork

KBSubcategory: ntgeneral


Q126335: Novell WLIBSOCK.DLL 8/30/94 causes mailslot error 10066

Novell WLIBSOCK.DLL Dated 8/30/94 Causes Mailslot Error 10066 [winnt]

ID: Q126335    CREATED: 21-FEB-1995   MODIFIED: 22-FEB-1995

2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT 2.1

----------------------------------------------------------------------

SUMMARY

=======

When you run the SNA Server 2.1 Windows 3.x client using the TCP/IP sockets interface over Novell LAN Workplace version 4.2 with a WLIBSOCK.DLL file dated 8/30/94 size 47,878, the following error may appear:

   Error -- The NAP is not started

   SNA Server Error: 553

   could not create mailslot, rc=10066

RESOLUTION

==========

Replacing WLIBSOCK.DLL with an earlier version (dated 2/1/94) should eliminate this error.

The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

KBCategory: kbnetwork

KBSubcategory: ntdistrib

Additional reference words: prodsna 2.10 lwp work place mail slot


Q130594: Err Msg 2139 - Could not create mailslot w/SNA Server client

Err Msg: 2139 - Could Not Create Mail Slot w/ SNA Server Client[winnt]

ID: Q130594    CREATED: 23-MAY-1995   MODIFIED: 02-JUN-1995

2.00 2.10 2.11

WINDOWS

PARTNER | kbnetwork

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.00 2.10 and 2.11

-------------------------------------------------------------------------

SYMPTOMS

========

When you attempt to launch SNABase on an SNA Server MS-DOS client over IBM's LAN Requester, or when you load WNAP.EXE on an SNA Server Win3x client over LAN Requester, the following error message appears if LAN Requester has not been configured for mailslot and named pipe support:

   Could not create mail slot - 2139

RESOLUTION

==========

To correct this, add the following lines to the DOSLAN.INI file and reboot your computer:

   /API

   /NBC:4

   /NBS:1K

   /NVS:1

   /NMS:2

KBCategory: kbnetwork

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.00 2.10 2.11


Q126392: SNA Server Vines PC-base service doesn't get created

SNA Server Vines PC-based Service Doesn't Get Created         [winnt]

ID: Q126392    CREATED: 22-FEB-1995   MODIFIED: 24-FEB-1995

2.1

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

--------------------------------------------------------------------------

SYMPTOMS

========

SNA Server registers itself with the Banyan Vines Directory Services when the SNABASE service is started. This is necessary for SNA Server clients that are communicating over the Banyan Vines redirector to connect to SNA Server. If the StreetTalk username is the same as the SNA Server machine name, the Vines StreetTalk server rejects a request from SNA Server to create its PC-based service.

CAUSE

=====

When SNABASE service starts up, it attempts to create a PC-based service with its local StreetTalk Server using the StreetTalk Group name (for example, CNS@Microsoft).

The PC-based service name that SNA Server submits to the Vines StreetTalk server is a combination of the SNA Server computername along with the StreetTalk group name. For example, if the computername is Godzilla, then Godzilla@CNS@Microsoft is the PC-based service submitted by SNA Server.

If there is a StreetTalk username with Godzilla@CNS@Microsoft, then the Banyan Vines server rejects the request (return code 1013) to create a PC-based service.

WORKAROUND

==========

To work around this problem, change the SNA Server computername or delete the user record from the Vines StreetTalk server. You can do this using the Vines Manage program.

KBCategory: kbnetwork

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.1 Banyan Vines computer user name


Q126393: SNA Server configurations that produce XID rejections

SNA Server Configurations that Produce XID Rejections         [winnt]

ID: Q126393    CREATED: 22-FEB-1995   MODIFIED: 22-MAR-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

--------------------------------------------------------------------------

SYMPTOMS

========

The following SNA Server XID rejection events are logged in the application event log you connect to an AS/400:

 - Event ID: 56

   Event description: Connection <connection_name> failed: XID rejected by remote computer

 - Event ID: 230

   Event Description: Connection <connection_name> Not responding to XID commands.

The connection goes into a Pending state and users get APPC primary return code: 0003; secondary return code: 00000005,  when attempting to open a 5250 session.

CAUSE

=====

Causes of Event ID 56:

 - There is already a controller defined on the AS/400 with the same name as the one defined in SNA Server, but it has a different "LAN remote adapter address (ADPTADR)" associated with it.

 - There is already a different controller name defined on the AS/400 with the same "LAN remote adapter address (ADPTADR)" (Autocreate Controller [AUTOCRTCTL] is set to YES in the AS/400 Line Description).

 - The "LAN remote adapter address (ADPTADR)" defined on the AS/400 represents the network interface card address of the SNA Server machine. To determine this, type the following at a Windows NT Command Prompt:

      c:> net config server

 - The Remote Control Point Name in the SNA Server Administrator Connection Properties dialog box does not match the Local Control Point Name in the AS/400 Network Attributes screen.

Causes of Event ID 230:

 - Autocreate controller (AUTOCRTCTL), which is configured in the AS/400 Line Description, is set to No and you are using the incorrect Local Node ID value for the controller you have manually created on the AS/400.

 - The Remote SAP Address in the SNA Server connection properties is different than the SSAP address in the AS/400 line description.

   NOTE: The SAP address defined in the SNA Server link service setup does not have to match anything on the AS/400.

 - The administrator configured the Remote Network Address using an address that already exists on the LAN (and is bound to the DLC protocol) but it is not the address that the AS/400 administrator is attempting to connect to. For example, an administrator used the SNA Server machine address or other Windows NT machine that has the MS-DLC protocol installed.

KBCategory: kbnetwork

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.00 2.10 nic adapter admin


Q126394: SNA Server doesn't include bundled support for Windows HLLAPI

SNA Server Doesn't Include Bundled Support for Windows HLLAPI [winnt]

ID: Q126394    CREATED: 22-FEB-1995   MODIFIED: 24-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

--------------------------------------------------------------------------

SNA Server is not bundled with an emulator that supports the Windows HLLAPI application program interface (API), though the SNA Server CD-ROM does include the WOSA-compliant Windows HLLAPI specification and library/header files necessary to build an HLLAPI application.

If you require Windows HLLAPI support for your application, obtain a third-party product which supports Windows HLLAPI. Most Windows 3270 and 5250 vendors include Windows HLLAPI support. Refer to the SNA Server third-party companion guide (Word for Windows format) located on the SNA Server CD-ROM (COLLATRL\GENERAL\ISVCATAL.DOC) for information on emulators that support Windows HLLAPI.

KBCategory: kbnetwork

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.10 2.00 winhllapi ehllapi


Q126395: Ways to increase the number of AS/400 LU6.2 sessions

Ways to Increase the Number of AS/400 LU6.2 Sessions          [winnt]

ID: Q126395    CREATED: 22-FEB-1995   MODIFIED: 24-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

--------------------------------------------------------------------------

By default there are 64 sessions per LU-LU pairing in SNA Server, as defined by the QPCSUPP mode. To increase the number of sessions, perform one or both of the following:

1. Create more Local APPC LUs in SNA Server Administrator, and partner them with the Remote APPC LU, using the QPCSUPP mode. Each LU/LU partnering supports up to 64 sessions by default.

2. Increase the session limits in QPCSUPP mode on the AS/400 and in the SNA Server Administrator. The maximum for session limits is 512. This number is imposed by OS/400 (the AS/400 operating system).

   To increase these session limits in SNA Server:

   a. Choose Remote LU.

   b. Choose Partners.

   c. Choose Mode.

   d. On the QPCSUPP mode, change the Parallel Session Limit to 512 (or the desired number) and change the Minimum Contention Winner Limit to half this value.

To change the session limits on the AS/400, use the CHGMODD(QPCSUPP) command.

 - Maximum sessions (MAXSSN) must match the parallel session limit.

 - Maximum conversations (MAXCNV) must match the parallel session limit.

 - Locally controlled sessions (LCLCTLSSN) must match the partner minimum contention winner limit.

KBCategory: kbnetwork

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.00 2.10 admin


Q107193: Running IBM PC Support/400 on SNA Server

Running IBM PC Support/400 on SNA Server                      [winnt]

ID: Q107193    CREATED: 16-NOV-1993   MODIFIED: 12-JUN-1995

2.00 2.10 2.11

WINDOWS

PUBLIC | kbtool

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 2.1 and 2.11

--------------------------------------------------------------------------

SNA Server for Windows NT includes a APPC router for MS-DOS which supports the IBM PC Support/400 product. When loaded, IBM PC Support/400 users may access their AS/400 through SNA Server, using an SNA Server MS-DOS client. This article describes configuration changes to use IBM PC Support/400 through SNA Server.

MORE INFORMATION

================

To use IBM PC Support/400 through SNA Server, do the following:

Do the following from SNA Server Admin:

1. Configure a connection to the AS/400 (see the SNA Server "Administration Guide" or Help for details on configuring a connection for each link  service type).

2. Add a Remote APPC LU to the connection:

   a. Highlight the connection and press Insert Select: APPC (Remote)

   b. Add Remote LU Properties LU Alias:

      Control Point Name of the AS/400 Network Name: AS/400 network name

      LU Name: same as LU Alias

      Uninterpreted LU Name: same as LU Name or blank

      Supports Parallel Sessions: Yes

      Enable Automatic Partnering: Yes/No (optional)

      Choose OK. (Partners will be set up later.)

3. Add a Local APPC LU to the Server

   a. Highlight the Server (the computer name running SNA Server) and press Insert; in the New Logical Unit field, select APPC (Local).

   b. Add Properties:

      LU 6.2 Type: Independent

      LU Alias:  User name (or any unique LU name)

      Network Name: Same as network name on node definition for this server (usually APPN)

      LU Name: same as LU Alias

   c. Partners (select):

      Select Add and the select the correct Partner LU (created in step 2 above) and partner with the "QPCSUPP" Mode (this is partnered by default), then select Close on the Partner dialog box and choose OK on the Properties dialog box.

   d. Save the new configuration and activate SNA Server and connection.

Do the following on the SNA Server client workstation:

1. Install the SNA Server MS-DOS client software (run the SETUP program off the \\<server>\CLIENTS\MSDOS directory)

2. Copy the SNA Server MS-DOS client ROUTER.EXE and INITRTR.EXE into your PCS directory.

3. In the CONFIG.PCS file, change the Network.LUName on the RTLN line to match the Network.LUName configured at the server. The network name should match the network name of the server and the LUName should match the Local APPC LU name.

4. Start SNABASE and ROUTER.

Once they have started, you should be able to use IBM PC Support/400.

NOTE: IBM PC Support/400 runs on the SNA Server MS-DOS client. In order to use the Windows 3270 or 5250 applet included with SNA Server, you must load the SNA Server Windows client software. The SNA Server MS-DOS client software does not operate concurrently with the SNA Server Windows client software--only one can be loaded at one time.

5. Using the Enhanced version of IBM PC Support

If you are using the Enhanced version of IBM PC Support (instead of the Basic version), the Enhanced functions will not be able to find the real-mode SNA Server MS-DOS router. To solve this, the RTRMAP.EXE utility must be downloaded from the AS/400 shared folders drive (by default, located in the I:\FL2 directory), copied to the client workstation and loaded after the ROUTER utility is loaded.

NOTE: There are known problems running the enhanced mode shared folders function over the real mode MS-DOS router. There is no solution for this problem, except to revert to the Basic version of PC Support, or to upgrade to IBM Client Access/400 and the SNA Server 2.11 Windows client software.

Please see the Microsoft SNA Server 2.1 Installation Guide, Chapter #3, pg.82-89 for detailed instructions on installing and configuring the SNA Server MS-DOS router to support IBM PC Support, and for special considerations when running on a Windows or Windows for Workgroups client machine.

KBCategory: kbtool

KBSubcategory: ntutil

Additional reference words: wfw wfwg prodsna 2.00 2.10 2.11 DOS

PCSupport/400


Q126396: SNA Server 3270 LU is Available, but no signon screen appears

SNA Server 3270 LU is Available, But No Sign On Screen Appears[winnt]

ID: Q126396    CREATED: 22-FEB-1995   MODIFIED: 24-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

--------------------------------------------------------------------------

SYMPTOMS

========

After a positive response to an ACTLU (ACTLU +RSP), the SNA Server service submits a notify message to the host indicating that the LU can be activated. The SNA Server service waits for a response to the message by default. However, some VTAM/NCP versions do not respond properly to notify messages, causing 3270 LU session activation problems with SNA Server.

If the host system does not support notify messages, when you attempt to bind your computer to an LU using a 3270 emulator, the host sign on screen does not appear. The administrator can run SNA Server Administrator and observe that the LU status is Available.

If you run SNATRACE and turn on SNA Server SNA Format or Data Link Control tracing, the following message sequence occurs:

 - ACTPU RQD

 - ACTPU +RSP

  <Other messages>

 - ACTLU RQD

 - ACTLU +RSP

 - NOTIFY RQD

 - No NOTIFY +RSP is received

RESOLUTION

==========

To correct this problem, add the following registry entry using REGEDT32, as described in Appendix C of the SNA Server 2.1 "Reference Guide" (page 198):

   \HKey_Local_Machine

      \System

         \CurrentControlSet

            \Services

               \SNAServr

                  \Parameters\NONOTIFYRSP:REG_SZ:YES

Stop and start the SNA Server service so the change can take effect.

KBCategory: kbnetwork

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.00 2.10 admin signon


Q126397: SNA Server installation guidelines (DC or Member Server)

SNA Server Installation Guidelines (DC or Member Server)      [winnt]

ID: Q126397    CREATED: 22-FEB-1995   MODIFIED: 24-FEB-1995

2.10

WINDOWS

PUBLIC | kbnetwork

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

--------------------------------------------------------------------------

SUMMARY

=======

This article covers the implications of installing SNA Server on a primary domain controller/backup domain controller rather than a member server.

MORE INFORMATION

================

If SNA Servers in the same domain are located across routers, an administrator must install SNA Server on a primary domain controller (PDC) or backup domain controller (BDC). SNA Server to SNA Server communication is mailslot or datagram based. SNA Server uses the winlogon protocols when sending messages across routers.

NOTE: To configure SNA Server to communicate across IP routers, run SNA Server Administrator, choose Server Broadcasts from the Options menu, and select Microsoft Networking and Route Server Broadcasts over IP Routers.

SNA Server logs users onto the Windows NT domain before allowing any requests to be processed, regardless of the transport used by the client to connect to SNA Server. If SNA Server logs users onto the domain over named pipes, the users is not prompted for the domain password or username. For other client server protocols (IPX/SPX, TCP/IP, Banyan, and AppleTalk), the user is prompted for the domain password and username. As a result, each new client connection to SNA Server results in a winlogon transaction which, in the case of a member server, needs to be authenticated across the network by a PDC or BDC. A Windows NT member server does maintain the domain user database, and therefore must rely on a BDC or PDC to validate the user over a secure channel.

If the PDC or BDC spend a large percentage of CPU time servicing winlogon requests, and the clients generally stay connected to SNA Servers for a long time, then the administrator should install SNA Server on a member server. If clients connect and disconnect frequently from SNA Server, and the Windows NT domain is primarily used for SNA access (as is likely the case when you install in an existing NetWare or Banyan environment), you should install SNA Server on the PDC or BDC.

KBCategory: kbnetwork

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.10 backup domain controller bdc dc

admin user name mail slot


Q126398: Limits on OtherServers parameter in SNA Server

Limits on OtherServers Parameter in SNA Server.               [winnt]

ID: Q126398    CREATED: 22-FEB-1995   MODIFIED: 23-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork kbenv

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server version 2.1.

 - Microsoft SNA Server version 2.0.

----------------------------------------------------------------------

Summary

=======

The OtherServers option on SNA Server clients gives the client access to LUs through SNA Servers that are outside of the client's primary SNA Server domain. The number of servers that can be listed in the OtherServers parameter depends on the client's computer platform as follows:

Platform         Maximum Number of Servers in OtherServers

----------           -----------------------------------------

Windows NT   No limit

Win3.x:          15 (or 256/<length of server name>)

MS-DOS:        8

More Information

================

The number of servers in the local domain may limit the number of OtherServers you can actually use. Local servers are added to the service table before OtherServers. The service table has 32 entries in Win3.x, 16 in DOS, and no limit for Windows NT.  The sponsor naps and the local nap reserve one entry in the service table. Also, if any invokable APPC transaction programs (TP) are configured on an SNA Server client, each local TP reserves one service table entry.

Additional reference words: ntprotocol prodsna 2.0 2.1

KBCategory: kbnetwork kbenv

KBSubCategory: ntconfig


Q126399: Event ID 49: Node ID from remote computer was rejected

Event ID 49: Node ID from Remote Computer was Rejected        [winnt]

ID: Q126399    CREATED: 22-FEB-1995   MODIFIED: 23-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork kbenv

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server version 2.1

 - Microsoft SNA Server version 2.0

----------------------------------------------------------------------

SYMPTOMS

========

On your SNA Server, an attempted connection is not able to activate and holds in a pending state. This error message appears in the error log:

   Event ID 49   Node ID from remote computer was rejected

From the SNA Server client, when you attempt to connect using a 5250 emulator the following error message appears:

   There is a problem with the configuration of the connection to the AS/400

   Primary return code = 0003

   Secondary return code = 00000005

CAUSE

=====

One of the two following conditions exist:

 - The Network Name in the Connection Properties or the Server properties does not match the Local Network ID in the Network attributes screen on the AS/400.

 - The Remote Control Point Name in the Connection Properties does not match the Local Control Point name defined in the AS/400 Network Attribute Screen.

RESOLUTION

==========

Reconfigure to correct the problem.

Additional reference words: prodsna 2.00 2.10

KBCategory: kbnetwork kbenv

KBSubCategory: ntconfig


Q126400: AS/400 connection active, but no sessions negotiated

SNA Server-AS/400 Connection Active, But No Sessions Negotiated[winnt]

ID: Q126400    CREATED: 22-FEB-1995   MODIFIED: 24-FEB-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork kbenv

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT version 2.1

 - Microsoft SNA Server for Windows NT version 2.0

----------------------------------------------------------------------

SYMPTOMS

========

When you try to connect from an SNA Server client using a 5250 emulator, the following error message appears:

   There is a problem with the configuration of the connection to the AS/400

   Primary return code = 0003

   Secondary return code = 00000005

In SNA Server Admin, you find the AS/400 connection is active, but it has not negotiates any sessions.

NOTE: You can identify how many sessions have been negotiated by starting the Local APPC LU icon and choosing the Status button.

You will see something like this:

   Partner LU         Mode            Connection             Sessions   Limit

   ----------------------------------------------------------------------------------------------

   <remote LU>   QPCSUPP      <connection_name>   0          64

   <remote LU>   SNASVCMG   <connection_name>   0          2

The value is commonly 64, but may be different if the QPCSUPP mode has been modified in SNA Server Admin and on the AS/400. If the Limit on the QPCSUPP mode is 0, then SNA Server has failed to negotiate any sessions. The maximum Parallel Session Limit that QPCSUPP supports on the AS/400 is 512. This limit was imposed by IBM.

CAUSE

=====

The following configurations cause 0 sessions to be negotiated:

 - The local APPC LU is not partnered with a Remote APPC LU in SNA Server Admin.

 - The LU-LU pairing is not using QPCSUPP mode. SNA Server AS/400 connections require that this mode be used. However, LU6.2 connections configured to other SNA devices do not necessarily require this mode.

 - The LU-LU pairing is using the QPCSUPP mode, but the mode has been modified in SNA Server or on the AS/400 so they no longer match. For instance, the Parallel Session Limit parameter is not the same on the SNA Server and on the AS/400.

 - The APPC remote LU's LU name does not match the AS/400 Local Control Point Name as defined in the AS/400's Network Attribute screen.

RESOLUTION

==========

Reconfigure to correct the problem.

Additional reference words: prodsna 2.1

KBCategory: kbnetwork kbenv

KBSubCategory: ntconfig


Q126432: SNA Server Windows client memory tuning

SNA Server Windows Client Memory Tuning                       [winnt]

ID: Q126432    CREATED: 23-FEB-1995   MODIFIED: 12-APR-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

----------------------------------------------------------------------

SUMMARY

=======

The following tuning suggestions can reduce conventional memory usage on Windows 3.x and Windows for Workgroups 3.x clients running the SNA Server Windows 3.x client software. If the machine is running low on available conventional memory (memory between zero and one megabyte), you may see the following problems, no matter how much RAM you have installed:

 - One of the following error message appears:

      Out of Memory

      SNA Server Error 546: Cannot establish connection with SNA Server

      NAP not started

 - The SNA Server Windows client icon (WNAP.EXE) does not maintain its sponsor connection

 - A 5250 emulator displays the following APPC error:

      Primary return code = F011        (AP_UNEXPECTED_DOS_ERROR)

      Secondary return code = 00000008  (out of memory)

 - Applications the do not properly handle low memory situations cause general protection (GP) faults or stop responding (hang).

MORE INFORMATION

================

Windows client memory tuning suggestions:

SNA Server Windows Client Memory Allocation

-------------------------------------------

By default, WNAP reserves enough internal buffers to handle connections through several servers. If you only connect through one or two SNA Servers, you can add the following entry to the [wnap] section of WIN.INI:

   maxpipes=6

This entry determines the number of communication buffers that the SNA client software allocates, regardless of the client network interface selected (named pipes, IPX/SPX, TCP/IP or Banyan IP).

Stop and restart WNAP so this change can take effect.

Disabling Network DDE on Windows for Workgroups Version 3.11 Machines

---------------------------------------------------------------------

A significant amount of conventional memory can be gained by disabling Network DDE, if it is not being used. To do this, run the Windows for Workgroups 3.11 Control Panel, choose Network, choose Startup, and clear the Network DDE check box. Quit and restart Windows for Workgroups so this change can take effect.

You can make more conventional memory available by removing any unnecessary drivers or terminate-and-stay-resident (TSR) programs from the configuration, and maximizing the use of available upper memory block (UMB) areas if MS-DOS 5.0 or later is being used.

Identify Low Memory Situations

------------------------------

You can use the Heap Walker utility (HEAPWALK.EXE), included with the Windows 3.1 SDK, to help identify low conventional memory situation in Windows:

 - Select the Sort/Address option to view memory allocation from low to high memory addresses. Conventional memory addresses start with 000xxxxx while virtual addresses start with 80xxxxxx.

 - All segments which appear as Fixed memory (where the FLG field is set to F) cannot be moved or discarded by Windows. Low conventional memory problems occur when excessive Fixed memory regions occupy conventional memory space, and very few free conventional memory areas are available, even though the may be large amounts of virtual memory available.

 - You can save Heap Walker information to a file called HWG0x.TXT (where x increments from 0 - 9) by choosing Save from the file menu.

If HEAPWALK is not available, you can run MEM /C (before running Windows or Windows for Workgroups) to determine how much free conventional memory is available before Windows is loaded. You cannot view Windows memory allocation.

KBCategory: kbnetwork

KBSubcategory: ntconfig

Additional reference words: 2.00 2.10 prodsna tcp/ip gpf


Q126434: Configuring a Windows NT user as an SNA Server Administrator

Configuring a Windows NT User as an SNA Server Administrator  [winnt]

ID: Q126434    CREATED: 23-FEB-1995   MODIFIED: 24-FEB-1995

2.10

WINDOWS

PUBLIC | kbnetwork

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

----------------------------------------------------------------------

SYMPTOMS

========

SNA Server Admin allows an authorized administrator to define administrative access to SNA Server. However, if a Windows NT user is granted Full Control using SNA Admin, the following error occurs when the user attempts to save the SNA Server configuration file:

   Error: 4006

   Unable to get or set security information on the config file.

Windows NT administrators do not have this problem.

RESOLUTION

==========

To allow a Windows NT user to fully administer the SNA Server:

1. Run Windows NT User Manager for Domains.

2. Choose Policies and then choose User Rights.

3. Select "Manage Auditing And Security Log."

4. Grant the user this user right.

For more information on security, see Chapter 12 "Setting up security with SNA Server" of the "SNA Server version 2.1 Admin Guide."

KBCategory: kbnetwork

KBSubcategory: ntsecurity

Additional reference words: ntprotocol prodsna 2.10 4006 user admin


Q126451: SNA Server Windows NT client loses session to server

SNA Server: Windows NT Client Loses Session To Server         [winnt]

ID: Q126451    CREATED: 23-FEB-1995   MODIFIED: 14-APR-1995

2.10 3.50

WINDOWS

PUBLIC | kbnetwork kbbug3.50

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft SNA Server for Windows NT, version 2.1

----------------------------------------------------------------------

SYMPTOMS

========

When you close an SNA Server 5250 (or APPC) session on a Windows NT 3.5 computer, any other SNA applications with a connection to the server lose their session. As a result:

 - If SNA Admin is also running on the same machine, and the 5250 session is disconnected. SNA Admin may also lose its connection to SNA Server, causing an SNA Server Admin Error.

   NOTE: 5250 emulators also use the SNA Server APPC interface.

 - The Windows NT system event log includes the following error (for each time the user disconnected their 5250 session), if TCP/IP is being used:

      Event: 2012

      Source: Srv

      Description: The server has encountered a network error.

 - Within an internal SNA Server client trace, the named pipe session fails with rc=59 (An unexpected network error occurred).

 - Any other APPC applications with sessions against the same SNA Server receive the following error:

      primary return code = F003 = AP_COMM_SUBSYSTEM_ABENDED

   This error returned by SNA Server when its client-server LAN session is lost.

CAUSE

=====

If a Windows NT process has a pending write request on a named pipe and then calls ExitProcess() before the write completes, all other applications connected to the same server pipe fail with error 59 (unexpected pipe close).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5. A fix to this problem is in development, but has not been regression-tested and may be destabilizing in production environments. Contact Microsoft Product Support Services for more information on the availability of this fix.

KBCategory: kbnetwork kbbug3.50

KBSubcategory: ntnetserv

Additional reference words: prodnt prodsna 2.10 3.50 rdr.sys 2012 sna f003


Q126546: Problems running SNA Server 5250 applet (autoconnect enabled)

Problems Running SNA Server 5250 Applet (Autoconnect Enabled) [winnt]

ID: Q126546    CREATED: 26-FEB-1995   MODIFIED: 27-FEB-1995

2.10

WINDOWS

PUBLIC |

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

----------------------------------------------------------------------

SYMPTOMS

========

If you run the SNA Server 2.1 5250 applet, and the 5250 Session/Autoconnect switch is enabled, the following problems can occur:

 - When connecting over any SNA Server client-server interface that requires a user logon (TCP/IP sockets, NetWare IPX/SPX, or Banyan IP):

    - The session does not automatically activate.

    - Connecting the session resulting in the Interface Not Found" error message.

    - The following error message appears when you quit the 5250 applet:

         SNASRV caused a General Protection Fault in module SNASRV.EXE at 0001:0589

    - When the SNA client login fails and you select Close, the client machine stops responding (hang).

 - When connecting over the SNA Server client-server named pipes interface, if WNAP fails to start due to a 629 or 546 error (where the client cannot find or connect to an SNA Server), the following error appears:

      TP Started verb has completed with primary return code Unexpected DOS Error:

      Primary Return Code = F011

      Secondary Return Code = 08000000

CAUSE

=====

The SNA Server 5250 applet does not wait long enough for the underlying SNA client module (WNAP) to initialize, and then fails to work properly when WNAP fails to initialize.

RESOLUTION

==========

This problem is fixed in SNA Server 2.11.

To workaround this problem on SNA Server 2.1, configure WNAP to start before the 5250 applet is started. To do this, add a WNAP.EXE icon to the Windows or Windows for Workgroups Startup group.

STATUS

======

Microsoft has confirmed this to be a problem in SNA Server 2.1. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug2.10

KBSubcategory: ntnetserv

Additional reference words: prodsna 2.10 5250 F011 snasrv autoconnect wfw

wfwg Windows 3.x 3.10 3.11 application auto connect automatically


Q127740: Eicon WAN Services V3R2 problems with SNA Server

Eicon WAN Services V3R2 Problems with SNA Server              [winnt]

ID: Q127740    CREATED: 15-MAR-1995   MODIFIED: 17-MAR-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork kb3rdparty

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

-------------------------------------------------------------------------

SYMPTOMS

========

The following problems have been observed using SNA Server 2.0 and 2.1 with an X.25 connection supported by Eicon WAN Services V3R2 (over an Eicon adapter):

 - When SNA Server is configured to autostart, it stop responding (hangs) at Windows NT start up. SNA Admin may hang indefinitely with an hourglass or clients may receive an XCLOCK status in their 3270 emulator when opening a session.

 - Random 3270 LU's configured off an X.25 connection supported by the Eicon adapter may hang or fail to work when opened by an SNA Server 3270 client.

CAUSE

=====

Both problems have been isolated to the SNA Server link service included with Eicon WAN Services V3R2.

RESOLUTION

==========

Eicon WAN Services V3R2a maintenance release corrects both of these

problems. Contact Eicon Technology technical support to obtain this update.

KBCategory: kbnetwork kb3rdparty

KBSubcategory: ntnetserv ntprotocol

Additional reference words: prodsna 2.10 HSI 3.2 3.2a


Q128118: SNA Server Win 3.x setup error: no network installed

SNA Server Win3.x Client Setup Err Msg: No Windows network... [winnt]

ID: Q128118    CREATED: 26-MAR-1995   MODIFIED: 27-MAR-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork kbsetup kbinterop kb3rdparty

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

-------------------------------------------------------------------------

SYMPTOMS

========

When you run SNA Server Win3.x Client Setup the following error message appears:

   No Windows network Installed

CAUSE

=====

Setup has failed to detect your network.

MORE INFORMATION

================

SNA Server Win3.x Client Setup uses the following methods to check for various LAN interfaces on Win3.x clients:

Named Pipes

-----------

If you are running Windows for Workgroups, Setup checks the SYSTEM.INI file for the following:

   [boot]

   ...

   network.drv=wfwnet.drv

If you are running Microsoft LAN Manager or IBM LAN Requester, Setup looks for LANMAN.INI or DOSLAN.INI, respectively. If both are found, Setup uses the LANMAN.INI file. If either is found, Setup loads NETAPI.DLL and calls NetWkstaGetInfo() to get the version information.

NetWare IPX/SPX

---------------

Setup calls LoadLibrary( "nwipxspx.dll" ). If that fails, Setup calls LoadLibrary( "a:\nwipxspx.dll" ). If that succeeds, Setup tries to call SPXInitialize() in that library.

TCP/IP Sockets

--------------

NOTE: The following text does not apply to SNA Server version 2.0 as it does not include support for TCP/IP sockets.

Setup calls into WINSOCK.DLL to check for its presence. It needs to support Windows Sockets version 1.1.

Banyan IP

---------

NOTE: The following text does not apply to SNA Server version 2.0 as it does not include support for Banyan IP.

Setup calls LoadLibrary( "VNSAPI.DLL" ). If that succeeds, Setup considers Banyan to be installed. Setup then calls VnsGetUserName() from that library to get the default StreetTalk group name.

KBCategory: kbnetwork kbsetup kbinterop kb3rdparty

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.00 2.10 prodsna wfw wfwg street talk


Q128168: Configuring Windows 3.x clients to use TCP/IP with SNA Server

Configuring Windows 3.x Clients to use TCP/IP with SNA Server [winnt]

ID: Q128168    CREATED: 27-MAR-1995   MODIFIED: 28-MAR-1995

2.10

WINDOWS

PUBLIC | kbnetwork kbinterop kbusage kbsetup

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

------------------------------------------------------------------------

SUMMARY

=======

To configure Windows 3.x clients to use TCP/IP when communicating with SNA Servers running Microsoft TCP/IP, either run setup and choose TCP/IP or manually change the WIN.INI file.

MORE INFORMATION

================

To manually change the WIN.INI file so Windows 3.x clients use TCP/IP when communicating with SNA Servers running Microsoft TCP/IP:

1. Set LocalFlag= ( REMOTE | LOCAL ).

   Use remote if the domain or workgroup name of the SNA Server is different from the one used in the WORKGROUP= entry. Use Local if the WORKGROUP= name is the same as the SNA Server. This LocalFlag entry is only used by setup to determine which option was selected.

2. Set Remote = ( domainname | \\servername | \\ipaddress ), where:

      domainname =   The Windows NT domain name where SNA Server resides

      \\servername = The Windows NT computername of an SNA Server in the domain

      \\ipaddress =  The Windows NT IP address of SNA Server (for example, \\11.22.33.44)

3. Change NosType= ( TCPIP | NOVELL | LANMAN ) to NosType=TCPIP.

4. Change NosSetup= ( TCPIP | NOVELL | WFW ) to NosSetup=TCPIP.

5. Add LogonUserName= and LogonDomainName=. These entries are used to specify the default  username and logon domain for the workstation.These options are also used by the NetWare and Vines interfaces.

After you configure Windows 3.x clients use TCP/IP when communicating with SNA Servers running Microsoft TCP/IP, you can use two additional command line switches (/user: and /pwd:) with WNAP.EXE.

NOTE: If you don't want to have to provide user and password information when you use the above command, add the preftrans= entry to the [network] section of Windows for Workgroups client's SYSTEM.INI file.

KBCategory: kbnetwork kbinterop kbusage kbsetup

KBSubcategory: ntprotocol nthowto

Additional reference words: prodsna 2.00 2.10 3.50 3.1 domain computer

server name local flag nos setup type logon user log on


Q128244: SNA Server Load Balancing and Hot Backup

SNA Server Load Balancing and Hot Backup                      [winnt]

ID: Q128244    CREATED: 28-MAR-1995   MODIFIED: 31-MAR-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

------------------------------------------------------------------------

SUMMARY

=======

This article describes how SNA Server clients perform load balancing and hot backups across SNA Servers.

When an SNA session is opened on an SNA Server client machine, the underlying SNA client software randomly chooses a server to try. In effect, load balancing and hot backups are initiated by the client. However, this requires two or more SNA Servers to be configured to support the same LU resources (3270, LUA pool, or APPC LU aliases spanning two or more servers).

Load balancing and hot backups are supported regardless of the SNA Server client-server LAN interface used (Named pipes, IPX/SPX, TCP/IP sockets, Banyan IP, or AppleTalk).

MORE INFORMATION

================

How SNA Server Clients Load Balance and Hot Backup to SNA Servers

-----------------------------------------------------------------

 - The SnaBase service on each SNA Server broadcasts a list of SNA Server services running on the server to all other SNA Servers in the domain. The SnaBase service listens for these broadcasts and dynamically maintains a list of SNA Server services in the domain.

   NOTE: The transports used and frequency of SNA Server broadcasts are controlled at the Server Broadcasts dialog box, found by choosing Server Broadcasts from the Options menu of the SNA Server Administrator. This configures the domain.

 - The SNA client process (SnaBase service on Windows NT, WNAP.EXE on Windows 3.x, SNABASE.EXE on MS-DOS, and COMNAP.EXE on OS/2) opens a sponsor connection to the SnaBase service on an SNA Server in the domain. This sponsor connection remains active while the SNA client process is running. When the SNA client process first starts, the client receives a list of all SNA Servers in the domain. Afterward, only server changes are sent (as SNA Servers are started and stopped in the domain).

   NOTE: The transports that an SNA Server supports for client connections is configured in the Protocol dialog box in SNA Server Setup. This is configured on a server by server basis.

 - When an SNA application requests a session (3270, LUA, APPC, or CPIC, etc.), the underlying SNA client sends the request to a randomly selected server. If the server supports the LU being requested and the LU resource is available, the session is established through the server.

   NOTE: Besides opening sessions to SNA Servers in the sponsor domain, an "otherservers" parameter can be configured on the client to specify additional servers that the client should try to open sessions with. More information about the otherservers parameter is included below.

 - If a second or subsequent client session is opened, the client first tries the servers that it already has a session with to conserve LAN resources on the client.

Configuring Fault Tolerance For 3270 Sessions

---------------------------------------------

1. Group similar types of 3270 display LU's across servers and connections into a 3270 LU pool using the LU Pools dialog box in SNA Server Administrator. Only LU's of a given type can be pooled together. Secondary connections can be configured as "On demand" to only start when needed.

   NOTE: SNA Server doesn't support pooling of 3270 Printer LU's. Specific Printer LU's must be preassigned to a user in order for print jobs to be routed to a known printer destination. For example:

      In the Servers and Connections window in SNA Administrator:

      SERVER1                         SERVER2

         TOKEN1  connection               TOKEN2 connection

              SRV1LU02 (3270 LU)              SRV2LU02  (3270 LU)

              SRV1LU03 (3270 LU)              SRV2LU03  (3270 LU)

              SRV1LU04 (3270 LU)              SRV2LU03  (3270 LU)

      In the LU Pools window in SNA Administrator:

         Pool: 3270POOL

         LU Names: SRV1LU02

                   SRV1LU03

                   SRV2LU02

                   SRV2LU03

2. Assign one or more instances of the 3270 pool to an SNA Server user or group, using the Users and Groups windows in SNA Server Administrator. For example:

      User: Everyone

         LU or LU Pool Session #1: 3270POOL

      User: DOMAIN\Domain Users

         LU or LU Pool Session #1: 3270POOL

         LU or LU Pool Session #2: 3270POOL

      NOTE: In this example, one pooled session has been granted to the Everyone group and two pooled sessions have been granted to users from the Domain Users group.

3. When an SNA client opens a 3270 pooled session, a session is established through a server which supports an available instance of the LU pool. For example, in the Session / Session Configuration dialog box in the 3270 applet, configure the pool like this:

      LU or Pool Name: 3270POOL

   and choose Session / Connect.

Configuring Fault Tolerance for APPC/5250 Sessions

--------------------------------------------------

1. Configure redundant Local/Remote LU Aliases across SNA Servers in the SNA Server Administrator. For example:

      Within Servers and Connections window in SNA Administrator:

      SERVER1

             Local APPC LU alias = SNASERV

             Local APPC LU network name = APPN, LU Name = SERVER1

         TOKEN1  connection

             Remote APPC LU alias = AS400

             Remote APPC LU network name = APPN  LU Name = AS400

             (partnered with SNASERV using the QPCSUPP mode)

      SERVER2

             Local APPC LU alias = SNASERV

             Local APPC LU network name = APPN, LU Name = SERVER2

         TOKEN2  connection

             Remote APPC LU alias = AS400

             Remote APPC LU network name = APPN  LU Name = AS400

             (partnered with SNASERV using the QPCSUPP mode)

NOTE: While the Local APPC LU alias must be the same for SNA Servers to support fault tolerance, the LU Names must be unique to ensure that unique AS/400 device names are used.  Otherwise, if an AS/400 device is in use, another 5250 user may hang when attempting to open the same device name.

2. In the APPC application (such as the 5250 emulator), open a session using the Local and Remote LU aliases supported by the servers. For example, using the 5250 applet, open the Session / Session Configuration dialog box and enter:

       Local LU alias   = SNASERV

       Partner LU alias = AS400

   NOTE: It's possible to "Default" the Local and Remote LU aliases on a user or group record in SNA Server Admin. When APPC LU aliases are defaulted on a user/group record, these LU aliases are used if no LU aliases are provided by the APPC application. Other ways of defaulting APPC LU's are described in Chapter 6 of the SNA Server 2.1 Admin Guide.

The "Otherservers" Feature

--------------------------

The SNA Server client software supports an "otherservers" configuration entry, as described in Appendix C of the SNA Server Reference Guide. This entry allows the client to try connecting to a list of SNA Servers when opening an SNA session, in addition to the SNA Servers running in the domain to which the client has a sponsor connection.

The SNA Server client will always retrieve it's user/group (3270 and APPC alias) configuration entries from the domain which the client has an established sponsor connection. The SNA Server client has no way of retrieving the user/group record configured on servers outside of this domain (unless the SNA client is reconfigured to connect to a different sponsor server).

In order to open a session through an "otherserver" (located outside of the client domain), these servers must be configured to support the same LU resource names (i.e. 3270 pool names and APPC LU alias names) as the primary domain.

Troubleshooting Suggestions

---------------------------

If users don't appear to be load balancing across SNA Servers:

- Using SNA Administrator, make sure the SNA Servers are running, the connections supporting the pooled LU's (or APPC LU's) are active and the LU's are available. The 3270 LU status should appear as "Available". The APPC LU status is viewable by zooming on the Local LU and choosing "Status". The APPC LU session limit should be non-zero. If it is zero, this indicates an APPC LU session activation problem where SNA Server Data Link Control traces and SNA Server configuration file (COM.CFG) are needed to diagnose the cause. If the active session count is the same as the LU session limit, this means all available sessions are in use on this APPC LU/LU pair.

- If the servers are operating normally, check the Windows NT application event log (using Event Viewer) to see if the SNA Server service or connections were recently restarted. If so, only recent users have established sessions to this server.

- For 3270, make sure the users opening sessions against the servers have been assigned an instance of an LU pool which spans the servers evenly. Note that once a user has a session against a server, additional client sessions will be opened to the same server first.

- Make sure the user has LAN access to open a session against the servers in the domain or to the "otherservers". This is especially true if a user is unable to get a session through an "otherserver" which resides outside of the domain.

- Check the Windows NT system event log for any indication of Server service resource shortages. If so, this could indicate LAN connection problems for SNA clients connecting over a named pipe connection.

KBCategory: kbnetwork

KBSubcategory: ntnetserv ntprotocol

Additional reference words: prodsna 2.00 2.10 backup prodsna


Q128245: CPIC/APPC program may hang opening Dependent APPC session

CPIC/APPC Program May Hang Opening a Dependent APPC Session   [winnt]

ID: Q128245    CREATED: 28-MAR-1995   MODIFIED: 31-MAR-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork kbprg

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

-------------------------------------------------------------------------

SYMPTOMS

========

When a CPIC or APPC application allocates a dependent LU6.2 session where the dependent APPC LU is defined in SNA Server Admin to be a "Member of Default Outgoing Local APPC LU Pool", the allocate request may hang. Within an APPC application, the call to [MC_]ALLOCATE may not return. Within a CPIC application, the call to CMINIT may not return (since CPIC runs over APPC, the underlying APPC [MC_]ALLOCATE hangs).

CAUSE

=====

SNA Server does not support pooling of dependent APPC LU's, however, the SNA Server Admin program doesn't prevent it. The problem doesn't occur if independent APPC LU's are configured to be a member of the default outgoing APPC LU pool.

With dependent APPC LU's, SNA Server may have allocated the dependent APPC LU/LU session to another APPC or CPIC application. If a second APPC or CPIC application attempts to open the same dependent APPC LU (which can occur if a dependent APPC LU is configured to be a member of the default APPC LU pool), the second application's [MC_]ALLOCATE call will hang until the session becomes available.

RESOLUTION

==========

This problem is fixed in SNA Server 2.11.

To workaround this problem on SNA Server 2.1, each CPIC or APPC application must use a unique dependent Local APPC LU.

For an APPC application, the application must be predefined to use a specific dependent Local APPC LU alias. If the Local LU alias is left blank, the default Local APPC LU can be associated to a user or group within the "Users and Groups" window of SNA Server Admin.

For a CPIC application, the Local APPC LU alias must be preset within SNA Server by either:

   Defaulting the user/group to use a specific Local APPC LU alias:

   Within the "Users and Groups" window of SNA Admin, the user or group record can be configured with a default Local and Remote APPC LU aliases.

   -or-

   Defaulting the workstation to use a specific Local APPC LU alias:

   The SNA Server client software can be defined with a default Local APPC LU alias, as described in the CPI-C API section of Appendix C in the SNA Server Reference Guide:

Windows NT clients (within the Registry):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SnaBase\Parameters\Client

            application: REG_SZ: localLUalias

         Win 3.x clients (within WIN.INI) or OS/2 clients (within SNA.INI):

            [ApplicationName]

            APPCLLU=localLUalias

            where application is the name of the CPIC application (without the .EXE extension).

STATUS

======

Microsoft has confirmed this to be a problem in SNA Server version 2.1. Customers should either upgrade to SNA Server 2.11, or follow a workaround described above.

KBCategory: kbnetwork kbprg

KBSubcategory: ntnetserv

Additional reference words: prodsna 2.00 2.10 3.50 allocate


Q128390: Different ways a Macintosh can connect through SNA Server

Different Ways a Macintosh Can Connect Through SNA Server     [winnt]

ID: Q128390    CREATED: 30-MAR-1995   MODIFIED: 31-MAR-1995

3.10 3.11 3.50

WINDOWS

PUBLIC | kbnetwork kbsetup kbinterop kb3rdparty

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

-------------------------------------------------------------------------

SUMMARY

=======

This article discusses the three ways to connect a Macintosh to a mainframe through SNA Server.

MORE INFORMATION

================

Downstream PU

-------------

On the Macintosh, install a Token Ring card and bind the DLC protocol to it. In SNA Server Admin, configure a downstream connection for the Macintosh. For instructions on setting up downstream connections see Chapter 9 of the SNA Server "Administration Guide."

This configuration works with any Macintosh 3270 emulator.

NOTE: Macintoshes are not supported as Downstream PUs on Ethernet because there is no DLC support for Ethernet on a Macintosh.

TN3270

------

On the Macintosh, install TCP/IP and use any Macintosh TN3270 emulator for host sessions. On the SNA Server, install the OpenConnect Systems TN3270 Server and configure an LUA LU for the Macintosh computer.

For instructions on how to configure SNA Server Admin for LUA, see Chapter 8 of the SNA Server "Administration Guide." See OpenConnect Systems documentation for complete instructions on installing their TN3270 Server. Information on OpenConnect Systems can be found in the Third Party Companion Catalog on <sna_cd_root>\collatrl\general\isvcatal.doc. This file can also be found on the CompuServe MSSNA forum, library 1, as ISVCAT.EXE. This self extracting file contains a Microsoft Word for Windows version 2.0 formatted document.

Windows NT Services For Macintosh

---------------------------------

Configure a Windows NT machine for Services for the Macintosh, and then run Attachmate's IRMA Workstation for Macintosh v4.0 or greater and follow the instructions outlined in the "Configuring for a Microsoft SNA Server" section in Chapter 2 of the Attachmate Irma Workstation for Macintosh User's Guide.

For instructions on how to setup Services for Macintosh on a Windows NT machine see "Services for Macintosh" install guide that ships with Windows NT Server.

Currently, the only Macintosh emulator supporting AppleTalk through SNA Server is Attachmate's. However, see <sna_cd_root>\collatrl\general\isvcatal.doc for an updated list of emulators. This file can also be found on the CompuServe MSSNA forum, library 1, as ISVCAT.EXE. This self extracting file contains a Microsoft Word for Windows version 2.0 formatted document.

KBCategory: kbnetwork kbsetup kbinterop kb3rdparty

KBSubcategory: ntprotocol

Additional reference words: prodsna 2.10 sfm


Q128966: SNA Server X.25 PVC incoming calls

SNA Server X.25 PVC incoming calls.                           [winnt]

ID: Q128966    CREATED: 16-APR-1995   MODIFIED: 17-APR-1995

2.00 2.10

WINDOWS

PUBLIC |

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

-------------------------------------------------------------------------

SYMPTOMS

========

If an SNA Server X.25 Permanent Virtual Circuit (PVC) connection is configured for incoming calls only, the connection is never established.

CAUSE

=====

The SNA Server Admin program should not allow this type of configuration. Outgoing calls should always be configured for PVC connections.

WORKAROUND

==========

To work around this problem, always configure an X.25 PVC connection to support outgoing calls.

STATUS

======

Microsoft has confirmed this to be a problem in SNA Server versions 2.0 and 2.1. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug2.00 kbbug2.10

KBSubcategory: ntnetserv

Additional reference words: prodsna 2.00 2.10 admin x.25 pvc


Q131461: Forcing Windows NT clients to use Non-Named Pipe LAN Transport

Forcing Windows NT Clients to Use Non-Named Pipe LAN Transport[winnt]

ID: Q131461    CREATED: 12-JUN-1995   MODIFIED: 13-JUN-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork kbsetup kbbug2.10 kbfix2.11

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

-------------------------------------------------------------------------

SYMPTOMS

========

During SNA Server Windows NT client setup, you configure which LAN transport the SNA Server client should use to communicate to the SNA Server. SNA Server 2.0 supports Microsoft Networking (Named pipes) or Novell Netware (IPX/SPX). SNA Server 2.1 supports those, plus Banyan Vines, and TCP/IP.

SNA Server version 2.0 and 2.1 Windows NT clients default to named pipes even when the TCP/IP sockets, NetWare IPX/SPX, or Banyan IP interface is the only option chosen.

CAUSE

=====

In version 2.0 and 2.1, the SNA Server Windows NT client software defaults internally to use named pipes, even if named pipes is not chosen during SNA Server client setup.

RESOLUTION

==========

This problem is fixed in SNA Server 2.11. Under 2.11, the SNA Server Windows NT client will only try the LAN transport(s) configured during SNA Server Windows NT client setup.

WORKAROUND

==========

Under SNA Server 2.0 and 2.1, the following registry setting can be used to force the SNA Server Windows NT client to try a specific transport first:

WARNING: Using the Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of the Registry Editor can be solved. Use this tool at your own risk.

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SnaBase\Parameters

   TransportBase: REG_DWORD: 1

This will cause the SNA Server client to try the first transport selected in the SNA client installation, assuming the Microsoft Networking (named pipes) option is not chosen. If the client-server connection attempt fails, the SNA Server client will try the next transport configured during SNA client setup. If all of these fail, named pipes is tried.

STATUS

======

Microsoft has confirmed this to be a problem in SNA Server for Windows NT, versions 2.0 and 2.1. This problem has been corrected in SNA Server for Windows NT version 2.11.

The products included here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

KBCategory: kbnetwork kbsetup kbbug2.10 kbfix2.11

KBSubcategory: ntsetup nthowto ntprotocol

Additional reference words: prodsna 2.00 2.10 2.11 3.50


Q131640: Running the SNA Win 3.x client on Windows NT causes 100% CPU

Running the SNA Win 3.x client on Windows NT causes 100% CPU. [winnt]

ID: Q131640    CREATED: 15-JUN-1995   MODIFIED: 15-JUN-1995

2.00 2.10

WINDOWS

PUBLIC |

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

------------------------------------------------------------------------

SUMMARY

=======

When running the SNA Server Windows 3.x client software on Windows NT 3.1 or 3.5 machine, running Performance Monitor will show CPU utilization at 100%.  This occurs whenever the SNA Server Windows 3.x client process (WNAP.EXE) is started, even when not being used.

The WNAP process, which calls PeekMessage(), is causing the Windows NT WOW subsystem to use all available idle cycles of the CPU. However, due to sophisticated process scheduling implemented by Windows NT, other tasks/threads running at a higher priority (including foreground tasks which receive an automatic priority boost), and tasks/threads running at the same priority will continue to run.   The user will likely not experience any performance degradation.

The excessive CPU usage does not occur when running on Windows NT 3.51.

MORE INFORMATION

================

The high CPU usage occurs on Windows NT 3.1 or 3.5 with any 16-bit Windows application which implements a PeekMessage() loop to process Windows messages.  The SNA Server Windows 3.x client (WNAP.EXE) uses a PeekMessage() loop.

KBCategory: kbnetwork kbinterop

KBSubcategory: ntnetserv

Additional reference words: prodsna 2.00 2.10 3.50 CPU


Q128985: Comparing SNA client TCP/IP named pipes vs sockets

Comparing SNA client TCP/IP named pipes vs sockets            [winnt]

ID: Q128985    CREATED: 17-APR-1995   MODIFIED: 20-APR-1995

2.10

WINDOWS

PUBLIC | kbnetwork kbinterop

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

------------------------------------------------------------------------

SUMMARY

=======

The SNA Server 2.1 client software supports different LAN interfaces to communicate with SNA Server, configured during SNA Server client setup:

  - Microsoft Networking (named pipes)

  - Novell Netware (native ipx/spx)

  - Banyan VINES  (via Banyan IP)

  - TCP/IP  (via windows sockets)

When the Microsoft TCP/IP protocol is installed onto a Windows 3.1, Windows for Workgroups 3.11, or Windows NT machine, the SNA Server client can communicate to the server over:

 - Microsoft Networking (named pipes over tcp/ip)

   -or-

 - TCP/IP (over the Windows sockets interface)

The TCP/IP windows sockets interface was added to SNA Server 2.1 and is the recommended SNA Server client connection method for customers using the TCP/IP transport. NOTE: To use TCP/IP sockets, the SNA Server client software requires that the TCP/IP transport support the Windows Sockets version 1.1 specification.  TCP/IP sockets provides better performance and better reliability when connecting to servers across routed IP networks.

This article compares these two methods of connecting from an SNA Server

client.

MORE INFORMATION

================

Named Pipes over TCP/IP

-----------------------

When communicating over named pipes, the SNA Server client opens a named pipe resource (\\server\PIPE\...) which is created by the SNA Server. A named pipe is an interprocess communication facility supported by the client redirector (that is, Windows for Workgroups protected mode redirector) and the Windows NT Server. The SNA Server client and server send messages to each other over this named pipe.

As with shared file and printer connections, named pipe session traffic flows over a NetBIOS session between the client redirector and the Windows NT server using the "Server Message Block" (SMB) protocol. The following illustrates the message flow:

  SNA Client         <- Named Pipe ->           SNA Server

  Redirector   <- SMB over NetBIOS session ->   NT Server

  TCP/IP          <- TCP/IP connection ->       TCP/IP

  Network card <---------------------------->   Network card

A typical message packet would include the following information:

   [ IP | TCP [ NetBios [ SMB ( SNA application data ) ] ] ]

Disadvantages of Using Named Pipes

----------------------------------

- The client redirector and Windows NT server process all messages passed between the SNA Server client and the server. All named pipe messages are formatted within "SMB" requests by the client redirector and NT server which flow over a NetBios session.

- Each NetBios session requires "keep-alive" messages to flow between the client redirector and Windows NT server. These NetBIOS level acknowledgments lead to network overhead, and the possibility of NetBIOS-level timeout conditions when traveling across a routed IP network.

- A NetBIOS session over TCP/IP requires NetBIOS-to-IP address name resolution, requiring a client LMHOSTS file entry for each server, or a WINS server to provide this name resolution. DNS servers don't provide this name resolution.

- Since each SNA Server client has one outstanding read request pending on the sponsor connection, and one read pending on the SNA application session, Windows NT server resources are required to handle these pending I/O requests even when the SNA client session is idle.

Advantages of Using Named Pipes

-------------------------------

- Windows NT user validation is performed by the client redirector and the Windows NT server (as part of the SMB protocol). This allows the user's initial network login to be used.

TCP/IP Sockets

--------------

When communicating over TCP/IP sockets, the SNA Server client opens a TCP/IP socket number created by the SNA Server. A socket is a session-oriented interprocess communication facility supported directly over the TCP/IP transport. The following illustrates the message flow:

  SNA Client         <- TCP/IP socket ->         SNA Server

  TCP/IP           <- TCP/IP connection ->       TCP/IP

  Network card  <---------------------------->   Network card

A typical message packet includes the following information:

   [ IP | TCP ( SNA application data ) ]

Advantages of Using TCP/IP Sockets

----------------------------------

- The SNA Server client and server communicate directly over the Windows sockets interface, bypassing NetBIOS, the SMB protocol, and overhead introduced using the named pipes interface.

- TCP/IP name-to-IP address resolution is provided by the client HOSTS file, DNS server, or WINS server

- TCP/IP session keep-alive timeout processing is handled directly by the SNA Server client and server. The SNA Server WatchDogTimeOut setting controls the timeout value, as described in the SNA Server 2.1 readme file (the default is 60 seconds).

- The SNA Server Win 3.x client uses a larger buffer size to exchange data with the server than does the SNA client named pipe interface. Also, data transfer is performed using byte stream protocol which makes better use of network resources (named pipes uses message mode protocol).

Disadvantages of Using TCP/IP Sockets

-------------------------------------

- User authentication is handled by the SNA Server client and server. This requires the user to "login" to the Windows NT network when the SNA client software is loaded. This client login can be automated to some degree, as described on page 208 of the SNA Server 2.1 Reference Guide.

KBCategory: kbnetwork kbinterop

KBSubcategory: ntnetserv ntprotocol

Additional reference words: prodsna 2.10 tcp/ip sockets named pipes


Q128986: Connecting over TCP/IP to SNA Server with multiple net cards

Connecting over TCP/IP to SNA Server with Multiple Net Cards  [winnt]

ID: Q128986    CREATED: 17-APR-1995   MODIFIED: 20-APR-1995

2.10

WINDOWS

PUBLIC | kbnetwork kbsetup kbbug2.10

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

-------------------------------------------------------------------------

SYMPTOMS

========

When connecting from an SNA Server client using the TCP/IP sockets interface to SNA Server, the following problems may occur if the Windows NT TCP/IP Protocol is bound to more than one network card on the server, and different IP addresses are configured for each card:

 - When opening a 3270 session, the session may never activate (the SNA 3270 applet may display "No SNA Server found in domain" on the status line).

 - When opening a 5250 session, an APPC error may occur (F004 - or AP_COMM_SUBSYSTEM_NOT_LOADED). This indicates that the SNA client could not locate a running SNA Server in the domain which supports the local and remote LU aliases being requested.

 - If multiple SNA Servers are configured the same way, the client may not be able to open a session through one or more of the servers, but not all.

NOTE: A network trace will indicate that the IP router is returning an "ICMP Destination Unreachable" message to the SNA client's connection request.

CAUSE

=====

When SNA Server is configured (using SNA Setup) to accept client sessions over TCP/IP sockets, SNA Server only searches for the first IP address that is configured on the server. The first IP address corresponds with the first adapter that the Windows NT TCP/IP Protocol is bound to.

When an SNA client opens its "sponsor connection" to an SNA Server in the domain, SNA Server sends down the server name and IP address it finds. However, the SNA client may not be able to connect to the server over this first IP address since the IP address may only be available over the other server's network card.

RESOLUTION

==========

There are two possible resolutions to the problem:

* Configure the TCP/IP Transport on the Windows NT Server using the Control Panel / Network utility and select "Enable IP Routing".  This will allow the client to locate either IP address supported by the server.

or,

* if you don't want to enable IP routing, you can control which IP address is used by the SNA Server clients by configuring the Windows NT TCP/IP  Protocol on SNA Server to bind to the desired adapter:

1. Open the Network icon in Control Panel

2. Choose the Bindings button

3. Select the TCP/IP Protocol and choose OK

4. Select the desired adapter and choose the "up" arrow button on the right side of the Network Bindings dialog. Move the adapter to make it the first in the list.

5. Choose OK.

NOTE: It doesn't matter which SNA Server in the domain is providing the sponsor connection" for the SNA client software (the sponsor server is indicated when installing the SNA client software within the "primary" and "backup" servers when the "remote domain" option is selected). The client sponsor connection will work against either of these servers.  However, this problem will prevent the client from opening a 3270 or APPC session through the servers.

KBCategory: kbnetwork kbsetup kbbug2.10

KBSubcategory: ntnetserv ntprotocol

Additional reference words: prodsna 2.10 tcp/ip sockets


Q129625: SNA Server Event 18 includes Sense Data = 00320008

SNA Server: Event 18 Includes Sense Data = 00320008           [winnt]

ID: Q129625    CREATED: 01-MAY-1995   MODIFIED: 02-MAY-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork kbinterop

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

------------------------------------------------------------------------

SYMPTOMS

========

If the host sends an UNBIND in response to an SNA Server BIND attempt to activate independent LU6.2 sessions, SNA Server logs the following event into the Windows NT application event log:

   Event:  18

   Description: APPC session activation failure: BIND negative response or UNBIND request received:

   Sense data = 0032xxxx

   Connection = <connection name>

   LU alias   = <local LU name>

   PLU alias  = <remote LU name>

   Mode name  = < SNASVCMG or LU6.2 mode name>

where 0032 means UNBIND, and xxxx is the unbind type. In this case, 0032xxxx is not SNA sense data.

NOTE: Chapter 5 of the "IBM SNA Formats Guide" lists all unbind types and their format. The most common sense code logged during session activation is:

   Sense data = 00320008

This indicates the route extension used by the LU-LU session has become inoperative, thus forcing the deactivation of the identified LU-LU session.

NOTE: The Sense data field includes an SNA sense code if the host responds with SNA sense data instead of an UNBIND. SNA sense data codes are listed in Chapter 9 of the "IBM SNA Formats Guide".

CAUSE

=====

This situation can occur when there is a configuration mismatch between SNA Server and the host system (for example, VTAM or CICS), or when the CICS region (matching the SNA Server Remote APPC LU name) is not running.

RESOLUTION

==========

To correct this problem, correct the configuration mismatch or ensure the CICS region (matching the SNA Server Remote APPC LU name) is running. The SNA Server 2.1 "Administrator's Guide" includes sample VTAM and CICS parameters for independent LU6.2 (pages 111-116). Follow this sample configuration to check for configuration mismatches between SNA Server and the host.

KBCategory: kbnetwork kbinterop

KBSubcategory: ntnetserv ntprotocol

Additional reference words: prodsna 2.10


Q129747: SNA Server connects to S/36 and S/38 with Coexistence PRPQ

SNA Server Connects to System/36 and /38 with "Coexistence PRPQ"[winnt]

ID: Q129747    CREATED: 03-MAY-1995   MODIFIED: 04-MAY-1995

2.00 2.10

WINDOWS

MSONLY | kbnetwork kb3rdparty

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

-------------------------------------------------------------------------

SUMMARY

=======

The IBM System/36 and System/38 do not natively support LU6.2 connections, and therefor, will not allow SNA Server to connect to them. However, there is a an IBM product, Coexistence PRPQ, available that allows these systems to support PC Support client access. Since SNA Server uses the same LU6.2 communication method as PC Support clients, this Coexistence PRPQ should also allow SNA Server to connect to System/36s and System/38s over an LU6.2 connection.

NOTE: This has not been tested by Microsoft.

KBCategory: kbnetwork kb3rdparty

KBSubcategory: ntprotocol ntinterop

Additional reference words: prodsna 2.00 2.10


Q129786: SNA Server and 802.2 connection timers (t1,t2,ti)

SNA Server and 802.2 Connection Timers (t1, t2, ti)           [winnt]

ID: Q129786    CREATED: 04-MAY-1995   MODIFIED: 08-MAY-1995

2.00 2.10

WINDOWS

PUBLIC | kbnetwork kbusage

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

------------------------------------------------------------------------

SUMMARY

=======

By default, the SNA Server Admin program sets the t1, t2 and ti timers on all 802.2 connections to a value of "Default". This article describes the actual timer values used by SNA Server when this default setting is configured, as well the various DLC timers and default settings.

Tuning the SNA Server 802.2 connection and/or DLC timers may be necessary if 802.2 connections are dropping due to timeout problems. A timeout may be occurring if SNA Server logs Event 23, Qualifier = AE or AF within the Windows NT application event log. However, a network monitor or sniffer trace would be necessary to confirm if a timeout problem is occurring (as opposed to an underlying network or bridge/router problem).

If an SNA Server 802.2 connection timer is changed, the change will take effect when the SNA Server service is stopped and restarted.

MORE INFORMATION

================

DLC Timer Parameters

--------------------

The following information describes various DLC timer parameters and how DLC timer values are calculated.

The DLC class II protocol uses three timers:

   t1 - Response timer

   t2 - Acknowledgment timer

   ti - Inactivity timer

The timer values are specified in timer ticks. Each timer requires a short timer tick (xxTickOne, where xx is t1, t2, or ti) and long timer tick (xxTickTwo, where xx is t1, t2 or ti). The length of these timer ticks are specified within the Windows NT DLC Transport driver (in the registry) in 40 millisecond increments.

The actual length of each timer (t1, t2, ti) is selected with parameters provided by the DLC application (SNA Server in this case) when the DLC_OPEN_SAP, DLC_OPEN_STATION, or DLC_MODIFY commands are issued. In these commands, the timer value is selected with a number between 1 and 10. If the number is between 1 and 5, the short timer tick (xxTickOne) is used. The timer value is equal to the selected number multiplied by the short timer tick value:

   timer value = selected number * xxTickOne * 40ms

If the selected number is between 6 and 10, the long timer tick (xxTickTwo) is used. In this case the timer value is equal to the selected number minus 5 multiplied by the long timer tick value.

   timer value = (selected number - 5) * xxTickTwo * 40ms

The response timer (t1) is used to detect a failure to receive an acknowledgment or a response from the remote link station.

The link station starts t1 when it transmits either an Information (I-frame) or Supervisory (S-frame, such as a RR/RNR/REJ) with the poll bit set. The t1 will be reset when the station receives a response frame with the final bit set. If t1 expires, the link station sends an S-frame with the poll bit set in order to query the status of the remote link station. The link station then restarts t1. If there is no recovery after the specified number of retries, the link station assumes that the link is inoperative and disconnects the link.

The duration of t1 must take into account any delays introduced by the source routing bridges or routers separating SNA Server and the remote system.

The link station uses the acknowledgment timer (t2) to delay the sending of an acknowledgment for a received I-frame. The t2 timer is started when a link station receives an I-frame. The t2 timer is reset when a link station sends an acknowledgment in an I-frame or in an S-frame. If the t2 expires, the link station must send an acknowledgment as soon as possible.

The value of t2 must be less than the value of t1 of the remote station. This ensures that the remote link station will receive the acknowledgment before its response timer expires.

The inactivity timer (ti) is used to detect an inoperative condition in the remote link station or in the transmission medium. If a station does not receive any S- or I-frames before its ti expires, it must query the status of the remote link station with an S-frame with the poll bit set. If it does not get a response after specified number of retries, it disconnects the link.

SNA Server and 802.2 Connection Timers

--------------------------------------

When an SNA Server 802.2 connection is activated, SNA Server sends a TEST frame to the remote network address configured for the connection.

On Token Ring, the local ring is tried first. If there is no response to the TEST frame, SNA Server resends the TEST frame with the "all routes broadcast" setting enabled which is then forwarded by source routing bridges. If there is source routing data present in the TEST frame response from the remote system, then long tick timers are used on the connection. Otherwise, short tick timers are used.

On Ethernet, since there is no source routing data, the short tick timers are always used.

Here are the short tick and long tick timers used by SNA Server:

   Parameter   Short Tick Timer   Long Tick Timer

   ---------        ----------------          ---------------

   t1                       2                  7

   t2                       2                  6

   ti                        5                  10

These multiplier values are used in conjunction with Windows NT Data Link Control transport settings to calculate the actual timer value used on the connection. The Windows NT DLC transport is configured with the following default timer values:

   t1TickOne = 5

   t1TickTwo = 25   (hex = 0x19)

   t2TickOne = 1

   tT2TickTwo = 10   (hex = 0xa)

   tiTickOne = 25   (hex = 0x19)

   tiTickTwo = 125  (hex = 0x7d)

   NOTE: These values are defined in the HKEY_LOCAL_MACHINE subtree of the registry in the  \SYSTEM

                      \CurrentControlSet

                        \Services

                          \DLC

                            \Parameters

                              \<network_adapter> directory.

   WARNING: Using the Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of the Registry Editor can be solved. Use this tool at your own risk.

These default settings yield the following timeout periods:

If SNA Server is connecting to the remote system over Ethernet or Token Ring where no source routing bridges are involved, then short tick timers are used, giving the following default timer settings:

  t1 timer = 2 * 5  * 40ms = 400ms  (.4 seconds)

  t2 timer = 2 * 1  * 40ms = 80ms   (.08 seconds)

  ti timer = 5 * 25 * 40ms = 5000ms (5 seconds)

If SNA Server is connecting to the remote system over Token Ring across source routing bridges, then long tick timers are used, giving the following default timer settings:

  t1 timer = (7-5)  *  25 * 40ms = 2000ms  (2 seconds)

  t2 timer = (6-5)  *  10 * 40ms = 400ms   (.4 seconds)

  ti timer = (10-5) * 125 * 40ms = 25000ms (25 seconds)

The SNA Server ti, t2 and ti timers can be manually set for each connection. The maximum value of each timer is 10, which yields the following timeout periods:

  t1 timer = (10-5) *  25 * 40ms = 5000ms  (5 seconds)

  t2 timer = (10-5) *  10 * 40ms = 2000ms  (2 seconds)

  ti timer = (10-5) * 125 * 40ms = 25000ms (25 seconds)

To increase these timers further, the DLC transport timer settings must be increased within the registry. However, caution should be taken before changing these settings.

KBCategory: kbnetwork kbusage

KBSubcategory: ntconfig ntprotocol nthowto

Additional reference words: prodsna 2.00 2.10


Q130290: DCA IRMA for Macintosh client doe not understand Master Domain

DCA Irma for Macintosh client does not understand Master Domai[winnt]

ID: Q130290    CREATED: 16-MAY-1995   MODIFIED: 16-MAY-1995

3.50

WINDOWS

PUBLIC |

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server versions 2.1 and 2.11

--------------------------------------------------------------------

SUMMARY

=======

DCA's Irma for the Macintosh is an add-on product which supports connectivity to SNA Server over Appletalk. However, Irma for the Macintosh only understands the single domain model when logging a client onto the SNA Server's domain.

MORE INFORMATION

================

When Irma for the Macintosh requests the domain of the SNA Server, it uses that domain name when passing the user name and password across for validation. This works fine when the SNA Server is a member server/Backup Domain Controller/Primary Domain Controller of a single domain model. However, if the SNA Server is a member server/BDC/PDC of a resource domain with no local domain user accounts, the validation fails for the Irma client.

RESOLUTION

==========

This problem can be resolved in 1 of 2 ways currently:

1) Enable the guest account on the resource domain (SNA SERVER) so the DCA Irma clients can be validated as guest.

2) Create user accounts in the resource domain for each Macintosh client who will be accessing the SNA Server.

The products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

KBCategory: kbnetwork kbsetup kbinterop kb3rdparty

KBSubcategory: ntprotocol

Additional reference words: 3.50 prodsna 2.10 DCA appletalk IRMA


Q130291: Mac 3270 err msg after installing Windows NT 3.5 Service Pack 2

Mac 3270 Err Msg After Installing Windows NT Service Pack 2   [winnt]

ID: Q130291    CREATED: 16-MAY-1995   MODIFIED: 17-MAY-1995

2.10

MACINTOSH

PUBLIC | kbnetwork kbbug3.50

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.1

 - Microsoft Windows NT 3.5 U.S. Service Pack 2

------------------------------------------------------------------------

SUMMARY

=======

When you install Microsoft Windows NT 3.5 U.S. Service Pack 2, Macintosh 3270 applications (such as DCA IRMA Workstation for the Macintosh) are not be able to establish a connection to an SNA server. The following error message appears:

   Getting configuration record: Unable to obtain configuration information from the server

CAUSE

=====

The Windows NT AppleTalk protocol does not work correctly after you install Microsoft Windows NT 3.5 U.S. Service Pack 2.

WORKAROUND

==========

To work around this problem, reinstall Services for Macintosh (SFM) from the original installation media.

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft Windows NT 3.5 U.S. Service Pack 2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug3.50

KBSubcategory: ntmac

Additional reference words: prodsna 2.10 3.50 mac clients


Q130386: RECEIVE_ALLOCATE may return AP_UNEXPECTED_DOS_ERROR (F011)

RECEIVE_ALLOCATE may return AP_UNEXPECTED_DOS_ERROR (F011)    [winnt]

ID: Q130386    CREATED: 18-MAY-1995   MODIFIED: 19-MAY-1995

2.00 2.10

WINDOWS

PUBLIC |

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft SNA Server for Windows NT, version 2.0 or 2.1

------------------------------------------------------------------------

SUMMARY

=======

If an APPC application doesn't properly issue TP_ENDED for each matching TP_STARTED or RECEIVE_ALLOCATE, the SNA Server client software will eventually run out of TP control blocks, causing the following error to be returned on a subsequent RECEIVE_ALLOCATE or TP_STARTED call:

  primary_rc = AP_UNEXPECTED_DOS_ERROR (0xF011)

MORE INFORMATION

================

When writing an invokable APPC transaction program (TP), which issues RECEIVE_ALLOCATE to accept a new conversation, each successful RECEIVE_ALLOCATE call returns with a unique transaction program id (tp_id) as well as a conversation id (conv_id).

The conversation is eventually terminated by the TP or the partner TP by issuing a DEALLOCATE call.  However, the program must still issue TP_ENDED to free up the tp_id as well, or a TP control block will remain in use on the SNA Server client.  This may eventually cause the SNA Server client to run out of these control blocks, causing the APPC interface to return AP_UNEXPECTED_DOS_ERROR in response to a RECEIVE_ALLOCATE call.

NOTE: If the AP_UNEXPECTED_DOS_ERROR is occurring as a result of some other failure scenario (i.e. not as the result of a RECEIVE_ALLOCATE), this indicates that the SNA Server software may have encountered an error from an underlying operating system call.  Internal SNA Server client traces and APPC API traces should be generated and passed to SNA Server support personnel to troubleshoot this type of problem.

KBCategory: kbnetwork kbprg

KBSubcategory: ntnetserv

Additional reference words: prodsna 2.00 2.10 f011