First of all, you only need the kix32.exe file on Windows NT and Windows 2000 computers. You don't need the kx16.dll, etc. If someone is on dialup, then when hog up their bandwidth trying to send these files?

I have recently had my own problems using kix logon scripts over dialup with Windows 2000. I am using a similar setup as far as running kix locally and having the script on the server. Everything was slow before I copied over the kix32 to the %windows% folder. I found that the user having trouble did not have administrative rights, so the kix32.exe file had to be copied over manually. Once this was accomplished, things still ran a little slowly, but at least they ran. I did NOT have a problem needing a direct mapping for the script location. The way you have it set:

c:\scr\kix32.exe %0\..\script.kix is very similar to what I'm using, so it should run. I get my drive mapping just fine without a direct mapping to the script. That's why I think the problem is elsewhere.

Brian