WFWG login script hangs

Can anyone tell me why it is when a WFWG user logs into a NT domain, the login script sometimes appears to hang just after completion, so that the message box saying "Please wait while your login script executes" has to be dismissed by pressing the cancel button? (In every case so far, the script has executed correctly.) This is not a showstopper, but it's very irritating.

Sorry to ask this here if it's a WFWG problem, but there doesn't seem to be a WFWG section.
acarlisleAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

arminlCommented:
You most likely ran into an old (but still never fixed) bug in the wfw logon script processor: whenever any network error occurs (e.g. a drive could not successfully be NET USEd) NET.EXE will set the ERRORLEVEL variable > 0. WfW does not handle this situation properly and the scripts seems to "hang" upon termination.
The fix is to reset the Errorlevel on the last line of the logon script. Unfortunatly there is no DOS command to do it, but Microsoft has released a tiny tool called CLRLEVEL that fixes this. ClrLevel  is included in the Microsoft Systems Management Server (SMS) package.
Copy Clrlevel.exe into the directory where your login-scripts reside, and add
%0\..\clrlevel
 at the end of your login script. This (rather old, but still undocumented) batch file trick will tell the system to load ClrLevel from where the login script was loaded from, and you don't have to copy ClrLevel to all of your clients. Works great with any Batch processor I've seen so far, including W95 and NT 4, NT 4.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
acarlisleAuthor Commented:
There still seemes to be problem if a login script calls another batch file. Is this another undocumented feature of WfW?

0
arminlCommented:
Have lots of nested logon-scripts here. Never had any problems except the errorlevel problem fixed with clrlevel. Sorry.
0
acarlisleAuthor Commented:
Chez nous, it seems that if *any* program run by a login script under WfW returns non-zero, the script will hang at the end, and clrlevel.com makes no difference. Sigh. But thanks for your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.