[18.3 64bit XFCE K4.13.0-41] Share Linux to Win10Pro 1703 [SOLVED]

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
VUMeter
Level 1
Level 1
Posts: 16
Joined: Tue May 15, 2018 12:19 pm

[18.3 64bit XFCE K4.13.0-41] Share Linux to Win10Pro 1703 [SOLVED]

Post by VUMeter »

Hi,
My first post here so please excuse any faux pas.

[A little background]
Purchased an HP 15" FHD Notebook (Intel N3710, 4GB RAM, 1TB HDD) just over a week ago.
It came with Windows 10 Home 1709 (Fall Creators), and I spent a couple of days setting it up, but Microsoft have managed to irritate me so much with their aggressive and imposing forced updates, that I could stand it no longer and "turned to the dark side" *edit* or is that "saw the light" and shifted to Linux.

XFCE seemed like a good choice as it's lighter in weight than Cinnamon, and has customisation options which I will likely take advantage of later down the line.

- Realtek RTL8723DE wifi drivers (thanks to smlinux) make'd and installed.
- Kernel updated to 4.13.0-41.
- Realtek wifi driver removed, and re-make'd/installed for new Kernel.
- Wine installed for Foobar2000 audio player.
- Windows 7 share (users "Everyone") seen, mounted and accessed without issue.

[The issue]
I am trying to create a share on the Linux Mint machine, so that the Windows 10 Pro 1703 machine can read/write files to it.
The end goal will be to use the Windows "D:" NTFS partition (which I have auto-mounted via fstab) as the share folder and have only the desired PC @ IP or User/PW on the LAN access it.

Share folder: /home/userlx/share
Assumed network share location: \\192.168.0.102\Files or \\HP_15\Files
Firewall (gufw) is open for both in/out 192.168.0.100 (Windows 10 PC)
Windows 10 is using ZoneAlarm FW, and the Linux Notebook 192.168.0.102 is in the trusted Zone with file and print sharing enabled (just like the Win7 machine).

I've searched for all sorts of terms relating to this, and have finally given in after 2 solid days of trying to get this to work. I just have to call for help.

At the Windows 10 command prompt:
> net view
Mostly kicks off a 6118 error, but does sometimes list it's own PC name as well as the Windows 7 PC and "\\HP_15" the Linux machine.
> net view <\\win7_machine_name>
Shows two shared folders
> net view \\HP_15
System error 53 occurred. The network path was not found.


Here are some of the output of the Linux machine:

testparm

Code: Select all

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
Processing section "[printers]"
Processing section "[print$]"
Processing section "[Files]"
Loaded services file OK.
Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions
# Global parameters
[global]
	workgroup = ZX26T42PI
	netbios name = HP_15
	server string = %h server (Samba, Ubuntu)
	server role = standalone server
	map to guest = Bad User
	obey pam restrictions = Yes
	pam password change = Yes
	passwd program = /usr/bin/passwd %u
	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
	unix password sync = Yes
	syslog = 0
	log file = /var/log/samba/log.%m
	max log size = 1000
	name resolve order = bcast
	dns proxy = No
	wins support = Yes
	usershare allow guests = Yes
	panic action = /usr/share/samba/panic-action %d
	idmap config * : backend = tdb


[printers]
	comment = All Printers
	path = /var/spool/samba
	create mask = 0700
	printable = Yes
	browseable = No


[print$]
	comment = Printer Drivers
	path = /var/lib/samba/printers


[Files]
	comment = Linux Share
	path = /home/userlx/share
smbtree -d3

Code: Select all

lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
WARNING: The "syslog" option is deprecated
added interface wlo1 ip=192.168.0.102 bcast=192.168.0.255 netmask=255.255.255.0
Enter userlx's password: 
tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied
name_resolve_bcast: Attempting broadcast lookup for name ZX26T42PI<0x1d>
name_resolve_bcast: Attempting broadcast lookup for name ZX26T42PI<0x1b>
name_resolve_bcast: Attempting broadcast lookup for name __MSBROWSE__<0x1>
pdbedit -L -v

Code: Select all

---------------
Unix username:        userlx
NT username:          
Account Flags:        [U          ]
User SID:             S-1-5-21-3367000538-3987066231-266316221-1000
Primary Group SID:    S-1-5-21-3367000538-3987066231-266316221-513
Full Name:            UserLX
Home Directory:       \\hp_15\userlx
HomeDir Drive:        
Logon Script:         
Profile Path:         \\hp_15\userlx\profile
Domain:               USERLX-HP-LAPTOP-15-BS0XX
Account desc:         
Workstations:         
Munged dial:          
Logon time:           0
Logoff time:          Wed, 06 Feb 2036 15:06:39 GMT
Kickoff time:         Wed, 06 Feb 2036 15:06:39 GMT
Password last set:    Tue, 15 May 2018 16:00:33 BST
Password can change:  Tue, 15 May 2018 16:00:33 BST
Password must change: never
Last bad password   : 0
Bad password count  : 0
Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
/etc/samba/smb.conf

