Hi
I am still struggling to setup a home network of:
- 2 laptops running Windows 7 Home
- 1 laptop running Windows 10 Home
- 1 Raspberry Pi ‘RPHS’ running Rasbian Jesse and Samba 4.1.17-Debian
The current status is that only one of the Windows machines can see the Samba
shared drive /mnt/data. The other machines don’t discover the Pi at all.
I’m wondering if there is something wrong with my Samba configuration file.
I’ve shown the contents below. Please will someone kindly review it for me?
Best regards
David
[global]
usershare allow guests = yes
workgroup = WORKGROUP
wins support = true
map to guest = bad user
dns proxy = no
passwd program = /usr/bin/passwd %u
panic action = /usr/share/samba/panic-action %d
max log size = 1000
os level = 20
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:*
%n\n *password\supdated\ssuccessfully* .
log file = /var/log/samba/log.%m
passdb backend = tdbsam
pam password change = yes
server role = standalone server
obey pam restrictions = yes
syslog = 0
unix password sync = yes
realm = RPHS
netbios name = RPHS
name resolve order = wins lmhosts hosts bcast
[homes]
comment = Home Directories
browseable = no
read only = yes
create mask = 0700
directory mask = 0700
valid users = %S
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
[Data]
comment=Raspberry Pi Share
path = /mnt/data
browseable=yes
writeable = yes
only guest = no
public = yes
On 02/01/16 18:10, DavidA wrote:> Hi > > I am still struggling to setup a home network of: > > - 2 laptops running Windows 7 Home > - 1 laptop running Windows 10 Home > - 1 Raspberry Pi ‘RPHS’ running Rasbian Jesse and Samba 4.1.17-Debian > > The current status is that only one of the Windows machines can see the Samba shared drive /mnt/data. The other machines don’t discover the Pi at all. > > I’m wondering if there is something wrong with my Samba configuration file. I’ve shown the contents below. Please will someone kindly review it for me? > > Best regards > > David > > [global] > usershare allow guests = yes > workgroup = WORKGROUP > wins support = true > map to guest = bad user > dns proxy = no > passwd program = /usr/bin/passwd %u > panic action = /usr/share/samba/panic-action %d > max log size = 1000 > os level = 20 > passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . > log file = /var/log/samba/log.%m > passdb backend = tdbsam > pam password change = yes > server role = standalone server > obey pam restrictions = yes > syslog = 0 > unix password sync = yes > realm = RPHS > netbios name = RPHS > name resolve order = wins lmhosts hosts bcast > > [homes] > comment = Home Directories > browseable = no > > read only = yes > create mask = 0700 > directory mask = 0700 > valid users = %S > > [printers] > comment = All Printers > browseable = no > path = /var/spool/samba > printable = yes > guest ok = no > read only = yes > create mask = 0700 > > [print$] > comment = Printer Drivers > path = /var/lib/samba/printers > browseable = yes > read only = yes > guest ok = no > > [Data] > comment=Raspberry Pi Share > path = /mnt/data > browseable=yes > writeable = yes > only guest = no > public = yes >Hi David, there are things wrong with your smb.conf: It is for a standalone workgroup server and as such shouldn't have the 'realm' line, also even if it should, you cannot have the same netbios name and realm name. There are other minor problems, but *none* of your errors would cause the problem you are having, the sheer fact that one of your computers can see your Samba server, means that it is working correctly. If you now accept that the server is working correctly, then the problem must lie in the machines that cannot see the Samba server. Are all machines using the same workgroup name, are they all in the same ip range e.g. 192.168.0.0/24, do all machines have the same dns domain name. Have you tried turning off the firewall and anti-virus software on the machines that cannot see the Samba server. Whatever the problem is, I am very sure it has nothing to do with the Samba server. Rowland
Hi Rowland Thanks for your review. I will check all the points you raise, but one I do not understand is: "do all machines have the same dns domain name?" What is the dns domain name in the context of a NetBios workgroup? The only dns I am aware of is the one provided by my ISP, and that won't be relevant I think. Best regards David -----Original Message----- From: Rowland penny Sent: Saturday, January 02, 2016 8:02 PM To: samba at lists.samba.org Subject: Re: [Samba] Please review my smb.conf On 02/01/16 18:10, DavidA wrote:> Hi > > I am still struggling to setup a home network of: > > - 2 laptops running Windows 7 Home > - 1 laptop running Windows 10 Home > - 1 Raspberry Pi ‘RPHS’ running Rasbian Jesse and Samba 4.1.17-Debian > > The current status is that only one of the Windows machines can see the > Samba shared drive /mnt/data. The other machines don’t discover the Pi at > all. > > I’m wondering if there is something wrong with my Samba configuration > file. I’ve shown the contents below. Please will someone kindly review > it for me? > > Best regards > > David > > [global] > usershare allow guests = yes > workgroup = WORKGROUP > wins support = true > map to guest = bad user > dns proxy = no > passwd program = /usr/bin/passwd %u > panic action = /usr/share/samba/panic-action %d > max log size = 1000 > os level = 20 > passwd chat = *Enter\snew\s*\spassword:* %n\n > *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . > log file = /var/log/samba/log.%m > passdb backend = tdbsam > pam password change = yes > server role = standalone server > obey pam restrictions = yes > syslog = 0 > unix password sync = yes > realm = RPHS > netbios name = RPHS > name resolve order = wins lmhosts hosts bcast > > [homes] > comment = Home Directories > browseable = no > > read only = yes > create mask = 0700 > directory mask = 0700 > valid users = %S > > [printers] > comment = All Printers > browseable = no > path = /var/spool/samba > printable = yes > guest ok = no > read only = yes > create mask = 0700 > > [print$] > comment = Printer Drivers > path = /var/lib/samba/printers > browseable = yes > read only = yes > guest ok = no > > [Data] > comment=Raspberry Pi Share > path = /mnt/data > browseable=yes > writeable = yes > only guest = no > public = yes >Hi David, there are things wrong with your smb.conf: It is for a standalone workgroup server and as such shouldn't have the 'realm' line, also even if it should, you cannot have the same netbios name and realm name. There are other minor problems, but *none* of your errors would cause the problem you are having, the sheer fact that one of your computers can see your Samba server, means that it is working correctly. If you now accept that the server is working correctly, then the problem must lie in the machines that cannot see the Samba server. Are all machines using the same workgroup name, are they all in the same ip range e.g. 192.168.0.0/24, do all machines have the same dns domain name. Have you tried turning off the firewall and anti-virus software on the machines that cannot see the Samba server. Whatever the problem is, I am very sure it has nothing to do with the Samba server. Rowland -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba