problem with config of samba2.03 on VMS5.5-2 / UCX 4.1
Klaus Thonke
klaus.thonke at physik.uni-ulm.de
Fri Mar 1 12:15:44 GMT 2002
Since I installed Samba 2.03 replacing 1.9.17p4, I cannot get the network
running correctly, although I use the old smb.conf file.
The VAX is visible for the Win PCs as a member of the workgroup, but I
cannot browse or connect to a specific exported drive --> some error message
like ".. network path not found" is displayed.
When I try to connect from my W2K PC, I find the following in the logit
file:
==================================================================
[2002/02/25 11:58:48, 2]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]INTERFACE.C;1:(213)
Added interface ip=134.60.22.21 bcast=134.60.255.255 nmask=255.255.0.0
[2002/02/25 11:58:50, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(155)
Failed to set socket option TCP_NODELAY
[2002/02/25 11:58:51, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
WARNING: no chroot!
[2002/02/25 11:58:52, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(810)
getpeername failed. Error was invalid argument
[2002/02/25 11:58:52, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(855)
getpeername failed. Error was invalid argument
[2002/02/25 11:58:52, 0] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]ACCESS.C;1:(252)
[2002/02/25 11:58:52, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(810)
getpeername failed. Error was invalid argument
[2002/02/25 11:58:52, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(855)
getpeername failed. Error was invalid argument
Denied connection from UNKNOWN (0.0.0.0)
[2002/02/25 11:58:52, 1]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.SMBD]PROCESS.C;1:(557)
[2002/02/25 11:58:52, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(855)
getpeername failed. Error was invalid argument
Connection denied from 0.0.0.0
[2002/02/25 11:59:15, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(411)
write_data: write failure. Error = broken pipe
[2002/02/25 11:59:16, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(190)
write_socket: Error writing 5 bytes to socket 3: ERRNO = broken pipe
[2002/02/25 11:59:16, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(572)
Error writing 5 bytes to client. -1. Exiting
[2002/02/25 11:59:20, 2]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]INTERFACE.C;1:(213)
Added interface ip=134.60.22.21 bcast=134.60.255.255 nmask=255.255.0.0
[2002/02/25 11:59:21, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(155)
Failed to set socket option TCP_NODELAY
[2002/02/25 11:59:23, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(155)
Failed to set socket option TCP_NODELAY
[2002/02/25 11:59:24, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
WARNING: no chroot!
[2002/02/25 11:59:24, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(810)
getpeername failed. Error was invalid argument
[2002/02/25 11:59:24, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(855)
getpeername failed. Error was invalid argument
[2002/02/25 11:59:24, 0] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]ACCESS.C;1:(252)
[2002/02/25 11:59:24, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(810)
getpeername failed. Error was invalid argument
[2002/02/25 11:59:24, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(855)
getpeername failed. Error was invalid argument
Denied connection from UNKNOWN (0.0.0.0)
[2002/02/25 11:59:33, 1]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.SMBD]PROCESS.C;1:(557)
[2002/02/25 11:59:33, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(855)
getpeername failed. Error was invalid argument
Connection denied from 0.0.0.0
[2002/02/25 11:59:33, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(411)
write_data: write failure. Error = broken pipe
[2002/02/25 11:59:33, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(190)
write_socket: Error writing 5 bytes to socket 3: ERRNO = broken pipe
[2002/02/25 11:59:34, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(572)
Error writing 5 bytes to client. -1. Exiting
$
=========================== my smb.conf-File:
================================
; Configuration file for smbd.
; Template for VMS
; For the format of this file and comprehensive descriptions of all the
; configuration option, please refer to the man page for smb.conf(5).
;
; The following configuration should suit most systems for basic usage and
; initial testing. It gives all clients access to their home directories and
; allows access to all printers specified in /etc/printcap.
;
; Things you need to check:
; --------------------------
;
; 1: Check the path to your printcap file. If you are using a system that
does
; not use printcap (eg., Solaris), create a file containing lines of the
; form
;
; printername|printername|printername|
;
; where each "printername" is the name of a printer you want to provide
; access to. Then alter the "printcap =" entry to point to the new file.
;
; If using Solaris, the following command will generate a suitable
printcap
; file:
;
; lpc status | grep ":" | sed s/:/\|/ > myprintcap
;
; 2: Make sure the "print command" entry is correct for your system. This
; command should submit a file (represented by %s) to a printer
; (represented by %p) for printing and should REMOVE the file after
; printing.
;
; One most systems the default will be OK, as long as you get "printing
="
; right.
;
; It is also a good idea to use an absolute path in the print command
; as there is no guarantee the search path will be set correctly.
;
; 3: Make sure the "printing =" option is set correctly for your system.
; Possible values are "sysv", "bsd" or "aix".
;
; 4: Make sure the "lpq command" entry is correct for your system. The
default
; may not work for you.
;
; 5: Make sure that the user specified in "guest account" exists. Typically
; this will be a user that cannot log in and has minimal privileges.
; Often the "nobody" account doesn't work (very system dependant).
;
; 6: You should consider the "security =" option. See a full description
; in the main documentation and the smb.conf(5) manual page
;
; 7: Look at the "hosts allow" option, unless you want everyone on the
internet
; to be able to access your files.
;
[global]
workgroup = HLP
dead time = 10
map archive = no
; printing = bsd
; printcap name = /sys$manager/ucx$printcap.dat
load printers = no
; status = yes
; print command = print %f/queue=%p/delete/passall/name="""""%f"""""
; lprm command = delete/entry=%j
security = user
default service = default
create mode = 0777
hosts allow = 134.60.22.0/255.255.255.0
remote announce = 134.60.22.255/hlp
server string = Samba V%v %h Bomem-Vax
; interfaces 134.60.22.21/24
guest account = nobody
guest ok = no
;
; This next option sets a separate log file for each client. Remove
; it if you want a combined log file.
; log file = /samba_log/log.%m
log level = 3
log file = /dka300/samba203/log/logit
; read raw = no
read prediction = yes
socket options = TCP_NODELAY
; socket options = SO_REUSEADDR
; smbrun = smbrun
; 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/var/locks
share modes = no
[homes]
comment = Meine Bomem-Files auf Benutzerplatte /dkb300/user/<account>
browseable = no
; browseable = yes
guest ok = no
public = no
; path = /dkb300/user/%S
read only = no
; andere duerfen lesen:
create mask = 0744
[user]
comment = allg. Bomem-Benutzerplatte /dkb300/user (nur Lesen)
; browseable = no
browseable = yes
guest ok = no
public = no
path = /dkb300/user
read only = yes
create mask = 0700
read list = @users
[myshare]
comment = Fuer den Boss
path = /dkb300/user
valid users = system
public = no
writable = yes
; printable = no
create mask = 0765
[dka300]
comment = Systemplatte 1
path = /dka300
valid users = system
public = no
writable = no
[dka200]
comment = Systemplatte 2
path = /dka200
valid users = system
public = no
writable = no
;[printers]
; comment = All Printers
; path = /dsa1/pcfs_spool/default
; browseable = no
; printable = yes
; public = no
; public = yes
; writable = no
; create mode = 0700
; you might also want this one
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
;
; Other examples.
;
; A private printer, usable only by fred. Spool data will be placed in
fred's
; home directory. Note that fred must have write access to the spool
directory,
; wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
;
; A private directory, usable only by fred. Note that fred requires write
; access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
;
; A publicly accessible directory, but read only, except for people in
; the staff group
;[public]
; comment = Public Stuff
; path = /usr/somewhere/public
; public = yes
; writable = no
; printable = no
; write list = @staff
;
; a service which has a different directory for each machine that connects
; this allows you to tailor configurations to incoming machines. You could
; also use the %u option to tailor it by user name.
; The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writeable = yes
;
;
; A publicly accessible directory, read/write to all users. Note that all
files
; created in the directory by users will be owned by the default user, so
; any user with access can delete any other user's files. Obviously this
; directory must be writable by the default user. Another user could of
course
; be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
;
;
; The following two entries demonstrate how to share a directory so that two
; users can place files there that will be owned by the specific users. In
this
; setup, the directory should be writable by both users and should have the
; sticky bit set on it to prevent abuse. Obviously this could be extended to
; as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
============================================================================
=====
The problem is similar when trying to connect from WinNT or Win98 clients.
Does anybody have a hint what to change?
Thanks for any help!
Klaus
=============================
Priv. Doz. Dr. Klaus Thonke
Abteilung Halbleiterphysik
Universitaet Ulm
Albert-Einstein-Alle 45
D 89069 Ulm
Tel. ++49 - 731 - 50- 26131
FAX: - 26108
WWW: http://hlhp1.physik.uni-ulm.de
=============================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Klaus Thonke.vcf
Type: text/x-vcard
Size: 430 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-vms/attachments/20020301/e369da0a/KlausThonke.vcf
More information about the samba-vms
mailing list