LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 04-28-2017, 06:04 AM   #1
pconstantatos
LQ Newbie
 
Registered: Dec 2016
Posts: 29

Rep: Reputation: Disabled
Server problems


I tried to make a backup server using an old Fujitsu Econel and Ubuntu 16.04. I installed the OS and followed the instruction to share a folder on the network. It worked fine. Now I added a second HD (2TB) on which I created a folder to share and followed instructions to share this folder to the network but to no avail. I used nautilus (gksudo nautilus) and it seems to go fine but when I reboot I cannot access the folder from my other pc's. Any ideas?
 
Old 04-28-2017, 07:14 AM   #2
Rickkkk
Senior Member
 
Registered: Dec 2014
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch
Posts: 1,253

Rep: Reputation: 467Reputation: 467Reputation: 467Reputation: 467Reputation: 467
Hey pconstantatos ... How are you sharing - nfs or samba ? Can you post a config file ? Problems like this are often related to incomplete samba or nfs config on the server or permissions conflicts.

Cheers.
 
Old 04-28-2017, 09:43 AM   #3
pconstantatos
LQ Newbie
 
Registered: Dec 2016
Posts: 29

Original Poster
Rep: Reputation: Disabled
Hi, yes it is samba. Below is the config file


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

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

#### 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.d$
# 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:* %$

# 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" $

# 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
 
Old 04-28-2017, 10:03 AM   #4
pconstantatos
LQ Newbie
 
Registered: Dec 2016
Posts: 29

Original Poster
Rep: Reputation: Disabled
Attached is a screenshot where you can see the shared folder in Home. The one it cannot share is the 2.0tb hdd.
Attached Thumbnails
Click image for larger version

Name:	Screenshot from 2017-04-28 17-49-27.png
Views:	4
Size:	114.3 KB
ID:	24866  
 
Old 04-28-2017, 10:34 AM   #5
Rickkkk
Senior Member
 
Registered: Dec 2014
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch
Posts: 1,253

Rep: Reputation: 467Reputation: 467Reputation: 467Reputation: 467Reputation: 467
Hi again ... You may have to provide a little more info - unless I missed something, the only defined shares I can find in your samba config file seem to have to do with printer drivers.

You said you have at least one working share - can you provide the details (the path to the directory being shared on the server, the samba name you assigned the share ...).

Since you are using samba, am I correct in presuming that the computers you wish to connect to the shares with are running Windows ? Have you ensured that user names on the Ubuntu server have been created on both the linux side and the samba side ?

Let's start with that.
 
1 members found this post helpful.
Old 04-28-2017, 11:50 AM   #6
pconstantatos
LQ Newbie
 
Registered: Dec 2016
Posts: 29

Original Poster
Rep: Reputation: Disabled
I will provide all info as soon as I am near the server again. As for the presumption, it is 50% correct. There are three desktops running windows 10. one desktop running Linux Mint 18.1, and two laptops one with W10 and the other with Mint 18.1. I was thinking if maybe it would be better if I uninstalled Samba from the server and reinstalled it with all drives attached. Thanks for the reply
 
Old 04-28-2017, 12:04 PM   #7
Rickkkk
Senior Member
 
Registered: Dec 2014
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch
Posts: 1,253

Rep: Reputation: 467Reputation: 467Reputation: 467Reputation: 467Reputation: 467
Hi again,

