I have spent the entire evening yesterday again testing and playing around with different settings with no success.
Windows 10 Pro 64x (different computers with different users) wired connection to ac86u.
Enabled/disabled SMB1/SMB2 in windows and in router settings as well as turning on/off the various other settings.
Reset user permissions, created the same user account I am using on windows and the network drive is being mapped without asking for credentials (as it uses the windows account).
I am still getting the same error. As soon as I try to create a New folder on the disk I receive the error message:
Error 0x8007010B: The directory name is invalid.
Even though, the folder is indeed created!
When using EXT4 partition no error message!
Anyone any ideas why NTFS behaves like that? Anything else I can do?
@RMerlin
As your NTFS drive is working, could you please let me know your setup?
OS version, SMB version, settings on the router, same user accounts between them?
Thanks
EDIT: Maybe I should have mentioned that googling the error and reading around, it seems that people with a Synology NAS had a similar problem and it was fixed when Synology released a firmware update.
EDIT2: I enabled log level =2 on smb.conf.
I cannot see anything failing apart from
Code:
[2018/01/31 13:01:08.306127, 2] ../lib/util/util_file.c:227(map_file)
Failed to load /usr/share/samba/codepages/upcase.dat - No such file or directory
[2018/01/31 13:01:08.306209, 2] ../lib/util/util_file.c:227(map_file)
Failed to load /usr/share/samba/codepages/lowcase.dat - No such file or directory
[2018/01/31 13:01:08.306252, 1] ../lib/util/charset/codepoints.c:60(load_case_tables_library)
Failed to load upcase.dat, will use lame ASCII-only case sensitivity rules
[2018/01/31 13:01:08.306286, 1] ../lib/util/charset/codepoints.c:64(load_case_tables_library)
Failed to load lowcase.dat, will use lame ASCII-only case sensitivity rules