I recently added a second samba server to my network running FreeBSD (Local IP address is 172.16.0.41). The first server runs openSUSE (Local IP address is 172.16.0.3) and worked perfectly before adding the second one. When I added the FreeBSD server, I noticed I could no longer access my shares on the openSUSE server. Due to this, I chose to restart the samba process with systemctl restart smb nmb. When this did not fix the issue, I ran the command systemctl status smb nmb and got this output:
● smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2018-06-17 15:13:16 EDT; 6ms ago
Process: 31184 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
Main PID: 31373 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smb.service
├─31373 /usr/sbin/smbd -D
├─31375 /usr/sbin/smbd -D
├─31376 /usr/sbin/smbd -D
├─31377 /usr/sbin/smbd -D
└─31380 /usr/sbin/smbd -D
Jun 17 15:13:16 linux-3kds systemd[1]: Starting Samba SMB Daemon...
Jun 17 15:13:16 linux-3kds systemd[1]: smb.service: Supervising process 31373 which is not our child. We'll most likely not notice when it exits.
Jun 17 15:13:16 linux-3kds smbd[31373]: [2018/06/17 15:13:16.387676, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Jun 17 15:13:16 linux-3kds smbd[31373]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
● nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2018-06-17 15:13:16 EDT; 292ms ago
Main PID: 31153 (nmbd)
Status: "nmbd: ready to serve connections..."
Tasks: 2 (limit: 4915)
CGroup: /system.slice/nmb.service
├─31153 /usr/sbin/nmbd -D
└─31154 /usr/sbin/nmbd -D
Jun 17 15:13:15 linux-3kds systemd[1]: Starting Samba NMB Daemon...
Jun 17 15:13:15 linux-3kds systemd[1]: nmb.service: Supervising process 31153 which is not our child. We'll most likely not notice when it exits.
Jun 17 15:13:15 linux-3kds nmbd[31153]: [2018/06/17 15:13:15.799420, 0] ../source3/nmbd/asyncdns.c:158(start_async_dns)
Jun 17 15:13:15 linux-3kds nmbd[31153]: started asyncdns process 31154
Jun 17 15:13:16 linux-3kds nmbd[31153]: [2018/06/17 15:13:16.110985, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Jun 17 15:13:16 linux-3kds nmbd[31153]: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
Jun 17 15:13:16 linux-3kds systemd[1]: Started Samba NMB Daemon.
Jun 17 15:13:16 linux-3kds nmbd[31153]: [2018/06/17 15:13:16.122964, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Jun 17 15:13:16 linux-3kds nmbd[31153]: query_name_response: Multiple (2) responses received for a query on subnet 172.16.0.3 for name WORKGROUP<1d>.
Jun 17 15:13:16 linux-3kds nmbd[31153]: This response was from IP 172.16.0.41, reporting an IP address of 172.16.0.41.
I do not understand the reason for this and I would like to fix the problem. Both servers have different host names and they have different NICs. I am also able to access the shares on the FreeBSD server.
Here is the smb.conf on the openSUSE server:
# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
[global]
workgroup = WORKGROUP
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
usershare allow guests = No
wins support = Yes
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
## Share disabled by YaST
# [groups]
# comment = All groups
# path = /home/groups
# read only = No
# inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775
[Backup]
comment = Backup Disk
guest ok = Yes
inherit acls = Yes
path = /Data/Backup
read only = No
vfs objects =
[Seagate 4TiB Raid]
comment = Raid Array of 4 TiB Seagate Drives
inherit acls = Yes
path = /Data/seagate4tb_raid
read only = No
vfs objects =
Here is the smb4.conf on the FreeBSD server:
[global]
workgroup = WORKGROUP
server string = Samba Server Version %v
wins support = Yes
security = user
passdb backend = tdbsam
map to guest = Bad User
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[Public]
comment = Public Directory
inherit acls = Yes
path = /Network/Public
read only = No
guest ok = Yes
How could I fix this issue?
● smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2018-06-17 15:13:16 EDT; 6ms ago
Process: 31184 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
Main PID: 31373 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smb.service
├─31373 /usr/sbin/smbd -D
├─31375 /usr/sbin/smbd -D
├─31376 /usr/sbin/smbd -D
├─31377 /usr/sbin/smbd -D
└─31380 /usr/sbin/smbd -D
Jun 17 15:13:16 linux-3kds systemd[1]: Starting Samba SMB Daemon...
Jun 17 15:13:16 linux-3kds systemd[1]: smb.service: Supervising process 31373 which is not our child. We'll most likely not notice when it exits.
Jun 17 15:13:16 linux-3kds smbd[31373]: [2018/06/17 15:13:16.387676, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Jun 17 15:13:16 linux-3kds smbd[31373]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
● nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2018-06-17 15:13:16 EDT; 292ms ago
Main PID: 31153 (nmbd)
Status: "nmbd: ready to serve connections..."
Tasks: 2 (limit: 4915)
CGroup: /system.slice/nmb.service
├─31153 /usr/sbin/nmbd -D
└─31154 /usr/sbin/nmbd -D
Jun 17 15:13:15 linux-3kds systemd[1]: Starting Samba NMB Daemon...
Jun 17 15:13:15 linux-3kds systemd[1]: nmb.service: Supervising process 31153 which is not our child. We'll most likely not notice when it exits.
Jun 17 15:13:15 linux-3kds nmbd[31153]: [2018/06/17 15:13:15.799420, 0] ../source3/nmbd/asyncdns.c:158(start_async_dns)
Jun 17 15:13:15 linux-3kds nmbd[31153]: started asyncdns process 31154
Jun 17 15:13:16 linux-3kds nmbd[31153]: [2018/06/17 15:13:16.110985, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Jun 17 15:13:16 linux-3kds nmbd[31153]: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
Jun 17 15:13:16 linux-3kds systemd[1]: Started Samba NMB Daemon.
Jun 17 15:13:16 linux-3kds nmbd[31153]: [2018/06/17 15:13:16.122964, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Jun 17 15:13:16 linux-3kds nmbd[31153]: query_name_response: Multiple (2) responses received for a query on subnet 172.16.0.3 for name WORKGROUP<1d>.
Jun 17 15:13:16 linux-3kds nmbd[31153]: This response was from IP 172.16.0.41, reporting an IP address of 172.16.0.41.
I do not understand the reason for this and I would like to fix the problem. Both servers have different host names and they have different NICs. I am also able to access the shares on the FreeBSD server.
Here is the smb.conf on the openSUSE server:
# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
[global]
workgroup = WORKGROUP
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
usershare allow guests = No
wins support = Yes
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
## Share disabled by YaST
# [groups]
# comment = All groups
# path = /home/groups
# read only = No
# inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775
[Backup]
comment = Backup Disk
guest ok = Yes
inherit acls = Yes
path = /Data/Backup
read only = No
vfs objects =
[Seagate 4TiB Raid]
comment = Raid Array of 4 TiB Seagate Drives
inherit acls = Yes
path = /Data/seagate4tb_raid
read only = No
vfs objects =
Here is the smb4.conf on the FreeBSD server:
[global]
workgroup = WORKGROUP
server string = Samba Server Version %v
wins support = Yes
security = user
passdb backend = tdbsam
map to guest = Bad User
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[Public]
comment = Public Directory
inherit acls = Yes
path = /Network/Public
read only = No
guest ok = Yes
How could I fix this issue?
Facebook
Twitter
Instagram