NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AndyMet
Nov 01, 2018Aspirant
ReadyNAS 6.9.4 CIFS SMB no longer functions
Hi, has something in 6.9.4 given issues for SMB/SAMBA/CIFS. I cannot connect to former working shares via SMB. A packet capture shows I make a TCP connection on port 445, but the readynas replies with a TCP RST. So this is way before we start negotiating SMB1 2 3 etc. This is as if the SMB service is not running on the NAS. To test I created new shares and enabled SMB disabled SMB etc but no joy, rebooted etc. (My shares are available through other protocols such as FTP - just as a test) Tried with and without the SMB+ app. I'm Convinced 6.9.4 has broken SMB in some way.
Any troubleshootng tips regarding the services on the readynas?
4 Replies
Replies have been turned off for this discussion
- StephenBGuru - Experienced User
6.9.4 hasn't broken the SMB service on my machines, though I have run into some specific hangs on my RN526. There is also an issue specific to the arm-based NAS like yours.
I suggest downgrading the NAS back to 6.9.3, and then seeing if your problem resolves. If it does, then you could try the 6.9.5 beta, which does have a fix for the arm-based problem. Others here have reported that it solved their problem and is stable.
- AndyMetAspirant
Sorry for being a long time replying, neither helped. so I had a biot of a deeper dig, and followed instructions for someone else. I removed and re-added SMB service through root ssh access but no joy, then smb service is broken with the following feedback
root@nas-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 Sun 2018-12-23 01:16:08 WET; 15s ago
Process: 3172 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 3172 (code=exited, status=1/FAILURE)
Dec 23 01:16:07 nas-nas systemd[1]: Starting Samba SMB Daemon...
Dec 23 01:16:08 nas-nas systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Dec 23 01:16:08 nas-nas systemd[1]: Failed to start Samba SMB Daemon.
Dec 23 01:16:08 nas-nas systemd[1]: smb.service: Unit entered failed state.
Dec 23 01:16:08 nas-nas systemd[1]: smb.service: Failed with result 'exit-code'.any help would be graetfully recevied
- StephenBGuru - Experienced User
Can you see why it failed? You might need to look at the full journal (or download the log zip and look in system.log or kernel.log). How full is the OS partition?
The brute force option is to do a factory reset - though it is painful it will completely rebuild the OS partition. You'd have to reconfigure the NAS and restore the data from backup.
You could also try downgrading to 6.9.3, and see if that resolves it.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!