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
- 6.2.3 Beta 4 is available: http://www.readynas.com/forum/viewtopic.php?f=154&t=78866
- Presumably this is a samba bug, please can it be shared? Thanks...
- I don't have any units running 6.x, as I only have Duo v1 (Sparc) and NV+ v2 (ARM), however I see this problem sometimes. I just scanned my network, and can see my Duo is the master browser *and* windows explorer is finding all network devices including the Duo and NV absolutely fine.
- This bug affects 6.2.x firmware.
I doubt legacy firmware would be affected. - Light at the end of the tunnel!
Has the issue been reproduced on other readynas firmware? If one has several readynas units on the lan with other firmware, will these also be prone to this bug?
I have 4.2.27 and 4.1.14 active. - Thanks for the update! Most appreciated.
- We have reproduced this issue.
There are two things to note:
1. On modern Windows systems it is much more difficult to find systems outside of your own workgroup. Please make sure your NAS is in the same workgroup as your PC. If it isn't please change it (note that currently rebooting is required for this change to take effect. This will be fixed in 6.2.3).
2. We have identified a bug when the NAS is elected the master browser. As a workaround until a firmware update addressing this is available you can try turning off the NAS trying to become the master browser as Chairface described above. Alternatively you can wait for a fix in 6.2.3. - I meant to update sooner. Rather than change the settings on the PC side, I decided to stop the ReadyNAS from ever becoming the master browser, as the default seems to sometimes become a local master..
Adding:
local master = no
/etc/frontview/samba/smb.conf.overrides
to the overrides file has windows managing the NetBIOS for me full time, and the other PCs now see the NAS under Network properly. I'm still thinking there is a breakdown in samba's current implementation of NetBIOS. As long as Windows is doing the lifting it appears to be ok (Windows receives and processes the NetBIOS info from the NAS box and broadcasts it out properly). Which is a shame since the NAS box is more of the "always on" piece most of the time. However my TV-PC is always on the network and only occasionally sleeping, so this setup should work for me.
So others that see it occasionally working, and occasionally not working, probably want to stop the NAS box from trying to become a master browser to work around this. Maybe a future update to the samba client may resolve it.
Thanks for all the help. - I found this utility which will scan your LAN to identify workgroups and master browsers:
http://scottiestech.info/2009/02/14/how ... workgroup/
I would think since this is a windows network problem, then a windows pc is the best machine to be master browser even if it's not on all the time, not the readynas.
You can also set a PC to be a master browser by editing the registry:
HKLM/System/CurrentControlSet/Services/Browser/Parameters/MaintainServerList
It should be set to Auto. You can add the value IsMasterBrowser and set it to 1 to make that machine a master browser. Not sure if this will be applicable for all windows versions though.
You can have more than one master browser on a LAN.
Alternatively you can stop the computer browser service on all pcs except the one you want to be master browser. - It is worth trying to change the workgroup name on all devices.
Start with your main PC, change the workgroup name to something else, then reboot it.
Then change all other PC's workgroup names to match this and do the same with your nas devices. Reboot each device after changing the name.
I don't know why this worked for my LAN or whether it will provide a stable, sustained solution. It has probably worked by forcing the master browser role onto my main PC, then forcing this to rescan the LAN. This should be automatic though.
If I change back to "WORKGROUP" the problem of one (of 3) missing readynas on the windows network recurs - on both PCs on the LAN.
Weird.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
