NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 netwo...
Of course NFS has no security at all. So you could simply reinstall the SMB1/CIFS client on your windows PCs.
snahl wrote:
This way we can keep them units on the Network and in production as redundant backups of backups
If they are backing up another NAS, then you can disable both SMB and NFS on the NAS, and back them up with rsync.
snahl wrote:
Apparently the NAS OS (RAIDiator) uses varying codepages for SMB/CIFS and NSF.
Those language options apply to the web pages, not the file sharing protocols. In the specific case of NFS, NFSv2 and NFSv3 doesn't allow for character encoding - the assumption there is that the client and server have to match.
NFSv4 is supposed to use UTF-8, however that isn't enforced in the NFS clients. And I don't think your legacy NAS supports NFSv4.
StephenBwrote:
NFSv4 is supposed to use UTF-8, however that isn't enforced in the NFS clients. And I don't think your legacy NAS supports NFSv4.
The client is the one built into Windows 10 (enabled as optionl feature). Anyone with a Windows10 machine can easily check for themselves.
The share itself is already provided by ReadyNAS, access it as follows:
\\<ipaddress-ofNAS>\c\<sharename-defined-on-NAS>
I am afraid that only ANSI and some far-eastern decoding option are available in that Windows10 NFS-client.
On the NAS "Unicode" is selected, thus everything is written to the NAS using Unicode and must be read that way by whatever device/application.
At this point I haven't found the solution yet.
I've just run in to exactly the same issue. Did you find a solution?
I don't think there is one (other than perhaps finding alternative NFS clients).
I solved the filenaming / code-page problem with the following operations on Windows 10:
- copy & verify ALL content from the NAS to some newly formated disk(s). Copyied folders and files using robocopy.
- delete ALL content on the NAS
- configure & access the NAS with the NFS-client
- copy & verify content back onto the NAS
That did it for me.
Tip: try with a few affected files first.
snahl wrote:
I solved the filenaming / code-page problem with the following operations on Windows 10:
- copy & verify ALL content from the NAS to some newly formated disk(s). Copyied folders and files using robocopy.
- delete ALL content on the NAS
If you know what files are affected, you could probably just rename them from an NFS mount, which would of course be much faster.
It'd be pretty simple to write a script to identify files on the SMB mount that can't be found on the NFS mount. Not so easy to figure out the corresponding NFS file name.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
