Comment 4 for bug 222734

The reason the sharename is lowercased is so we can tell immediately if another usershare exists using a case-variant of the same name (SMB shares are case insensitive). In order to fix this (it's not an issue in the server code as far as I can see) the usershare creation code would have to scan the entire directory to look for case-differing versions of the new sharename, and replace them if needed.

Jeremy.