NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
windows not showing ReadyNAS name in network
My windows systems (win7 & 8.1) are not showing my ReadyNAS when I browse the network:
nmbd looks like it is running OK:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\schapman>net view
Server Name Remark
-------------------------------------------------------------------------------
\\CHAPTOP Scott Chapman's laptop
The command completed successfully.
C:\Users\schapman>net view \\storage
Shared resources at \\storage
Storage
Share name Type Used as Comment
-------------------------------------------------------------------------------
Documents Disk Document folder
ESATA_HDD_1 Disk Seagate ST3000DM003-1F216N
Music Disk Music folder
Pictures Disk Picture folder
Scott Disk (UNC) Home directory of Scott
Videos Disk Video folder
The command completed successfully.
nmbd looks like it is running OK:
[2014/11/25 14:53:54.081070, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2014/11/25 14:54:18.293011, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****
Samba name server STORAGE is now a local master browser for workgroup OURHOME on subnet 192.168.2.93
*****
[2014/11/25 14:55:06.891433, 0] ../source3/nmbd/nmbd.c:169(nmbd_sig_hup_handler)
Got SIGHUP dumping debug info.
[2014/11/25 14:55:06.891648, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.2.93: netmask= 255.255.255.0:
OURHOME(1) current master browser = STORAGE
STORAGE 40849a03 (Storage)
[2014/11/25 14:59:17.944256, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****
Samba name server STORAGE is now a local master browser for workgroup OURHOME on subnet 5.205.249.48
*****
[2014/11/25 20:29:27.991705, 0] ../source3/nmbd/nmbd.c:169(nmbd_sig_hup_handler)
Got SIGHUP dumping debug info.
[2014/11/25 20:29:27.991956, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 5.205.249.48: netmask= 255.0.0.0:
OURHOME(1) current master browser = STORAGE
STORAGE 40849a03 (Storage)
[2014/11/25 20:29:27.992231, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.2.93: netmask= 255.255.255.0:
IRIS(2) current master browser = CHAPTOP
OURHOME(1) current master browser = STORAGE
STORAGE 40849a03 (Storage)
STEWIE 40011003 ()
ZENBOOK 40011003 (Andra's Laptop)
[2014/11/25 20:29:50.893727, 0] ../source3/nmbd/nmbd.c:169(nmbd_sig_hup_handler)
Got SIGHUP dumping debug info.
[2014/11/25 20:29:50.893926, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 5.205.249.48: netmask= 255.0.0.0:
OURHOME(1) current master browser = STORAGE
STORAGE 40849a03 (Storage)
[2014/11/25 20:29:50.894197, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.2.93: netmask= 255.255.255.0:
IRIS(2) current master browser = CHAPTOP
OURHOME(1) current master browser = STORAGE
STORAGE 40849a03 (Storage)
STEWIE 40011003 ()
ZENBOOK 40011003 (Andra's Laptop)
Hello, I'm not sure if this reply is in the correct spot but after searching for a solution myself I read many of the comments here I also have had problems over the last few days since upgrading the Firmware to 6.4.1 on my NAS RN202 - I wasn't sure if was a Windows (10) update that caused it or something else but everything changed and my NAS202 stopped showing up under 'Network' - I was able to improve this by moving some files and folders into different directories as it seemed that the more files the unit had to refresh (or what ever the NAS does) the more often it couldn't find things, I also found that some of my permissions seemed different (always take a screenshot of what works) but the REAL kicker was when I discovered that under Accounts >> Authentication >> Workgroup Name: this had somehow become VOLUME... I would never have called it this opting for the more obvious choice of WORKGROUP... once I changed this everything started working correctly again including on my Laptop connect wirelessly to the network. Might be something to check :-)
93 Replies
Replies have been turned off for this discussion
ScottChapman wrote: 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.
Thank you for your quick responses.Chairface wrote: ScottChapman wrote: 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.
Thank you for your quick responses.
Sure, please post results back to the forum?Sure, please post results back to the forum?
Will do! I've opened a support ticket.- Received a response from Netgear Support:
Hi Sean,
Thank you for the quick response.
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.
None that I know of.Chairface wrote: 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 - sigh....
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"
(c) and (d) will show the sharename in Computer. - 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.
Thanks all! - 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.
Let us know what you find. - Someone tried by installing a earlier version of OS? I don't know if it's possible...
My d6300 Netgear router see the ReadyNAS as attached device without any problem.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
