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
- 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. - This is a recurring theme, and not just about OS6 products. I suspect windows network discovery is a bit hit or miss myself.
- Yea, I agree. the NAS is just doing SAMBA.
- 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.
- I haven't booted my switch in a while. Mine is a D-Link smart managed switch (so there's tons of stuff there)
- 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 *****
Is there a bug open to address this?
Thank you. - I kinda just gave up on it since it can be worked around. But still, I know it was working before (6.1.9 I think) quit reliably.
Nothing else changed on my network. ScottChapman wrote: I kinda just gave up on it since it can be worked around. But still, I know it was working before (6.1.9 I think) quit reliably.
Nothing else changed on my network.
Hi Scott.. What workaround was successful for you? I have rebooted everything on the network.. no change..- mapping network drives. Not a great solution. But once you know what shares you need, it helps to have them mounted.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
