Upgrade 10.1.0.2.1761 to 10.2.0.2.1803 breaks CIFS/SMB

[jackstraw]

I have tried upgrading from 10.1 to 10.2 a couple of times [different 10.2 builds] and in each case my working CIFS/SMB shares break. This is connecting from Win 10 x64 release, using only local SAM credentials [not pin or microsoft live account]. The error is: The password is invalid, followed by System error 5 has occurred then Access is denied. This is connecting to a local user account on NAS4Free and I reconfirmed the password as correct - if I downgrade to 10.1 the connection starts working again.

In Services | CIFS/SMB | Settings | Auxiliare parameters I have the following: client signing = mandatory, restrict anonymous = 1 [for improved security]. These work fine in 10.1. From the Win 10 topic in this thread I tried adding 'smb port = 445' but that did not seem to make any difference. I suspect something has changed in the Samba configuration for 10.2. Have others seen Samba issues like this between 10.1 and 10.2? Thanks

[jackstraw]

The problem appears to be a username consisting of all digits e.g. 123456. In 10.1 it works fine, in 10.2 it fails, because no user entry is created in /etc/master.passwd. A username consisting of alpha characters e.g. jackstraw works fine and shows up in /etc/master.passwd. I suspect this is a bug with the web interface and/or backend used for user account creation.

[daoyama]

This is not NAS4Free change. It's FreeBSD's change since 10.2.
Yes, you cannot use numeric string in 10.2 series and later version like 10.3, 11.0 etc.