NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
garyd9
Jun 24, 2016Virtuoso
BUG: domain names - upper vs lower case
OS 6.5.0/6.5.1 (and many earlier versions) (NOTE: I'm currently dealing with netgear on a completely different problem which is preventing me from rebooting my NAS or doing anything that would c...
garyd9
Aug 09, 2016Virtuoso
...another issue completely ignored by netgear. :(
- mdgm-ntgrAug 10, 2016NETGEAR Employee Retired
I have just asked engineering about this.
Do you have any steps to reliably reproduce this problem?- garyd9Aug 10, 2016Virtuoso
Reliably, 100% of the time? No. about 20% of the time after a reboot of the NAS I see it. The simple solution would be for netgear to just force any domain name to upper case (as Windows/SMB is case insensitive.) Obviously, that's a samba issue, but I'm pretty sure that netgear makes modifications to the base samba distro for the readynas products.
- garyd9Aug 10, 2016Virtuoso
mdgm-ntgr, is there an image of 6.5.x that I can run in a hyper-v VM floating around somewhere to test different cases of this?
My reason for asking is that I have a test domain running in a vlan that use slightly different configuration that might help to shed more light on the issue.
For example, my primary domain (as shown above) has a netbios name of "mydomain" and a FQDN of "mydomain.local", but I also have a test domain in a vlan that has a netbios name of "MYDOMAIN" and FQDN of "mydomain.local" (the only difference being that the netbios name is in all caps.)
From a windows point of view, these two are identical. However, based on my findings shown in the first two posts in this thread, it's possible that the second domain (with an all uppercase netbios name) would have a different result. In particular, it might hide the problem (because the netbios domain name would always be upper case, instead of sometimes coming back as upper and sometimes as lower case.) Based on what I've experienced, I'd be able to tell the different based on the output of "wbinfo" and if the "native" field returns true or false.
(No, I can't rebuild my domain to work around the issue, but if I can help to isolate it, then it might help netgear to either fix or work around the issue.)
- SkywalkerAug 10, 2016NETGEAR Expert
Strange, that's not supposed to happen. The %D subsitution code does forcibly uppercase the domain name, and lowercase the username; thus the home directory should always be /home/DOMAIN/user. So there must be somewhere in the code that somehow bypasses that substitution. On the machine that returns the lowercase domain, can you run `getent passwd $user` and check the home directory that gets returned?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!