Solved: It had to do with the Windows 10 and the FreeNAS server was not on the same subnet. Next day my Windows 10 got IP in the same subnet and could connect to the file share. Similar to this thread https://forums.freenas.org/index.php?threads/cannot-resolve-netbios-name-of-freenas-machine.36363/
Edit: I cannot find this is the Windows 10 WINS/BIND problem (now adays fixed) when computer assuming the Master Browse role on network when another machine already has that role. Disabling FreeNAS Local Master does not make any difference, and I don't get error 1231 when doing "net view /all" after "net stop browser") https://social.technet.microsoft.co...res-shared-folders-in-windows-10-after-update
Has anyone else had problem finding the FreeNAS server or connecting to CIFS on Windows 10?
I'm runningFreeNAS-9.3-STABLE-201602031011 FreeNAS-9.10-STABLE-201606270534. It is not frequently online since used mostly for backup.
nbtstat -n only lists my local Windows 10 desktop.
net view /domain only lists my WORKGROUP.
Connecting to CIFS server fails both with the IP-address and NetBIOS name. Acutally, when connecting to the IP-address first attempt displays a strange Select Certificate dialog (see attached image), but any next attempts fails with "Windows cannot access \\192.168.1.123\Backup".
I can successfully connect to CIFS server on OS X, but it uses the DNS smb://freenas.local/Backup, not the NetBIOS name.
Any hints what can be wrong? Or what to try next to get it working?
Thanks for any hints!
__________________________________
Edit: I cannot find this is the Windows 10 WINS/BIND problem (now adays fixed) when computer assuming the Master Browse role on network when another machine already has that role. Disabling FreeNAS Local Master does not make any difference, and I don't get error 1231 when doing "net view /all" after "net stop browser") https://social.technet.microsoft.co...res-shared-folders-in-windows-10-after-update
Has anyone else had problem finding the FreeNAS server or connecting to CIFS on Windows 10?
I'm running
nbtstat -n only lists my local Windows 10 desktop.
NetBIOS Local Name Table
Name Type Status
---------------------------------------------
GO <20> UNIQUE Registered
GO <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
WORKGROUP <1E> GROUP Registered
WORKGROUP <1D> UNIQUE Registered
__MSBROWSE__ <01> GROUP Registered
net view /domain only lists my WORKGROUP.
Connecting to CIFS server fails both with the IP-address and NetBIOS name. Acutally, when connecting to the IP-address first attempt displays a strange Select Certificate dialog (see attached image), but any next attempts fails with "Windows cannot access \\192.168.1.123\Backup".
I can successfully connect to CIFS server on OS X, but it uses the DNS smb://freenas.local/Backup, not the NetBIOS name.
Any hints what can be wrong? Or what to try next to get it working?
Thanks for any hints!
__________________________________
FreeNAS configuration:
Enabled "Local Master" in CIFS.
Windows configuration:
In "Network and Sharing Center" under "Change Advanced Settings":
Enabled "Turn on network discovery" for both "Private (current profile)" and "Guest or Public".
Services control panel
Set startup type Automatic for "Function Discovery Resource Publication"
Attachments
Last edited: