The PC command net view \\NUC shows all of the default Home Assistant shared folders on my Intel NUC computer.
C:\Users\steve>net view \\nuc
Shared resources at \\nuc
Samba Home Assistant
Share name Type Used as Comment
-------------------------------------------------------------------------------
addons Disk
backup Disk
config Disk
media Disk
share Disk
ssl Disk
The command completed successfully.
But, only the config share will map to a drive letter in the PC using net use. (The config folder is the only default folder that is also shared in my smb.conf file.) All of the other Home Assistant default directories return an error: The network name cannot be found.
The command smbtree shows all of the folders on my host shared in smb.conf.
They all map to a drive letter on the PC using net use.
steve@NUC:/$ smbtree
MSHOME
\\NUC NUC server (Samba, Ubuntu)
\\NUC\Artisan-1430 EPSON Artisan 1430
\\NUC\IPC$ IPC Service (NUC server (Samba, Ubuntu))
\\NUC\mntD SATA drive on NUC
\\NUC\snapshots Home Assistant Snapshots folder
\\NUC\steve Shared folder on Steve
\\NUC\config Home Assistant config folder
\\NUC\nuc Nuc/ folder
\\NUC\print$ Printer Drivers
So, here’s my confusion. Why does the PC command net view show all of the Home Assistant default directories, but I can’t see them in File Explorer?
Thanks for the feedback.
The PC command net view shows all of the Home Assistant default directories, so they are exposed to SMB. But why can’t I see them in File Explorer, or net use?
Samba on the PC is running fine as I can see and map other folders on my
Intel NUC computer that are in my smb.conf file.
Do I need to add the Home Assistant Default Directories to my smb.conf file as well?
The SMB shares work, but I think what you might be dealing with is an old windows problem when when you connect to one share on an SMB system that other shares pop this message. It’s been a while since I had to deal with it myself, but I know it used to be a problem and you had to disconnect all the SMB shares and then reboot and try again and there might be a registry change too.
I’ve definitely had this problem with Windows to SMB before, and I have read a forum post elsewhere in the recent past regarding this still happening in Windows 10.
This makes sense. It didn’t occur to me (but it should have) that it is a Windows problem.
The issue seems to be random. (I hate the way that Windows does networking. For example I can’t net use to the same server, different folders, with the same hostname).
After installing your samba share, windows side show system error 67 has occurred, the network name cannot be found. If I use the old samba share, the network is ok. Please help.
So, it sounds like you’re trying to to gain access to the other folders and not just the config folder in your FIle Explorer:
Go to your File Explorer
RIght Click on ‘Network’
Click on ‘Map Network Drive…’
Click on ‘Connect to a Web site that you can use…’ listed in blue for me as the bottom line of the dialogue box
Click Next
Click Next (in regard to ‘Choose a custom network location’)
Type in the name of your Home Assistant IP using the following:
\192.168.x.x\share
Click Next
Done!
I realize that this is an old question for you, but in case you haven’t been able to do this, or for anyone else who may desire an answer to this question.