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 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.
7 Replies
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?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
