We're trying to use the 802.1x features of the 4.91 SP4 client, but login
scripts don't execute correctly.

This is the login resuls page:
------------------------
Your current tree is: fdu
You are attached to server ATHENA.
You are attached to server FDUSVR1.
LOGIN-LGNWNT32.DLL-923: An unexpected error has occurred: 9 (8801).
LOGIN-LGNWNT32.DLL-918: This utility was unable to get connection
information.
Error code: 8801.
Drives A,C,D,E,F map to a local disk.
----- Search Drives -----
S1: = C:WINDOWSsystem32
S2: = C:WINDOWS
S3: = C:WINDOWSSystem32Wbem
S4: = C:WINDOWSsystem32nls
S5: = C:WINDOWSsystem32nlsENGLISH
LOGIN-LGNWNT32.DLL-923: An unexpected error has occurred: 13 (8801).
LOGIN-LGNWNT32.DLL-923: An unexpected error has occurred: 15 (8801).
------------------------

Nothing from the container, profile, or personal script is executing,
which I think is reflected in the 3 error messages above.

If, after closing the login script window, I do a login over login (using
the red N) the scripts are read and execute correctly. This works
correctly with "Use 802.1x authentication during subsequent eDir-only
logins" enabled or disabled.

My test machine has only Windows XP SP2, IE7, all critical MS patches, and
Client 4.91 SP4.

Clients not using 802.1x have no problem with scripts, so I don't suspect
rights to read scripts are the problem. It appears to be related to the
initial 802.1x authentication, but we can't figure out what. I'd
appreciate any ideas on this.