I have a samba PDC. and I am using the version 2.2.3a. The clients are
windows 2000 Advanced Server.
My samba is compilet with these options:
./configure --prefix=/usr --with-configdir=/etc/samba --with-logfilebase=/va
r/log/samba --with-ssl --with-quotas --with-privatedir=/etc/samba/private --
with-lockdir=/var/locks --with-swatdir=/usr/swat
I copied a file named radicali05.jpg on a share, and three files appeared in
the directory, with these names.
What is going on?
-rwx------ 1 davide users 107243 Dec 22 01:40 radicali05.jpg*
-rwx------ 1 davide users 5068 Dec 22 01:40
radicali05.jpg:\005Q30lsldxJoudresxAaaqpcawXc:$DATA*
-rwx------ 1 davide users 0 Dec 22 01:40
radicali05.jpg:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA*
This is my smb.conf
[global]
; Who I am
netbios name = LINUX
workgroup = PIPPO
server string = Main Storage
; What will I do to Windows Machines
os level = 99
preferred master = yes
domain master = yes
local master = yes
domain logons = yes
socket options = TCP_NODELAY
; Where Should I write what I am doing
log file = /var/log/samba/samba.%m
max log size = 5000
debug level = 2
; How should user behave
security = user
encrypt passwords = yes
domain admin group = @adm
domain guest group = @guest
printer admin = @adm
name resolve order = wins dns
write cache size = 262144
logon path = \\%N\profiles\%u
logon drive = Z:
logon home = \\LINUX\%u
logon script = logon.cmd
add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u
wins proxy = yes
wins support = yes
dns proxy = yes
load printers = no
ssl = no
time server = yes
#============================ Share Definitions
=============================
; The first two directories MUST exist to let SAMBA work as PDC
[netlogon]
; Put here any script that sholud be exexute at logon
comment = Netlogon
path = /mnt/fs2/netlogon
writeable = no
write list = root
allow hosts = 172.30.30.0/255.255.255.0
[profiles]
; Here will be stored all personal things, also windows shit
comment = profiles
path = /mnt/fs2/ntprofile
writeable = yes
create mask = 0600
directory mask = 0700
allow hosts = 172.30.30.0/255.255.255.0
[homes]
; This dir will be mount as Z: in your windows system
comment = Home Directories
path = /mnt/fs2/homes/%S
browseable = no
writable = yes
allow hosts = 172.30.30.0/255.255.255.0
[public]
comment = Public Stuff
path = /mnt/fs2/public
public = yes
writable = yes
allow hosts = 172.30.30.0/255.255.255.0
[napster]
comment=Mega Archivio MP3
path=/mnt/media/mp3
public= yes
writeable= yes
allow hosts = 172.30.30.0/255.255.255.0
[image]
comment=Archivio Immagini
path=/mnt/fs2/picture
public= no
writeable= yes
allow hosts = 172.30.30.0/255.255.255.0
[burn]
comment=Directory per Masterizzare
path=/mnt/burn
public= yes
writeable= yes
allow hosts = 172.30.30.0/255.255.255.0
[video]
comment=Archivio Video
path=/mnt/fs2/video
public= no
writeable= yes
allow hosts = 172.30.30.0/255.255.255.0
[backup]
comment=Backup Storico
path=/mnt/fs2/backup
public= no
writeable= yes
allow hosts = 172.30.30.0/255.255.255.0
[oldocs]
comment=Documenti OLD
path=/mnt/fs2/oldocs
public= no
writeable= yes
allow hosts = 172.30.30.0/255.255.255.0
Davide Parise
E-Mail: d.parise@agora.it
Hi folks I hope someone might be able to shed some light on a problem that I am experiencing with a Samba server. I installed this server about 2 and a half years ago on a client's site. The server has been running fine. We are now experiencing two problems which according to the client occured overnight. The first problem started about a week and a half ago when they found that when trying to access their accounts from a Windows 2000 workstation using Sage Accounting, the workstation would appear to freeze. They went through Sage support and came to the conclusion that there was no problem with Sage, it had to be the server or the workstation. Since his other MS 98 workstations seemed to still work fine, we thought it had to be the MS 2000 work station. He did find however, that when the workstation seemed to hang, he could get it out of it's state by pulling out the network cable. The confusing part however is that this happened overnight. Does anybody have any ideas as to what might be causing this - how can I be sure that it is not a Samba problem. The next problem came up a few days later. The client found that he couldn't access any of his .csv files on the server. When trying to access them using Excel, he would get an error: The file may be read-only, or you may be trying to access a read-only location. Or, the server the document is stored on may not be responding. He can however, save an xls file to exactly the same location and still open it without a problem. This problem occurs from all the work stations. I checked the user rights on the files and they are exactly the same for the xls and the csv file, ie rwx for the user. I found the following type of entries in the log: couldn't find service c [2003/11/10 15:16:59, 0] smbd/service.c:make_connection(252) workstation (10.0.0.12) couldn't find service fileserve and [2002/03/13 17:04:35, 0] smbd/oplock.c:oplock_break(768) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file SHARED DATA/LINE 50 Product CSV/Uploaded to Line 50/Castle Boilersuits .csv (dev = 305, inode = 1847780). [2002/03/13 17:04:35, 0] smbd/oplock.c:oplock_break(841) oplock_break: client failure in oplock break in file SHARED DATA/LINE 50 Product CSV/Uploaded to Line 50/Castle Boilersuits .csv [2002/03/13 17:04:35, 0] smbd/reply.c:reply_lockingX(4328) reply_lockingX: Error : oplock break from client for fnum = 12197 and no oplock granted on this file (SHARED DATA/LINE 50 Product CSV/Uploaded to Line 50/Ca stle Boilersuits .csv). I have oplocks set to no in the conf file. I don't know anything about oplocks. Can someone perhaps help or suggest something. Thanks Jannetta