Try a start of the logon script with kix32.exe /f to flush the token cache... just to be on the safe side.
Maybe start the task manager during the logon script to verify it is not the kix32 process itself (In this case you might want to replace the local kix32.exe)
[edit] post the bat file and the logon script if possible[/edit]
Edited by Jochen (2006-05-24 04:03 PM)
_________________________
