Ed Sanborn said:
>Date: Tue, 9 Mar 1999 14:06:46 -0500
>From: "Sanborn, Ed" <esanborn@northc.com>
>To: "Samba List (E-mail)" <samba@samba.anu.edu.au>
>Cc: "Sanborn, Ed" <esanborn@northc.com>
>Subject: Ditch Samba in favor of Exceed!
>Message-ID:
<C1E763AF1EB6D21197170090271E09B202E595@forge.northc.com>
>That is what I'm thinking of doing if I can't resolve this?
>PLEASE, some kind soul help me on this. I have shares from
>a Solaris 2.6 system running the new Samba 2.02 release.
>Everything runs fine except that every so often (sometimes
>way more often than I like) shared resources convert over to
>the Samba guest account which is setup to go to the default
>account "nobody". Why does Samba do this? Everything seems
>fine for someone and then this happens. If they
>logoff and log back on to their NT systems thing's are
>fine again. I am using server style security.
>Why does this keep happening? I clipped out the top 5 lines.
There
>are actually alot more instances of this but I thought I'd spare
you
>the length.
><root@brigade:/raid5/tools/samba/bin>./smbstatus|grep nobody
>hw_root nobody nobody 231 massacre (192.168.164.115)
Mon Mar 8
>21:00:27 1999
>public nobody nobody 6879 stamp (192.168.164.146)
Tue Mar 9
>10:48:56 1999
>sw_root nobody nobody 6879 stamp (192.168.164.146)
Tue Mar 9
>10:48:56 1999
>IT Softwar nobody nobody 22192 sgt (192.168.164.122)
Mon Mar 8
>21:01:20 1999
>hw_root nobody nobody 22192 sgt (192.168.164.122)
Mon Mar 8
>21:01:21 1999
><root@brigade:/raid5/tools/samba/bin>
I am running Linux 2.0.30 with a few W95.SR2 boxen on an isolated
network. I am also running another Linux 2.0.30 with about 20-40 W95 boxen
on a corporate mixed ipx-Novell/tcpip network behind a firewall. I have
experienced the above with all Samba versions I have used but have only
taken notice since 1.9.18p4. I am now running 2.0.2 (or should that
be 2.0p2). Both of these Linux boxen are using small dead-time
values and I suspect that
the invalid guest access occurs during automatic reconnection.
More worrisome is that I have occasionally had the situation occur
that several non-public
shares would only be connected to as guest, even immediately after a
cold reboot of the
workstation. The cure in these cases was to delete the username.PWL
file (cached passwords) on the workstation; reboot the workstation and
login, typing in passwords as
requested. In a few of the worst cases I have also had to change
access passwords at
the Linux end and/or disconnect the workstation from the shares and
reconnect.
All of the above has led me to assume that the problem is at least
initiated by a W95 bug
or is caused by poor installation. Since someone else has had
similar experiences I am
finally moved to announce it. Here follows a portion of my
smb.conf.
[global]
server string = CPNB's Linux/Samba %v Science Server.
; max disk size = 10
debug level = 1
status = yes
domain master = yes
preferred master = yes
wins support = yes
domain logons = yes
null passwords = yes
Unix password sync = true
passwd program = /usr/bin/passwd.linux
dos filetime resolution = yes
fake directory create times = yes
os level = 64
; os level = 1
workgroup = CPN_BRANCH
encrypt passwords = yes
security = USER
; security = SHARE
; protocol options are CORE, COREPLUS, LANMAN1, LANMAN2, NT1.
Default is NT1
protocol = NT1
hide dot files = yes
load printers = no
printing = BSD
printcap name = /etc/printcap
print command = /usr/bin/lpr -h -r -P %p %s
lpq command = /usr/bin/lpq %p
lprm command = /usr/bin/lprm -P %p %j
lppause command = /usr/bin/lpc down %p Printer %p stopped by
Samba user %U from %m at %T
lpresume command = /usr/bin/lpc up %p; /usr/bin/lpc start %p
mangled names = no
preserve case = yes
short preserve case = yes
; case sensitive = yes
guest account = guest
read size = 1500
lpq cache time = 5
socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_THROUGHPUT
SO_RCVBUF=4096 SO_SNDBUF=4096
deadtime = 3
read prediction = yes
; This next option sets a separate log file for each client. Remove
; it if you want a combined log file.
; log file = /usr/local/samba/var/log.smb.%U
; You will need a world readable lock directory and "share
modes=yes"
; if you want to support the file sharing modes for multiple users
; of the same files
lock directory = /usr/local/samba/locks
share modes = yes
strict locking = yes
; This section makes their home directory available to all account
holders
[homes]
comment = Home Directory
public = no
guest ok = no
browseable = no
writeable = yes
printable = no
veto files
/.bash_history/.dir_colors/.kermrc/.less/.lessrc/.login/.mc.ini/.mc.tree/.sa
mba.login/.samba.logout/.Xdefaults/
create mode = 0600
oplocks = true
root preexec = /usr/local/samba/lib/login.sh %u
root postexec = /usr/local/samba/lib/logout.sh %u
==================================== _--_|\
peter.sanders@dsto.defence.gov.au (Business)
/ DSTO \ Combatant Protection & Nutrition Branch, AMRL.
\_.--._/ Defence Science & Technology Organisation
v Fax : 61-3-9626 8410 Voice: 61-3-9626 8411
Peter Sanders
sandersp@melbpc.org.au (Private)
Voice: 61-3-9337-6612
BMW K100RT (Brunnhilde the Blue)
=====================================