From owner-freebsd-questions Tue Aug 7 5:41:16 2001 Delivered-To: freebsd-questions@freebsd.org Received: from ritchie.compwest.net.au (ritchie.compwest.net.au [203.38.14.8]) by hub.freebsd.org (Postfix) with ESMTP id 90E1337B40C for ; Tue, 7 Aug 2001 05:40:52 -0700 (PDT) (envelope-from paul@compwest.net.au) Received: from wks (ant.parkview.compwest.net.au [203.38.14.227] (may be forged)) by ritchie.compwest.net.au (8.9.3/8.9.3/DIALixFlat) with SMTP id UAA42588; Tue, 7 Aug 2001 20:39:10 +0800 (WST) (envelope-from paul@compwest.net.au) From: "Paul Hamilton" To: "Joe Clarke" Cc: Subject: RE: Running Samba on FreeBSD 4.2 and 4.3 - errors on FreeBSD side of things! Date: Tue, 7 Aug 2001 20:41:03 +0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20010806232406.D418-100000@shumai.marcuscom.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG No, I don't have tcp_wrappers turned on, and I have "ALL : ALL : allow" in my /etc/hosts.allow file. TIA, Paul -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Joe Clarke Sent: Tuesday, 7 August 2001 11:26 AM To: Paul Hamilton Cc: questions@FreeBSD.ORG Subject: Re: Running Samba on FreeBSD 4.2 and 4.3 - errors on FreeBSD sideof things! If you have samba compiled with tcp_wrappers support, what do you have in /etc/hosts.allow? A test with: ALL : ALL : allow Should let you know if that's the problem. I'm not seeing this on 4.3 with Samba 2.0.10 compiled from ports. You should be able to open a TCP connection to port 139 on the server to make a SMB connection. Joe Clarke On Tue, 7 Aug 2001, Paul Hamilton wrote: > Hi, > > I have tried installing Samba 2.0.7 and 2.2 from the cd packages, and 2.0.9 > >from source onto FreeBSD 4.2. I kept getting: > > /usr/local/samba/bin/smbclient -d 9 -L 192.168.0.4 > > INFO: Debug class all level = 5 (pid 21362 from pid 21362) > pm_process() returned Yes > added interface ip=192.168.0.4 bcast=192.168.0.255 nmask=255.255.255.0 > Client started (version 2.2.1a). > Connecting to 192.168.0.4 at port 139 > socket option SO_KEEPALIVE = 0 > socket option SO_REUSEADDR = 0 > socket option SO_BROADCAST = 0 > socket option TCP_NODELAY = 4 > socket option IPTOS_LOWDELAY = 0 > socket option IPTOS_THROUGHPUT = 0 > socket option SO_REUSEPORT = 0 > socket option SO_SNDBUF = 17520 > socket option SO_RCVBUF = 32 > socket option SO_SNDLOWAT = 2048 > socket option SO_RCVLOWAT = 1 > socket option SO_SNDTIMEO = 0 > socket option SO_RCVTIMEO = 0 > write_socket(3,76) > write_socket(3,76) wrote 76 > Sent session request > read_socket_with_timeout: timeout read. read error = Connection reset by > peer. > size=0 > < - snip - > > > This is with the default smb.conf file, which passes testparm! Thinking > it's a 4.2 problem, I upgraded to 4.3. Same problem! I tried 2.0.8 and 2.2 > >from the packages cd, and also 2.2 built from source. > > I looked through the samba news archives, and find a few references to the > problem, but no fixes. > > I tend to think it's a FreeBSD problem, as I get the same error all the > time. I have seen a reference about trying to access udp port 0x10007 (from > memory, as I don't have access to the smbd.log file ATT. I just remember > that it was a large numbered port, and that it couldn't open it). nmbd > seems to work ok. > > Any idea's anyone? > > Thanks, > > Paul Hamilton > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message