Cannot See Windows 10 shares from a Linux Mint 19

Connection sharing, Firewall, Samba..etc
Forum rules
Before you post please read how to get help
Post Reply
Level 3
Level 3
Posts: 129
Joined: Thu Apr 12, 2012 6:09 pm

Cannot See Windows 10 shares from a Linux Mint 19

Post by RobertX » Tue Jul 10, 2018 1:49 am

I have three computers in my network, and I will list them here:

1. P-Four: Linux Mint 19 Tara MATE
2. Batista: Windows 10 Pro
3. Mini-Grandma: Windows 7 Ultimate

For starters: Both Batista and Mini-Grandma can see each other, alter each other's files, and see/alter P-Four. P-Four can see/alter Mini-Grandma but only see the Batista.icon in the Network app and not open/alter it.

Specifically, the problem I had was that when I used P-Four to open Batista from the network app, there is either "Failed to retrieve share list from server: Connection Refused." When I used the command line caja smb:// (which was the internal IP of Batista), the message changed from "Connection refused" to "Connection Timed Out."

Now, what I tried to do before posing:

Code: Select all

Add the line client max protocol = NT1 on smb.conf as prescribed by altair4
Actually, I didn't "try" here, before I installed Windows 10 on Batista, I already had that entry here on P-Four due to an earlier recommendation by another peer. It didn't work. In fact, as I said, the message originated here.

Code: Select all

change the client max protocol from NT1 to SMB3 or something else
I got mixed up here. The point is, when I changed the protocol around, I was able to access Batista, but Mini-Grandma cannot be opened/altered by P-Four.

Code: Select all

Changing hosts by adding the IP address of Batista and Mini-Grandma
Did absolutely nothing.

Code: Select all

Tried to use IP addresses and hostnames instead of depending on Caja network app
Did absolutely nothing as well.

Code: Select all

Pinged Batista
WAIT - Just did it now, and it's not responding. Something amiss here?

Code: Select all

Set all computers to the same workgroup: TEAM NO REGRET
Did that since the beginning.

Code: Select all

Here's what it says on smbtree

	\\P-FOUR         		P-Four server (Samba, Ubuntu)
		\\P-FOUR\IPC$           	IPC Service (P-Four server (Samba, Ubuntu))
		\\P-FOUR\print$         	Printer Drivers
	\\MINI-GRANDMA   		Mom's Computer
		\\MINI-GRANDMA\print$         	Printer Drivers
		\\MINI-GRANDMA\Mini-Grandma Storage	
		\\MINI-GRANDMA\IPC$           	Remote IPC
		\\MINI-GRANDMA\C$             	Default share
		\\MINI-GRANDMA\Brother HL-2140	Family Printer
		\\MINI-GRANDMA\ADMIN$         	Remote Admin
	\\BATISTA        		RobertX's Base Computer

As you can see, nothing is happening with Batista - something else amiss?

Code: Select all

Most of the stuff here:
Can't really understand it all, but I believe the main concern is to stick to the part where I create a login. Is the login for the Windows 10 computer or the Linux Mint one?

And that's all I've tried. I would be glad to be assisted in any way; I'll be very humble.

By the way, here's my smb.conf content:

Code: Select all


# Browsing/Identification
   client max protocol = NT1

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

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

# 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 = 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 <<> 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 = yes

# 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
;   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.)
;   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
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

   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
   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

Level 3
Level 3
Posts: 129
Joined: Thu Apr 12, 2012 6:09 pm

Re: Cannot See Windows 10 shares from a Linux Mint 19

Post by RobertX » Tue Jul 10, 2018 2:59 am

Never mind, I'll do away with Windows 10 and make the best of Windows 7.

The problem never existed with Windows 7 and this has happened with Windows 10.

Have a nice day.

User avatar
Level 8
Level 8
Posts: 2280
Joined: Wed Sep 10, 2014 9:07 pm
Location: Rural South Australia

Re: Cannot See Windows 10 shares from a Linux Mint 19

Post by lsemmens » Tue Jul 10, 2018 3:36 am

I had all sorts of strife with Windoze networking. Getting it set up and working reliably was great until "patch tuesday" and then I'd have to go back in and reset all my permissions. I'd set them and then, at random, they'd disappear from the network. Since I've given up on Windoze all together I've not had any more issues.
Going back to Windoze 7 is probably your best bet if you must keep Windoze either that, or ditch Windoze all together.
Kernel: 4.15.0-46-generic x86_64 bits
Desktop: Cinnamon 3.8.9
Distro: Linux Mint 19 Tara

Laptop HP-ProBook-470-G2 8Gb RAM SSD
Server AMD Phenom 9650 - GEForce 9400GT 6Gb RAM
+ three other Mint machines
Out of my mind - please leave a message

Post Reply

Return to “Other networking topics”