Sorry, At first I wanted to know that it is possible to browse the files. I'm running on a Raspberry PI 4. I've got a SSD hooked up to it via USB. I'm on GBit hard wired network. Both computer and Raspberry PI are plugged directly into switch ports on the back of the switch. Anything else?
Thanks!
It is very much possible. You are running the channels rpi4 image or raspian, or something else?
This is for Raspian:
https://www.pcmag.com/how-to/how-to-turn-a-raspberry-pi-into-a-nas-for-whole-home-file-sharing#:~:text=Head%20to%20your%20Windows%20PC,and%20see%20your%20shared%20drive.
If you're running the Channels image, the process may not be the same. In that case, a dev @tmm1 or someone with more linux / pi experience will probably have to help finish this up.
Windows also needs to be configured properly too but if you chose for it to be 'visible' to the network it shouldn't.
What OS on your RPi4, Channels image, Raspian, Ubuntu, something else?
I down loading the image from the channels site so I believe it's the rpi4 image. In the setting page it says to browse via: //dvr-server/media/dvr but that doesn't work. It also gives USB link. Neither are working. Obviously the raspberry pi must make the drive visible to the network. I assume I don't have to do anything to make that work?
If you are using the Channels Pi Image, all you have to do is enable the setting for Samba in the server web ui, and then go to that location on your network given that address listed. u literally can copy and paste that into an Explorer window.
If it does not work, then it is an issue with your Windows computer...which could be many.
Network device discovery and device sharing needs to be on and the network your connected to set as Private (not public).
it also could be blocked by any firewall/anti-virus software.
Trying the ping command from your windows machine to “DVR-server” and see if it successfully returns an ip and pings it. When using a name instead of ip you’re relying on name resolution so a good first step is to make sure that is working.
When I do //192.168.1.3/media/dvr I get a 404 Not Found Error. I'm using the image I got from Channels. I have a SSD connected to my RaspberryPI and everything has been working great. I love Channels! It's very well done. In the settings Samba is checked. On my Win10 I turned off all firewalls, network discovery and file and print sharing is turned on. Both the PI and my Win10 are hardwired to the same switch.
\\DVR-SERVER\MEDIA\DVR\ from the settings page doesn't work, neither does \\192.168.1.3\MEDIA\DVR. It's starting to drive my crazy!! Is it because the drive is connected to the PI and not my computer? That wouldn't make sense to me but I'm running out of ideas. I can ping 192.168.1.3 just fine.
When I browse the network I see DVR-SERVER but if I click on it I get a Windows cannot access error. I've turned on NetBIOS and even turned on SMBv1. Nothing is working! Maybe the PI is the problem. Anything I can do to test that?
404 not found would appear if you're typing those urls into a browser.
You should put them into the start menu, or into the windows file explorer.
But if you're getting cannot access error via the network browser, it suggests something else is going on. Maybe the samba setup on the Pi is not compatible with your Windows for some reason. Can you screenshot that error you're seeing?
No, when you enter the address with forward slashes it pops open a browser to display the 404. I use file explorer with back slashes. Are you using Samba v1 or v2? From a file explorer I get:
So, looking on the server side. I can ping my computer. If I type smbstatus or "smbstatus -- shares" both come back with empty list.
I see that the recordings go to /media/DVR not /MEDIA/DVR.
I also don't see
wins support = yes
in the smb.conf. Not sure if it's needed but I usually have it.
Those commands are empty for me too, so I guess that part is normal.
Does systemctl status smb show it running?
Can you click Support > Troubleshooting > Submit Diagnostics from the DVR web UI and I'll see if there are any errors in your logs.
This error code is “access denied”, which implies a port blockage or authentication problem. With modern Windows you can easily test the port availability. Launch powershell and type “test-netconnection 192.168.1.3 -port 445” and see if the port test succeeds.
I submitted the logs. The Samba service is running. All looks fine there. test-net-connection also looks fine? I'm really stumped. How about the smb.config not containing "wins support = yes"? It's write protected or I'd change it.
This proves that it is listening on the SMB port, so a firewall blockage is not the issue.
Should smbstatus or "smbstatus -- shares" come back with the share listed? It isn't.
Thanks
Marshall
I had same issue.. I found an article http://woshub.com/cannot-access-smb-network-shares-windows-10-1709/#:~:text=To%20enable%20access%20under%20the,policy%20Enable%20insecure%20guest%20logons.
I used the registry editor setting AllowInsecureGuestAuth to a value of numeric 1....
reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v AllowInsecureGuestAuth /t reg_dword /d 00000001 /f
It works fine now.
Donna,
Funny I had seen this before too but never tried it. Your reply made me try and guess what..... IT WORKED!!!
Thank you so much much for your reply, I can now browse the drive. THANK YOU, THANK YOU, THANK YOU!
Funny, my laptop as always been able to browse doesn't have the entry. So, either not having the "AllowInsecureGuestAuth" is the same as having it set to 1 or there is another way it works....
FYI I just had this same issue. However I tried using...
\DVR-SERVER.local\MEDIA\DVR\
instead and that worked. That .local thing seems to be relatively new and something that's required for me to access the webui as well. I'm using a Pi 4 server so maybe it's part of an update to that, I'm not sure. The webui should probably be updated to show this in the "Access your recordings via..." part.
Also I don't see the smba share listed in the Network section of my Windows Explorer. I have an older NAS that uses v1 shares so I already have the old shares option enabled. My only guess as to why is the work group might be wrong? I don't see an option anywhere in the webui to see, or edit, that so I'm not sure.
I don't use the Pi but after seeing so many people having issues with SMB/Samba I was thinking the same thing. I never use the default workgroup name on my NAS's or any Windows machine I setup, so forget what the default name is.
How is it configured on the Channels DVR Pi image?
