NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Can't enable SMB on RN102 running 6.8.1
I cannot enable SMB in the system settings on my RN102. I can access the shares with AFP (MacOS) and NFS (Debian Linux) clients, but not SMB (Windows 10). When I go to Settings -> Services, click on ...
Several folders are owned by guest, some by root:
root@Heinz-Home-NAS:/# ls -l total 80 drwxrwxr-x 1 guest guest 140 Oct 14 16:31 apps drwxr-xr-x 2 root root 4096 Oct 13 17:49 bin drwxr-xr-x 2 root root 4096 Jun 17 2012 boot -rwxrwxrwx 1 guest guest 0 Oct 31 2014 cp_check_md5sums.sh drwxrwxrwx 1 guest guest 254 Mar 31 2017 data drwxr-xr-x 14 root root 3360 Oct 13 17:50 dev drwxr-xr-x 88 root root 4096 Oct 17 05:52 etc drwxr-xr-x 7 root root 4096 Oct 13 17:50 frontview -rwxrwxrwx 1 guest guest 0 Aug 23 2015 ftp_ban.tbl drwxr-xr-x 1 guest guest 32 Jan 12 2015 home lrwxrwxrwx 1 guest guest 5 Dec 17 2013 homes -> /home drwxr-xr-x 15 root root 4096 Oct 13 17:49 lib drwxrwxrwx 2 guest guest 16384 Oct 30 2013 lost+found drwxr-xr-x 2 root root 4096 Nov 17 2012 media drwxr-xr-x 2 root root 4096 Apr 29 2016 mnt drwxr-xr-x 9 root root 4096 Jul 28 12:15 opt dr-xr-xr-x 177 root root 0 Dec 31 1969 proc drwx------ 3 root root 4096 Oct 13 17:49 root drwxrwxr-x 27 root admin 940 Oct 17 05:52 run drwxr-xr-x 2 root root 4096 Oct 13 17:49 sbin drwxrwxrwx 2 guest guest 4096 Jun 10 2012 selinux drwxr-xr-x 2 root root 4096 Nov 17 2012 srv dr-xr-xr-x 11 root root 0 Oct 13 17:50 sys drwxrwxrwt 7 root root 4096 Oct 17 05:52 tmp drwxr-xr-x 10 root root 4096 Jul 28 12:15 usr drwxr-xr-x 18 root root 4096 Oct 13 17:49 var root@Heinz-Home-NAS:/#
That's the issue then. Mine looks like this:
drwxr-xr-x 1 root root 1338 Sep 26 07:39 bin drwxr-xr-x 1 root root 0 May 21 2012 boot drwxr-xr-x 1 root root 412 Sep 21 08:53 data drwxr-xr-x 16 root root 3340 Sep 26 07:40 dev drwxr-xr-x 1 root root 2614 Sep 26 14:27 etc drwxr-xr-x 1 root root 58 Sep 26 07:39 frontview -rw-r--r-- 1 root root 0 Nov 9 2016 ftp_ban.tbl drwxr-xr-x 1 admin admin 10 Jan 26 2017 home lrwxrwxrwx 1 root root 5 Nov 22 2016 homes -> /home drwxr-xr-x 1 root root 462 Sep 26 07:39 lib drwxr-xr-x 1 root root 40 Sep 26 07:39 lib64 drwxr-xr-x 1 root root 32 Jun 4 2012 media drwxr-xr-x 1 root root 0 Jan 25 2016 mnt drwxr-xr-x 1 root root 98 Jul 28 13:14 opt dr-xr-xr-x 223 root root 0 Sep 26 07:39 proc drwx------ 1 root root 64 Sep 26 07:39 root drwxrwxr-x 25 root admin 800 Oct 9 06:22 run drwxr-xr-x 1 root root 2428 Sep 26 07:39 sbin drwxr-xr-x 1 root root 0 Jun 4 2012 srv dr-xr-xr-x 12 root root 0 Sep 26 07:39 sys drwxrwxrwt 1 root root 140 Oct 17 07:17 tmp drwxr-xr-x 1 root root 70 Jul 28 13:14 usr drwxr-xr-x 1 root root 146 Sep 26 07:39 var
This can get messy, since of course the ownership is likely wrong in the subfolders too.
Ok but I should be able to do a chown -r, which will run recursively, so not too ugly.
bheinz874 wrote:
Ok but I should be able to do a chown -r, which will run recursively, so not too ugly.
Some stuff is likely owned by admin, and not root. You also need to be careful on the mount points, since you don't want the shares to be owned by root.
Good point.
I think at this point it's just going to be easier for me to make sure I have a current copy of everything on this thing and do a factory reset on it.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
