Kixtart scripting not working in NT/Novell environment.

Windows 98 Clients.
2 x Windows NT 4.0 SP5 servers. One PDC One BDC.
2 x Windows NT 4.0 Terminal servers. Both BDCs.
1 x Novell Netware v3.12 Server.

Client Primary Network Logon is the Novell Server.

I tested 1 userid, by doing the following:
Start1.Bat was created with the line "c:\kixtart\kix32".
Usermanager was modified so Logon Script=Start1.bat
The Kixtart files were copied to c:\Kixtart and to the
"\WINNT\system32\Repl\Import\Scripts" folder of the PDC and the BDC.
The script works when you execute Kix32 directly from explorer.

This setup did nothing. No indication of it even attempting to run the script.

I then ran KXRPC on both the PDC and BDC.
      No Change.
I then copied the Kixtart DLL files into the C:\Windows\System folder
      No Change.
I then copied Kix32.exe into the windows system folder and renamed it Lmscript.exe.
      No Change.

Can anyone advise what I'm doing wrong?????? This scripting on NT is frustrating...............kd
Who is Participating?
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.

Tim HolmanCommented:
Do the 98 clients pick up ANY logon scripts at all ?
> The script works when you execute Kix32 directly from explorer.
Does it work when you execute it from a command.xom on your W98 machine?
Kix is very picky about syntax, and does not report much errors.
If your primary logon is Netware, then your clients will run the Netware logon script, not the one located on your NT servers.

Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

kduquettAuthor Commented:
The clients run the "Novell" Login script fine.

Is it not possible to run the Novell login script then run the NT login script?

Not as far as I know.

Tim HolmanCommented:
..unless you put a CALL \\ntserver\netlogon\logonscr.bat in the Novell login script ?
Hi, kduquett

The followings are acctually in Kix Doc, I think this is what you need.

You can run Kix32.exe from a batch file that is used as the logon script for the user. For example, if Kix32.exe is in the root directory of the NETLOGON share, the batch file might contain the following commands:


If you installed Kix32.exe on the client's local hard disk, you must refer to the local directory, for example: C:\Kixtart\Kix32.exe.

Use of the syntax %0\..\ is discussed in Knowledge Base article Q121387.

Hope this help.


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
huben's got it.

Had same problem.  Used same solution.
kduquettAuthor Commented:
Thanks Huben. I'll try that, however I may have found another solution. Dump the Novell server, the Novell client has seemingly caused us many a head scratching issue.

Thanks again guys for all your help....kd
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 Networking

From novice to tech pro — start learning today.