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
- Can you try 6.2.3 Beta 4 on your 102?
- Yes I will try that and come back to you on both queries (your PM) as soon as I have got the data off the Duo that is trying to die again. It is taking forever to do it and I have come across more irritations* on the journey! I'm sure a lot of it is down to me, but it takes some understanding. Still, I have until Thurday to get it sorted, when I have a customer coming for a demo, with an intention to purchase.
*It will not recognise an 8Gb memory stick in any RN102 port
*SSH connects and then immediately drops out on password entry. 2 different programs do that. ## Me again!. Username can only be "root"
*One of my source directories on the Duo just vanished on its own. ## It is still there on the source Duo but 102 can't see it.
*Rsync of the most important shares completed without copying more than 20% of the files ## Trying another backup run as well as a direct copy.
*USB backup from the Duo has put everything mixed up into the root directory. ## I gather that is expected behaviour. - The 6.2.3 Beta fixed this issue for me, so it was an issue with the master browser as stated in the release notes.
- Works for me too.
- Can we have this on the list of things to fix in the older units, particularly NV+ v2 (ARM), and for a real bonus my old Duo (Sparc).
- I all. I have the same issue also. Suddenly I cannot connect my laptop by smb to the nas. Also from android by fxexplorer or nasutils. The only way to fix temporary is to reset the router and then see all. Now I have d6300 but I'l change to another (provider one) and I hope will be better.
- norrispackard 6.2.3 beta has a fix for this problem.
mdgm wrote: norrispackard 6.2.3 beta has a fix for this problem.
Thanks for the news. You mean wasn't a router problem?
Well, i'll try to upgrade to beta :DHi
ReadyNAS 102, windows 7, firmware 6.4, no router just switch, static IP assigned: 10.0.0.89
the drive is mappable, but does not show up in network devices????
any ideas? thanks!
update finally i got the readynas showing in devices turned out had the wrong subnet mask in the readynas network config now all are 255 much better. all pcs see the readynas under network as if it was another shared pc
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 :-)
Well John.............thanks for the Christmas present. I had got around my original problem using the shortcut method, but I thought I would give this one last go after checking your post...........and it damn WORKS!!!!
Finally back to how I wanted it all. Thanks so much for this last bit of info.
Have a great holiday.
Hey Drover, I'm glad this helped someone, I get really frustrated when Tech companies make changes to essentially consumer targeted products and change things around that previously worked for no real gain :-(
Some of the suggested 'fixes' are way to technical for the market the products are targetted at and many of the fixes are just hacks or work-arounds to solve problems that products (in a perfect world) shouldn't even have... Merry Christmas :-)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
