Hello -
I have recently upgraded my rh linux system from rh 6.2 to rh 7.0. Prior to
the upgrade, I had samba correctly configured and working to allow password
protected shares from the linux box to a win2k box that I also have on a
private network. Since the upgrade it has not worked again. I have tried
running the following versions of samba:
samba-2.0.6-9
samba-2.0.7-20000425
samba-2.0.7-21ssl
samba-2.0.7-4
I copied the smb.conf from the old configuration to the new smb.conf
location, and I started it up - and not it won't work. Also, note that the
win2k box has already had the registry hack to make it send plain text
passwords.
In all cases, the win2k box shows the 'server' (that's the netbios
name as
well as the computer name) in the network neighborhood, but will not allow it
to be expanded. I have gotten various errors from "semaphore timeout"
to
"network path not found" or "network path not accessible."
I get a constant
error message in the log that says -
[2001/01/05 00:15:25, 0] lib/util_sock.c:write_socket_data(540)
write_socket_data: write failure. Error = Broken pipe
[2001/01/05 00:15:25, 0] lib/util_sock.c:write_socket(566)
write_socket: Error writing 4 bytes to socket 7: ERRNO = Broken pipe
[2001/01/05 00:15:25, 0] lib/util_sock.c:send_smb(754)
Error writing 4 bytes to client. -1. Exiting
The smb.conf file I've been using is:
# Samba config file created using SWAT
# from home.ritz.2y.net (192.168.0.1)
# Date: 2000/10/27 00:13:13
# Global parameters
[global]
workgroup = BRAGAW
netbios name = SERVER
server string = Samba Main Server
interfaces = 192.168.0.20/24
security = SHARE
debug level = 0
log file = /var/log/samba/log.%m
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
os level = 0
domain master = Yes
dns proxy = No
comment = server linux box
hosts allow = 192.168.0. 127.
[homes]
comment = Home Directories
path = /home/%u
writeable = Yes
browseable = No
available = No
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
[tmp]
comment = Temporary file space
path = /tmp
writeable = Yes
guest ok = Yes
[chiphome]
comment = Chip's Home Directory
path = /home/cekillia
valid users = cekillia
writeable = Yes
browseable = No
[mikehome]
comment = Mike's Home Directory
path = /home/mtcrotty
valid users = mtcrotty
writeable = Yes
browseable = No
[pephome]
comment = Pepper's Home Directory
path = /home/eljobe
valid users = eljobe
writeable = Yes
browseable = No
[ccmhome]
comment = Catholic-ncsu's Home Directory
path = /home/catholic-ncsu
valid users = cekillia eljobe mtcrotty
writeable = Yes
browseable = No
Like I say - it worked before, and now I can't get it to work, and I'm
quite
baffled. Please help -
Thanks-
Chip
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at
http://webmail.netscape.com/
Chip Killian wrote:>...> [2001/01/05 00:15:25, 0] lib/util_sock.c:write_socket_data(540) > write_socket_data: write failure. Error = Broken pipe > [2001/01/05 00:15:25, 0] lib/util_sock.c:write_socket(566) > write_socket: Error writing 4 bytes to socket 7: ERRNO = > Broken pipe > [2001/01/05 00:15:25, 0] lib/util_sock.c:send_smb(754) > Error writing 4 bytes to client. -1. Exiting > > > # Global parameters > [global] > hosts allow = 192.168.0. 127...... While not related to the upgrade, this error often appears with failed reverse DNS lookups due to the hosts allow line in your smb.conf. For testing purposes, try either removing this line or adding the necessary entries to DNS (or /etc/hosts) Cheers, jerry ---------------------------------------------------------------------- /\ Gerald (Jerry) Carter Professional Services \/ http://www.valinux.com/ VA Linux Systems gcarter@valinux.com http://www.samba.org/ SAMBA Team jerry@samba.org http://www.plainjoe.org/ jerry@plainjoe.org "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
Thanks a bunch everyone for your help. I finally figured it out. The problem, it turns out - was with the reverse DNS somehow. I don't know how, but when I did a tcpdump, though I didn't understand most of it - I understood that there were icmp packets that were not reaching the server. So I looked into some newsgroups for more info about that problem, and then ended up comparing the files like /etc/hosts and /etc/resolv.conf and syncing them between my two servers. Then, after some reloads of services, the servers were working properly. Thanks Again - Chip Gerald Carter <gcarter@valinux.com> wrote:> > Chip Killian wrote: > > > > Okay - I have removed the hosts allow statement from the smb.conf file -and> > I restarted... I am now working with samba-2.0.7-4. > > > > I get the same error. > > > > When I walk through the diagnose steps - the first thing that seemspeculiar> > is that when I run > > > > smbclient -L SERVER > > > > it prompts me for a password. This is not mentioned in the diagnose page. > > The error I am getting is specifically: > > > > Error accessing network path. > > Network path does not exist. > > > Send me level 10 debug logs or the entire > smbclient connection attempt and I'll take a look. > > > > > Cheers, jerry > -- > ---------------------------------------------------------------------- > /\ Gerald (Jerry) Carter Professional Services > \/ http://www.valinux.com/ VA Linux Systems gcarter@valinux.com > http://www.samba.org/ SAMBA Team jerry@samba.org > http://www.plainjoe.org/ jerry@plainjoe.org > > "...a hundred billion castaways looking for a home." > - Sting "Message in a Bottle" ( 1979 ) >__________________________________________________________________ Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/