Questions about access from Windows and via VPN to Linux

Connection sharing, Firewall, Samba..etc
Forum rules
Before you post please read how to get help
Post Reply
User avatar
Calimero
Level 1
Level 1
Posts: 10
Joined: Sun Jun 16, 2019 6:46 am

Questions about access from Windows and via VPN to Linux

Post by Calimero » Mon Jul 01, 2019 1:23 pm

I have as a beginner Linux Mint 19.1 Cinnamon.

I have installed Samba on Linux and can also access my Windows network from my Linux computer if I am directly in the network. I can access Windows computers as well as QNAP NAS. As router I have a Fritzbox 7490 and a Samsung printer. The Linux computer is part of the WORKGROUP. I have registered the same user with the same password on all computers. The access from Windows to QNAP and from Linux to Windows and QNAP works.

Now to my problems:

1. if I try to access Linux Mint from my Windows 7 computer, it only works partially. Because I only see the Samsung network printer and no other shared folders on the Linux computer. I gave the user for the WORKGROUP read and write permissions. What additional information or files are required for error analysis?

2 If I dial in via another Fritzbox or a mobile hotspot via VPN, I don't see any network at all: No Windows computer nor the QNAP. I don't understand, because VPN dials into the actual network. Besides the Linux computer I only see WINDOWS NETWORK (but without content). However, if I dial into my network with a Windows 10 laptop via VPN, it works. Also here I hope to have described everything as far as possible. What other information/files are needed.

On the one hand I want to solve the problem or find a solution and on the other hand I want to understand the solution.

I hope to have described everything comprehensibly and in detail

Code: Select all

Sudo] Passwort für user:       
---------------
Unix username:        smbguest
NT username:          
Account Flags:        [U          ]
User SID:             S-1-5-21-1920303431-3085711883-3951780017-1000
Primary Group SID:    S-1-5-21-1920303431-3085711883-3951780017-513
Full Name:            Samba guest account
Home Directory:       \\user-3000-n200\smbguest
HomeDir Drive:        
Logon Script:         
Profile Path:         \\user-3000-n200\smbguest\profile
Domain:               USER-3000-N200
Account desc:         
Workstations:         
Munged dial:          
Logon time:           0
Logoff time:          Mi, 06 Feb 2036 16:06:39 CET
Kickoff time:         Mi, 06 Feb 2036 16:06:39 CET
Password last set:    So, 31 Mär 2019 19:01:27 CEST
Password can change:  So, 31 Mär 2019 19:01:27 CEST
Password must change: never
Last bad password   : 0
Bad password count  : 0
Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
---------------
Unix username:        root
NT username:          
Account Flags:        [DU         ]
User SID:             S-1-5-21-1920303431-3085711883-3951780017-1001
Primary Group SID:    S-1-5-21-1920303431-3085711883-3951780017-513
Full Name:            root
Home Directory:       \\user-3000-n200\root
HomeDir Drive:        
Logon Script:         
Profile Path:         \\user-3000-n200\root\profile
Domain:               USER-3000-N200
Account desc:         
Workstations:         
Munged dial:          
Logon time:           0
Logoff time:          Mi, 06 Feb 2036 16:06:39 CET
Kickoff time:         Mi, 06 Feb 2036 16:06:39 CET
Password last set:    So, 31 Mär 2019 19:01:28 CEST
Password can change:  So, 31 Mär 2019 19:01:28 CEST
Password must change: never
Last bad password   : 0
Bad password count  : 0
Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
---------------
Unix username:        homebasemaster
NT username:          
Account Flags:        [U          ]
User SID:             S-1-5-21-1920303431-3085711883-3951780017-1007
Primary Group SID:    S-1-5-21-1920303431-3085711883-3951780017-513
Full Name:            Kommentar
Home Directory:       \\user-3000-n200\homebasemaster
HomeDir Drive:        
Logon Script:         
Profile Path:         \\user-3000-n200\homebasemaster\profile
Domain:               SAMBA24
Account desc:         
Workstations:         
Munged dial:          
Logon time:           0
Logoff time:          Mi, 06 Feb 2036 16:06:39 CET
Kickoff time:         Mi, 06 Feb 2036 16:06:39 CET
Password last set:    Di, 07 Mai 2019 21:32:54 CEST
Password can change:  Di, 07 Mai 2019 21:32:54 CEST
Password must change: never
Last bad password   : 0
Bad password count  : 0
Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

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 = HOMEBASE
name resolve order = bcast host lmhosts wins
server max protocol = SMB2
client max protocol = NT1

