ReadyNAS NV+ - The remote device or resource will not accept the connection

---

StephenB wrote:

---

pimpyoda wrote:

---

Sandshark wrote:

Also, make sure you are not running any security software that also blocks SMB1.

---

I'm using Webroot and Windows Defender Firewall that comes with Windows 10. Could those be causing the issue and is there a way to check?

---

Just disable them.

 

Maybe also check that your NAS is still using IP address 192.168.0.2.

---

I disabled both WebRoot and Windows Defender Firewall and it still does not work.

The IP address is correct. I can still access Frontview through Chrome with it and it is the IP listed in Frontview as well as when I press the power button on the NAS.

Do you see the share list if you enter

net view \\192.168.0.2

net view \\192.168.0.2

When I type it into command prompt, it says  

System error 53 has occurred.

The network path was not found.

Could it have something to do with router settings?

---

pimpyoda wrote:

Could it have something to do with router settings?

---

Not if you can log into Frontview ( https://192.168.0.2/admin )

Maybe double-check that the SMB 1 client is enabled on the PC, and that the PC's network is classified as private.

Yes, it is Private and SMB 1.0 Client is checked under "Turn Windows Features On or Off".

---

pimpyoda wrote:

Yes, it is Private and SMB 1.0 Client is checked under "Turn Windows Features On or Off".

---

Maybe reboot the NAS and the PC, and try the "net view" command again.

Already tried rebooting everything. No luck.

Are you sure webroot is completely disabled?  Does it have any logging that you could check?

Yes, I tried accessing with Webroot completely disabled. Also tried accessing it from another laptop but no success. 

I can download scan log and threat log in Webroot, but not sure what I would be looking for.

Perhaps the NAS simply is no longer working properly? It was purchased in 2008. If I am unable to get it to work, is there a way to access the data? Perhaps purchasing a hard drive enclosure and switching the drives into it?

Let's try using a different file sharing protocol.

Enable FTP for one of your shares in Frontview.  Then download the FileZilla client, and see if that can access your files.  Use admin as the username, and the NAS admin password. https://filezilla-project.org/

Also:

• what firmware are you running on the NV+?
• Are you using share security or user security?

On the last question, you can tell by clicking on security in the left pane of frontview.

Firmware = [1.00a043] 

Under Security - Security Mode, there are 3 possible choices: Share, User and Domain. User is selected. 

Under Shares - Share Listing, CIFS, NFS, AFP, and HTTP/S are the options for file sharing. Not sure which enables FTP, but one of my shares has the first 3 selected and the last share has CIFS and HTTP/S selected.

When attempting FTP - 

Status: Connecting to 192.168.0.2:21...
Status: Connection attempt failed with "ECONNREFUSED - Connection refused by server".
Error: Could not connect to server

Also, when I got to System - Update - Check for Update, it says error connecting to remote server. 

---

pimpyoda wrote:

Not sure which enables FTP, but one of my shares has the first 3 selected and the last share has CIFS and HTTP/S selected.

 

---

FTP is it's own choice.  First you need to enable it as a file sharing protocol.

1. From the FrontView main menu, select Services > Standard File Protocols.
2. Select  the FTP check box.
3. Select User in the Authentication drop-down list
4. Enable "allow upload resumes"
5. Click the Apply button.

Then go back to the share settings and you will see an FTP column.

---

pimpyoda wrote:

 

Under Security - Security Mode, there are 3 possible choices: Share, User and Domain. User is selected. 

User is the right option for you.

---

pimpyoda wrote:

Firmware = [1.00a043] 

 

---

Otherwise known as 4.1.16 (which is the current firmware).  No idea why Netgear has two ways of identifying firmware on the sparc-based NAS.

---

pimpyoda wrote:

Also, when I got to System - Update - Check for Update, it says error connecting to remote server. 

---

Do you have a static address configured on the NAS?  If so, do you have a DNS server configured?

Also, is the NAS showing the correct time and date?

I was able to enable FTP and it is now showing up as an option in Share Listings. But when I changed "Allow Upload Resumes" to "Enabled", the following error message popped up:

Could not find the masquerade address in DNS. Please check that the value has a DNS entry or enter a numeric IP address.

Other settings under FTP:

Port: 21

Passive Ports: 1024-65535

Masquerade as: readynas

Regaring static IP and DNS, where do I go to see that? I clicked on Network - Interfaces and IPv4 assignment says "Use Values from a DHCP Server". So I assume that means it is not static. 

The time is 2 hours ahead but the date is correct. 

Something odd happened when I tried to enable FTP on one of the shares and click "Apply" Now it says "No Shares Exist" when I click on Share Listings. 

Navigating through Frontview also seems really slow.

---

pimpyoda wrote:

Regarding static IP and DNS, where do I go to see that? I clicked on Network - Interfaces and IPv4 assignment says "Use Values from a DHCP Server". So I assume that means it is not static. 

---

The address isn't static, but it is still possible there is an issue with the network configuration.

Go back to the network section, and select global settings. 

• Double-check the hostname - if it isn't readynas, then make a note of it.
• Check the Domain Server 1 field.  Normally it should be set to your router IP address.  

---

pimpyoda wrote:

 the following error message popped up:

Could not find the masquerade address in DNS. Please check that the value has a DNS entry or enter a numeric IP address.

If the masquerade isn't set to the hostname, then change it to that.  If that still fails, set the masquerade address to the IP address of the ReadyNAS (not a great workaround, but it will work as long as the NAS IP address doesn't change).

---

pimpyoda wrote:

 

The time is 2 hours ahead but the date is correct. 

 

---

Go to system->clock, and check that the time zone is set properly.

After that, try unchecking the synchronize clock box, click apply, then check it again (and click apply again).  Then see if you get an NTP error on the status->log page.  This last test is to see if your NAS can reach the internet.

---

pimpyoda wrote:

 

Something odd happened when I tried to enable FTP on one of the shares and click "Apply" Now it says "No Shares Exist" when I click on Share Listings. 

 

---

Not a good sign.

Do you have a backup of the data on the NAS?

1) The hostname is readynas. Domain Name Server 1 was blank and it is greyed out, so I cannot enter anything in there. 

2) Masquerade was set to the hostname  (readynas). I tried to change it to the IP address instead, but it still didn't work. 

3) Got this error when trying to sync the clock to Netgear's servers:

Unable to connect to specified NTP server(s).

I don't have a backup of the NAS. Does that mean the data could be gone?

---

pimpyoda wrote:

I don't have a backup of the NAS. Does that mean the data could be gone?

---

That is possible.

But it is also possible that you have a full root partition, and that the NAS configuration files have gotten corrupted.  That could also explain why we weren't able to gain access to the shares.

If you are the original purchaser, you can contact Netgear paid support (my.netgear.com) and they can troubleshoot remotely.  You'd boot up in tech support mode (one of the boot menu options), and give them a code that appears on the LCD screen.

Per-incident paid support is about $75 USD (I think).  If data recovery is needed, it would be a lot more expensive.  https://kb.netgear.com/69/ReadyNAS-Data-Recovery-Diagnostics-Scope-of-Service   

Note you don't want to pay for the "gearhead" support.  If you have difficulty getting per-incident support, the mods ( JohnCM_S and Marc_V  should be able to facilitate.

OK - thanks for trying to help with this.