CIFS and Windows 10 Access Error

[mstang1988]

• Running Windows 10 Build 10240 Factory Install (just booted)
• Running FREENAS FreeNAS-9.3-STABLE-201509282017
• Multiple CIFS shares, NETBIOS name "FREENAS"
• CIFS setup max version SMB 2.0
• Freenas setup as master browser
• *Shares are of Windows/NFSv4 ACL type

I create a brand new dataset called "test" and provide user1/user1 access to file. In windows 7 I can browse the computers on the network and access this dataset. Windows 10 I get access denied when browsing via the netbios name but success when going to the IP.

I've tried the following:

• Enabled netbios for IPv4 in the adapter
• modified the registry for guest access
• Modified the local user policies for networking to allow guest

I'm an shock as to why the IP would work but not the browsable netbios name.

 

[Ericloewe]

Sounds very weird. Using the NetBIOS name works fine here.

 

[mstang1988]

Deleting this comment. I was wrong.

 

[mstang1988]

Well, I have two freenas instances configured. In the CIFS config I have identical settings. Shares are windows type shares. One works, the other doesn't. Huh.

 

[anodos]

Well, I have two freenas instances configured. In the CIFS config I have identical settings. Shares are windows type shares. One works, the other doesn't. Huh.

Check /var/log/samba4/log.nmbd. What's the deal with the registry hacks? Those shouldn't be needed for guest access.

 

[mstang1988]

Did some more testing on this and it seems related to freenas acting as the primary browser. I've opened a bug with reproducible steps.
https://bugs.freenas.org/issues/12069