No File sharing on Windows Networks

[jdunn]

I installed SAMBA on a fresh install of Feisty and I have a Windows XP computer in my network. I've shared files successfully in the past between the two machines when I ran previous versions of Kubuntu (dapper, edgy). Now, no matter what I try, I can't share between the two machines. I first tried gui samba config. Then I tried manual changes to the smb.conf file. I made changes per this bug report https://bugs.launchpad.net/ubuntu/+s...mba/+bug/95460. I can ping both machines. Its as though there is a firewall or something blocking smb file sharing but I checked both machines and no firewalls are running. Is there something else in Feisty that's broken? I wouldn't be surprised.
Edit/Delete Message

jdunn@faramir:/etc/samba$ smbclient -L localhost
Password:
session setup failed: NT_STATUS_LOGON_FAILURE
jdunn@faramir:/etc/samba$ smbclient -L boromir
Connection to boromir failed

[javierrivera]

Re: No File sharing on Windows Networks

This seems to be a security related problem:

Have you created a samba user with smbpasswd?

How is your samba server security set to (i.e user, share,...)?

Javier.

[jdunn]

Re: No File sharing on Windows Networks

This seems to be a security related problem:

Have you created a samba user with smbpasswd?

Yes

How is your samba server security set to (i.e user, share,...)?

Javier.

user

[javierrivera]

Re: No File sharing on Windows Networks

Is there any additional information in the log files (/var/log/samba) log.smbd or lod.nmdb?

Javier.

[dibl]

Re: No File sharing on Windows Networks

Yep -- see also

http://kubuntuforums.net/forums/inde...opic=3082605.0

I think maybe there's a bug lurking in the Samba version for Feisty. On my system, it looks like it works fine, until I actually do the "paste" part of a file copy process. Then (and only then) it puts up an error that either the file on the Windows filesystem does not exist, or cannot be read.

But file copying works fine on the Linux system from the Windows machine, both directions.

I think we're awaiting further discoveries and announcements ....

[jdunn]

Re: No File sharing on Windows Networks

Is there any additional information in the log files (/var/log/samba) log.smbd or lod.nmdb?

Javier.

Nothing useful that I can see

log.smbd sample

[2007/04/30 07:28:49, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/30 09:14:50, 1] smbd/server.c:open_sockets_smbd(408)
 Reloading services after SIGHUP
[2007/04/30 09:14:50, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!

log.nmbd sample

[2007/04/30 00:00:39, 0] nmbd/nmbd.c:terminate(58)
 Got SIGTERM: going down...
[2007/04/30 06:16:37, 0] nmbd/nmbd.c:main(699)
 Netbios nameserver version 3.0.24 started.
 Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/04/30 06:22:20, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
 *****

 Samba name server FARAMIR is now a local master browser for workgroup WORKGROU
P on subnet 192.168.xxx.xxx

[javierrivera]

Re: No File sharing on Windows Networks

Now in the same dir log.127.0.0.1. There should be some lines there. Any tip?

How is this machine named? Boromir or Famarir?. What is the other?. windows machine?

For the logs, seems like the linux machine is Faramir, but he seems unable to see the name Boromir (in your first post).

Javier.

[jdunn]

Re: No File sharing on Windows Networks

Now in the same dir log.127.0.0.1. There should be some lines there. Any tip?

How is this machine named? Boromir or Famarir?. What is the other?. windows machine?

For the logs, seems like the linux machine is Faramir, but he seems unable to see the name Boromir (in your first post).

Javier.

Correct. Linux machine is named faramir, Windows machine is named boromir. Workgroup is "WORKGROUP".

'127.0.0.1' is the loopback address, correct? I see nothing of it in log.smbd or log.nmbd

[javierrivera]

Re: No File sharing on Windows Networks

There should be there (in /var/log/samba/) a file called:

log.127.0.0.1

Where the authentication errors from (smbclient -L localhost) should go.

Of course, it could be called log.localhost or log.faramir.

Just looking from some tip. It looks so different from dibl problems...

Javier.

[jdunn]

Re: No File sharing on Windows Networks


cores log.127.0.1.1 log.faramir log.smbd
log.127.0.0.1 log.192.168.15.200 log.nmbd


log.faramir

[2007/04/29 16:11:13, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/29 16:11:13, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/30 06:50:01, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(195)
 startsmbfilepwent_internal: file /etc/samba/smbpasswd did not exist. File succ
essfully created.
[2007/04/30 07:15:10, 0] lib/util_sock.c:read_data(534)
 read_data: read failure for 4 bytes to client 192.168.15.200. Error = Connecti
on reset by peer

[jdunn]

Re: No File sharing on Windows Networks

Here is my current smb.conf. Most of it is commented out. I made changes to [homes] in the share definitions.

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

# 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/Samba3-HOWTO/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 = 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 <<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/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
[homes]
  comment = Home Directories
  browseable = yes

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

# 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
  browseable = no
  path = /var/spool/samba
  printable = yes
  public = no
  writable = no
  create mode = 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.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
;  write list = root, @ntadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;  comment = Samba server's CD-ROM
;  writable = no
;  locking = no
;  path = /cdrom
;  public = yes

# The next two parameters show how to auto-mount a CD-ROM when the
#	cdrom share is accesed. For this to work /etc/fstab must contain
#	an entry like this:
#
#    /dev/scd0  /cdrom iso9660 defaults,noauto,ro,user  0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
#	is mounted on /cdrom
#
;  preexec = /bin/mount /cdrom
;  postexec = /bin/umount /cdrom

[penguin.ch]

Re: No File sharing on Windows Networks

This seems to be a security related problem

Right from the Samba manual (the printed version):

"If you attempt to connect with user credentials and instead get NT_STATUS_LOGON_FAILURE, verify that the account exists and you have the correct login name and password."

[2007/04/30 06:50:01, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(195)
startsmbfilepwent_internal: file /etc/samba/smbpasswd did not exist.

[jdunn]

Re: No File sharing on Windows Networks

This seems to be a security related problem

Right from the Samba manual (the printed version):

"If you attempt to connect with user credentials and instead get NT_STATUS_LOGON_FAILURE, verify that the account exists and you have the correct login name and password."

[2007/04/30 06:50:01, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(195)
startsmbfilepwent_internal: file /etc/samba/smbpasswd did not exist.

My samba username and pw = my linux username and pw = my windoze username and pw...case sensitive, letter for letter.

The smbpasswd file was only created AFTER I changed my smbpassword (Yes, I already had a pw...It prompted me for the current + new pw + new pw retype)...Is that normal? The smbpasswd file appears to be blank but I assume it is encrypted.

[javierrivera]

Re: No File sharing on Windows Networks

No. The tdbsam backend doens't use a smbpasswd file.

Try to issue again

$ smbpasswd

Javier.

[jdunn]

Re: No File sharing on Windows Networks

I just found out the netmask in my network settings didn't match between the two machines :P. Oh well...I tried to be thorough. Having fixed that, my smb client seems to be working now, as I can connect to shares on my Windoze PC...but not the other way around. I need to take a break from this but I will come back later and attempt to get the rest of this working. Hopefully, the rest will come easy, now that I've finished overlooking the obvious :P. Thanks Jav and others for your helpful input...I may still be back here today if I have further trouble.

***Solved***