My ReadyNAS does not show up as a Network Computer

yes, tried both and neither works.

---

jmacedo wrote:

yes, tried both and neither works.

 

That is very different from not seeing the NAS in the right storage category.  

Looking back at your original post, you said that you ended up in the browser when you entered \\nasname in windows explorer.

Usually that happens when you use the wrong slash (//nasname).  Can you try that again, just to be certain you did use the correct \\

Thank you so much!!! The suggestion to check out this thread https://community.netgear.com/t5/Using-your-ReadyNAS/windows-not-showing-ReadyNAS-name-in-network/m-p/945867 lead me to a post that suggested I check the workgroup name under Accounts>Authentication and make sure it matches the Workgroup name of your computer by typing in sysdm.cpl in search and comparing workgroup names. If they are different change it to the workgroup name of your computer and BAM!! My problem was solved. I can now see my ReadyNAS under Network. I now have to remount my shares but that isn't a big deal and EASILY fixed.

Thanks BaJohn for linking me to this thread and StephenB for writing the post in this thread. You guys are the best!

Thanks BaJohn. Nope, workgroup names were the same, one of the first things I checked.

However, after trying a bunch of things yesterday and coming back to the machine this morning, the NAS appeared in Network! On both the machine I was working on, and the other Win10 machine with a Microsoft account. Interestingly, the only thing I had done on the second machine was add a Windows credential to match a user account on the NAS. Perhaps it took time for the Windows network to sort out the permissions?

I still needed credentials to actually access the shares. Frustratingly, entering the newly created NAS user account details - or admin login - doesn't work. What seems to have worked - and is replicable - is allowing Anonymous access to the shares, and specifying the IP addresses of the computers that are allowed to connect. Which then leads one down another rabbit hole of assigning static IPs to all the machines... but at least is doable!

Might not work for everyone, but good enough for me where I HAVE to have a mapped drive to a NAS share.

StephenB I confirm I used backslash for the name and the IP in both Win Explorer and a browser, both directed to the NAS admin login.

However I think I have solved it for my circumstances - see other post

I am just pleased to have had a hand in you finding the solution to your problem.

Regards

---

jmacedo wrote:

StephenB I confirm I used backslash for the name and the IP in both Win Explorer and a browser, both directed to the NAS admin login.

 

 

You should of course use the forward slash (/) in the browser and the back slash (\) in windows file explorer.  

Entering the back slash in my browser (chrome) results in the browser converting the URL to file://nasipaddress/, and displaying "ERR_FILE_NOT_FOUND".  

Entering the forward slash in windows file explorer results in file explorer launching the browser (which of course does give me the NAS login screen)

---

jmacedo wrote:

 

However I think I have solved it for my circumstances - see other post

I'm glad it is accessible, but it sounds to me like something is still wrong.  You shouldn't need the host list (or switch to static addresses).  

FWIW it is better to reserve addresses in the router than assign static addresses - that has the same effect, but gives you the benefits of central management (avoiding inadvertant IP address conflicts, and allowing you to more easily change to a new IP address range).

Here's an update to my original solution. 

The NAS drive was showing up under Network computers fine for a few hours yesterday but now it has disappeared again. I've checked the Workgroup names and they are still the same. :/

---

StephenB wrote:
 

FWIW it is better to reserve addresses in the router than assign static addresses - that has the same effect, but gives you the benefits of central management (avoiding inadvertant IP address conflicts, and allowing you to more easily change to a new IP address range).

Both on my Win 7 and Win 10 I have always used reserved addresses in the router and found it is very useful.

As I do not allow any 'spare' addresses, this works as another minor barrier to access from 'unknown' machines.

It does mean a little bit more work when one of the family wants to change iPhone or gets a new 'caster' for the TV.

You also have to allow for 'dual' access on both the 2.4 GHz and the 5 GHz channels (if used).

Thus 10 systems MAY (not necessarily) require 20 records to be setup in the Router.

---

BaJohn wrote:

---

You also have to allow for 'dual' access on both the 2.4 GHz and the 5 GHz channels (if used).

Thus 10 systems MAY (not necessarily) require 20 records to be setup in the Router.

 

---

I also reserve all my addresses.  WiFi capable systems do have 2 addresses (one for wifi and one for ethernet).  

All my dual-band equipment uses one mac address for both bands - I've not seen a case where wifi addresses are needed for each band.

---

StephenB wrote:

 

---

I also reserve all my addresses.  WiFi capable systems do have 2 addresses (one for wifi and one for ethernet).  

 

All my dual-band equipment uses one mac address for both bands - I've not seen a case where wifi addresses are needed for each band.

---

Interesting .... my equipment is probably a few years old, and YES I find it a pain that I have to enter both MAC addresses if I want the hardware to operate on both bands.

It may be worth me investing in some more up to date equipment, which also might be a bit faster.

I will need to investigate further as I am surprised at what you say (I don't doubt that you are correct).

MAC addresses are associated with the individual chips in devices and each is unique in the world.

What it means is that the manufacturers have built both systems at different frequencies on the same chip.

I suppose that is progress, as the chips get smaller, easy to install, hence cheaper etc

---

BaJohn wrote:

---

---

 

manufacturers have built both systems at different frequencies on the same chip.

 

---

Correct (and that has been true for years).  For instance, this intel line: http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/wireless-ac-8x70-brief.pdf has dual-band wifi and bluetooth in the same chip.  Plus they threw in FM radio.

Also, cellular radio can be/often is built in.

---

StephenB wrote:

---

BaJohn wrote:

---

---

manufacturers have built both systems at different frequencies on the same chip.

 

---

Correct (and that has been true for years).  For instance, this intel line: http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/wireless-ac-8x70-brief.pdf has dual-band wifi and bluetooth in the same chip.  Plus they threw in FM radio.

 

Also, cellular radio can be/often is built in.

  

---

Yep .. given enough time, we will have 1 chip computers (getting close), all the interconnection protocols you can think off and small enough to fit in a pair of glasses.

It will except speech, use headup display and tell you when you are not feeling well. (Probably phone your vitals to the Doctor automatically and book a bed in the hospital)

There already are SoC (system on chip) packages - and the ARM ReadyNAS systems use them.  That's close enough to a "1 chip computer" to me.

Hi all.

Not solved for me.

I have been trying all the leads in this forum for two weeks now. Microsoft forums techs wont acknowlege the issue with their Win10.

One difference with mine is that under "my PC" even though I can see the files in the NAS, I cant access them.

Any new ideas?

Just for Info ... my Win 10 setup looks like this

Note that the ReadyNAS does NOT show up on the left hand side.

The only thing that does is the PC itself (TOP-MOUSE) within the Network.

I do NOT use Homegroup, BUT my WorkGroup (not shown) is set to 'FAMILY' both on the PC and the ReadyNAS.

I have static IP addresses (as mentioned) set by Router, and the 'hosts' file includes a reference to XNAS as 192.168.1.2.

Also the XNAS has acccess setup in the Windows Credentials Manager.

Just one strange thing, before a Win 10 and ReadyNAS OS updates recently double clicking the XNAS on the right brought up my XNAS login.

It now brings up 'ReadyCloud' which I haven't used for ages. Interesting, but not bothered about it particularly.

Good Luck in your quest to solve this... the above probably won't help, BUT  .....

---

RevellG wrote:

Hi all.

 

Not solved for me.

 

I have been trying all the leads in this forum for two weeks now. Microsoft forums techs wont acknowlege the issue with their Win10.

 

One difference with mine is that under "my PC" even though I can see the files in the NAS, I cant access them.

 

Any new ideas? 

 

Hardly a new idea, but as StephenB commented and others have discussed in other posts, there is a rumour that the problem REALLY IS with Win 10, and a fix might be coming out soon.

So my non-original idea, is to maybe 'live with it' one way or another and hope that this annoyance goes away in one of the many Win 10 updates coming your way soon.

Regards

---

RevellG wrote:

Hi all.

 

Not solved for me.

 

I have been trying all the leads in this forum for two weeks now. Microsoft forums techs wont acknowlege the issue with their Win10.

 

One difference with mine is that under "my PC" even though I can see the files in the NAS, I cant access them.

 

---

I think we need more information.  

Are you saying that you cannot access any shares from the file explorer?  

Are you using a local account, or a Microsoft account?  

Are you using the PIN logon or entering your password?

So after many attempts to get this thing to work on my Windows 10 machine I decided to try again with my Windows 8.1 machine. And it works! I'm guessing one of the many suggestions on this thread got it to work for Windows 8.1 (my suspicion is checking the workgroup names matched). 

So now I am wondering if this really is a Windows 10 issue? And if so I hope the rumors of recent updates from microsoft fixing the issue are true (not sure where I read it in these forums). 

Julian

---

jmacedo wrote:
............... What worked for me, after checking all were on the same Homegroup, ...............

I'm intrigued by the mention of 'Homegroup'. Is that essential to it working? 
It might be useful to know what would happen if you made them NOT on the same Homegroup or switched it off.

And it's working again!

I just received a windows update and restarted my computer and now my ReadyNAS is showing up as a computer in my network. I don't know if this will help anyone but below is the udpate that fixed it for me.

Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3140743)

---

sharpycl wrote:

And it's working again!

 

I just received a windows update and restarted my computer and now my ReadyNAS is showing up as a computer in my network. I don't know if this will help anyone but below is the udpate that fixed it for me.

 

Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3140743)

