How to find out if SMBv2 is enabled on your PC 5, make sure to clear the SMB 1.0/CIFS Client option. You can easily do this following the same steps mentioned above, but on Step No. If the manufacturer can't provide an update, you should consider getting a network device that includes support for the more secure version of the network protocol.Īfter you've either migrated your data off the network or you updated the software that supports the more secure version of the protocol, we recommend disabling SMBv1 on your computer. Ideally, if you're saving your data on a drive connected to a router with file sharing capabilities or NAS, you should contact the device manufacturer for specific instructions to update the device to a version that supports SMBv2.02 or later. Of course, you should only use these steps as a temporary solution to regain access to your files stored on the network. Maybe something like this should be mentioned on the DietPi’s Samba Info page, wondering why not more people had problems with this… Maybe its because of the 1903 windows update, which is relatively new.After completing these steps, you'll once again be able to see and connect to network devices running the old protocol on your local network from your Windows 10 computer. I didn’t have this problem with Samba shares with Open Media Vault and my TPLink Routers Samba service.ĭon’t know, what kind of Dietpi samba version or extra commands this is causing not to work with a new Windows installation with default configs. Searched way to long to fix this, because I thought the fault was on DietPi’s side. “By enabling insecure guest logons, this setting reduces the security of Windows clients.” It still can’t be found by windows network search (even after reboot), you have to manually enter \dietpi"yoursharedfolder".Ĭan be found by searching with Android Solid Explorer though !?ĭon’t know if this is a good solution, Microsoft says to this: Had the same fault, I’m on Windows, this one fixed it for me:Ĭomputer configuration\administrative templates\network\Lanman Workstationīy enabling this, the Samba dietpishare can be found and connected with “dietpi” user & password. So as I said in the beginning: the good news is that I don’t have the problem anymore, the bad news is that I have no clue what caused it Until I did one thing: Reboot the pc.Īfter rebooting, my home pc is finally able to mount Dietpi’s volume. My home PC’s network was already tagged as “Private”, and in facts it insisted on being able to flawlessly mount my OMV Samba shares, but not my Diepis’. Good, so when I came back home I readily went and checked wether also my home pc had the same “issue”. Switching to “Private” category solved the problem instantly. Unlike what happened from within the internal LAN (see previous post) when I tried to configure a new remote mount the system did not even show me existing SMB shares, but rather let me wait indefinitely.įiddling around, I found out that my business laptop’s main windows LAN profile was under the “Public” category. Once the VPN is established I can regularly access my home network, with the exception of SMB shares. I think I found a solution, although I am unable to detail exactly where the problem lied.įrom my company I am connecting back home via a VPN configured on my home router. Which is indeed the user+pwd which is being used to successfully access from Android.Īnyone has ideas on what may be going on ? Choose this, put username and password in, BAM, it works.įrom the Windows 10 client / m圜omputer → Add network connection → \10.10.0.233 → quite a long time “looking around” on the network → SAMBA shares are finally shown → give user/pwd → not authorisedįor completeness, of course I am pretty sure that the user is the one specified inside the smb.conf file, and its pwd is indeed the one set with smbpasswd -a. Why?Īfter a few seconds, server 10.10.0.233 is finally discovered, which is the Dietpi machine. Instantly, it lists a 10.10.0.0 server instance, which indeed does not exist on the network. While adding a new LAN/SMB connection, the first thing the Android/SolidExplorer app does it to survey the LAN for active servers. Android + SolidExplorer can connect no problem. When trying to connect to server 2 (Dietpi) I connect to such machines from 2 possible clientsī) Android, by way of the SolidExplorer appīoth clients behave perfectly when connecting to server 1 (OMV) On this machine PiHole is also configured, and it does its job OK on the LAN. A fresh Dietpi install on a Raspberry Pi 3 B.On my LAN I have 2 machines sharing some folders via SAMBA protocols.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |