We've been using Kix for years without problems, until now. Let me give you some more details:

Each of our site in Europe is starting the script with a batch looking like that:

%0\..\kix32.exe %0\..\script.kix

The only exception was in France (Ah, French!). They were still calling the script with the 'old' method:

NET USE Z: \\BDC\NETLOGON
KIX32 SCRIPT.SCR
C:
NET USE Z: /DELETE /YES >NUL

The disadvantage of this (mapping Z is that it will force KIX to use short names (SCRIPT~1.KIX) when done on Windows 95.
This morning I've changed that script to the %0\..\ trick, but KIX returns empty @UserID and InGroup()!!! Howerever, this works in other sites.

Who has seen that before? Thanks in advance for any hint.

"
Windows 9x clients must install both Kix32.exe and two dynamic-link libraries (DLLs) called KX16.DLL and KX32.DLL.
"

they have to be from the same package as the exe. i.e. the same version.

Maybe I should try to map IPC$ on the DC?

(Et voilà encore une après-midi de perdue!)

I'll do some more extended checks and post my results.

Failed to determine logonserver (0x35/53)

It seams that the problem occurs with only 2 BDCs out of 3, maybe those servers are the culprits...