# 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 = 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 = 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
Is something missing or is something too much that prevents access from Windows or via VPN to Windows?

Explaining to me why something is not working would help. Thank you very much in advance
Linux Mint 19.2 Cinnamon Lenovo 3000 N200 mit 4GB RAM

User avatar
Calimero
Level 1
Level 1
Posts: 10
Joined: Sun Jun 16, 2019 6:46 am

Re: Questions about access from Windows and via VPN to Linux

Post by Calimero » Sun Sep 08, 2019 5:38 am

Anyone who could advice or help me on this?
Linux Mint 19.2 Cinnamon Lenovo 3000 N200 mit 4GB RAM

User avatar
Spearmint2
Level 16
Level 16
Posts: 6241
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Questions about access from Windows and via VPN to Linux

Post by Spearmint2 » Sun Sep 08, 2019 9:31 am

Use the Public folder in Linux for those on windows to access shared folders.
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

altair4
Level 19
Level 19
Posts: 9690
Joined: Tue Feb 03, 2009 10:27 am

Re: Questions about access from Windows and via VPN to Linux

Post by altair4 » Sun Sep 08, 2019 9:55 am

I can't help you with the VPN part of this but:
Calimero wrote:
Mon Jul 01, 2019 1:23 pm
1. if I try to access Linux Mint from my Windows 7 computer, it only works partially. Because I only see the Samsung network printer and no other shared folders on the Linux computer. I gave the user for the WORKGROUP read and write permissions. What additional information or files are required for error analysis?
Based on your smb.conf file you have nothing shared so there is nothing for Win7 to access.

Do you see any share definitions here:

Code: Select all

net usershare info --long
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

User avatar
Spearmint2
Level 16
Level 16
Posts: 6241
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Questions about access from Windows and via VPN to Linux

Post by Spearmint2 » Sun Sep 08, 2019 9:58 am

Code: Select all

ls /var/lib/samba/usershares/
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

User avatar
Calimero
Level 1
Level 1
Posts: 10
Joined: Sun Jun 16, 2019 6:46 am

Re: Questions about access from Windows and via VPN to Linux

Post by Calimero » Sun Sep 08, 2019 1:58 pm

I had a quick look through the smb.conf and could not find anything there on the usershare...

So in whichs ection would I need to put the share and how?

I am sorry to ask these questions as I am still new to Linux...
Linux Mint 19.2 Cinnamon Lenovo 3000 N200 mit 4GB RAM

altair4
Level 19
Level 19
Posts: 9690
Joined: Tue Feb 03, 2009 10:27 am

Re: Questions about access from Windows and via VPN to Linux

Post by altair4 » Sun Sep 08, 2019 2:25 pm

I had a quick look through the smb.conf and could not find anything there on the usershare...
You won't find anything in smb.conf for shares created through your file manager - usershares.

Run the command I posted above:

Code: Select all

net usershare info --long
If it has no output you have no samba shares at all so you will have to create one.

For a quick test:

** Open your file manager.

** Right click your Public folder.

** Select Sharing Options > Share this Folder > check the other 2 boxes.

** Confirm that you have a valid usershare by running: net usershare info --long

Now you should have a samba share of your Public folder accessible to anyone.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

User avatar
Calimero
Level 1
Level 1
Posts: 10
Joined: Sun Jun 16, 2019 6:46 am

Re: Questions about access from Windows and via VPN to Linux

Post by Calimero » Sat Sep 14, 2019 8:39 am

