Page 1 of 1
NetBIOS name & mdsnsresponder.conf (bug?)
Posted: 14 Dec 2015 21:38
by sfranzis
Hi *,
CIFS/SMB registers his service only with the hostname in the file mdnsresponder.conf.
Example
Hostname: nas4free
NetBIOS name on config page CIFS/SMB: nas4freeSMB
Entry in mdnsresponder.conf:
nas4free
_smb._tcp. local.
445
I think this should be:
nas4freeSMB
_smb._tcp. local.
445
Stefan
Re: NetBIOS name & mdsnsresponder.conf (bug?)
Posted: 15 Dec 2015 18:49
by daoyama
sfranzis wrote:
CIFS/SMB registers his service only with the hostname in the file mdnsresponder.conf.
This is DNS name, not NetBIOS name.
Re: NetBIOS name & mdsnsresponder.conf (bug?)
Posted: 16 Dec 2015 17:17
by sfranzis
Hello Daoyama,
daoyama wrote:
This is DNS name, not NetBIOS name.
why then do you use the /afp/afpname in mdnsresponder.conf in case of AFP?
I changed mdnsresponder on my nas to use the NetBIOS name for SMB and with this I can work around a very nasty issue in OS-X el Capitan:
viewtopic.php?f=26&t=9674
My change in /etc/rc.d/mdnsresponder is:
Code: Select all
-i "count(//samba/enable) > 0" \
- -v "//system/hostname" -n \
+ -v "//samba/netbiosname" -n \
-o "_smb._tcp. ${_domain}" -n \
-o "445" -n \
-n \
You can still use the dns name in your CIFS configuration, but you are free to choose another one.
If you need more details feel free to ask
Stefan
Re: NetBIOS name & mdsnsresponder.conf (bug?)
Posted: 19 Jan 2016 07:03
by Chucko
I have run across this too. I would prefer to see the NetBIOS name advertised.