samba - Jan 2008 - Strange issue with share visibility

I am running Samba, version 3.0.25b-1.el5_1.4 , on a Linux box running
CentOS version 5.

My smb.conf is as follows:

 

#

#======================= Global Settings
====================================
[global]

 

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH

   workgroup = FCGNET

 

# server string is the equivalent of the NT Description field

   server string = Samba Server

 

# Security mode. Defines in which mode Samba will operate. Possible 

# values are share, user, server, domain and ads. Most people will want 

# user level security. See the Samba-HOWTO-Collection for details.

#   security = user

   security = server

 

# This option is important for security. It allows you to restrict

# connections to machines which are on your local network. The

# following example restricts access to two C class networks and

# the "loopback" interface. For more examples of the syntax see

# the smb.conf man page

#;   hosts allow = 192.168.1. 192.168.2. 127.

 

# If you want to automatically load your printer list rather

# than setting them up individually then you'll need this

#   load printers = yes

 

# you may wish to override the location of the printcap file

#;   printcap name = /etc/printcap

 

# on SystemV system setting printcap name to lpstat should allow

# you to automatically obtain a printer list from the SystemV spool

# system

#;   printcap name = lpstat

 

# It should not be necessary to specify the print system type unless

# it is non-standard. Currently supported print systems include:

# bsd, cups, sysv, plp, lprng, aix, hpux, qnx

#;   printing = cups

 

# This option tells cups that the data has already been rasterized

#cups options = raw

 

# Uncomment this if you want a guest account, you must add this to
/etc/passwd

# otherwise the user "nobody" is used

#;  guest account = pcguest

  guest account = nobody

 

# this tells Samba to use a separate log file for each machine

# that connects

   log file = /var/log/samba/%m.log

   log level = 3

 

# Put a capping on the size of the log files (in Kb).

   max log size = 50

 

# Use password server option only with security = server

# The argument list may include:

#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]

# or to auto-locate the domain controller/s

#   password server = *

   password server = stant05

#;   password server = <NT-Server-Name>

 

# Use the realm option only with security = ads

# Specifies the Active Directory realm the host is part of

#;   realm = MY_REALM

 

# Backend to store user information in. New installations should 

# use either tdbsam or ldapsam. smbpasswd is available for backwards

# compatibility. tdbsam requires no further configuration.

#;   passdb backend = tdbsam

;   passdb backend = smbpasswd

 

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

# Note: Consider carefully the location in the configuration file of

#       this line.  The included file is read at that point.

;   include = /usr/local/samba/lib/smb.conf.%m

 

# Configure Samba to use multiple interfaces

# If you have multiple network interfaces then you must list them

# here. See the man page for details.

#;   interfaces = 192.168.12.2/24 192.168.13.2/24 

 

# Browser Control Options:

# set local master to no if you don't want Samba to become a master

# browser on your network. Otherwise the normal election rules apply

   local master = yes

 

# OS Level determines the precedence of this server in master browser

# elections. The default value should be reasonable

#;   os level = 33

   os level = 20

 

# Domain Master specifies Samba to be the Domain Master Browser. This

# allows Samba to collate browse lists between subnets. Don't use this

# if you already have a Windows NT domain controller doing this job

#;   domain master = yes 

   domain master = no 

 

# Preferred Master causes Samba to force a local browser election on
startup

# and gives it a slightly higher chance of winning the election

#;   preferred master = yes

   preferred master = no

 

# Enable this if you want Samba to be a domain logon server for 

# Windows95 workstations. 

#;   domain logons = yes

   domain logons = no

 

# if you enable domain logons then you may want a per-machine or

# per user logon script

# run a specific logon batch file per workstation (machine)

#;   logon script = %m.bat

# run a specific logon batch file per username

#;   logon script = %U.bat

 

# Where to store roving profiles (only for Win95 and WinNT)

#        %L substitutes for this servers netbios name, %U is username

#        You must uncomment the [Profiles] share below

#;   logon path = \\%L\Profiles\%U

 

# Windows Internet Name Serving Support Section:

# WINS Support - Tells the NMBD component of Samba to enable it's WINS
Server

#;   wins support = yes

   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

 

# WINS Proxy - Tells Samba to answer name resolution queries on

# behalf of a non WINS capable client, for this to work there must be

# at least one  WINS Server on the network. The default is NO.

#;   wins proxy = yes

   wins proxy = no

 

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names

# via DNS nslookups. The default is NO.

   dns proxy = no 

 

# These scripts are used on a domain controller or stand-alone 

# machine to add or delete corresponding unix accounts

#;  add user script = /usr/sbin/useradd %u

#;  add group script = /usr/sbin/groupadd %g

#;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d
/dev/nul

l -s /bin/false %u

#;  delete user script = /usr/sbin/userdel %u

#;  delete user from group script = /usr/sbin/deluser %u %g

#;  delete group script = /usr/sbin/groupdel %g

 

 

#============================ Share Definitions
=============================
[homes]

   comment = Home Directories

   browseable = no

   writable = yes

 

