NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Readynas 104 SMB won't activate
Been using it for almost 2 years and no problem.
All of suddent I can't enalbe SMB. Did a OS reinstallation, and upgrade to 6.9.4-T8, non of them helped.
I did some research and the only way is to factory reset, but with almost 3TB data stored on my 4 hard drives, I really hate to do that.
Please help me as this is a really common problem and I have no idea why can't I just fix it with simple reset on the settings.
Please let me know if you need any log files
I tried so:
apt-get remove samba samba-common smbclient swat samba-doc smbfs libpam-smbpass libsmbclient libsmbclient-dev winbind
This removes all samba-related packages.
Then:
apt-get install samba
Then reboot and:
systemctl status -a smb
give:
root@NAS:~# systemctl status -a smb ● smb.service - Samba SMB Daemon Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: enab led) Active: active (running) since Sat 2018-05-19 16:30:45 MSK; 19min ago Main PID: 2219 (smbd) Status: "smbd: ready to serve connections..." CGroup: /system.slice/smb.service ├─2219 /usr/sbin/smbd --foreground --no-process-group ├─2325 /usr/sbin/smbd --foreground --no-process-group ├─2326 /usr/sbin/smbd --foreground --no-process-group ├─2355 /usr/sbin/smbd --foreground --no-process-group └─3723 /usr/sbin/smbd --foreground --no-process-group May 19 16:30:39 NAS systemd[1]: Starting Samba SMB Daemon... May 19 16:30:45 NAS systemd[1]: Started Samba SMB Daemon. May 19 16:30:45 NAS smbd[2219]: [2018/05/19 16:30:45.997388, 0] ../lib/ util/become_daemon.c:124(daemon_ready) May 19 16:30:46 NAS smbd[2219]: STATUS=daemon 'smbd' finished starting up and ready to s
12 Replies
I have/had this same exact problem. It started after installing the latest firmware upgrade. I have a temporary fix but it seems to revert itself after a while.
Your problem is most likely caused by the Samba(SMB) service not being able to start. For me this is caused by the fault value for "smb encrypt = (null)" in the /etc/samba/smb.conf file.
What you'll wanna do is enable ssh in your readynas admin page. Then download something like putty and connect to your nas. Login with root and the password you use to login to your admin page. Next open the /etc/samba/smb.conf file with your preferred editor and edit the above value to "smb encrypt = default"Reboot the nas.
This fixes it for me atleast temporarily.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
