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
Jun 24, 2016Virtuoso
Perhaps related (and hopefully helps netgear resolve this issue)... (I have two NAS devices running right now. Both are joined to the AD. One has the ALL UPPERCASE DOMAIN NAME in the home path (nas516) and one has the domain in all lower case (NasPro.) BOTH devices are configured identically on the authentication page of frontview. Yesterday, both devices were using all lowercase domain names in the home paths. Today, Nas516 switched to all uppercase domain names in the paths.
I've run a few samba commands on both devices to try and see what might be different:
NasPro (working properly)
root@NasPro:/etc/frontview/samba# wbinfo -D mydomain Name : mydomain Alt_Name : mydomain.local SID : <removed> Active Directory : Yes Native : Yes Primary : Yes
Nas516 (switch to uppercase today)
root@Nas516:/etc/samba# wbinfo -D mydomain Name : MYDOMAIN Alt_Name : MYDOMAIN.LOCAL SID : <removed> Active Directory : Yes Native : No Primary : Yes
What's different: Obvously, nas516 is showing my domain name in all upper case, while NasPro is showing in all lower case. The SID's appeared identical (and didn't seem interesting to me anyway.) What I'm not quite understanding is the "Native" field. On NasPro it's "yes" and on Nas516 it's "no". Could that "native" field be related to the domain name case issue?
So, just for giggles, I removed the nas516 machine from the domain (changed Authentication->access type from "active directory" to "local users") and saved. Waited a minute or 5, and then changed it back to "active directory" (typing in my pw again.) Suddenly, on nas516, garyd9's home directory is again referencing "/data/home/mydomain/garyd9" again. As well, "wbinfo -D mydomain" output looks exactly like the output seen on the naspro (lowercase domain names and native is "yes.")
So, that partially answers why the domain name is coming up in all upper case in some situations. The next question becomes: Why would samba NOT connect in native mode some of the time (but not all the time)?
Another question (directed towards netgear) is: Can you change the readynas firmware somehow to detect if "native mode" didn't happen, and somehow retry the samba negotiation?
(I'm sure I'll keep replying to myself as I find more information. It'd be REALLY nice if netgear's samba/AD SME could also jump in and offer some feedback...)
- garyd9Jun 26, 2016Virtuoso
Another problem that this bug seems to cause: home directory snapshots aren't taken (or are taken from the wrong place.) So, instead of taking a snapshot of /data/home/mydomain/garyd9, it's taking a snapshot of /data/home/MYDOMAIN/garyd9.
This is becoming a silly mess...
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!