Changing a kubuntu system to a client from server in a network

Asked by S.S.Mani

I installed Kuntu 12.04 LTS and updated to 14.04 LTS. My major problem is networking bothway with other windows computers and also installing network printer from other system, that i am unable to see.

1) Somehow I set up, or by default, my system remains a server.
I am in a network.
i understand that i must be client if I need to to use the network in full.
Am i correct.
And if so how do I do that.

2) "Thanks to life0riley in, i read that i must add the following in the Global section of myr smb.conf below dns proxy = no

name resolve order = lmhosts host wins bcast

Then do

sudo restart smbd
sudo restart nmbd" if my smaba file share is to work. How do I do that as many times it says I dont have permission to change!

As i have carried out many attempts in this I am alittle confused as to what all achnges I have made.
Is there a way to check that

Or is there something in kubuntu like system restore in windows!
My global settings shows

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


## Browsing/Identification ###

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

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

# 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 <<email address hidden> 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
 username map = /etc/samba/smbusers
 security = user
 encrypt passwords = no
 guest ok = yes
 guest account = smbguest

#======================= 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
 writeable = yes
 valid users = root, smbguest
# 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

[for sharing]
 path = /home/manihome/for sharing
 writeable = yes
; browseable = yes
 valid users = root, smbguest
 comment = windows file sharing

Testparm output is

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Processing section "[print$]"
Processing section "[for sharing]"
Loaded services file OK.
Press enter to see a dump of your service definitions

        workgroup = MSHOME
        server string = %h server (Samba, Kubuntu)
        server role = standalone server
        encrypt passwords = No
        map to guest = Bad User
        obey pam restrictions = Yes
        guest account = smbguest
        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* .
        username map = /etc/samba/smbusers
        unix password sync = Yes
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        dns proxy = No
        usershare allow guests = Yes
        panic action = /usr/share/samba/panic-action %d
        idmap config * : backend = tdb
        guest ok = Yes

        comment = All Printers
        path = /var/spool/samba
        create mask = 0700
        printable = Yes
        print ok = Yes
        browseable = No

        comment = Printer Drivers
        path = /var/lib/samba/printers
        valid users = root, smbguest
        read only = No

[for sharing]
        comment = windows file sharing
        path = /home/manihome/for sharing
        valid users = root, smbguest
        read only = No

Hope my requirements are clear. and thanks for your time and answers

Question information

English Edit question
Ubuntu samba Edit question
No assignee Edit question
Solved by:
Last query:
Last reply:
Revision history for this message
Thomas Krüger (thkrueger) said :

Just for your understanding: SMB aka the Windows file sharing system is not a typical client / server architecture.
Infact every machine serves the purpose of both client and server. It is more like an P2P architecture.
That means if you access a resource (file share, printer, ...) on a remote machine, you are a client, if a remote machine access a resource on your system you are a server. Both can happpen at the same time.
So, there is no actual need (or way) to define the role.

Also one of your pathes contains a space, it is possible it has to be put in quotes:
/home/manihome/for sharing → "/home/manihome/for sharing"

Revision history for this message
S.S.Mani (airomatic) said :

thank you first for taking time to read my very long posting.

I did that but nothing changed.

Then i went on trying so many things and now more complications.

i am able to see th network, but clicking any file in a computer says timeout on server! At times it is asking for some authentication.

 I know I am not listing my question clearly.

Wish me good luck for the problem to solve.

At least if I can find a way to totally uninstall kubuntu so that i can reinstall once again, i am not succeeding there also!

Thanks once again, sincerely.

Revision history for this message
S.S.Mani (airomatic) said :

I posted a few questions here and I got many sincere answers. Thanks for everyone.

However i was not able to solve my problem of accessing other network computers from mu Kubuntu and also my kubuntu was not showing in other computers.

I have now successfully uninstalled Kubuntu using OS uninstaller. I propose to reinstall directly 14.04 LTS unlike my earlier method of 12.04 and updating it, and hope to succeed.

However i want to record one peculiar(my observation) thing that happened during the last attempt.

While i was trying to uninstal, for once I "Tried Kubuntu".

During that time I was able to access all network computers!

However after uninstalling and reinstalling the same version of kubuntu in the same computer in the same network, I got into the same network issues as earlier! I wonder why?

The only difference, to my knowledge in my installation was, during installtion i had allowed the third paty installations as well as updates to be installed? Could that be the reason for this behaviour?