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
- The workgroup is set correctly?
- Yep, just double checked. It is "OURHOME" on all my PCs and
workgroup = OURHOME
appears in mysmb.conf - PCs have been rebooted?
You can access the shares?
Everything in the same subnet? - Only one subnet, rebooted all machines. I can access the shares just fine.
- I have an RN102 with 6.2.0 that doesn't show up under Network in Windows Explorer. If I go to map a network drive, and enter the path to the share manually, that works though. I originally had it set up with 6.1.9 and it showed up as expected, but then I put two new disks which went to 6.2.0 as it set up.
- Same here. It was working like a champ on 6.1.9
- That is working for me. The RN102 shows up under "Computer", "media device" and "storage".
Overall, showing up in "network" seems to be hit or miss with Windows, so this might not be a regression in 6.2. There is a direct workaround - just set up a windows shortcut on the desktop. - What do you mean by 'The RN102 shows up under "Computer", "media device" and "storage".'? I was only talking about the Network browser
And I agree, Samba is such a tricky thing to get configured properly. Was it update in 6.2.0? - In advanced sharing settings in network and sharing center, is network discovery on?
Perhaps turn it off and then on again and refresh the network places screen.
It works on my windows 7 pc, before and after upgrading to 6.2.0 - Yea, tried that. Made sure I am on a private network, turned discovery on and off. Behaves same way on my 2 windows 8.1 machines and my one windows 7 machine.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
