Microsoft KB Archive/66976

= MS-DOS LAN Man Logon Scripts Do Not Load from Win 3.0 =

Article ID: 66976

Article Last Modified on 9/30/2003

-

APPLIES TO


 * Microsoft LAN Manager 2.0 Standard Edition
 * Microsoft LAN Manager 2.1 Standard Edition

-



This article was previously published under Q66976



SYMPTOMS
When you log onto Microsoft MS-DOS LAN Manager from within Microsoft Windows version 3.0 or 3.1 (for example, from the Windows Control Panel), LAN Manager logon scripts are not executed.



CAUSE
This is known behavior under Windows version 3.0 (or 3.1) and arises from the inability to synchronize separate COMMAND.COM sessions under Windows.

When MS-DOS LAN Manager logs a user onto the network, it performs three steps (at a high level) to execute the logon script:


 * 1) Add a USE for the NETLOGON share at the server processing the logon (for example, NET USE Z: \\xxxxx\NETLOGON).
 * 2) Execute the user's logon script (for example, Z:NETLOGON).
 * 3) Remove the USE for the NETLOGON share (for example, NET USE Z: /D).

Step 2 (Z:NETLOGON), requires that a new instance of COMMAND.COM be created (for example, by using a WinExec call), and this new instance does not run (and cannot be made to run) synchronously with the MS-DOS LAN Manager logon process. Windows, however, allows the DOS LAN Manager logon code to continue executing before control is passed to the new COMMAND.COM instance, so that step 3 (the removal of the USEd drive) is executed before the logon script is given a chance to run. When Windows does let the new COMMAND.COM process execute, the USEd drive (Z in the above example) is gone and the logon script does not execute.



RESOLUTION
If you need logon scripts, issue a NET LOGON command before starting Windows, or use an MS-DOS LAN Manager profile instead of a script. See the Microsoft MS-DOS LAN Manager &quot;User's Guide&quot; for more information.

Additional query words: 2.00 2.0 2.10 2.1 3.00 3.10 windows netlogon scripts

Keywords: KB66976

-

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

© Microsoft Corporation. All rights reserved.