---

That's good to here.

Did you see how many files were updated in that release .... wow man.

My ReadyNAS was already showing so I didn't have the problem ... BUT I did lose my HP Mono printer's visibility in 'network' earlier today (before the Win 10 update).

... and no it did not come back afterwards.

Strangely enough, even though it is the default printer, it does not show in the 'network'.

BUT it shows in 'Control Panel' => devices and printers.

Weird seeing as how it is a WiFi connected printer in another room.

"The truth is out there" ... we just can't find Mulder!

---

BaJohn wrote:

---

sharpycl wrote:

And it's working again!

 

I just received a windows update and restarted my computer and now my ReadyNAS is showing up as a computer in my network. I don't know if this will help anyone but below is the udpate that fixed it for me.

 

Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3140743)

---

That's good to here.

Did you see how many files were updated in that release .... wow man.

My ReadyNAS was already showing so I didn't have the problem ... BUT I did lose my HP Mono printer's visibility in 'network' earlier today (before the Win 10 update).

... and no it did not come back afterwards.

 

Strangely enough, even though it is the default printer, it does not show in the 'network'.

BUT it shows in 'Control Panel' => devices and printers.

Weird seeing as how it is a WiFi connected printer in another room.

 

"The truth is out there" ... we just can't find Mulder!

---

Sorry to hear about that BaJohn. I haven't had any problems with printers in my network places (knocks on wood) but I am starting to notice the conspiracy against the Network Places in file explorer (just jk).