Linux – Unable to connect to a Linux Samba server via hostname on Windows 10

dnslinuxnetworkingsambawindows 10

I have setup a Samba server running on CentOS. I am able to connect to it when typing \\ip-address\share into the address bar of Windows Explorer but it doesn't appear in the network list and if I try to connect to it using the hostname it tells me Windows cannot access \\hostname\share.

I also cannot ping the hostname but can ping the IP. I can ping the hostname from the CentOS

The Samba server has DHCP enabled (using NetworkManager) and the hostname is configured on the router via a static IP rule. hostname is also set via hostnamectl.

I have winbind is enabled and running, but have no idea if it is configured properly.

Firewall-cmd is active and running, and it has samba services open in the public zone.

I have updated seLinux with sudo setsebool -P samba_enable_home_dirs on

Here is a partial dump of the smb.conf file;

[global]
    workgroup = WORKGROUP
    netbios name = *hidden*
    wins support = Yes
    encrypt passwords = true
    security = user

    passdb backend = tdbsam

    printing = cups
    printcap name = cups
    load printers = yes
    cups options = raw

[homes]
    comment = Home Directories
    valid users = %S, %D%w%S
    browseable = Yes
    read only = No
    inherit acls = Yes

[printers]
    comment = All Printers
    path = /var/tmp
    printable = Yes
    create mask = 0600
    browseable = Yes

