Microsoft KB Archive/118381

= Making and Running APING/APINGD Samples =

Article ID: 118381

Article Last Modified on 3/8/2005

-

APPLIES TO


 * Microsoft SNA Server 2.0
 * Microsoft SNA Server 3.0
 * Microsoft SNA Server 3.0 Service Pack 4
 * Microsoft SNA Server 4.0

-



This article was previously published under Q118381



This article includes instructions for making and running APING/APINGD samples on SNA Server.

The following are the steps for making and running APING/APINGD samples on SNA Server.

Building APING/APINGD
Follow step A.1. (Building the TPs) in the SNA Server SDK README.TXT file. The ISVLIBS, ISVINCS and SAMPLEROOT environment paths must properly point to the SNA Server libraries, include files and sample programs. To build the APING samples, run:

NMAKE -F MAKEPING.MAK

Install the APINGD Service on SNA Server
You can use the TPSETUP applet (shipped with the SNA SDK), or the INSTSRV Windows NT service installer sample (shipped with the Win32 SDK). If you use INSTSRV, configure extra settings through REGEDT32 for the APINGD service.

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.

Sample Registry entries:  HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/APINGD DisplayName: REG_SZ: APINGD ErrorControl: REG_DWORD: 0x1 ImagePath: REG_EXPAND_SZ: C:\SNA\SDK\APINGD.EXE ObjectName: REG_SZ: LocalSystem Start: REG_DWORD: 0x3 Type: REG_DWORD: 0x10 Linkage: OtherDependencies: REG_MULTI_SZ: SnaBase Parameters: AlreadyVerified: REG_SZ: no     ConversationSecurity: REG_SZ: no      LocalLU: REG_SZ: LUPINGD SNAServiceType: REG_DWORD: 0x5 Security: Security: REG_BINARY: 

Configure Entries in the SNA Server Configuration File
In this configuration, APING is running on a client against APINGD which is installed on the server (that is, they're running locally to one server). Sample LU settings:

Local APPC LUs (configured off the server):  LU Alias: LUPING - Independent LU6.2 - Network name = APPN - LU Name = LUPING - Member of default outgoing local APPC pool - Timeout for starting TP: 60 seconds

LU Alias: LUPINGD - Independent LU6.2 - Network Name: APPN - LU Name = LUPINGD - Timeout for starting TP: 60 seconds - Partners: - Partner LU = LUPING, Mode = #INTER, Connection = [Local] CPI-C Symbolic Destination Name (configured via Options/CPIC dialog):  Name = APINGD - Partner TP name: Application TP = APINGD - Partner LU name: Alias = LUPINGD - Conversation security = None - Mode Name = #INTER Users/Groups window:

Add an SNA Server user account (or "Everyone" access) for the Windows NT client user that will be running the APING program.

Save the SNA Server configuration file.

Running the APING Sample Program
 Start the SNA Server service on the server, using SNA Admin, or by the command line ("net start snaserver"). Start the APINGD service on the server, using the Control Panel Services applet. On the Windows NT client machine, run APING:

APING APINGD



Enable the "APING" Local LU as a "Member of default outgoing local APPC pool"; this is the Local LU name that will be used. If this is not enabled, APING will display error 20 (product specific error).

Additional query words: prodsna 2.00

Keywords: KB118381

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.