Thanks for the guideance. I seem to stuck however. As you assumed, there seems to be no usershare at all.

Code: Select all

$ net usershare info --long
info_fn: file /var/lib/samba/usershares/plugins is not a well formed usershare file.
info_fn: Error was Path not allowed.
I looked for the public folder, could not find it or at least I found it and tried to give access to it.....did not change anything. I still get the above message.

So when I get you right, I would need to add usershare to the smb.cnf to give me access to the system from outside Linux....similar to the printer, which I can see and access from windows....


30 Minutes later:

In the meantime I discovered Nautilus and was able to share some hof the folders, which I know see in Windows....however, access is not possible and forces Windows into trying to connect mode and the file explorer to freeze

Code: Select all

$ net usershare info --long

[Downloads]
path=/home/user/Downloads
comment=
usershare_acl=Everyone:F,
guest_ok=n

[Dokumente]
path=/home/user/Dokumente
comment=
usershare_acl=Everyone:F,
guest_ok=n

[Bilder]
path=/home/user/Bilder
comment=
usershare_acl=Everyone:F,
guest_ok=n

[Videos]
path=/home/user/Videos
comment=
usershare_acl=Everyone:R,Unix User\user:F,
guest_ok=n

[Öffentlich]
path=/home/user/Öffentlich
comment=
usershare_acl=Everyone:F,
guest_ok=n

[Musik]
path=/home/user/Musik
comment=
usershare_acl=Everyone:F,
guest_ok=n
Thus I see them now, but access is not possible as Windows starts to freeze....even not able to enter Username and Pasword to access folders on MINT.
Linux Mint 19.2 Cinnamon Lenovo 3000 N200 mit 4GB RAM

altair4
Level 19
Level 19
Posts: 9690
Joined: Tue Feb 03, 2009 10:27 am

Re: Questions about access from Windows and via VPN to Linux

Post by altair4 » Sat Sep 14, 2019 10:32 am

I cannot reproduce this "freeze" issue you speak of but all of your shares require a username and password to access. So if you want to access the shares with the "user" username ( the same user as in /home/user/Downloads ) you need to add that user to the samba password database:

Code: Select all

sudo smbpasswd -a user
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

User avatar
Calimero
Level 1
Level 1
Posts: 10
Joined: Sun Jun 16, 2019 6:46 am

Re: Questions about access from Windows and via VPN to Linux

Post by Calimero » Sat Sep 14, 2019 11:08 am

That was the solution. I thought, I would connect via my usual Samba user....but it is the current windows user....thus Username and Password are not asked for...done and I am happy!

would his also work when I connect via VPN to my Linux maschine?
Linux Mint 19.2 Cinnamon Lenovo 3000 N200 mit 4GB RAM

altair4
Level 19
Level 19
Posts: 9690
Joined: Tue Feb 03, 2009 10:27 am

Re: Questions about access from Windows and via VPN to Linux

Post by altair4 » Sat Sep 14, 2019 11:50 am

Calimero wrote:
Sat Sep 14, 2019 11:08 am
That was the solution. I thought, I would connect via my usual Samba user....but it is the current windows user....thus Username and Password are not asked for...done and I am happy!

would his also work when I connect via VPN to my Linux maschine?
That I do not know. I'm guessing no but I never tried.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

User avatar
Spearmint2
Level 16
Level 16
Posts: 6241
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Questions about access from Windows and via VPN to Linux

Post by Spearmint2 » Sat Sep 14, 2019 6:06 pm

.
Last edited by Spearmint2 on Sun Sep 15, 2019 1:01 pm, edited 1 time in total.
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

altair4
Level 19
Level 19
Posts: 9690
Joined: Tue Feb 03, 2009 10:27 am

Re: Questions about access from Windows and via VPN to Linux

Post by altair4 » Sun Sep 15, 2019 12:56 pm

@Calimero,

Please ignore Spearmint2's post. It has nothing to do with your question.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

Post Reply

Return to “Other networking topics”