Bug #3593


CIFS crash windows 8 client while editing security on a share

Added by x-cimo x over 9 years ago. Updated over 9 years ago.

Start date:
Due date:
% Done:


Estimated time:
Gerrit CR:


On both OI and OmniOS, when editing security on a CIFS share on Windows 8 as root, adding a new user local to the server crash the windows 8 client..

Related issues

Related to illumos gate - Bug #6021: Windows Explorer Stops Working / Crashes when Security Tab is accessedClosedGordon Ross2015-06-21

Actions #1

Updated by Rich Ercolani over 9 years ago

Can you please provide more details?

When you say "add a user on the server", do you mean with e.g. useradd, or changing the ACLs on the share, or ?

Can you reliably reproduce this every time?

What do you mean by "crashes the Windows 8 client"? Does the CIFS mount fail? Does the machine die with a kernel panic and reboot?

Actions #2

Updated by x-cimo x over 9 years ago

Hello Rich,

Sorry I should have been more specific, I've put more time to test this one.

So basically what happens is: On the ZFS server (let's call it ZFSSERVER) running native CIFS share, I have the following accounts:

root (default)
User1 (local solaris user)
User2 (local solaris user)
Group1 (contain User1 & User2, local solaris group)

The default permission on a CIFS share is root (full perm.), and everyone

On a Windows 8 machine, by authenticating as root, I can go and edit security permission on the share.

I can successfully add a ZFSSERVER\\User1 and ZFSSERVER\\User2 and give them some permission.

However I found out that it's adding the group that cause the crash,

In windows 8, going on properties on the share, then Security Tab, then edit, then add, then advanced, then Find Now,

It list all the Users group and default built in group there,
the important one is ZFSSERVER\\Group1

If I select that group and click OK, explorer.exe crash (explorer.exe is the process that display any window open, as well as taskbar) windows then restart it automatically.

In the event viewer I have this:

Faulting application name: Explorer.EXE, version: 6.2.9200.16433, time stamp: 0x50763312
Faulting module name: samcli.dll, version: 6.2.9200.16384, time stamp: 0x50108a11
Exception code: 0xc0000005
Fault offset: 0x000000000000bb5d
Faulting process id: 0xf0c
Faulting application start time: 0x01ce13cf72de31cd
Faulting application path: C:\\Windows\\Explorer.EXE
Faulting module path: C:\\Windows\\SYSTEM32\\samcli.dll
Report Id: 4901381c-7fc3-11e2-be87-002618fd4d42
Faulting package full name:
Faulting package-relative application ID:

Actions #3

Updated by Alek Pinchuk about 7 years ago

  • Related to Bug #6021: Windows Explorer Stops Working / Crashes when Security Tab is accessed added

Also available in: Atom PDF