Hi Brian,

I just did an update on a system and it says.
Modify smb.conf to use WINS settings from DHCP?

The behavior does not implicate configuration, or if it does, it implicates configuration for exactly one domain name, and I have no idea how THAT happens. I think this behavior indicates something Windows-specific, since something is preventing my use of "NAS0.TCLC.org" and only prevents it on Windows machines. I am not prevented from any investigation of the domain name, meaning Windows knows about it and has a correct evaluation and willingly tells me whatever I want to know. I am prevented from using it: "net use n: \\NAS0.TCLC.org\d0" or "dir \\NAS0.TCLC.org\d0"

I can do everything I should be able to do if I use the IP address, 10.1.1.80, and not the domain name.
I can do everything I should be able to do if I use a different domain name, NASX.TCLC.org, with exactly the same IP address, 10.1.1.80.
I can do everything I should be able to do with the domain name, NAS0.TCLC.org, except reference that NAS with Windows.

PS H:\> dir \\10.1.1.80\d0 Directory: \\10.1.1.80\d0 Mode LastWriteTime Length Name ---- ------------- ------ ---- d----- 2023-01-16 23:30 Justice.TCLC.org
PS H:\> dir \\NASX.TCLC.org\d0 Directory: \\NASX.TCLC.org\d0 Mode LastWriteTime Length Name ---- ------------- ------ ---- d----- 2023-01-16 23:30 Justice.TCLC.org	PS C:\Windows\system32> nslookup nasx.tclc.org Server: aequitas.tclc.org Address: 10.1.1.11 Name: nasx.tclc.org Address: 10.1.1.80
PS H:\> dir \\NAS0.TCLC.org\d0 dir : Cannot find path '\\NAS0.TCLC.org\d0' because it does not exist.	PS C:\Windows\system32> nslookup nas0.tclc.org Server: aequitas.tclc.org Address: 10.1.1.11 Name: nas0.tclc.org Address: 10.1.1.80

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?