[frombangalore]

        comment = Files transferred from Bangalore

        writeable = yes

        path = /home/afd/frombangalore

 

[fromnashville]

        comment = Files transferred from Nashville

        writeable = yes

        path = /home/afd/fromnashville

 

 

 

The strange part is that if I execute the "net view" command from a
DOS
prompt, I will get the listed shares, but if I run the "smbclient -L"
command from the Linux server, I am prompted for a password and then I
get an error message.  I know that it must be something in my config
file, I just can not seem to figure out what.

 

N:\>net view \\stalinux02

Shared resources at \\stalinux02

Samba Server

Share name     Type  Used as  Comment

--------------------------------------------------------------

frombangalore  Disk           Files transferred from Bangalore

fromnashville  Disk           Files transferred from Nashville

fromwayne      Disk           Files transferred from Wayne

The command completed successfully.

 

 

[root@stalinux02 samba]# smbclient -L stalinux02

Password: 

session setup failed: NT_STATUS_LOGON_FAILURE

 

 

Pati 

"UNIX is user friendly. It's just picky about who it's friends
with."

 


This email may contain material that is confidential, privileged, and/or
attorney work product for the sole use of the intended recipient.  Any review,
reliance, or distribution by others or forwarding without express permission is
strictly prohibited.  If you are not the intended recipient, please contact the
sender and delete all copies.

> [root@stalinux02 samba]# smbclient -L stalinux02
>
> Password:
>
> session setup failed: NT_STATUS_LOGON_FAILURE
>
>
Is root a valid user in your PDC?

John

On Jan 29, 2008 8:35 AM, Moss, Patricia <pmoss@fcg.com>
wrote:
> Honestly, I don't believe so.
> Is there a way to test using the root account, or any other non-PDC
> account?
>
Use the -U parameter to smbclinet to specify a valid user.

John

On Jan 29, 2008 8:40 AM, Moss, Patricia <pmoss@fcg.com>
wrote:
> I don't know if I worded that correctly.
> What I'm trying to say is that there are going to be Unix users, that
> don't have PDC accounts that will need to access these shares.  Is that
> possible?
>
I believe you need accounts on the PDC. You can use smbusers to map
each unix username to a samba username on the PDC if needed.

I have all my unix and windows users authenticated via LDAP. Samba and
pam are both using ldap for the passwords and accounts.

John

> I have one more question for you.  If the users only want 1 specific
account
> to access the shares, how do I handle that?  This is actually on a
different
> server now.  This server is running Solaris 10.
>
I am a little confused at what you are looking for. I mean does this
one account already exist in the PDC (samba side not unix)? Can every
user have the password and username for this account?

John

On Jan 29, 2008 9:52 AM, Moss, Patricia <pmoss@fcg.com>
wrote:
> I am confused by samba side versus Unix side.
> The account is created on the Linux server but is not a PC account on
> our company domain.
> All users that use this account have the password for it.
>
You need to create a samba user account on stant05 for this user.

Are you using ldap?

John

On Jan 29, 2008 10:01 AM, Moss, Patricia <pmoss@fcg.com>
wrote:
> I am not.  I know I am going to run into a roadblock when I request that
> user on the PC server.  Is there any other way to gain access to the
> shares?
>
Is there any reason why you can not have your CentOS  box be its own
password server? I mean you create the samba users on that box
instead.

John

On Jan 29, 2008 10:08 AM, Moss, Patricia <pmoss@fcg.com>
wrote:
> I'm not sure if that would have an affect on anything else that is
> accessible on the server.  There is only one way to find out.  Is it
> just a matter of changing my smb.conf to reflect the Unix server as my
> password server?
>
> Pati
Get rid of the password server line and then uncomment the passdb
backend line in your smb.conf file. Then you need to add the user on
the samba server depending on how you have you linux accounts setup
you may only need to do the smbpasswd step to add the user.

http://www.samba.netfirms.com/addusers.htm#adduser

John



-- 
John M. Drescher

On Jan 29, 2008 11:12 AM, Moss, Patricia <pmoss@fcg.com>
wrote:
>
>
>
>
> I commented out the password line and uncommented the passdb line.  It was
> set as follows:
>
>    passdb backend = smbpasswd
>
>
>
> I stopped and restarted samba and then tried the smbclient command;
>
>
>
> pasun05/# /usr/sfw/bin/smbclient -L pasun05 -U dmadmin
>
>
> Password:
>
>
>
> session setup failed: NT_STATUS_LOGON_FAILURE
>
>
>
> Here are the last few lines in the log file:
>
> [2008/01/29 11:10:27, 1] auth/auth_server.c:(363)
>
>   password server * rejected the password
>
> [2008/01/29 11:10:27, 2] auth/auth.c:(317)
>
>   check_ntlm_password:  Authentication for user [dmadmin] -> [dmadmin]
> FAILED with error NT_STATUS_WRONG_PASSWORD
>
> [2008/01/29 11:10:27, 2] smbd/server.c:(614)
>
>   Closing connections
>
Did you run smbpasswd -a dmadmin

on the samba box?

John