1st and most important I have searched on this topic and found nothing that works so far -- I am using the latest Unraid 6 -- I can connect to it via. IP but NOT HOSTNAME from several Windows 10 clients -- I have included my ifconfig from the NAS (unraid) as well as the IP config in Unraid's Web Inteface. I can ping an example Windows 10 workstation from my Unraid telnet session via HOSTNAME of said workstation or IP but  not the other way around (Windows Ping -> Unraid only works via. IP). Appreciate any assistance with this -- it was working fine initially and stopped for no reason that I am aware of.

 

IP: 192.168.1.25

Netmask: 255.255.255.0

Gateway: 192.168.1.1

DNS: 192.168.1.1

 

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 172.17.42.1  netmask 255.255.0.0  broadcast 0.0.0.0

        ether 56:84:7a:fe:97:99  txqueuelen 0  (Ethernet)

        RX packets 24753  bytes 5346443 (5.0 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 27701  bytes 24062961 (22.9 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.1.25  netmask 255.255.255.0  broadcast 192.168.1.255

        ether c8:1f:66:36:84:58  txqueuelen 1000  (Ethernet)

        RX packets 1113366  bytes 100086575 (95.4 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 2972283  bytes 4405812921 (4.1 GiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        loop  txqueuelen 0  (Local Loopback)

        RX packets 90901  bytes 31499373 (30.0 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 90901  bytes 31499373 (30.0 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

veth00803a8: flags=67<UP,BROADCAST,RUNNING>  mtu 1500

        ether fa:a0:da:33:83:91  txqueuelen 0  (Ethernet)

        RX packets 16325  bytes 4538160 (4.3 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 17846  bytes 3752954 (3.5 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

veth4bbac25: flags=67<UP,BROADCAST,RUNNING>  mtu 1500

        ether 6a:af:96:f0:30:2a  txqueuelen 0  (Ethernet)

        RX packets 7239  bytes 1011426 (987.7 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 10234  bytes 20040261 (19.1 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

veth78ea08f: flags=67<UP,BROADCAST,RUNNING>  mtu 1500

        ether 6e:c3:70:e7:7f:7e  txqueuelen 0  (Ethernet)

        RX packets 1189  bytes 143399 (140.0 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 2789  bytes 535572 (523.0 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

vethcc60bff: flags=67<UP,BROADCAST,RUNNING>  mtu 1500

        ether d6:a3:6d:01:37:85  txqueuelen 0  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 1604  bytes 136749 (133.5 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

root@topaz:~#

 

Telnet into the server and post the output of the following command:

 

cat /boot/config/ident.cfg

NAME="topaz"

COMMENT="NAS"

SECURITY="user"

WORKGROUP="WORKGROUP"

DOMAIN=""

DOMAIN_SHORT=""

localMaster="yes"

DOMAIN_LOGIN="Administrator"

DOMAIN_PASSWD=""

timeZone="America/New_York"

USE_NTP="yes"

NTP_SERVER1="pool.ntp.org"

NTP_SERVER2=""

NTP_SERVER3=""

SYS_MODEL="Custom"

SYS_ARRAY_SLOTS="24"

SYS_CACHE_SLOTS="1"

 

NAME="topaz"

.....

 

The host name is topaz.  Is that what you are using?

 

Second thing is that Windows Netbios DNS is not the most reliable scheme in existence.  Its basic implantation goes back to Windows 3.1 (Windows for Workgroups) when we were using 386 CPU's and network speed could be under 1mb/s. 

 

The problem is usually the polling time to elect the Local Master and to propagate that information across the Samba network.  The best thing is to select one server to always serve as the Local Master.  If your unRAID server is on 24-7, it is the best choice to have as the Local Master.  First thing to do that is to go to 'Settings', 'SMB', 'Workgroup settings' and set 'Local Master' to 'yes'.  Then turn off every other computer (including any media servers that might be using SMB) on the network for a few minutes EXCEPT your server that you want to be the Local Master.  Restart the other computers and go out to Starbucks for a cup of coffee.  (Time between Polling in Windows was originally ten minutes!  It does not seem to have change since those days.)