Solved: - found a residual zfs filesystem I touught I had removed, but I found it with sharesmb="name=,guestok=true" ! - changed to sharesmb="off", still smbutil shows the empty share - forced destroy of the fs, still smbutil shows the empty share - had to disable/enable smb/server, empty share disappeared! Now windows connect and browse happily :) Da: Gabriele Bulfon A: [email protected] Data: 22 luglio 2015 16.11.57 CEST Oggetto: [discuss] empty residual smb share probably crashing windows on access Hi, I have an xstreamos system used for testing, that started crashing any windows trying to access smb shares (workgroup mode). It served smb shares fine since a point in time I couldn't figure out. I also tried removing any windows shares, but even trying just to access the machine via \\192.168.1.1 caused a reset of win explorer. Just left the problem unsolved for sometime. Now I decided I had to solve it, before it ever happened on any production machine. After some inspection I found this: sonicle@xstreamstorage:~$ smbutil view //localhost Share Type Comment ------------------------------- disk c$ disk Default Share IPC$ IPC Remote IPC vss$ disk VSS 4 shares listed from 4 available ??? 4 shares? there are actually 3!! Oh yes...one has a totally empty name...what's that?? I also tried with smbclient -L, receiving the same empty share... I strongly suspect this is the reason for the crash. I also suspect it happaned when I forced a "zfs destroy" of an smb shared filesystem. How can I get rid of that useless share? Any clue? Thanks! Gabriele illumos-discuss | Archives | Modify Your Subscription
------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
