CIF home share not accessible on Windows 10 if capitol letter in user name
AMD Turion(tm) II Neo N40L Dual-Core Processor
HP ProLiant N40, 16 GB RAM
On FreeNAS 9.10, build FreeNAS-9.10-STABLE-201606270534 (dd17351), if I create a user with capitols in the name, as in "Lauri", the home directory is not accessible from a Windows 10 machine. However, if I delete that user, and create a new user "lauri", I can access the home network share from Windows 10.
#8 Updated by Christopher Shaker over 4 years ago
I updated to FreeNAS-9.10.1 (d989edd), and created a new user named 'Testing'. I went to my Windows 10 machine, and created a new user named 'Testing', with the same password as on FreeNAS. Opened File Explorer, and clicked on Network. Clicked on my FREENAS machine. I've got shares named 'archive' and 'backup', which user Testing CAN access just fine.
When I attempt to open the folder named 'homes', or the folder named 'Testing', it fails with Error code 0x80070043 The network name cannot be found.
#11 Updated by William Grzybowski over 4 years ago
Shouldn't this go to someone with more experience in Samba?
I can certainly try to look at this but I am sure it will take a lot more time since I have no knowledge about this and still have to setup all the infrastructure to test this, including Windows.
#16 Updated by Jan Stevenson over 4 years ago
I am unable to reproduce this issue. I took a Windows 10 VM and mapped a network share to a test FreeNAS box here and authenticated with user "Lauri" and was able to read and write in the network share without issue.
Christopher: I see from your screenshots that you're accessing your smb share from the "Network" option in the left panel on the Windows 10 UI. What's happens if you simply Map a Network Share (accessible from "This PC" -> "Computer" -> and then "Map a Network Drive" from the ribbon) and authenticate with a user account with a capital letter?
Also, could you create debug file and attach it to this ticket please (FreeNAS UI -> System -> Advanced -> Save Debug).