Cannot see lmde3 pc on network

[skeeter1479]

Hi, I'm a newbie and am trying out LMDE3. The install went well and all seemed to work and it's fast. I am able to see other pc's on my home network with other linux builds, MXLinux, Manjaro and Mint 19.3 Cinnamon. The problem is with samba installed I am unable to see my LMDE3 pc from any of my other linux pc's. I have gufw firewall installed and I used ' sudo ufw allow samba' to created a Samba exception rule like I did with my other pc's. I cannot even see my LMDE3 pc on nemo networks on the pc itself. I want to share my LMDE3 pc on the network because I have an 8GB usb drive with media on it I want to be able to see on my network. I'm sure I'm missing something obvious.Any help would be appreciated.

[nielo]

I had fun and games with sharing. At the moment, I don't have my LMDE3 laptop with me, I am using another wich is running LM 19.3. However, have you tried this:

edit /etc/samba/smb.conf and add the following lines under "workgroup = WORKGROUP", in the "[global]" section:

name resolve order = bcast host lmhosts wins
client max protocol = NT1

Save the file and reboot.

Obviously, if all your other PCs are on a network where the worgroup/domain is called something else then make that correction in "workgroup=SomethingElse"

That worked for me.

[skeeter1479]

I tried your suggestion but it didn't work. Here is a copy of my smb.conf if that helps

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP

name resolve order = bcast host lmhosts wins
client max protocol = NT1

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Only allow connections from machines on our LAN
hosts allow = 127.0.0.0/8 10.10.1.0/24

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = no
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin

I'm not even sure if it's samba related at this point.

[altair4]

So I downloaded LMDE3 and am running it in Live mode. Installed samba, created a share in smb.conf and .. um ... yep .... it's nowhere t be found in my network.

Looks like the version of samba in LMDE3 doesn't do this automatically but you can fix that by doing it yourself:

[1] Create a file at /etc/avahi/services/samba.service

[2] Put this into it:

Code: Select all

<?xml version="1.0" standalone='no'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
   <name replace-wildcards="yes">%h SMB</name> ## Display Name
   <service>
       <type>_smb._tcp</type>
       <port>445</port>
   </service>
</service-group>

[3] Save the file.

That's pretty much it. All of your the other Linux systems as well as any stray MacOS systems you may have in your network will see the Mint machine. You don't need to change the name resolver order or workgroup settings because we aren't using NetBIOS.

Note: You do need to have avahi running on this system so check to make sure:

Code: Select all

sudo service avahi-daemon status

[altair4]

Didn't see your smb.conf before I posted ... You have no shares defined in smb.conf. Did you create them in Nemo?

Code: Select all

net usershare info --long

And btw are all your other machines in this range:

hosts allow = 127.0.0.0/8 10.10.1.0/24

[nielo]

There are two troubleshooting threads that I found useful:

viewtopic.php?f=42&t=88146

viewtopic.php?f=157&t=185410#p960482

[skeeter1479]

Making some progress. I can now see a folder on my other pc's called 'offlmde3-pc SMB' (off for office) but when I click on it in nemo it says 'unable to mount location. Failed to receive share list from server.' Avahi is enabled and my shares are created using nemo-share. I see them under 'var/lib/samba/usershares'.

[altair4]

Can you post the output of the this command:

Code: Select all

net usershare info --long

[skeeter1479]

dad@offlmde3-pc:~$ net usershare info --long
[Elements_3]
path=/media/dad/Elements_3
comment=
usershare_acl=Everyone:F,
guest_ok=n

[Elements_1]
path=/media/dad/Elements_1
comment=
usershare_acl=Everyone:R,OFFLMDE3-PC\dad:F,
guest_ok=n

[Shared]
path=/home/dad/Shared
comment=
usershare_acl=Everyone:F,
guest_ok=y

[Elements_2]
path=/media/dad/Elements_2
comment=
usershare_acl=Everyone:R,OFFLMDE3-PC\dad:F,
guest_ok=n

[altair4]

All of the "Elements.." shares will only be accessible to dad so unless you are providing dads username and samba password you will not gain access. In fact the client machine would not even know it's there.

The same thing would happen to the "Shared" share if you encrypted your home directory.

Um .... If you are not accessing this machine as "dad" on the client I would edit /etc/samba/smb.conf and add a line under the workgroup = WORKGROUP line:

Code: Select all

force user = dad

Then restart smbd: sudo service smbd restart

There is still the possibility that this is a resolution error of some sort. I would access the machine by it's mDNS name just to be sure. So in the file manager on the client access the share this way: smb://offlmde3-pc.local

[skeeter1479]

Tried your last suggestions but still no luck. I think I'll reboot into Manjaro or MXLinux since they both seems to work fine. The nice thing about those distros is they still can use the Samba Server Configuration Tool, so easy. Maybe I will revisit lmde3 later and see if it's resolved. Thanks for all your help.