Mailinglist Archive: opensuse (1599 mails)

[Marc Chamberlin <marc@xxxxxxxxxxxxxxxxxx>]

Marc Chamberlin wrote:
> Lars Müller wrote:
> > On Sun, Oct 25, 2009 at 05:25:23AM -0400, Michael S. Dunsavage wrote:
> >  
> > > Marc Chamberlin wrote:
> > >    
> > > > Michael S. Dunsavage wrote:
> > > >      
> > > > > > Sure Michael, sure appreciate your taking the time to help me with
> > > > > > this! What follows is my smb.conf file..  This is set up for my SOHO
> > > > > > network at home...
> > > > > >
> > > > > >   Marc..
> > > > > >
> > > > > >
> > > > > >
> > > > > > # Samba config file created using SWAT
> > > > > > # from UNKNOWN ()
> > > > > > # Date: 2009/10/24 11:11:56
> > > > > >
> > > > > > [global]
> > > > > >    workgroup = CHAMBERLIN
> > > > > >    interfaces = eth1
> > > > > >               
> > > > > why eth1 and not eth0?  Do you have 2 NIC's? Try commenting that line
> > > > > out and restarting smb.
> > > > >           
> > > > Yes I have two NIC's.  eth0 connects to the wild outside world. eth1
> > > > connects to my internal network. This computer acts as my gateway and
> > > > protects my internal network with a firewall.
> > > >
> > > >   Marc..
> > > >
> > > >       
> > > Try putting this by interfaces:
> > >
> > >  interfaces = eth1 192.168.1.1 (change that ip to whatever your 
> > > local ip is for eth1)
> > >     
> >
> > Why should the IP address be added in addition to the NIC name?
> >
> > It might be required to add 127.0.0.1 to the list of interfaces.  In
> > particular if you set "bind interfaces only = Yes" (the default is No).
> >
> > The alternative might be to use "smbpasswd -r <remote machine>".
> >
> >  
> > > I got that from:
> > >
> > > http://www.faqs.org/docs/securing/chap29sec284.html
> > >     
> >
> > I consider this as an example.  It's enough to use the interface name or
> > the IP address.
> >
> > Lars
> >   
> I tried to add the IP addresses as suggested, but that made no 
> difference.  The parameter "bind interfaces only" is set to the 
> default of No.
>
> I don't understand the suggestion of setting the smbpasswd -r for a 
> remote machine. I guess I don't understand why passwords would have 
> anything to do with this problem, and for what remote machine would I 
> set it for?
>
> On a slightly related front, it appears I have been in communication 
> with Lars apparently, via a bug report I submitted about smbstatus not 
> working. It appeared that some files were missing that was preventing 
> it from running, and that discussion has led me to believe I don't 
> have the latest version of samba installed, and YaST is not allowing 
> me to access it for SuSE11.0  I am now wondering if perhaps getting 
> this later version of Samba - ver 3.2.4.4.8 might solve it.  I have 
> version 3.2.4.4.7 and YaST is not giving me any indication that a 
> later version is available... So how do I talk YaST into giving me 
> this newer version of Samba?
>
>   Marc...
Lars helped me to figure out what was going on with YaST and the 
installation of files on my system. (Much appreciated his help!) Version 
3.2.4.4.7 is the correct version, I somehow had gotten the wrong 
architecture versions of the samba-client package installed. Have no 
idea why but figured out how to correct it. Anywise that fix did not 
solve the socket bind problem I am observing in the log files, though 
for the most part the Samba server seems to be working ok. I can at 
least mount samba shares and navigate ok from across my network to this 
particular computer.

 Marc...



--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx