Hi Linus,
Did you say it all worked fine by ip address?
Windows PowerShell:
$ nslookup nasx.tclc.org -- works. Reports 10.1.1.80 $ nslookup nas0.tclc.org -- works. Reports 10.1.1.80
# mount //10.1.1.80/d0 /net/nas0/d0 -- works # mount //nasx.tclc.org/d0 /net/nas0/d0 -- works # mount //nas0.tclc.org/d0 /net/nas0/d0 -- works
dir \10.1.1.80\d0 -- works dir \nasx.tclc.org\d0 -- works dir \nas0.tclc.org\d0 -- fails
If I change nas0.tclc.org to a different IP, say 10.1.1.81, then dir \nas0.tclc.org\d0 still fails.
So, any inspection of nas0.tclc.org works everywhere, but any use of nas0.tclc.org fails only on Windows , regardless of the value. I no longer suspect a corruption, since I have purged and reinitialized all known sources and caches. This may be a collision, but that would require some rogue assignment that I haven't found. It may also be a permissions problem, but domain name level permissions is easily checked and I compared this name with nas1.tclc.org, which is not known to have problems. Ultimately, the culprit will have to be the NAS, since this all happened, coincidentally, after a system update. I have review all the settings for the NAS, and I have found nothing.
Thanks for the help,
Can't confirm anything but wow, finding a bug in windows, what are the odds?
On Tue, Jan 17, 2023 at 4:40 PM Chris Miller cjm@tryx.org wrote:
Hi Linus,
Did you say it all worked fine by ip address?
Windows PowerShell:
$ nslookup nasx.tclc.org -- works. Reports 10.1.1.80 $ nslookup nas0.tclc.org -- works. Reports 10.1.1.80
# mount //10.1.1.80/d0 /net/nas0/d0 -- works # mount //nasx.tclc.org/d0 /net/nas0/d0 -- works # mount //nas0.tclc.org/d0 /net/nas0/d0 -- works
dir \10.1.1.80\d0 -- works dir \nasx.tclc.org\d0 -- works
*> dir \nas0.tclc.org http://nas0.tclc.org\d0 -- fails*
If I change nas0.tclc.org to a different IP, say 10.1.1.81, then dir \ nas0.tclc.org\d0 still fails.
So, any inspection of nas0.tclc.org works everywhere, but any use of nas0.tclc.org fails *only on Windows*, regardless of the value. I no longer suspect a corruption, since I have purged and reinitialized all known sources and caches. This may be a collision, but that would require some rogue assignment that I haven't found. It may also be a permissions problem, but domain name level permissions is easily checked and I compared this name with nas1.tclc.org, which is not known to have problems. Ultimately, the culprit will have to be the NAS, since this all happened, coincidentally, after a system update. I have review all the settings for the NAS, and I have found nothing.
Thanks for the help,
Chris.
V:916.799.9461 F:916.974.0428
A: Because we read from top to bottom, left to right. Q: > Why should I start my reply below the quoted text?
Hi Linus,
Can't confirm anything but wow, finding a bug in windows, what are the odds?
This is very strange, but it doesn't smell like a bug or at least not like a Windows bug. I think it is more likely something about the NAS that is doing this, but I can't imagine what the mechanism might be. Yet. I'm hoping that these discussions might lead to something productive.
Thanks for the help,
Hi Folks,
First break through: I can create the problem! When I join the NAS to the domain, among other things he makes a DNS entry. There is something wrong with that entry! I don't know what, yet but I do know that I can add an entry, say "NASTY.TCLC.org = 10.1.1.80" and "dir \NASTY.TCLC.org\d0" works, until I name the NAS "NASTY" and join the domain. Then "dir \NASTY.TCLC.org\d0" no longer works.There seems to be no way to "rehabilitate" such a damaged domain name, but I'm sure there must be some cache that I am no purging.This is an "Active Directory" data storage DNS service, so there is probably some Active Directory cache that I need to find.
With a clear statement of the problem, I should be able to make progress.
Thanks for the help,
-
Chris Miller -
Linus Sphinx