C
Carl Hilton
OK, I have a user that tries to connect to a server with a share in explorer
and she receives an access denied message and another message about "unable
to impersonate using a named pipe until data has been read from that pipe".
Also the same "named pipe" error if she uses NET USE Z: \\SERVER\Share.
Now, as an administrator I have NO problem doing both from her machine. I
have seen numerous messages about this possibly being caused by a full
security log and the CRASHONAUDITFAIL, but this is not applicable as her
security log is 64K of 512K but I did try removing the CRASHONAUDITFAIL.
To isolate this from the workstation, I created a new non-administrator
user, and tried accessing the same share from a different workstation,
attached to a different router/hub and received the same errors..
I have also read the issues about IRPStackSize.. This entry does NOT exist
on the server.. This is a Win2003, with the latest updates. I have verifed
that local policy allows EVERYONE to connect through the network. These
users have NO problem connecting to other servers... This is only affecting
this one particluar server... Actually, it is the only Win2003 server they
are trying to connect to.. The others are Win2K..
HELP!!!!
Thanks
Carl
and she receives an access denied message and another message about "unable
to impersonate using a named pipe until data has been read from that pipe".
Also the same "named pipe" error if she uses NET USE Z: \\SERVER\Share.
Now, as an administrator I have NO problem doing both from her machine. I
have seen numerous messages about this possibly being caused by a full
security log and the CRASHONAUDITFAIL, but this is not applicable as her
security log is 64K of 512K but I did try removing the CRASHONAUDITFAIL.
To isolate this from the workstation, I created a new non-administrator
user, and tried accessing the same share from a different workstation,
attached to a different router/hub and received the same errors..
I have also read the issues about IRPStackSize.. This entry does NOT exist
on the server.. This is a Win2003, with the latest updates. I have verifed
that local policy allows EVERYONE to connect through the network. These
users have NO problem connecting to other servers... This is only affecting
this one particluar server... Actually, it is the only Win2003 server they
are trying to connect to.. The others are Win2K..
HELP!!!!
Thanks
Carl