January 20, 20242 yr Hello, This is a new setup, started just over a day. I have created 2 shares and both of them are public. Also created a Share user. When i am trying to access those shares using my windows 11 pro (not domain joined) machine and android device, it fails. I tried the following combinations: \\<ip address> - Shows empty folder \\<ip address>\<share-name> - Shows error, unable to access It. I have followed couple different articles on how to resolve the Issue, but none of them are successful. Screenshot of : ls -hal /mnt/User/ Attaching the diagnostic file. == Edit == Removed the diagnostic file as the Issue is resolved. Edited January 20, 20242 yr by dharmil7 Removed diagnostic file
January 20, 20242 yr Solution Have changed the SMB Export option for the shares you want visible on the network? The default is No which means they are not visible on the network.
January 20, 20242 yr Author Damn it!! I have been on this for past 2 hours, with no luck. Thank you soo much And this solution was not mentioned In any post atleast in first 20 google search. I actually did not know what that meant, so i just left It as is. Can you explain the usecase of that option?
January 20, 20242 yr 27 minutes ago, dharmil7 said: so i just left It as is. Can you explain the usecase of that option? Security considerations mean that shares are not exposed unless needed. The different values control visibility and access permissions required to access the share. The GUI built-in help gives more details as does this section of the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release.
January 23, 20242 yr On 1/20/2024 at 3:04 AM, itimpi said: Security considerations mean that shares are not exposed unless needed. I think the default setting was 'Yes' until relatively recently. (I can't remember when this was changed but it could not have been too far in the past as there have been several cases of this problem recently and I don't recall this being the case in the distant past. I also seem to recall that I actually went into all of my shares on both of my servers and turned off access to NFS and SMB to any share that was not being accessed via those protocols!) I suspect that this new default applies only to 'new' shares. Any existing shares were not affected-- a 'Grandfather' situation. Edited January 23, 20242 yr by Frank1940
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.