Windows 10: Error: The object was not found. Server name: FREENAS

[Mark Holtz]

This issue has been perplexing me for quite a while, and over several releases of FreeNAS and Windoiws 10. I am currently my configuration as follows:

• Network is configured with a gateway address of 192.168.0.1, DHCP range of 192.168.0.2-192.168.0.149, and DNS of 1.1.1.1 and 1.0.0.1 (previously configured for 8.8.8.8 and 8.8.4.4)
• FreeNAS-11.1-U4 - SMB share is configured as vaultron, server has fixed IP address of 192.168.0.150 for NAS, 192.168.0.151 for Transmission, 192.168.0.152 for Plex
  
• Microsoft Windows [Version 10.0.17134.48] - SMB v1 is disabled as recommended.
• I have checked against two other computers,

Symptoms that I am facing: I am unable to see my FreeNAS server from Network in File Explorer.

Troubleshooting performed:

• QFrom File Explorer, I am able to access my Network share using \\vaultron and \\192.168.0.150
• From command line, I am able to ping vaultron (resolves to 192.168.0.150) and 192.168.0.150
• When I bring up File Explorer → Network, I am not able to see Vaultron. Because I had previously browsed to it, it is available on the left hand side.
  
• Checked Control Panel → System → Advanced System Settings → Computer Name, workgroup is configured as WORKGROUP
  
• Checked Services → SMB , everything appears to match up.
  
  
• Checked /usr/local/etc/smb4.conf, and I see the following:
  
  Code:

  [global]
  	encrypt passwords = yes
  	dns proxy = no
  	strict locking = no
  	oplocks = yes
  	deadtime = 15
  	max log size = 51200
  	max open files = 1879976
  	logging = file
  	load printers = no
  	printing = bsd
  	printcap name = /dev/null
  	disable spoolss = yes
  	getwd cache = yes
  	guest account = nobody
  	map to guest = Bad User
  	obey pam restrictions = yes
  	ntlm auth = no
  	directory name cache size = 0
  	kernel change notify = no
  	panic action = /usr/local/libexec/samba/samba-backtrace
  	nsupdate command = /usr/local/bin/samba-nsupdate -g
  	server string = FreeNAS Server
  	ea support = yes
  	store dos attributes = yes
  	lm announce = yes
  	hostname lookups = yes
  	time server = yes
  	acl allow execute always = true
  	dos filemode = yes
  	multicast dns register = yes
  	domain logons = no
  	local master = yes
  	idmap config *: backend = tdb
  	idmap config *: range = 90000001-100000000
  	server role = standalone
  	netbios name = VAULTRON
  	workgroup = WORKGROUP
  	security = user
  	create mask = 0666
  	directory mask = 0777
  	client ntlmv2 auth = yes
  	dos charset = CP437
  	unix charset = UTF-8
  	log level = 1
  

  
  Now, I'm seeing the netbios name, workgroup, and server string, but NOT the minimum/maximum SMB level.
  
• Checked Control Panel → Administrative Tools → Event Viewer → Applications and Services → Microsoft → Windows → SMBClient → Connectivity, and I see the following:
  

QUESTIONS:

• Where the heck is Windows 10 getting the name FREENAS? I'm searching for VAULTRON.
• Where did I mess up in my configuration?

 

[sretalla]

What about your FreeNAS system configuration (that defaults to name FREENAS)?

Also it might be interesting for you to read the last few posts in this thread (but ignore the argument going on there):
https://forums.freenas.org/index.ph...-in-network-browsing.54698/page-3#post-456212

In particular this recommendation:

# FreeNAS server wins in any election process to become master browser
os level = 255

# Force a browser election if FreeNAS is restarted
preferred master = yes

Also ensure that at least one of your shares has "Browsable to Network Clients" set.

 

[Mark Holtz]

I only have the one FreeNAS server, and it's name is VAULTRON.

I checked my SMB shares, all are set to browsable.

As for that recommendation.... I'll give that a try. I assume it is going in the general section.

 

[BigDave]

As for that recommendation.... I'll give that a try. I assume it is going in the general section.

Master Browser setting would be found under Services > SMB

My Windows 10 machine has this setting for Samba, and works fine with detecting
the share from my FreeNAS servers

Though my configuration differs greatly from yours...
FYI - my version = 10.0.16299 Build 16299

 

[JohnL7]

Concerning the name, while you have your SMB settings showing as vaultron that does not mean that the hostname for the freenas server is set to the same thing. You may want to check your settings under System > Information and look for the Hostname field to see if it is set as Freenas or not. That may be a quick fix but may break other connections that are pointing it as as its previous name.

 

[Mark Holtz]

Well, I added those two lines.... no change.

As for System → Information....

Master Browser setting would be found under Services > SMB

My Windows 10 machine has this setting for Samba, and works fine with detecting
the share from my FreeNAS servers
View attachment 24117
Though my configuration differs greatly from yours...
FYI - my version = 10.0.16299 Build 16299

Sight problem with that. You have SMB1 enabled as a client, which is a big, problematic security hole. I have mine disabled and have no intention of enabling it.


As for local master, that's enabled. Here are are the current SMB settings including the two added lines suggested.


Yet, does vaultron show up on Network? Nope.


Do I have access to shares? Yup.

 

[JohnL7]

Specifically concerning the "Yet, does vaultron show up on Network? Nope."

If your network settings are not set for discovery on both sides, you wont look for or be found. Windows 10 does this when you join a new network and it asks if you want to make your device discoverable. That is a LLDP function outside of any network function and is not required for network connectivity as noted by your screenshot with the network shares when you navigate directly to the device. Honestly, thats kinda a nit-picky and has nothing to do with functionality of the SMB shares. Additionally, it shows up with the correct name and is reachable by the correct name so that all looks fine so far.

Are you dealing with HIPPA/SOX/JOC or some other regulatory source for your personal data security? I didn't get the impression that your setting this up for or as a business so I am curious to your need for security by not using SMB1 which may be why your having these problems? Have you tried using SMB1 to see if it corrects the problem as a troubleshooting step?

 

[sretalla]

That last post from @JohnL7 reminded me of something that I think may be behind it all...

I have the same settings as you have shown (including NTLM v1 off) on a Windows 10 system that can see my FreeNAS, so have been scratching my head about it.

It now occurs to me that we haven't seen if you have set your network as a "Private" or a "Public" network... if it's public, that would clearly explain the difference between how we are seeing the results.

To check it, open your network neighborhood (right click on Network and select Properties...) and have a look:

To change it, go to Settings|Network & Internet, then on the status panel, click "Change connection Properties"

Then select the Private profile (assuming you are set to Public):

Maybe that's it???

 

[Mark Holtz]

It's a home connection, thus set to Private:


Lets check the profiles...


How about the Windows 10 Settings?

 

[Mark Holtz]

Specifically concerning the "Yet, does vaultron show up on Network? Nope."

If your network settings are not set for discovery on both sides, you won't look for or be found. Windows 10 does this when you join a new network and it asks if you want to make your device discoverable. That is a LLDP function outside of any network function and is not required for network connectivity as noted by your screenshot with the network shares when you navigate directly to the device. Honestly, thats kinda a nit-picky and has nothing to do with functionality of the SMB shares. Additionally, it shows up with the correct name and is reachable by the correct name so that all looks fine so far.

Are you dealing with HIPPA/SOX/JOC or some other regulatory source for your personal data security? I didn't get the impression that your setting this up for or as a business so I am curious to your need for security by not using SMB1 which may be why your having these problems? Have you tried using SMB1 to see if it corrects the problem as a troubleshooting step?

See this blog post in regards to SMB1 from Microsoft.

And, just to make sure I'm perfectly clear: I am perfectly able to access my shares across the network. Yes, it's a personal FreeNAS server on a home network that was built primarily to hold automated backups from multiple computers, and, oh yeah, with 27TiB of total storage (8x5TiB drives in a RAIDZ2 configuration that went operational at the end of July, 2016), I am also using it as a Plex media server as well as a file storage locker. I'm at 46% capacity, and have 13.4TiB of space left. And, before I build Vaultron, I had a test box with a single drive running FreeNAS 9-dot-something (the release before 11) where I learned some of the nuances and did some SMB sharing

The root issue is that Vaultron isn't visible from Network (formerly Network Neighborhood). One of those "nice-to-have features" that just.... bugs.... me. My other computers show up on my network, but not Vaultron. Why? When I stared at "Event Viewer" and saw "FREENAS", the two questions that came up were "What the?" and "Why?"

Waitasecond... checking Control Panel → Credential Manager...


So, when I built Valutron, I built everything but the hard drives. (I was waiting for a special on some NAS drives). So, in addition to doing memory testing, I ran a test configuration using an old 1TB drive and set up the server as FreeNAS to test functionality. I'm seeing the old credential. Digging deeper....



Yup. "freenas". Let me delete out that old credential and see if that eliminates the error message from the SMB event view log.

 

[Mark Holtz]

Nope, deleting out the old credential did not clear out the error condition. Checked registry, deleted old entries referencing \\FREENAS..... nope.

Sysmon time....