This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I have a Duo v1 and NV+ v2, and both are currently not shown on Win 7 network browse session. But they have appeared in the past, and sometimes appear if i refresh and wait quite a while. When they appear, I see multiple entries as mentioned by StephenB, i.e. computer, storage, media, etc. If I enter the unit name or IP address, they are accessible all ok.
I think it changes if I reboot the switch between my PC and NASes, but I can't try that immediately, so maybe something kicks the networking interfaces on either end to reestablish reasonable communication?
I just tried browsing my network from my Win 7 PC, and my boxes *did* show up under "storage" but accessing through that just brings the management webpage. They didn't show up under anything else.
I rebooted the switch (Netgear GS108) and voila, both NASes show up under "Computer" and "Media Device" in the same network browser window.
Something triggers the NASes to start up (from idle/sleep, not power down), and once they are up they appear. I have no idea why!
I have the same problem with my ReadyNAS Ultra 4 with ReadyNAS OS 6 version 6.2.2 and Windows 7 x64 "Network" discovery. I cannot see my ReadyNAS on Network in "Windows Explorer". Other devices (desktop, leptop and other) are seen od the Network in "Windows Explorer".
Is there a problem with SMB version 3.0 set to default or a problem in ReadyNAS OS 6 version 6.2.2?
No, no IPv6 in use on my network (that I know of, as in all devices have regular IPv4 addresses).
I checked again, and my NAS's are still showing up fine, several weeks since my last reboot of the switch. I'm not sure it is a switch issue, but more that doing a power cycle forces the attached devices to reestablish their network connections. When the 'disappear' again, I will pull just the network cable from a NAS to check.
I have no concrete evidence here, but it is rather strange that it always seems to behave correctly once I reboot my switch, whereas rebooting the PC (a daily occurrence) never seems to change this. When it goes wrong again, I will attempt to get more information.
Any resolution to this? I am running into the same problem. No PCs (win7, Win8.1, and Win10) on my network will see the NAS device listed under network.
Workgroup is set properly on all devices..
nmbd appears to be up and running on the NAS104:
[2015/01/23 02:19:36.964147, 0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'nmbd' finished starting up and ready to serve connections [2015/01/23 02:19:59.212262, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) ***** Samba name server NAS is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.250 *****
mapping network drives. Not a great solution. But once you know what shares you need, it helps to have them mounted.
Oh, I have no problem accessing the device directly.. I'm looking for something to restore its listing in the network. If you have a lot of guest users that use the network, its a pain to explain to them how to mount it up since they can not see it on the network. I need to restore this functionality so guest users can find the device on their own..
It sounds like I need to contact netgear and open an issue.
mapping network drives. Not a great solution. But once you know what shares you need, it helps to have them mounted.
Oh, I have no problem accessing the device directly.. I'm looking for something to restore its listing in the network. If you have a lot of guest users that use the network, its a pain to explain to them how to mount it up since they can not see it on the network. I need to restore this functionality so guest users can find the device on their own..
It sounds like I need to contact netgear and open an issue.
I double checked on the forums as well and it shows that they already created a ticket for this kind of situation and is waiting for the response from the Engineering department.
Please do check the forums from time to time since we did not have any estimated time on when they can fix this.
Thank you for choosing NETGEAR.
Regards,
NETGEAR Support Expert
So sounds like a bug was created for Engineering to look at. At least we know its being addressed.
I guess there is no way for non-employees to follow bug updates tho.
I have exactly the same issue here. Just purchased ReadyNAS 102, working with Windows 8.1 and router Netgear D6300. Seen the NAS on the Lan for two hours, then disappeared. Tried on 4 different devices, but nothing. Accessible via \\ReadyNAS. Visible as Multimedia device and Storage device, but not as shared computer. Thank you
Sometimes is shows up, sometimes it won't. Personally I think its a windows issue, but its hard to be sure.
What you CAN DO is (a) enter \\nasname or \\nasipaddress in the windows explorer address bar (b) create a shortcut on the desktop to \\nasname\sharename (c) map \\nasname\sharename as a windows drive letter (d) add \\nasname\sharename as a "network location"
A breakdown in compatibility somewhere for sure, but I'm not sure Windows is to blame per-say.. Windows sees other Windows machines on the network perfectly with no misses for me. So the NetBIOS over IP name is being discovered/broadcast properly. Perhaps a snoop / tcpdump of the connection while the negotiating is occurring may shed some light on the issue. A wireshark capture from the Windows side even may show some sort of breakdown. If nmbd was upgraded as part of the NAS OS upgrade, perhaps some incompatibility was introduced. All speculation at this point, but I may try and do some troubleshooting here and update the forum.
Windows discovery on my Win7 systems is a bit temperamental, and sometimes also drops printers and other non-NAS devices. So I think it is most likely to be a windows discovery issue. I agree it might have another cause.
