Samba shares no longer visible after migration to systemd

Question

EDIT: Note the file server is CLI only.
I upgraded my file server to systemd about a week ago and have yet to get the Samba share visible from other devices within my network.  Eveything worked fine under initscripts and other than system upgrades the only thing that has changed about the system is the migration to systemd and addition of the netcfg package.  I can connect manually by typing "smb://<IP>" in a file manager address field but when trying to access the Share via browsing on two different WD media players, a Xoom tablet, typing "smb://" in the address bar of a basic file manager like Thunar or PCManFM or using browsing the Network or Samba Shares links in the Network place from Dolphin the share just doesn't show up.
The fact that I can access the Share directly, it's just not visible when browsing, makes me think samba is working properly but I'm not sure how to further diagnose the issue and I'd really like to solve the problem and learn something rather than just load up a previous image of the PC before the systemd migration.
Commands from client
my /etc/hosts...
cat /etc/hosts
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost dads-pc
192.168.10.131 dads-pc.HOMESERVER dads-pc
192.168.10.100 Serverbox.HOMESERVER Serverbox
Master Browser search, this does look odd, I don't use it on any machine so where the heck did the .255 at the end of the IP address come from? 
$ nmblookup -M HOMESERVER
querying HOMESERVER on 192.168.10.255
name_query failed to find name HOMESERVER#1d
I can sign in fine...
$ smbclient -L Serverbox
Enter dad's password:
Failed to load upcase.dat, will use lame ASCII-only case sensitivity rules
Failed to load lowcase.dat, will use lame ASCII-only case sensitivity rules
Domain=[HOMESERVER] OS=[Unix] Server=[Samba 3.6.9]
Sharename Type Comment
IPC$ IPC IPC Service (Samba Server)
Server Disk The Family Network Share Files
ParentalMovies Disk Movie folders for Mom and Dad
Movies Disk Family Movie folders
Domain=[HOMESERVER] OS=[Unix] Server=[Samba 3.6.9]
Server Comment
SERVERBOX Samba Server
Workgroup Master
HOMESERVER SERVERBOX
I can sign in as one of the media players fine...
$ smbclient -L Serverbox -U lr_mediaplayer
Enter lr_mediaplayer's password:
Failed to load upcase.dat, will use lame ASCII-only case sensitivity rules
Failed to load lowcase.dat, will use lame ASCII-only case sensitivity rules
Domain=[HOMESERVER] OS=[Unix] Server=[Samba 3.6.9]
Sharename Type Comment
IPC$ IPC IPC Service (Samba Server)
Server Disk The Family Network Share Files
ParentalMovies Disk Movie folders for Mom and Dad
Movies Disk Family Movie folders
Domain=[HOMESERVER] OS=[Unix] Server=[Samba 3.6.9]
Server Comment
SERVERBOX Samba Server
Workgroup Master
HOMESERVER SERVERBOX
Commands from Server
Both smbd and nmbd services appear functional...
$ systemctl status smbd nmbd
smbd.service - Samba SMB/CIFS server
Loaded: loaded (/etc/systemd/system/smbd.service; enabled)
Active: active (running) since Mon, 2012-11-19 17:48:07 CST; 2h 9min ago
Main PID: 534 (smbd)
CGroup: name=systemd:/system/smbd.service
├ 534 /usr/sbin/smbd -F
├ 551 /usr/sbin/smbd -F
└ 559 /usr/sbin/smbd -F
nmbd.service - Samba NetBIOS name server
Loaded: loaded (/etc/systemd/system/nmbd.service; enabled)
Active: active (running) since Mon, 2012-11-19 17:48:07 CST; 2h 9min ago
Main PID: 536 (nmbd)
CGroup: name=systemd:/system/nmbd.service
└ 536 /usr/sbin/nmbd -F
The global portion of my /etc/samba/smb.conf file...
[global]
workgroup = HOMESERVER
server string = Samba Server
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = No
valid users = dad, lisa, administrator,lr_mediaplayer, xoom, br_mediaplayer
read list = dad, lisa, administrator, lr_mediaplayer, xoom, br_mediaplayer
write list = dad, lisa, administrator
load printers = no
write cache size = 262144
large readwrite = yes
# These next lines have been added after systemd conversion based on web research, none of which has helped.
log level = 10
name resolve order = host bcast lmhosts wins
interfaces = eth0 192.168.10.100/19
preferred master = yes
Testing of the /etc/samba/smb.conf file, no errors ...
$ testparm smb.conf
Load smb config files from smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[Movies]"
Processing section "[ParentalMovies]"
Processing section "[Server]"
Loaded services file OK.
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
Server role: ROLE_STANDALONE
My network config file for [email protected]...
$ cat /etc/network.d/eth0
CONNECTION='ethernet'
DESCRIPTION='A basic static ethernet connection using iproute'
INTERFACE='eth0'
IP='static'
ADDR='192.168.10.100'
#ROUTES=('192.168.0.0/24 via 192.168.1.2')
GATEWAY='192.168.10.1'
DNS=('76.85.229.110' '76.85.229.111')
Master Browser search and again with the rogue .255 ending for the IP address being broadcast.
$ nmblookup -M HOMESERVER
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
doing parameter name resolve order = host bcast lmhosts wins
doing parameter log file = /var/log/samba/%m.log
doing parameter max log size = 50
doing parameter dns proxy = No
doing parameter valid users = dad, lisa, administrator,lr_mediaplayer, xoom, br_mediaplayer
doing parameter read list = dad, lisa, administrator, lr_mediaplayer, xoom, br_mediaplayer
doing parameter write list = dad, lisa, administrator
doing parameter load printers = no
doing parameter write cache size = 262144
doing parameter large readwrite = yes
doing parameter preferred master = yes
pm_process() returned Yes
lp_servicenumber: couldn't find homes
set_server_role: role = ROLE_STANDALONE
Substituting charset 'UTF-8' for LOCALE
added interface eth0 ip=fe80::3285:a9ff:fe8e:90f7%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=192.168.10.100 bcast=192.168.10.255 netmask=255.255.255.0
bind succeeded on port 0
Socket options:
SO_KEEPALIVE = 0
SO_REUSEADDR = 1
SO_BROADCAST = 1
Could not test socket option TCP_NODELAY.
Could not test socket option TCP_KEEPCNT.
Could not test socket option TCP_KEEPIDLE.
Could not test socket option TCP_KEEPINTVL.
IPTOS_LOWDELAY = 0
IPTOS_THROUGHPUT = 0
SO_SNDBUF = 212992
SO_RCVBUF = 212992
SO_SNDLOWAT = 1
SO_RCVLOWAT = 1
SO_SNDTIMEO = 0
SO_RCVTIMEO = 0
Could not test socket option TCP_QUICKACK.
Socket opened.
lang_tdb_init: /usr/lib/samba/en_US.UTF-8.msg: No such file or directory
querying HOMESERVER on 192.168.10.255
bind succeeded on port 0
Socket options:
SO_KEEPALIVE = 0
SO_REUSEADDR = 1
SO_BROADCAST = 1
Could not test socket option TCP_NODELAY.
Could not test socket option TCP_KEEPCNT.
Could not test socket option TCP_KEEPIDLE.
Could not test socket option TCP_KEEPINTVL.
IPTOS_LOWDELAY = 0
IPTOS_THROUGHPUT = 0
SO_SNDBUF = 212992
SO_RCVBUF = 212992
SO_SNDLOWAT = 1
SO_RCVLOWAT = 1
SO_SNDTIMEO = 0
SO_RCVTIMEO = 0
Could not test socket option TCP_QUICKACK.
parse_nmb: packet id = 9235
nmb packet from 192.168.10.100(35072) header: id=9235 opcode=Query(0) response=Yes
header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes
header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
answers: nmb_name=HOMESERVER<1d> rr_type=32 rr_class=1 ttl=259200
answers 0 char .....d hex 0000C0A80A64
Got a positive name query response from 192.168.10.100 ( 192.168.10.100 )
192.168.10.100 HOMESERVER<1d>
Thank you.
Last edited by imatechguy (2012-11-20 03:16:39)

Answer 1

ChojinDSL wrote:Do you have a firewall running on that server?
Are your clients also using systemd?
Yes I do have a firewall, iptables, and it's the same configuration from before the migration to systemd.  Also note that I can access the shares when explicitly defining the path whether that's in a File Manager, cli or other so access isn't being blocked.  For lack of a better explanation the whole thing gives the appearance that although the Share is active it's just not broadcasting it's existence like it should be.
I have two PC's, both Arch, one with Openbox and one running KDE that I have migrated to systemd.  Both can access the Share when the path is explicitly defined but don't see it when trying to just browse for the the Share.  I have a Xoom tablet, running Android Jelly Bean, that exhibits the same behavior.  I also have two media players, one an older WD LiveTV Plus model the other a newer WD LiveTV model, neither of which can see the share and browsing is the only option for those devices.  So I've got a pretty good assortment of devices and operating systems that could see the share when browsing previously but can not see the same share by browsing since the migration to systemd on the file server.
Thank you.