-   Linux - Networking (
-   -   Need some help setting up networking (

thekid 11-06-2007 01:08 AM

Need some help setting up networking
Both machines, which are running Kubuntu Feisty, are wired through a linksys router and are receiving IP's. I can connect to the internet on both, and they can ping eachother, as well as print to my network printer. I have shared both my home directories through NFS, but I cannot see the directory, nor the machines for that matter. When I look in System Services, networking, nfs-common and nfs-kernel-server are not running, nor will they start, and they are all set to start on boot. What am I missing? Thanks!

ranger_nemo 11-06-2007 11:54 AM

You are missing LISA. It allows network browsing.

There is a section in the control center where you configure it. Then, you start is as any normal service. Then, you can access a list of computers on the network, much like network neighborhood in Windows.

I'm at work, and can't remember specifics off the top of my head. I'll write again this evening if somebody else doesn't fill in the missing info.

thekid 11-06-2007 04:47 PM

OK, got LISA installed on both, and they appear to see eachother cuz now I get an authentication error when I try to connect by doing

in Konqueror. I have the local network in the remote places now, but the machines aren't showing up, so I will need to spend some more time going over networking when I get home later.

keratos 11-06-2007 05:44 PM


xubuntu is much easier than that...

1. Get rid of NFS and use Samba

2. Install "samba" server package from synaptic.

3. Then, from start menu in xubuntu choose system->Shared Folders.

4. Click add and add your share. Give it a name and make sure Share Through is set to SMB. If you assign a network domain/group name the same as Windows, then any linux and windows, Xbox etc client can see them!!!

5. As root, enter: /etc/init.d/samba restart


depending on how you are accessing your shares, you may need a separate client to see the share - e.g. xubuntu Thunar file manager cannot "see" samba shares, not natively anyway.

To test you could, as root, enter:

cd /tmp
smbget smb://<host>/<share>/<a file name>

<host> is the host name of the smb server (the pc you installed samba on). You can get the hostname by the command "hostname".
<share> is the share name you assigned the folder (as above)
<a file name> any file in the share folder.

If everything is setup okay, the file will be copied to /tmp

Check setup with the command "smbtree" as root.

lazlow 11-06-2007 06:07 PM

Be aware that samba is known to run considerably slower than NFS.

You might look and see if you have the right ports open. Do not know about buntu but on Fedora hosts.allow, and exports are also involved.

keratos 11-06-2007 06:14 PM


Originally Posted by lazlow (Post 2950378)
Be aware that samba is known to run considerably slower than NFS.

You might look and see if you have the right ports open. Do not know about buntu but on Fedora hosts.allow, and exports are also involved.

Says WHO?

OMG. This is a REALLY old debate, like the GNOME versus KDE issue.

EVERYONE but everyone has a view on this.

We could forum this for a day and eternity.

For every link you provide to NFS being superior, I could probably provide one to academia research here at UCL UK on smb/samba being more responsive.

It depends on what you are doing and the size and location of the blocks constituting the filesystems.

I'm not getting into the debate, period!

thekid: Just try both and see which one suits you.

p.s. I dont have any special ports open LAN side of the router!!

thekid 11-07-2007 02:18 AM

Ok, I got Samba setup, and using Smb4k, I can see the respective machines, but I cannot connect, because it keeps asking for authentication data, i.e. username and password, and I don't know what it wants. Any clues?

keratos 11-07-2007 07:42 AM

For info (in laymen terms)

The samba server needs to authenticate access to the files, just as a login server ("login:") would ask you to enter a username and password for the session.

A client connecting to a smb chare may not necessarily be a linux O/S or a Windows O/S. Provided it knows how to "talk samba" then it can see the share - but it cannot connect to the files in the share, until it provides a user name and password assigned by the samba server.

You just need to set this up. Its pretty simple.

You've done the "hard bit".

Okay, post the output of your /etc/samba/smb.conf file.

thekid 11-07-2007 09:29 AM


# 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
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentary and a ; for parts of the config file that you
# may wish to enable
# 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 =======================


## Browsing/Identification ###

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

# server string is the equivalent of the NT Description field

# 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

# What naming service and in what order should we use to resolve host names
# to IP addresses
;  name resolve order = lmhosts host wins bcast

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

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).
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 #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
security = share

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true

# 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

;  guest account = nobody
invalid users = root

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

# 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\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\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 = no

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
;  domain logons = yes
# The following setting only takes effect if '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
;  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

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
;  load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;  printing = bsd
;  printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;  printing = cups
;  printcap name = cups

# When using [print$], root is implicitly a 'printer admin', but you can
# also give this right to other users to add drivers and set printer
# properties
;  printer admin = @lpadmin

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

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#        SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;  message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
;  domain master = auto

# 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

#======================= 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, \\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
;  valid users = %S

# By default, the home directories are exported read-only. Change next
# parameter to 'yes' if you want to be able to write to them.
;  writable = no

# File creation mask is set to 0600 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0664.
;  create mask = 0600

# 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

# 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
;  writable = no
;  share modes = no

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

path = /home/keith/
guest ok = yes
case sensitive = no
strict locking = no
msdfs proxy = no
read only = no
hosts allow =

keratos 11-07-2007 11:00 AM

change end of file to :-


path = /home/keith/
guest ok = yes
read only = no
browseable = yes
public = yes

delete all lines after the "public = yes" line

keratos 11-07-2007 11:00 AM

..and then as root enter:-

/etc/init.d/samba restart

thekid 11-08-2007 02:22 PM

Great thanks! I got everything working now and am able to share my stuff across my network. Just curious, do you know how I can get movies to play on my laptop from the PC without having to copy it to the tmp folder first? I open it with Mplayer, but it copies it before playing, and I would rather it stream it.

keratos 11-08-2007 04:36 PM


unfortunately I dont use mplayer however if a samba share can be seen then there is no reason for a file to be copied. example: I have an Xbox that can see a linux filesystem on which is mounted a WindowsXP partition containing music+video. Nothing gets copied in my setup.

does mplayer have any "buffering" options I wonder, like to smooth playback it may be copying part or all of the file to /tmp?

have you tried other media players? look in synaptic.

All times are GMT -5. The time now is 06:46 AM.