NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Windows 10 Install: no longer able to access NAS shares
Hi, I upgraded 3 days a go to Windows 10 Enterprise build 16299. It was an installation from scratch I sadly have no longer access to any of my SMB shares. Access was working on Windows 7: see image below - I tried dropping to SMB1 in SMB Application + reboot both PC and NAS: no success - I disabled IPV6 under LAN adapter in Windows 10: no success - I enabled every sharing option under Windows 10 for both Private and Public networks: no success Using cmd in admin console to map the network share: net use * /delete net use t: \\nas-ip-address\data /user:admin nas-admin-password Under the shell cmd, I have access to the shares and their listing through drive T: However, it is wired that Explorer GUI cannot access to the T: drive. So I still cannot see my shares in GUI Under Explorer, I can see the NAS: - under "Media Devices", and brows the DLNA folders - under "Storage", double clicking brings the NAS web admin GUI - under "Computer", named correctly "NAS-01": but if I try to access the shares it gives me a "Network access error" I attach above the image with my error Please help me fix this asap, I am lost and really need the SMB access to manage my backups
Time Capsule on Orbi?
Just curious... has anyone gotten their Airport Time Capsule to work on Orbi yet? Or, more generally, is anyone using Time Machine with Orbi? I've got my Time Capsule hooked up to the Orbi satellite. You can see it in the list of attached devices, but it's showing up in my Finder as a SMB share (with a PC icon) and I'm unable to connect to it. Would it work better with the main Orbi hub? Thanks for any tips you might have! (I'm running macOS Sierra 10.12.2 with the Orbi Firmware Version 1.4.0.18)
Character encoding, Codepages, SMB/CIFS and NFS
We've got 4 ReadyNAS in operation. The 2 oldest units run RAIDiator: v4.1.16 with Samba v.3.6.25 and cannot be upgraded anymore. Microsoft finally decided to dump SMBv1 and all machines on our network got upgraded to a life without SMBv1 hence the 2 old NAS were no longer available to the network. To resolve this issue we decided to enable NSF and disable SMB/CIFS. Microsoft was nice enough to include the NSF-Client and server in their updates. This way we can keep them units on the Network and in production as redundant backups of backups - we first thought. We we're able to map the shares to Windows 10, read and write data for testing, etc. all is operational. So far so good and almost too nice to be true. But there is a problem! Folder- & file-names that use special characters changed their appearance. For instance all Umlaut like äöü became double characters. eg. the letter "ü" displays as double character "ü" in NSF-client. Yep it's an issue directly related to varying codepages. Apparently the NAS OS (RAIDiator) uses varying codepages for SMB/CIFS and NSF. The option for language selection in Frontview is missleading. To be on the safe side one would have to select english ASCII. By selecting any Unicode option incompatibility between SMB/CIFS and NFS filesystems/protocols gets in effect without any mention. This is not documented by Neatgear (at least we could not find anyting). We assume we're not the first and only customers experiencing this senselessness and would like to learn wether there is a solution that we might have missed. Looking forward to receiving responses.
