Greetings, Sketch!>>>> workgroup = INTERNAL >>>> realm = EXAMPLE.COM >>>> netbios name = SAMBA >> >>> Looks that way to me. Your realm should include the workgroup name: >>> INTERNAL.EXAMPLE.COM. >> >> Nothing is "SHOULD" as long as the settings follow basic requirements >> (single-label NETBIOS domain name, resolvable REALM name). >> I.e. I have domains provisioned with "ADS.<netbios domain name>.<tld>" >> All works fine, given correct DNS configuration.> Netbios name is basically irrelevant here.NETBIOS HOST name? Irrelevant. NETBIOS DOMAIN name? Not quite.> Do you mean that the realm > name does not have to match the workgroup name?There's no such requirement. AD domain is resolved from NETBIOS multicast or from domain suffix provided by DHCP or configured in system settings. But the end result is that the system receive correct DNS name once and then work out from that purely through DNS. I can show you examples of systems working from both premises in the same domain. P.S. Please don't CC me, I'm subscribed to the list. -- With best regards, Andrey Repin Wednesday, April 29, 2015 23:04:06 Sorry for my terrible english...
On Wed, 29 Apr 2015, Andrey Repin wrote:>> Netbios name is basically irrelevant here. > > NETBIOS HOST name? Irrelevant. NETBIOS DOMAIN name? Not quite. > >> Do you mean that the realm >> name does not have to match the workgroup name? > > There's no such requirement. AD domain is resolved from NETBIOS multicast or > from domain suffix provided by DHCP or configured in system settings. > But the end result is that the system receive correct DNS name once and then > work out from that purely through DNS.Makes sense. I know the netbios name should only matter for older clients, but I thought Samba still cared about it. I guess the DC shouldn't, though, since it's a modern DC.
Andrey, thanks for your help. It's discouraging getting stuck on these fundamentals, not making progress. Can you tell me how I would provision the following: hostnamectl status reports: Static hostname: a10 The registered FQDN is: mwllc.info I'd like to name the domain on the samba server: conpago.mwllc.info The static IP on the CentOS Samba box is set to: 10.10.1.225. Using INTERNAL_DNS setting and dns forwarder is set to my ISP's nameserver: 75.75.76.76 What's the correct provisioning parameters? Thank you for your patience. Mike
Greetings, Sketch!>>> Netbios name is basically irrelevant here. >> >> NETBIOS HOST name? Irrelevant. NETBIOS DOMAIN name? Not quite. >> >>> Do you mean that the realm >>> name does not have to match the workgroup name? >> >> There's no such requirement. AD domain is resolved from NETBIOS multicast or >> from domain suffix provided by DHCP or configured in system settings. >> But the end result is that the system receive correct DNS name once and then >> work out from that purely through DNS.> Makes sense. I know the netbios name should only matter for older > clients, but I thought Samba still cared about it.It do care, but not in the sense that you thought. The NETBIOS domain name is important, but there's no strings attached, other than technical restrictions to the name length and composition.> I guess the DC shouldn't, though, since it's a modern DC.That's largely true. DC's work over DNS from the start. -- With best regards, Andrey Repin Wednesday, April 29, 2015 23:36:37 Sorry for my terrible english...