From rjpower@washington.edu Sun Mar 26 13:50:33 2000 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA34676 for ; Sun, 26 Mar 2000 13:50:32 -0800 Received: from sttlpop5.sttl.uswest.net (sttlpop5.sttl.uswest.net [206.81.192.5]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id NAA28493 for ; Sun, 26 Mar 2000 13:50:31 -0800 Received: (qmail 26115 invoked by alias); 26 Mar 2000 21:50:31 -0000 Received: (qmail 26107 invoked by uid 0); 26 Mar 2000 21:50:31 -0000 Received: from ssdslppp180.sttl.uswest.net (HELO athlon600) (216.160.111.180) by sttlpop5.sttl.uswest.net with SMTP; 26 Mar 2000 21:50:31 -0000 Message-ID: <000d01bf976d$4897ca80$0400000a@athlon600> From: "Russell Power" To: References: Subject: Re: Samba question Date: Sun, 26 Mar 2000 13:50:21 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 That was it. Thanks, --Russell ----- Original Message ----- From: T. Tam To: UW Linux Group Sent: Sunday, March 26, 2000 1:31 PM Subject: Re: Samba question > Russel: > > What do you have in your /etc/smb.conf file for the line that > reads: > > interface= > > It should read: > > interface=your ip/24 (assuming that the netmask is 255.255.255.0) > > Terence > > On Sun, 26 Mar 2000, Russell Power wrote: > > > Hi, > > > > This isn't specific to Linux, but I figured it was worth a shot. Out of > > boredom, I decided to play around with the samba client on my local network. > > Using the rpms of version 2.0.5, I installed it, and everything works okay, > > except for the fact that I can't attach to any computers. It looks like the > > client is trying to use my loopback device to connect - and I'm not sure how > > to tell it to use the ethernet adapter. Here's what I get: > > > > [root@russserver russell]# smbclient -L \\Athlon600 > > Added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0 > > Connection to Athlon600 failed > > > > [root@russserver russell]# smbclient -L \\Athlon600 > > Added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0 > > Connection to Athlon600 failed > > > > [root@russserver russell]# smbclient -L \\10.0.0.4 > > Added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0 > > session request to 10.0.0.4 failed > > > > session request to *SMBSERVER failed > > [root@russserver russell]# smbclient -L -I 10.0.0.4 > > Added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0 > > Connection to -I failed > > > > It always says its adding an interface to 127.0.0.1 - even if I take down my > > loopback device. Is this normal? I know the computer I'm trying to connect > > to is working, as I can get to it via Windoze... > > > > Thanx, > > > > --Russell > > > > > > -- > > /* ------------------------------------------------------------- > Terence Tak-Shing Tam > http://students.washington.edu/ttstam/ > > "Our yellow sun yields to the dark, as I begin my web-based lark, > Flowing turning, thru the pipes, I grep for text and dump the hype, > But as I ride the fibre trail, I test my faith as as I read my mail, > Even as my bandwidth fattens, I question life and 1-click patents, > Although I ask and though I query, I know the truth, I grok the theory, > Life is a multimedia of sins, so he who collects the most m-peg wins > > -=- Illiad, UserFriendly.org > --------------------------------------------------------------*/ > .