[print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers
    write list = @printadmin root
    force group = @printadmin
    create mask = 0664
    directory mask = 0775

How do I make it so windows is able to access the share via hostname?

EDIT: adding nmcli dump

connection.id:                          MyEth
connection.uuid:                        4b4c8ef6-def8-3c7f-9c1c-e3bdd39d2ed4
connection.stable-id:                   --
connection.type:                        802-3-ethernet
connection.interface-name:              --
connection.autoconnect:                 yes
connection.autoconnect-priority:        -999
connection.autoconnect-retries:         -1 (default)
connection.auth-retries:                -1
connection.timestamp:                   1565104013
connection.read-only:                   no
connection.permissions:                 --
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.autoconnect-slaves:          -1 (default)
connection.secondaries:                 --
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        default
connection.mdns:                        -1 (default)
-------------------------------------------------------------------------------
802-3-ethernet.port:                    --
802-3-ethernet.speed:                   0
802-3-ethernet.duplex:                  --
802-3-ethernet.auto-negotiate:          no
802-3-ethernet.mac-address:             B8:27:EB:FF:F8:7D
802-3-ethernet.cloned-mac-address:      --
802-3-ethernet.generate-mac-address-mask:--
802-3-ethernet.mac-address-blacklist:   --
802-3-ethernet.mtu:                     auto
802-3-ethernet.s390-subchannels:        --
802-3-ethernet.s390-nettype:            --
802-3-ethernet.s390-options:            --
802-3-ethernet.wake-on-lan:             default
802-3-ethernet.wake-on-lan-password:    --
-------------------------------------------------------------------------------
ipv4.method:                            auto
ipv4.dns:                               --
ipv4.dns-search:                        --
ipv4.dns-options:                       ""
ipv4.dns-priority:                      0
ipv4.addresses:                         --
ipv4.gateway:                           --
ipv4.routes:                            --
ipv4.route-metric:                      -1
ipv4.route-table:                       0 (unspec)
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-timeout:                      0 (default)
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.dhcp-fqdn:                         --
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv4.dad-timeout:                       -1 (default)
-------------------------------------------------------------------------------
ipv6.method:                            auto
ipv6.dns:                               --
ipv6.dns-search:                        --
ipv6.dns-options:                       ""
ipv6.dns-priority:                      0
ipv6.addresses:                         --
ipv6.gateway:                           --
ipv6.routes:                            --
ipv6.route-metric:                      -1
ipv6.route-table:                       0 (unspec)
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.ip6-privacy:                       -1 (unknown)
ipv6.addr-gen-mode:                     stable-privacy
ipv6.dhcp-duid:                         --
ipv6.dhcp-send-hostname:                yes
ipv6.dhcp-hostname:                     --
ipv6.token:                             --
-------------------------------------------------------------------------------
proxy.method:                           none
proxy.browser-only:                     no
proxy.pac-url:                          --
proxy.pac-script:                       --
-------------------------------------------------------------------------------

firewall config:

public (active)
  target: default
  icmp-block-inversion: no
  interfaces: eth0
  sources:
  services: ssh dhcpv6-client http samba https
  ports: 22/tcp
  protocols:
  masquerade: no
  forward-ports:
  source-ports:
  icmp-blocks:
  rich rules:

Best Answer

Your issue is local DNS related and breaks down in the following way:

A more in-depth discussion in the FreeNAS Forum thread: SMB shares not showing in network browsing
1. Local Domain must be set in the Router and echoed across all LAN devices (#23)
  - In Windows, this would be the WorkGroup name
2. Static IP and Hostname must be set in the Router for the Samba Server (#30)
3. Windows' hosts file must have an entry in it for the Samba Server (#27)
  - Format (see #6 below): IP Hostname Hostname.LocalDomain
4. Traffic must be allowed on the correct TCP & UDP ports (#27)

To Resolve:

Ensure the Windows device, Samba Server, and Router serving local DNS are set to the same Local Domain
1. Router: Local Domain will be the name set under Domain in its WebAdmin UI
2. Samba Server: Will depend on the OS
3. Windows: Local Domain is the Workgroup name:
  1. Control Panel\All Control Panel Items\System > Computer name, domain, and workgroup settings
  2. Change settings > Change... > Workgroup > OK
    - Depending on the OS configuration, it may need to be rebooted
Ensure traffic between Windows and the Samba Server is allowed on the following ports:
1. TCP: 139, 445
2. UDP: 137, 138, 139
Ensure Samba Server has been assigned a static IP on the Router
```
  IP      '192.168.1.2'
  mac     'AA:BB:CC:DD:EE:FF'
  name    'Server'
```
- Without a static IP, which is where you set the client hostname & client MAC, configured in your Router, the Router has no idea on how to route traffic to the local DNS hostname.
- Reboot Router once changed to allow for new DHCP pull by Server
Windows 10 v1709 or greater, ensure SMB Direct is enabled and SMB v1.0 is disabled
1. Control Panel\Programs\Programs and Features > Turn Windows features on or off
2. Uncheck: SMB 1.0/CIFS File Sharing Support
  - SMB 1.0 is not secure and has been actively exploited for >2yrs on devices with SMB v1.0 enabled
  - There is no reason to utilize SMB1, as all devices support at least SMB2
3. Check: SMB Direct
4. OK (Follow on-screen instructions and Reboot)
Ensure Samba Server's smb.conf contains the following:
```
[global]
    server min protocol  = SMB2
    server max protocol  = SMB3_11
    netbios name         = <Samba Server Hostname>
    workgroup            = <Local Domain>
```
- Ensure workgroup Local Domain matches what was set in 1.3.2 (above)
- Ensure server max protocol is the max of what your Samba Server build supports
- Restart Samba to apply changes

Add Samba Server to Windows' hosts file

C:\Windows\System32\drivers\etc\hosts

#

         ##::[[---  Windows Host Config  ---]]::##

#===========================================================
                    ##----- LAN -----##
#===========================================================

  # OpenWrt:
    192.168.1.1        OpenWrt   OpenWrt.Wrt
    192.168.1.2        Server    Server.Wrt
    192.168.1.3        Win10     Win10.Wrt

1st Column: Static IP of host
2nd Column: Hostname of host
3rd Column: Hostname and Local Domain address, where Wrt is the Local Domain

Open This PC, navigating to the share in the Address Bar: \\ServerHostname\ShareName

Troubleshooting:

If this does not resolve your issue:

Power-off the Windows device, Samba Server, and Router
- Simplest way to ensure DHCP is cleared
Power-on Router and wait for it to fully boot up (if OEM firmware: wait 120s || all others: 60s)
Power-on Samba Server and Windows device

Please post a comment if this doesn't work, allowing the answer to be tweaked, or added to, ensuring it works for all with this issue.

Best Answer

To Resolve:

Troubleshooting:

Related Solutions

Resetting gone wrong

Related Question