Problems with CHECKRAS.EXE

[APotter]

We use checkras in our logon scripts (we have 60+ mobile users and 150+ static, NT4.0 SP4 or 5)<br>Most of the time, it works fine.<br><br>Sometimes, checkras hangs, occasionally for 10 or 15 minutes but mostly forever( until shutdown). Occasionally, the machine is unable to shutdown and we need to go for the power switch.<br><br>I have not found any reliable solution to this problem - sometimes re-application of the service pack fixes it, other times deleting the user's profile does the trick (nasty one, this!)<br><br>Has anyone any experience with this problem, or a better solution for detecting RAS logins?<br><br>Regards<br><br>Alex

 

[danoh]

Use Kixtart version 3.61+.&nbsp;&nbsp;It has a macro called @RAS.&nbsp;&nbsp;At the top of your logon script use the following:<br>IF @RAS &gt; &quot;0&quot; GOTO END<br>&nbsp;&nbsp;&nbsp;ELSE<br>&nbsp;&nbsp;&nbsp;GOTO Beginning of script<br>ENDIF<br>:BEGINNING of SCRIPT<br>; your usual script<br>:END<br>; RAS user, so exit the script<br><br>You should post this question on Brainbuzz under the scripts forum.&nbsp;&nbsp;Here's the link for Kixtart<br><A HREF="

http://networking.brainbuzz.com/boards/viewboardmessages.asp,b~S2B92"

TARGET="_new">

http://networking.brainbuzz.com/boards/viewboardmessages.asp,b~S2B92</A><br><br>Alternatively,

if you wish to stay with NT shell scripting, you could use the CHOICE command and ask them if they are dialing in.<br>CHOICE /c:YN Are you dialing in?<br>IF ERRORLEVEL 1 GOTO rasuser<br>IF ERRORLEVEL 2 GOTO begin<br>:rasuser<br>; dial up user abort script<br>:begin<br>;normal script here<br><br>I wouldn't recommend this way because they will most likely always say Yes to avoid running the script, but it works.<br>Hope it helped