NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ScottChapman
Nov 26, 2014Apprentice
windows not showing ReadyNAS name in network
My windows systems (win7 & 8.1) are not showing my ReadyNAS when I browse the network: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. ...
- Dec 21, 2015
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 :-)
Chairface
Jan 26, 2015Tutor
dsm1212 wrote: I don't have this problem but I do have the WINS server enabled in samba on the nas (See http://www.readynas.com/forum/viewtopic.php?f=160&t=79193). OS 6 seems to have removed that as a frontview option. Years ago I found having the always-on nas be the wins server seemed to make network neighborhood more reliable, but that may just be coincidence and there is something else buggy going on here.
steve
Hi Steve. Thanks for the tip, however no go so far for me. I attempted enabling WINS server with no change. I've attempted with the following mix of settings:
wins support = yes
wins proxy = yes
domain master = yes
preferred master = yes
In regards to the nmbd side..
nmbd appears to start up properly and register itself as a master browser:
[2015/01/25 23:34:25.479989, 0] ../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2)
*****
Samba server NAS is now a domain master browser for workgroup WORKGROUP on subnet 192.168.1.250
*****
[2015/01/25 23:34:27.504892, 3] ../source3/nmbd/nmbd_serverlistdb.c:401(write_browse_list)
write_browse_list: Wrote browse list into file /var/lock/samba/browse.dat
[2015/01/25 23:34:29.530157, 3] ../source3/nmbd/nmbd_namelistdb.c:263(add_name_to_subnet)
add_name_to_subnet: Added netbios name __MSBROWSE__<01> with first IP 192.168.1.250 ttl=0 nb_flags=e0 to subnet 192.168.1.250
[2015/01/25 23:34:29.530394, 3] ../source3/nmbd/nmbd_become_lmb.c:453(become_local_master_stage1)
become_local_master_stage1: go to stage 2: register the WORKGROUP<1d> name.
[2015/01/25 23:34:29.530492, 3] ../source3/nmbd/nmbd_namelistdb.c:263(add_name_to_subnet)
add_name_to_subnet: Added netbios name __MSBROWSE__<01> with first IP 192.168.1.250 ttl=0 nb_flags=e0 to subnet UNICAST_SUBNET
[2015/01/25 23:34:33.580989, 3] ../source3/nmbd/nmbd_namelistdb.c:263(add_name_to_subnet)
add_name_to_subnet: Added netbios name WORKGROUP<1d> with first IP 192.168.1.250 ttl=0 nb_flags=60 to subnet 192.168.1.250
[2015/01/25 23:34:33.581218, 3] ../source3/nmbd/nmbd_become_lmb.c:354(become_local_master_stage2)
become_local_master_stage2: registered as master browser for workgroup WORKGROUP on subnet 192.168.1.250
[2015/01/25 23:34:33.581302, 3] ../source3/nmbd/nmbd_sendannounce.c:70(broadcast_announce_request)
broadcast_announce_request: sending announce request for workgroup WORKGROUP to subnet 192.168.1.250
[2015/01/25 23:34:33.581534, 3] ../source3/nmbd/nmbd_namelistdb.c:263(add_name_to_subnet)
add_name_to_subnet: Added netbios name WORKGROUP<1d> with first IP 192.168.1.250 ttl=0 nb_flags=60 to subnet UNICAST_SUBNET
[2015/01/25 23:34:33.581663, 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 *****
[2015/01/25 23:34:33.581977, 3] ../source3/nmbd/nmbd_sendannounce.c:170(send_local_master_announcement)
send_local_master_announcement: type 8c9a03 for name NAS on subnet 192.168.1.250 for workgroup WORKGROUP
[2015/01/25 23:34:33.582160, 3] ../source3/nmbd/nmbd_sendannounce.c:189(send_workgroup_announcement)
send_workgroup_announcement: on subnet 192.168.1.250 for workgroup WORKGROUP
[2015/01/25 23:34:33.582327, 2] ../source3/nmbd/nmbd_browsesync.c:108(announce_local_master_browser_to_domain_master_browser)
announce_local_master_browser_to_domain_master_browser:
We are both a domain and a local master browser for workgroup WORKGROUP. Do not announce to ourselves.
Here we can see it process an incoming host announce:
[2015/01/25 23:34:33.587055, 3] ../source3/nmbd/nmbd_incomingdgrams.c:119(process_host_announce)
process_host_announce: from TV-PC<00> IP 192.168.1.200 to WORKGROUP<1d> for server TV-PC.
[2015/01/25 23:34:33.587250, 3] ../source3/nmbd/nmbd_serverlistdb.c:134(create_server_on_workgroup)
create_server_on_workgroup: Created server entry TV-PC of type 40011003 () on workgroup WORKGROUP.
A 2nd PC processed:
[2015/01/25 23:34:33.593303, 3] ../source3/nmbd/nmbd_serverlistdb.c:134(create_server_on_workgroup)
create_server_on_workgroup: Created server entry SEAN-PC of type 40011003 () on workgroup WORKGROUP.
[2015/01/25 23:34:34.027308, 3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
process_name_query_request: Name query from 192.168.1.100 on subnet 192.168.1.250 for name WPAD<00>
[2015/01/25 23:34:34.027541, 3] ../source3/nmbd/nmbd_winsserver.c:2027(wins_process_name_query_request)
Afterwards they are listed in the nmbd database on the NAS:
# cat /var/lock/samba/browse.dat
"WORKGROUP" c0001000 "NAS" "WORKGROUP"
"NAS" 408d9a03 "NAS" "WORKGROUP"
"TV-PC" 40011003 "" "WORKGROUP"
"SEAN-PC" 40011003 "" "WORKGROUP"
"BRW008092A6B761" 40002003 "" "WORKGROUP"
Still refuses to pickup the NAS from the client machines after various reboots and refreshes.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!