| tconrad 2004-01-23, 7:27 pm |
| I have been using Samba for a while now and never had this problem on RedHat
7.2, 7.3 or 8.0; now I am using RH 9.0 in conjuction with samba 3.0.0 and
am experiencing a strange problem. Any help would be greatly appreciated;
thanks in advance.
This is my complete 'smb.conf' file where the problem occurs.
[global]
workgroup = abc
netbios name = xyz
server string = Samba Server
security = SHARE
encrypt passwords = yes
log file = /var/log/samba/%m.log
max log size = 50
name resolve order = wins host
socket options = IPTOS_LOWDELAY TCP_NODELAY
load printers = no
show add printer wizard = no
os level = 65
preferred master = no
local master = no
domain master = no
browse list = no
dns proxy = no
wins server = 10.10.10.200
remote announce = 10.10.10.200
remote browse sync = 10.10.10.200
socket address = 10.10.10.215
guest account = joe
create mask = 0644
hosts allow = 10.10.10. 127.
printing = lprng
short preserve case = no
mangle case = yes
[tmp]
comment = tmp share
path = /share/tmp
force user = joe
force group = joe
read only = yes
guest ok = yes
The samba share 'tmp' shows up just fine and any user can browse it
just fine. However some files, while they are visible, cannot be opened.
Example Using MS Office 2002 SP-2 & AutoCAD 2002
Case 1: *.doc files open perfectly.
Case 2: *.xls files don't open on the first attempt, but they do on
the second attempt. On the first attempt to opent the file the error the
program reports is the "The 'filename' could not be found".
Case 3: *.dwg files don't open at all (These are AutoCAD Drawing
Files). The error the program reports is the "The 'filename' could not
be found".
I have another identical server where the "read only = yes" line is
commented out, and everything works just fine.
All unix file permissions are 644 and all directory permissions are
755. Also, all files and directories in the '/share' directory had the
following command run on them 'chown -R joe.joe', so they all belong
to the guest account.
Additional testing revealed that even if the the share itself is not read
only but there are files/directories on that share which, for example
belong to root but still have the same unix permissions, the exact same
problem still occurs.
I am thinking this whole problem could be tied in with an error I am seeing
repeatedly in the 'smbd.log' file:
[2003/12/17 10:18:51, 0] lib/util_sock.c:get_socket_addr(919)
getpeername failed. Error was Transport endpoint is not connected
I mention this because the 'smbstatus' command returns the IP addresses of
the computers on the network connected to the share rather than the NetBIOS
name, which is what I typically would see.
|