Unless your samba installation routine also contains some kind of auto-discovery and configuration steps (the usual installation of samba does not - you take care of that separately), there won't be any advantage in uninstalling and reinstalling samba on the server. I'll let you determine how that applies in your case (I am less used to Ubuntu's way of doing things and more used to the more manual way of doing things in Arch - perhaps other members here are familiar with the Ubuntu implementation of samba).

Given the diversity of your client computers, samba is a good choice.

We'll wait for your further info and move on then.

Cheers.
 
Old 04-28-2017, 02:06 PM   #8
pconstantatos
LQ Newbie
 
Registered: Dec 2016
Posts: 29

Original Poster
Rep: Reputation: Disabled
Click image for larger version

Name:	Screenshot from 2017-04-28 21-40-53.png
Views:	5
Size:	144.5 KB
ID:	24867

Click image for larger version

Name:	Screenshot from 2017-04-28 21-41-39.png
Views:	5
Size:	125.5 KB
ID:	24868

Click image for larger version

Name:	Screenshot from 2017-04-28 21-42-00.png
Views:	6
Size:	161.3 KB
ID:	24869

Click image for larger version

Name:	Screenshot from 2017-04-28 21-42-17.png
Views:	6
Size:	133.0 KB
ID:	24870

Click image for larger version

Name:	Screenshot from 2017-04-28 21-42-37.png
Views:	4
Size:	125.1 KB
ID:	24871

I am attaching screenshots of all properties screens of both the "share" folder that I can see as well as of the "photoshare" folder which was invisible. However, as I was doing that (I booted the server to take the screen shots) both folders appeared on my laptop and "photoshare" now shares perfectly. I have no idea as to what happened, I did not intervene in the least since my last message. perhaps the screenshots might make you understand something and enlighten me.
 
Old 04-28-2017, 02:09 PM   #9
pconstantatos
LQ Newbie
 
Registered: Dec 2016
Posts: 29

Original Poster
Rep: Reputation: Disabled
Click image for larger version

Name:	Screenshot from 2017-04-28 21-43-47.png
Views:	5
Size:	172.4 KB
ID:	24872

Click image for larger version

Name:	Screenshot from 2017-04-28 21-44-11.png
Views:	4
Size:	170.8 KB
ID:	24873

Click image for larger version

Name:	Screenshot from 2017-04-28 21-44-39.png
Views:	4
Size:	178.5 KB
ID:	24874

Click image for larger version

Name:	Screenshot from 2017-04-28 21-45-12.png
Views:	6
Size:	158.7 KB
ID:	24875

Click image for larger version

Name:	Screenshot from 2017-04-28 21-45-52.png
Views:	6
Size:	185.7 KB
ID:	24876
 
Old 04-28-2017, 02:11 PM   #10
Rickkkk
Senior Member
 
Registered: Dec 2014
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch
Posts: 1,253

Rep: Reputation: 467Reputation: 467Reputation: 467Reputation: 467Reputation: 467
Hi again - I've honestly never managed samba through GUI tools, so I'm not the best person to comment on those screenshots. I don't see anything obviously wrong.

I'm hearing you're up and running, now, though ? All is functional ? Maybe it was just a question of restarting the smbd and nmbd services on the Ubuntu server when you rebooted it ...

Maybe other members can comment - but I'm glad to hear that your problem is "solved" ...

Cheers.
 
Old 04-28-2017, 02:14 PM   #11
pconstantatos
LQ Newbie
 
Registered: Dec 2016
Posts: 29

Original Poster
Rep: Reputation: Disabled
I really want to thank you for all your assistance. I hope one day I will become proficient enough to manage everything from the terminal. Still, a long way to go I am afraid. I hope it keeps working properly. Until then I will close the thread. All the best to you.
 
Old 04-28-2017, 02:16 PM   #12
Rickkkk
Senior Member
 
Registered: Dec 2014
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch
Posts: 1,253

Rep: Reputation: 467Reputation: 467Reputation: 467Reputation: 467Reputation: 467
... and to you, pconstantantos. No shame in using GUI tools - whatever does the job. Glad if I was able to help.

Cheers and have a great weekend !
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
X server not working after yum update & font server problems snow93 Linux - Software 1 08-02-2006 05:26 AM
cisco 350 wireless problems and suse x-server problems incognito9 Linux - Wireless Networking 5 10-14-2004 07:53 AM
problems setting up apache and vsftp server behind a router that serves as a server xone Linux - Security 1 04-08-2004 10:46 AM
Mandrake 9.0 Installation Problems: X-Server, GUI Problems? chromelocust Linux - Software 4 03-21-2003 01:59 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 12:22 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration