|
Post a sample of the code you are using. It could be about anything....
I notice you said that the script is local and the kix32 is on the netlogon share... It would be more efficient over dialup if you could have your script transfer your kix32.exe (or wkix) locally and execute it from there. I am using a similar setup that runs the kix script from a batch file looking like this:
@echo off
if exist %windir%\kix32.exe %windir%\kix32.exe %0\..\kixtart.kix > nul
if not exist %windir%\kix32.exe %0\..\kix32.exe %0\..\kixtart.kix > nul
If the kix32.exe is found local then it runs locally. If not, it runs from the logon server. In my script I detect if the kix32.exe file is there, and if possible (user has admin access on machine), I create a subroutine to copy the necessary kix file(s) to the local machine. This may or may not help when using NT or W2K (i.e. local admin access not available), but if ever you make an install package that is deployed to everyone, you can sneak the kix32 files into your setup.
After saying all that, I realize this may be irrelevant to your question... One pertinent fact may be that the best way to get the script to run properly is to check the little box that says use dial-up networking on the initial W2K logon screen. Also, you may want to check the properties of their dial-up connections to see if they have the box checked that says "Include Windows logon domain".
Brian
| 
