I wrote a logon script for a network I maintain using kixtart - it's great. i love it. lets me do all sorts of things that make Windows network management more barable.. I seem to have encountered a bug or something with two of our client PCs. The network is a horrible mix of 95/98/NT/2k/XP and the logon script works great for everyone aside from 2 people on Windows 98. Both PCs are patched to the latest as per Windows Update, and they get an error 67 (can't resolve host? hmm?) when trying to map @HOMESHR to the H drive. I set both of them on batch scripts that do net use cmds specifically for them, and that works fine. that's what leads me to believe it could be a kixtart bug, or a bug in windows.

anyone have experience with this? i'm using Kix 4.21 with the RPC services on both of my domain controllers. it's a 250 PC network, no WAN or layer 2 segmenting or anything.. here's the code snippet:
code:
 if (@HOMESHR)
	USE H: /delete
	USE H: @HOMESHR
	if ((@error <> 0) and (@error <> 85) and (@error <> 1202))
		$return = messagebox("Error connecting to the H: drive. Error code: @error", 4103);
        else ? " ÃÄ H: (" @HOMESHR ")"
	endif
else ? " ÃÄ H: (no home share set)"
endif