[Samba] User not reported on file locked message
Bruce Hohl
brucehohl at access-4-free.com
Tue Mar 8 02:18:01 GMT 2005
I have a very small problem. Thanks for any suggestions.
Say user1 logs onto a Windows XP workstation and opens
file1. Then, if user2 attempts to open the file from
another workstation the following message is displayed:
"file1 is locked for editing by ''"
Problem: *user1* is not displayed between the single quotes.
However, say user1 logs onto a Win98 workstation and opens
file1. Then, if user2 attempts to open the file the
expected message is displayed: "file1 is locked for editing
by 'user1'".
Maybe (?) this is related to the above problem:
I have also noted that the smbstatus command always shows
the text Machine name for Win98 clients but for WinXP
clients only sometimes the text Machine name is shown, but
usually the IP address is shown:
filesrv1:~ # smbstatus
Samba version 3.0.9-2.1.6-SUSE
PID Username Group Machine
-----------------------------------------------------------------
27745 user1 Domain Users 192.168.1.49
(192.168.1.49) XP box
27739 user2 Domain Users 192.168.1.44
(192.168.1.44) XP box
27753 user3 Domain Users 192.168.1.40
(192.168.1.40) XP box
27880 user4 Domain Users spickett98
(192.168.1.207) 98 box
1317 user5 Domain Users darmc
(192.168.1.14) XP box
28480 user6 Domain Users saw
(192.168.1.251) 98 box
Environment:
SLES 9 + Samba 3.0.9 from SuSE update service joined to
Win2K domain.
[global]
workgroup = GROTECOMPANY
realm = GROTECOMPANY.COM
security = ADS
map to guest = Bad User
password server = visual1, filesrv2, *
log level = 1
socket options = TCP_NODELAY SO_RCVBUF=8192
SO_SNDBUF=8192
preferred master = No
local master = No
domain master = No
wins server = 192.168.1.201 192.168.1.55
ldap ssl = no
idmap backend = idmap_rid:GROTECOMPANY=10000-20000
allow trusted domains = No
idmap uid = 10000-20000
idmap gid = 10000-20000
winbind separator = /
winbind use default domain = Yes
printer admin = GROTECOMPANY/administrator
admin users = GROTECOMPANY/administrator
log file = /var/log/samba/%M.log
I also get the same behavior on my Samba test box which is
running SuSE 9.1 with Samba 3.0.11.
More information about the samba
mailing list