Microsoft KB Archive/180574

= Client Fails if WNAP Started Using /User: and /Pwd: Options =

Article ID: 180574

Article Last Modified on 7/15/2004

-

APPLIES TO


 * Microsoft SNA Server 3.0 Service Pack 2
 * Microsoft SNA Server 4.0

-



This article was previously published under Q180574



SYMPTOMS
A Windows 3.x SNA Server client fails to get an application session if you start Wnap.exe with /User: /Pwd: specified on the command line. When this occurs while you are using the 3270 Applet included with SNA Server, the following message is displayed on the 3270 Applet status bar:

No SNA Server Found in Domain.



CAUSE
The Windows 3.x client is not storing the password specified in the /Pwd: command line parameter for use after WNAP initializes. Because the password is not available when the application session starts, the user account cannot be validated by SNA Server. This prevents the application session from opening.



WORKAROUND
To work around this problem:
 * Start Wnap.exe without using the /User and /Pwd: options.



STATUS
Microsoft has confirmed this to be a problem in SNA Server versions 3.0 Service Pack 1 (SP1) and 3.0 SP2.

This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K



MORE INFORMATION
Please refer to the following Microsoft Knowledge Base article for another known issue when using the /User: and /Pwd: parameters with Wnap.exe:

171255 WNAP /User: and /Pwd: Parameters Fail In SNA Server 3.0

Keywords: kbbug kbfix kbnetwork KB180574

-

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

© Microsoft Corporation. All rights reserved.