Referring back to this early report of mine.
I’m again seeing the issue I reported there that I can only connect to the file shares by using an IP address, not by a host name or FQDN. Using a host name or FQDN, I always get this without any opportunity to enter a user/passwd:
Windows is obviously seeing the shares:
And I also confirmed that the server is reachable by name:
The last time it resolved itself when I rebuilt my NS8, but unfortunately that isn’t an option now.
Cheers.
Hi,
what is the “netbios name” in your /home/samba1/.local/share/containers/storage/volumes/config/_data/smb.conf ?
Is it ns8? or different like nsdc-… (which was in NS7)?
Yes, this was a migrated NS7 → NS8 setup:
Cheers.
Try connect with \\NSDC-NETHSERVER\ShareIt
Is it working? It would by useful info on Domain configuration panel at schema info.
For developers: could this possibly be modified somehow like the ip address?
Yes, that did work, but only because of this, otherwise I wouldn’t have a DNS entry to relate the name to IP.
Cheers.
Ciao a tutti,
yes, we recently received this request from Nethesis Support team and drafted this project card.
In the meantime, continue to access the shares using the DC host name or IP address, because the NS8 short host name or its FQDN doesn’t work.
Obviously, the client DNS must resolve the DC host name to the IP address: either use Samba DC as the DNS server or configure the DNS server to forward requests for the AD domain to the Samba DC.
Thanks for the info! The “netbios alias” setting works in the include.conf file. I tried it before, but I set the old NS7 hostname (“S0”), which gave secrets.keytab errors in the samba module log. I just deleted the old NS7 computer in RSAT from the computers and restarted the samba service on NS8 (it’s netbios name is “NSDC-S0”).
This way, I can finally connect the shared folders with the old server name, e.g.: \\S0\workdir