Code: Select all

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 

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

[global]

## Browsing/Identification ###

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

# New addition // NetBIOS
  netbios name = HP_15
  name resolve order = bcast

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

# 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 = 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
;[homes]
;   comment = Home Directories
;   browseable = yes

# 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

[Files]
	comment = Linux Share
	path = /home/userlx/share
	read only = yes
	browseable = yes
;	valid users = userlx
*edit: wrapped code in proper tags.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
AMD Ryzen 1700x // ASRock X370 TaiChi // Zotac GTX1070 8GB Mini // 32GB (2x16) G.Skill Flare X
Samsung 850 Pro 256GB // Seagate Barracuda 7200 SATA // Seasonic Prime Titanium Ultra 750w
Fractal Design Define R5 // Noctua NH-U14S // Noctua NF-A14 PWM.
VUMeter
Level 1
Level 1
Posts: 16
Joined: Tue May 15, 2018 12:19 pm

Re: [18.3 64bit XFCE 4.13.0-41] Share Linux to Win10Pro 1703

Post by VUMeter »

I'll add a little more information.

Editing /etc/sambda/smb.conf :
If "wins support = no" or commented, then the Linux machine is not ever visible to Windows 10.

Trying to "Map Network Drive" in explorer asks for user and password and nothing works there.
AMD Ryzen 1700x // ASRock X370 TaiChi // Zotac GTX1070 8GB Mini // 32GB (2x16) G.Skill Flare X
Samsung 850 Pro 256GB // Seagate Barracuda 7200 SATA // Seasonic Prime Titanium Ultra 750w
Fractal Design Define R5 // Noctua NH-U14S // Noctua NF-A14 PWM.
VUMeter
Level 1
Level 1
Posts: 16
Joined: Tue May 15, 2018 12:19 pm

Re: [18.3 64bit XFCE 4.13.0-41] Share Linux to Win10Pro 1703

Post by VUMeter »

Apologies for replying to my own thread, but I think I am discovering a potential break through.

Virtual Box with Host-Only Adapter
Installed Mint 18.3 XFCE from the same .iso as used for the Notebook PC install.
Used (VMBox) NAT network device so I could get online and install Samba.
Changed (VMBox) network device to "Host-Only", so I have no internet in the 'guest' Linux OS, but can establish connections between the Windows 10 'host' and the Linux VM.

Edited /etc/samba/smb.conf to add the following at the very bottom, nothing else changed from default.

Code: Select all

[readonly-share]
   comment = some share
   path = /home/roshare
   guest ok = yes
   browseable = yes
   read only = yes

Code: Select all

sudo mkdir /home/roshare
sudo service smbd restart
Lo and behold, I can see this share in Windows explorer by navigating the VM's IP\<share-name>

ufw is turned off, ZoneAlarm has the entire Host-Only network in trusted Zone.
smb.conf does not have wns messed about with.

Setting "guest ok = no" prevents access, which is not surprising at all.
I think I can now see how to manger samba users and transfer these settings to the Notebook machine.
AMD Ryzen 1700x // ASRock X370 TaiChi // Zotac GTX1070 8GB Mini // 32GB (2x16) G.Skill Flare X
Samsung 850 Pro 256GB // Seagate Barracuda 7200 SATA // Seasonic Prime Titanium Ultra 750w
Fractal Design Define R5 // Noctua NH-U14S // Noctua NF-A14 PWM.
VUMeter
Level 1
Level 1
Posts: 16
Joined: Tue May 15, 2018 12:19 pm

Re: [18.3 64bit XFCE 4.13.0-41] Share Linux to Win10Pro 1703

Post by VUMeter »

Hoorah! Success!

It was entirely my fault not setting up ufw firewall properly.

Being used to ZoneAlarm's GUI, lets you just add an IP address and it'll allow it to ALL ports unless you go about restricting it.
ufw is a different setup, and one has to manually enter a rule for each port (udp 137 and 138 / tcp 139 and 445) for each IP or IP range that they want to allow sharing with.

I worked it out in the VM, and then applied the rules to the Notebook and now all is fine. I can see a shared folder, I can see the shared file in the folder.

I had setup a samba user on the Notebook as the same name as the account (userlx) and with a different password. I had to enter this samba password for access to the share - fantastic, just what I wanted.

So all is now well. After a lot of hair pulling, swearing and general frustration, it takes a fresh new look at things and to be a little methodical.
AMD Ryzen 1700x // ASRock X370 TaiChi // Zotac GTX1070 8GB Mini // 32GB (2x16) G.Skill Flare X
Samsung 850 Pro 256GB // Seagate Barracuda 7200 SATA // Seasonic Prime Titanium Ultra 750w
Fractal Design Define R5 // Noctua NH-U14S // Noctua NF-A14 PWM.
Locked

Return to “Networking”