NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
SAMBA
7 TopicsCant enable SMB on ReadyNas 316
Hi, I noticed that SMB service on my ReadyNas 316 with version 6.9.3 stopped working 2 days ago and I can't turn it on. At first I didnt see the shares and after reboot, I saw that SMB was turned off. I have tried to search for any solutions but I cant find one. I really don't want to do an factory reset. What I tried so far: OS Reinstall Downgrade from: 6.9.3 -> 6.9.1 -> 6.9.0 -> 6.8.1 and then back to 6.9.3 = None version is working Update pagages with "apt upgrade" When I run "systemctl status -a smb": root@NAS:~# systemctl status -a smb smb.service - Samba SMB Daemon Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-04-28 13:18:04 CEST; 49s ago Process: 8988 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE) Main PID: 8988 (code=exited, status=1/FAILURE) Apr 28 13:18:03 NAS systemd[1]: Starting Samba SMB Daemon... Apr 28 13:18:04 NAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE Apr 28 13:18:04 NAS systemd[1]: Failed to start Samba SMB Daemon. Apr 28 13:18:04 NAS systemd[1]: smb.service: Unit entered failed state. Apr 28 13:18:04 NAS systemd[1]: smb.service: Failed with result 'exit-code'. When I try to manually start smb.service I get: root@NAS:~# systemctl start smb Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details. I find following in journalctl -xe: Apr 28 13:14:57 NAS systemd[1]: Starting Samba NMB Daemon... -- Subject: Unit nmb.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nmb.service has begun starting up. Apr 28 13:14:58 NAS systemd[1]: nmb.service: Main process exited, code=exited, status=1/FAILURE Apr 28 13:14:58 NAS systemd[1]: Failed to start Samba NMB Daemon. -- Subject: Unit nmb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nmb.service has failed. -- -- The result is failed. Apr 28 13:14:58 NAS systemd[1]: nmb.service: Unit entered failed state. Apr 28 13:14:58 NAS systemd[1]: nmb.service: Failed with result 'exit-code'. Apr 28 13:15:09 NAS readynasd[3398]: Service 'nmb.service' goto unexpected state 'failed'. Expect to be 'active'('activating'). Apr 28 13:15:09 NAS readynasd[3398]: Protocol 'cifs' is reloaded Apr 28 13:15:09 NAS systemd[1]: Starting Samba NMB Daemon... -- Subject: Unit nmb.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nmb.service has begun starting up. Apr 28 13:15:09 NAS systemd[1]: Started WSD/LLMNR Discovery/Name Service Daemon. -- Subject: Unit wsdd2.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit wsdd2.service has finished starting up. -- -- The start-up result is done. Apr 28 13:15:09 NAS wsdd2[8270]: starting. Apr 28 13:15:09 NAS systemd[1]: nmb.service: Main process exited, code=exited, status=1/FAILURE Apr 28 13:15:09 NAS systemd[1]: Failed to start Samba NMB Daemon. -- Subject: Unit nmb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nmb.service has failed. -- -- The result is failed. Apr 28 13:15:09 NAS systemd[1]: nmb.service: Unit entered failed state. Apr 28 13:15:09 NAS systemd[1]: nmb.service: Failed with result 'exit-code'. Apr 28 13:15:09 NAS systemd[1]: Starting Samba SMB Daemon... -- Subject: Unit smb.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit smb.service has begun starting up. Apr 28 13:15:09 NAS wsdd2[8270]: cannot read workgroup from testparm Apr 28 13:15:09 NAS wsdd2[8270]: cannot read workgroup from testparm Apr 28 13:15:09 NAS wsdd2[8270]: cannot read netbios name from testparm Apr 28 13:15:09 NAS wsdd2[8270]: cannot read netbios name from testparm Apr 28 13:15:09 NAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE Apr 28 13:15:09 NAS systemd[1]: Failed to start Samba SMB Daemon. -- Subject: Unit smb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit smb.service has failed. -- -- The result is failed. Apr 28 13:15:09 NAS systemd[1]: smb.service: Unit entered failed state. Apr 28 13:15:09 NAS systemd[1]: smb.service: Failed with result 'exit-code'. Apr 28 13:15:09 NAS wsdd2[8270]: Terminated received. Apr 28 13:15:09 NAS wsdd2[8270]: Terminated received. Apr 28 13:15:09 NAS systemd[1]: Stopping WSD/LLMNR Discovery/Name Service Daemon... -- Subject: Unit wsdd2.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel Can someone please help me?Solved2KViews0likes2CommentsSamba/SMB share access issues with ReadyNAS OS 6.8.0 on RN202
Sir(s) et al I've manually upgrade my RN202 from [ReadyNAS OS 6.7.5] to [ReadyNAS OS 6.8.0]. After the upgrade I wasn't able any more to access my samba/smb shares from my Linux computers running Manjaro Linux (some kind of Arch Linux) and Debian 9 Stretch (on a cubietruck): - I can see/browse the shares, get asked for the credentials, but can't login to the share - My Nextcloud installation has the same issues - On a virtual Windows 10 i can access the shares - Enable/disable the new MAC-OS feature didn't solve the problem - Using the SMB Plus tool didn't solve the issue either After a dirty rollback to [ReadyNAS OS 6.7.5] everything went back to normal/expected behavior. Another member seems to has reported a similar issue here: https://community.netgear.com/t5/Using-your-ReadyNAS/samba-issue-with-mac-KODI-after-upgrade-to-6-8-0/m-p/1345769#M134953 Regards,Solved11KViews0likes14CommentsSamba doesn't work anymore
Hello, pals! Today i'd face the problem with samba on my RN104. After turning the server off and that turned it on everything seemed ok unless i couldn't reach the server via samba. When i tryed to turn the SMB service on from web interface it delayed for 5-10 seconds and then nothing happend. It still off! Please help! I have ReadyNAS 104 server, sw ver. 6.7.5 FTP and SSH connections are ok. Here was very similar problem solved with overwriting default config file. But i have no idea which file to overwrite and were i could find the source for itSolved3.6KViews0likes5CommentsSamba hangs
Hello, I have frequent problems accessing NAS through Samba in LAN (no domain, ten Windows 10 computers in Workgroup). When it works it works, but it freezes randomly, when opening/saving file or folder. Latest firmware, antivirus disabled, ping <1ms. Any suggestions how to find the reason and fix are very welcome! I have no idea left what to do and now it's unussable with random freezes :(4.3KViews0likes13CommentsSamba doesn't work
Hello I have problem with my samba deamon, after last reboot, my NAS has updated automatically, and now samba doesn't work. I have tried to reinstall samba by hand but I don't have any idea how to install samba-common for netgear4 ? My sources.list: Can someone help how to install it ?Solved4.6KViews0likes10CommentsHaving trouble with user homedir shares on CIFS
Running ROS 6.4.1 and Mac OS X 10.11 I was having trouble connecting to some CIFS shares after recent ROS and Mac updates. I managed to resolve all the regular share access by resetting file ownership and flipping SMB status in the admin UI. But with homedirs, nothing I've tried so far works. After looking at the /etc/samba/smb.conf and files in /etc/frontview/samba, everything looks like it should work from what I can tell -- and I have some experience running Samba outside ReadyNAS. *But* when I attempt to log into the user share (even after successfully connecting to other shares as that user) I get "permission denied." I confirmed this running smbclient on the NAS itself. # smbclient -W DOMAIN -U user //nas/user password Domain=[DOMAIN] OS=[Windows 6.1] Server=[Samba 4.2.4] tree connect failed: NT_STATUS_ACCESS_DENIED I successfully used this CLI to access other shares as the user and indeed was able to connect as admin to //nas/home and browse the users' homedirs. So... not exactly sure what is afoot here. The tail of the smb.conf contains: include = /etc/frontview/samba/smb.conf.%a include = /etc/frontview/samba/smb.conf.overrides include = /etc/frontview/samba/Shares.conf include = /etc/frontview/samba/Shares.conf.%U include = /etc/frontview/samba/addons/addons.conf [homes] browseable = 0 writeable = 1 public = 0 valid users = %D\%S The recently updated files in /etc/frontview/samba are: -rw-r--r-- 1 admin admin 303 Jan 2 03:27 Shares.conf.admin -rw------- 1 admin admin 2991 Jan 2 03:37 Shares.conf -rw-r--r-- 1 admin admin 0 Jan 2 03:37 dfs.conf Based on this, nothing seems amiss... but I've avoided making any manual adjustments so far.... just using the levers in the admin UI. I have looked at the /home/ directory permissions and all looks well there too. And, sadly, nothing seems to be popping up in the samba logs on the NAS that give any indications of the permission denial.Solved3.1KViews0likes12CommentsUltra 6 plus - SMB not advertised anymore
Hello, ULTRA6 PLUS 6x3TB Xraid2 OS 4.2.28 36% capacity used Suddenly the SMB shares are no more showing on the windows clients - not related to 4.2.28 upgrade. Shares are still accessible via the IP address, SSH works. No mods were done recently, all disks are fine. Maybe the CIFS service is not running ? Some partitions get full ? I spent hours around this and can work my way around Windows and networking but would need pointers for Linux and such. Any ideas ? Thanks BenoitSolved4.2KViews0likes12Comments