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 summary: I can't connect to the file service from any device which I used to use before to read and write files successfully.
Context: this is used only on my home LAN. I don't want to use ReadyCloud or access things from outside my home.
Long version: I'll list what works first:
- the web interface works. I can see all the screens, browse the content, go to various admin screens.
- I can download files using the web interface.
- I can ask the update manager to check for new updates -- it works and gives no error
- rsync works. I can list the contents of my share by connecting to the NAS internal rsync daemon, when I connect using my command-line rsync client from my Linux laptop.
- ssh works. I have logged in, poked around at the shell level and logged out.
- I checked all the logs using the web browser interface. (I haven't downloaded the logs yet, just checked on-screen.) No errors.
- I did a restart, both from the web interface and by physically tapping the power button twice on the front panel. It restarted successfully.
What does not work: basically the file service.
- I used to connect from my Raspberry Pi box running Kodi and play my media: it cannot connect. It says "connection failed" or "connection refused".
- I used to connect from my Ubuntu GUI using the Nautilus application: I had defined an SMB connection. That too is saying "connection refused".
What should I do next?
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,
24 Replies
Replies have been turned off for this discussion
Hi shuvam, to use smb connections successfully the nas on the one hand and the clients on the other hand need to talk to each other at the same protocol level.
The nas on 6.10.1 by default uses SMB 3.1.1. If your clients don't you will not be able to connect. Basically you have 2 options:
1) Make your client(s) talk SMB3 or
2) Lower the protocol level on the nas side by installing app smb plus. This way you could configure the nas to talk SMB2 or lower if necessary
I would recommend to explore, whether you could configure your clients to talk SMB3. Talking that protocol level is most secure at the moment.
Kind regards
I am sorry if I did not explain my position clearly.
SMB 3 is quite old, and is well supported by both the Linux on LibreELEC (which runs on my RaspBerry Pi) and on my Ubuntu Linux laptop. I was actually using the ReadyNAS box from both these devices over SMB till yesterday. Therefore, this is not a case of SMB 3 support or lack of it. Something broke yesterday, without me doing anything with the NAS box, not even upgrading its firmware.
Incidentally, it seems to be purely an SMB problem. I am able to access the box over NFS very well -- I hadn't tried this till now, and it's working well now. So, my problem is now limited to SMB. And it's not about SMB level compatibility between client and server.
I found evidence of the malfunction on the GUI. For some reason, I never bothered to check back here.
The SMB service itself is switched off. I have no idea why. And when I click on that icon and try to start it, I go through all the settings, including checking the check-box which "enable SMB", and then I click "OK". The pop-up dialog box disappears, but SMB does not start.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
