The information in this article applies to:
SYMPTOMSWhen you use Microsoft Network Client for MS-DOS and Microsoft SNA Server 2.11 or 3.0 DOS Client, the 3270 terminal emulator may display communication status 505 and then stop responding (hang). CAUSEThe incorrect computer name is called up during network initialization. SNA DOS Client traces show the following:
where:
<SNA_Server> is the Server name in SNA Server Admin, <Incorrect_SNA_Client>
is the incorrectly specified computer name of SNA client, and <number> is
the service table entry number.
This situation occurs when both the MS-DOS-based and Windows-based clients are in the path. For example, your AUTOEXEC.BAT file contains the following: PATH C:\WINDOWS;C:\NET;C:\DOS;C:\;In this case, the Windows for Workgroups version of NET.EXE is called first. The Windows for Workgroups version of NET.EXE uses C:\WINDOWS\SYSTEM.INI, instead of C:\NET\SYSTEM.INI. This causes the error to occur. The SYSTEM.INI contains the following entry for the SNA Client's computer name: [Network] RESOLUTIONUse one of the following two methods to ensure the correct version of NET.EXE is used:
Additional query words: prodsna client dos applet computer name
Keywords : kbnetwork sna3270 snados |
Last Reviewed: September 29, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |