Hi Folks,
O.M.G.! I have spent all afternoon trying to diagnose a DNS problem that presents like
corruption but I can't find any trace, beyond the failure that I think is the result.
This is a Windows Server problem...
I have a domain name for my NAS -- "\\NAS0.TCLC.org = 10.1.1.80", and all
evaluations show me that translation. I can ping it; I can nslookup; I can run the DNS
management application. My linux machines can "mount //NAS0.TCLC.ORG/d0 /net/nas0/d0
..." All work exactly as you'd expect. Then I try to view the share with the
Windows File Explorer -- "Windows can't find the DNS name"!! In that case I
can use the IP address directly or the alternate domain name, so it is the domain name on
the windows machines that is the problem, not the disk access protocol. I also created a
second domain name "\\NASX.TCLC.org = 10.1.1.80" and that one work just fine
everywhere!
Here I tried the command prompt:
C:\Windows\system32>net use n: \\10.1.1.80\d0
The command completed successfully.
C:\Windows\system32>net use n: /delete
n: was deleted successfully.
C:\Windows\system32>net use n: \\NASX.TCLC.org\d0
The command completed successfully.
C:\Windows\system32>net use n: /delete
n: was deleted successfully.
C:\Windows\system32>net use n: \\NAS0.TCLC.org\d0
System error 64 has occurred.
The specified network name is no longer available.
Of course I have flushed all caches I can find, scavenged resources records, rebooted
every element -- Windows DNS server, Windows Server 2012r2, NAS, Client, ... the toaster
and the microwave!
So, I have a domain name that shows zero problems in any investigation, until I try to use
it for its intended purpose on the windows machines , and I have another one that is
nearly identical that has no problems!
Any thoughts?
Thanks for the help,
--
Chris.
V:916.799.9461
F:916.974.0428