The information in this article applies to:
SYMPTOMSWhen you attempt to start a 3270 or 5250 session from a Windows NT RAS client (or from a Windows NT computer which was rebooted without being initially connected to a network), the emulator does not start and the following error occurs: Also, once SnaBase is started, the Windows NT user must still be authorized to open a network session to the Windows NT server where SNA Server is running, or the SNA session cannot connect. If this occurs, the 3270 applet displays "No SNA Server found in domain", while the 5250 applet displays error F004 (Comm_Subsystem_Not_Loaded). CAUSE
When Windows NT starts up, the SnaBase service is configured to autostart.
However, if SnaBase cannot initially connect to an SNA Server, SnaBase
stops before the user can establish the RAS connection.
RESOLUTIONAn SNA Server 2.11 update is available to correct this problem. Microsoft has updated the following Windows NT client files to correct this problem: <snaroot>\SYSTEM\SNABASE.EXEWith this update applied, SnaBase does not terminate if you add the following registry Value under the HKEY_LOCAL_MACHINE subtree under the following subkey:
If this entry is not present, or is set to 1, then SnaBase terminates if it
cannot open the sponsor connection.
NOTE: This update is included in SNA Server versions 2.11 SP1 and later. Without applying this update, it is possible to work around this problem by assigning the following rights to local users so that they have authority to start SnaBase:
If the user passwords are not synchronized, and if the SNA client is connecting to the server over named pipes, the user can still gain access to the SNA Server by preestablishing a network session to the server before starting their SNA application. To do this, the user can issue the following command: net use \\<server_name>\ipc$ /user:<domain>\<user_name> *where <server_name> is the SNA Server, <domain> is the Windows NT domain, <user_name> is the Windows NT user name, and * causes the prompt for the user's Windows NT password. STATUSMicrosoft has confirmed this to be a problem in SNA Server for Windows NT. This problem was corrected in the latest SNA Server for Windows NT, 2.11 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): S E R V P A C K Additional query words: prodsna
Keywords : kbnetwork ntnetserv kbbug2.00 kbbug2.10 kbbug2.11 sna211 sna2 sna21 |
Last Reviewed: September 21, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |