Announcement

**Fintan** · Apr 21, 2007, 01:24 PM

Re: [SOLVED]Samba and shares files

A really dumb question:
How or where did you delete your shares from? I did that as well in K->system config->shares. But alas to no avail. So any help would be great because this is driving me nuts.

**Fenix-TX** · Apr 21, 2007, 03:18 PM

Re: [SOLVED]Samba and shares files

Originally posted by Fintan

A really dumb question:
How or where did you delete your shares from? I did that as well in K->system config->shares. But alas to no avail. So any help would be great because this is driving me nuts.

Well, my system was upgraded from edgy to feisty and the configuration was unchanged, so on kcontrol i removed the folders that i had sharing on the K->system config->shares. I added them again, and now works.

I've had some issues like this on other aspects (video driver, scanner, and now this), so i think that some configurations when you upgrade are wrong.

**Fintan** · Apr 22, 2007, 10:38 AM

Re: [SOLVED]Samba and shares files

That did nothing for me.
I am just going to do a fresh install. I thought upgrading from beta to full would...
anyway I'll get back and report if it helps. I am not upgrading my edgy, i still need that.

EDIT: You may find this interesting:
https://bugs.launchpad.net/ubuntu/+s...mba/+bug/95460

samba 3.0.24 on feisty is broken

**Fenix-TX** · Apr 23, 2007, 05:47 AM

Re: [SOLVED]Samba and shares files

Strange, for me deleting my shares and adding again solved my problem.
I can the related command on konsole: smbclient //127.0.0.1/my_shared_folder (where my_shared_folder is a folder that i have shared) and i can connect.

Perhaps there is something weird on smb.conf, perhaps deleting (before made a backup) and configuring samba again, solve the problem. I don't know...

**Fintan** · Apr 23, 2007, 05:52 AM

Re: [SOLVED]Samba and shares files

As long as it works

Do you have RW on your shares ifrom win?

**Fenix-TX** · Apr 23, 2007, 06:40 AM

Re: [SOLVED]Samba and shares files

Yes, i can read and write from windows to my shared folder on Feisty, and i can read and write from feisty to windows. Perhaps it can be hosts.deny or something like that?

This is my smb.conf

Code:

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

[global]

## Browsing/Identification ###

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

# 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

# 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 = 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 = 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/Samba-HOWTO-Collection/ServerType.html
# in the samba-doc package for details.
;  security = user

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

# 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 <<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\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/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
restrict anonymous = no
domain master = no
preferred master = no
max protocol = NT
ldap ssl = No
server signing = Auto
security = share
netbios name = TUXCT
acl compatibility = winnt

# 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
;[homes]
;  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.)
;[netlogon]
;  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
;[profiles]
;  comment = Users profiles
;  path = /home/samba/profiles
;  guest ok = no
;  browseable = no
;  create mask = 0600
;  directory mask = 0700

[printers]
comment = All Printers
path = /tmp
printable = yes
create mask = 0700
printer name = EPSONDX5000
guest ok = yes
force user = nobody
use client driver = yes

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
case sensitive = no
guest ok = yes
msdfs proxy = no
read only = no

[JUEGOS]
path = /media/Datos/Juegos
guest ok = yes
read only = no

[Datos]
path = /media/Datos/Compartido
guest ok = yes
read only = no

**Guest** · Apr 23, 2007, 07:50 AM

Re: [SOLVED]Samba and shares files

I had the same problem with a clean install of feisty.

I solved the problem by commenting out any line of:

msdfs proxy = no

and everything works fine.

Nathan

**Fintan** · Apr 23, 2007, 01:32 PM

Re: [SOLVED]Samba and shares files

A quote from your smb.conf:

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
case sensitive = no
guest ok = yes
msdfs proxy = no (should read: #msdfs proxy=no )
read only = no

**Fenix-TX** · Apr 24, 2007, 03:31 AM

Re: [SOLVED]Samba and shares files

No i don't have commented that line and works fine here. My problem was resolved when i deleted and added again my shared folders, and my printer works fine too (well, i'm using cups instead of samba to shared my printer because is faster, so i haven't tried using my printer with samba).

**Fintan** · Apr 24, 2007, 07:24 AM

Re: [SOLVED]Samba and shares files

I finally found the problem. I had to unmount all shares, reboot, remount all the shares, give them rw and reboot again.

Deleting the shares wasn't good enough.hmmmm...

No i don't have commented that line and works fine here.

maybe that works in the printer$ section??

Happy days are here again

**Fenix-TX** · Apr 24, 2007, 07:33 AM

Re: [SOLVED]Samba and shares files

Originally posted by Fintan

I finally found the problem. I had to unmount all shares, reboot, remount all the shares, give them rw and reboot again.

Deleting the shares wasn't good enough.hmmmm...

No i don't have commented that line and works fine here.

maybe that works in the printer$ section??

Happy days are here again

Well i don't know if works on printer section because i have configured all computers to use cups instead of samba, i have not tried if works or not.

**Fintan** · Apr 24, 2007, 07:38 AM

Re: [SOLVED]Samba and shares files

Yes cups is fatser thatn smaba

Announcement

[SOLVED]Samba and shares files

[SOLVED]Samba and shares files

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment