NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Ultra 6 Does Not Show Up On Windows 10 Network ... But Did At First
RE: ReadyNAS Ultra 6 Does Not Show Up On Windows 10 Network ... But Did At First At first the ReadyNAS 6 showed up and then it didn't. I restarted, switched the Network on and then off and back o...
Thankyou kindly for pushing me over the line there:
The case of the disappearing ReadyNAS Ultra 6 on Window 10 has been solved.
I will confirm file transfers are successful ... just a second ... yes.
A few questions: Why was it appearing at the beginning, and then suddenly refusing?
IF SMB 1.0 has been so unacceptable for so long ... surely the red flags would be waving a little louder on Windows 10?
Also why the Macs do not appear to require identification, and now this PC on a private internal ethernet network requires ID seems odd ? Is it ?
Either way, thankyou.
The network connection needs to be private, so double check that. I can't quite tell from your screen shot.
Don't bother with homegroups (they don't matter for the NAS). Workgroups do.
Right-click on "This PC" and select properties. You'll see "Computer name, domain, and workgroup settings" about halfway down the screen. You can select "change settings" and then "network id".
On the NAS, look in "security", then "security mode". The mode you want is "user", and there's a place there to enter the workgroup.
Also, you do need to reboot the PC after you enable the SMB v1 client.
Thankyou kindly for pushing me over the line there:
The case of the disappearing ReadyNAS Ultra 6 on Window 10 has been solved.
I will confirm file transfers are successful ... just a second ... yes.
A few questions: Why was it appearing at the beginning, and then suddenly refusing?
IF SMB 1.0 has been so unacceptable for so long ... surely the red flags would be waving a little louder on Windows 10?
Also why the Macs do not appear to require identification, and now this PC on a private internal ethernet network requires ID seems odd ? Is it ?
Either way, thankyou.
I glad you resolved it.
HBGChristo wrote:
A few questions: Why was it appearing at the beginning, and then suddenly refusing?
Access (transferring files) is different from discovery (showing up in the network list). When discovery fails, you can still reach the NAS by entering \\hostname or \\nas-ip-address in the file explorer address bar. And as you learned, you can have access issues even when the NAS is discovered.
Discovery of linux systems has always been a bit hit-or-miss with Windows, and over the years many people have seen their NAS suddently disappear (or re-appear) from the network list for no apparent reason. In most cases that's unexplained (and I have looked in many forums for information on that). I suspect that Apple's discovery implementation is closer to Linux (since underneath the GUI their OS is similar).
HBGChristo wrote:
IF SMB 1.0 has been so unacceptable for so long ... surely the red flags would be waving a little louder on Windows 10?
I've seen a lot of red flags waving on this, so perhaps it depends on what you follow.
Microsoft initially announced their plans to deprecate SMB 1 in 2013. The last Windows system that only supported SMB 1 was Windows Server 2003 (which Microsoft stopped supporting in 2015). So from Microsoft's point of view they provided a very long runway for phasing it out. https://blogs.technet.microsoft.com/josebda/2015/04/21/the-deprecation-of-smb1-you-should-be-planning-to-get-rid-of-this-old-smb-dialect/
Still, they left SMB 1 on by default, so they didn't seem to be in any hurry. That immediately changed when WannaCry Ransomware struck last year. https://redmondmag.com/articles/2017/05/18/more-advice-on-disabling-windows-smb-1.aspx
A few months after WannaCry, Microsoft began rolling out releases that didn't enable SMB 1 by default, and which disabled SMB 1 silently if it wasn't being used. In addition they've been tightening up guest access to Network Shares - which is why I recommend using explicit credentials instead of depending on that working.
There are plenty of other articles and forum posts on this topic in a lot of places.
HBGChristo wrote:
Also why the Macs do not appear to require identification
I'm not a Mac owner, so I don't know the details on how OSX handles SMB. And your Macs might also be using the AFP protocol if that is enabled on the NAS.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
