NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
File service connection failure: RN21200 2-bay home NAS
My NAS box is just a month old. It has two 6TB IronWolf drives operating in RAID 0, giving me 10.9TB effective capacity. Firmware version is 6.10.1 which is the latest as of 10 minutes ago. Short...
Hi shuvam,
The SMB service on your NAS is now fixed.
The NFS service seems to be fine. It appears to be enabled currently on your NAS. It has been running for 2 days now.
Can you check if you can access your shares via SMB and NFS?
Regards,
I poked around in the log files, found a lot of entries clearly indicating that the SMB daemon is not starting up, but couldn't figure out why. The NMB daemon is working well, it appears.
I pulled out contiguous sets of lines from three log files and created the PDF file:
- systemd-journal.log
- smbd.log
- nmbd.log
and you can see the lines here. These are not grep outputs -- they are contiguous sets of lines, nothing omitted in between.
Any idea what is going on?
Hi shuvam , while you wait for more feedback, you might want to check some things. Just my 2 cents.
In your system-journal.log there is a line saying:
"Jun 23 13:26:26 nas-c702 wsdd2[4929]: cannot read workgroup from testparm"
(1) There is a parameter "workgroup" you can set in /admin page/accounts/authentication. Please check, that is not empty.
(2) The smb configuration file could be broken. I do not know its original name; somebody else, please?. Could it have been replaced by something called "testparm"? If file testparm exists and is taken as the configuration file, is it empty (file length of 0) or read-only/protected?
In system-journal.log there is another line saying:
"Jun 23 13:26:26 nas-c702 smbd[4928]: WARNING: Ignoring invalid value '(null)' for parameter 'smb encrypt'"
(3) I had one case in the past on my guineapig nas (RN104), where smb protocol was not working, was switched off by I didn't know what and could not be enabled again. I could fix that by de-installing and re-installing app smb plus. Running through the configuration process of smb plus after the fresh install and changing something (eg set the smb encryption to "mandatory") it was forced to (re-)write a configuration file and by that fixed the problem.
Good luck with fixing and kind regards
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
