Re: [newbie] Samba a no-go
thats my problem,too. i configured bastille a few times now, and with allow=icmp and allow 139 and so on, the netbios ports still are closed on my internal trusted nic. i just cant get bastille to leave everything opened on it. also on the external nic everything is closed, although i told bastille to let the icmps open,.. regards On Wed, 6 Jun 2001, Civileme wrote: > On Tuesday 05 June 2001 23:50, s wrote: > > Hi all, > > I know it's a long shot anyone being able to help on such a project with so > > many variables, but I need to try... > > > > I'm trying to configure it, but it just won't work. I bascally followed > > the plan layed out at: > > http://www.linuxnewbie.org/nhf/intel/network/samba/samba1.html > > with a little: > > http://us1.samba.org/samba/docs/Samba-HOWTO-Collection.html#AEN209 on the > > side. > > > > However it's a no-go. Anyone seen errors like: error connecting to > > 127.0.0.1:139 (connection refused) when testing with smbclient -L > > localhost ? I have tripled checked the all files and such and just can't > > eyeball the problem. I reconfigured firewall using BastilleInteractive and > > tried to leave ports 137 & 139 open to internal interfaces. So if course > > none of the computers knows too much about the others existance, other than > > returned ping packets. > > > > I hate to lay out all the boring gory details right off the bat. If this > > rings any bells to anyone and need more info, I'll gladly post it. I would > > appreciate your help on this. > > > > As always, > > TIA, > > -s > > Take down the firewall > > Implement Samba > > Bring up the firewall, step by step, which is particularly easy to do with > Bastille. > > You are not going anywhere wuth so many variables to juggle, and it looks > like a firewalling problem. > > Civileme > > >
Re: [newbie] Samba a no-go
On Tuesday 05 June 2001 23:50, s wrote: > Hi all, > I know it's a long shot anyone being able to help on such a project with so > many variables, but I need to try... > > I'm trying to configure it, but it just won't work. I bascally followed > the plan layed out at: > http://www.linuxnewbie.org/nhf/intel/network/samba/samba1.html > with a little: > http://us1.samba.org/samba/docs/Samba-HOWTO-Collection.html#AEN209 on the > side. > > However it's a no-go. Anyone seen errors like: error connecting to > 127.0.0.1:139 (connection refused) when testing with smbclient -L > localhost ? I have tripled checked the all files and such and just can't > eyeball the problem. I reconfigured firewall using BastilleInteractive and > tried to leave ports 137 & 139 open to internal interfaces. So if course > none of the computers knows too much about the others existance, other than > returned ping packets. > > I hate to lay out all the boring gory details right off the bat. If this > rings any bells to anyone and need more info, I'll gladly post it. I would > appreciate your help on this. > > As always, > TIA, > -s Take down the firewall Implement Samba Bring up the firewall, step by step, which is particularly easy to do with Bastille. You are not going anywhere wuth so many variables to juggle, and it looks like a firewalling problem. Civileme
Re: [newbie] Samba a no-go
--- s <[EMAIL PROTECTED]> wrote: > I've got all those files, but who knows what is > wrong in them? > > But let me ask, (I feel so silly) but (a) the > netbios name would be the > computer's name or the network's name. I believe I > have it as the computer's > name presently. (b) And in windows, is the host > name the same as the netbios > name? > (c) Netbios name on the linux machine that > would be the first part of > the variation on localhost.localdomain? > > I've put all of them on the same workgroup name, I > think. (d) The workgroup > name would be the second part of the above reference > variation? > > tia, > -s > > Ps. Let me just post my lmhost & hosts files and > see if they look right to > you please. (I know something must be wrong > somewhere.) I have four > machines with one as a gateway and the samba server. > > /etc/lmhosts: > > 127.0.0.1 localhost > 192.168.0.1 localmachine > <-- mandrake gateway > Burner'swork Burner'swork > <-- windows machine > Nightrunner Nightrunner > <-- windows machine > tuxmachine tuxmachine > <-- mandrake workstation > > /etc/hosts: > > 127.0.0.1 localhost.localdomain localhost > 192.168.0.1 localmachine.snetwork localmachine > 192.168.0.3 Burner'swork.snetwork Burner'swork > 192.168.0.4 Nightrunner.snetworkNightrunner > 192.168.0.2 tuxmachine.snetwork tuxmachine > > > thanks again. > > > a) The computers name. My /etc/lmohosts is like: 192.168.0.1 bustedbox 192.168.0.2 graffix b) I think so but I could be wrong. I don't do windows often. I configured it once and backed it up so I'd never have to go through it again :) c) Yep d) Err um no. You set in your windows network tab thingies (<--very technical term there) somewhere. For example the howto with my network card said to put all the machines in the linksys workgroup. You set it in the same spot that you set the name of the pc if i remeber correctly. Hey I just realized I too am unable to connect to localhost (127.0.0.1) but I never tried till now. Try smbclient -L localmachine (I'm assuming that localmachine is really the name of the server your setting up) maybe it's just something with localhost. Your /etc/hosts looks cool but the /etc/lmhosts needs to look like mine I think (well mine woorks for me YMMV). Good Luck. BTW testparm is a utility that will check your smb.conf file and tell you if it's good. It has a man page. __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
Re: [newbie] Samba a no-go
On Tuesday 05 June 2001 07:24 pm, you wrote: > --- s <[EMAIL PROTECTED]> wrote: > > Hi all, > > I know it's a long shot anyone being able to help on > > such a project with so > > many variables, but I need to try... > > > > I'm trying to configure it, but it just won't work. > > Ok without your config file (/etc/smb.conf) it's > pretty difficult to tell what could be wrong. But > maybe check to see if localhost is in /etc/lmhosts and > check to see if your ip is in the host allow line in > your smb.conf file. One more thing, and I know this > sounds stupid but I've done it alot; After making > changes to the config files make sure you run > /etc/rc.d/init.d/smb restart (or start if it's not > already running). Good luck and btw theres a really > basic howto on mandrakeuser.org that has helped me > notice the little thing before. The URL is > http://www.mandrakeuser.org/docs/connect/csamba.html > It spans about 5 pages but it normally take five > minutes to skim through and check your files for any > obvious errors you may have overlooked. > I've got all those files, but who knows what is wrong in them? But let me ask, (I feel so silly) but (a) the netbios name would be the computer's name or the network's name. I believe I have it as the computer's name presently. (b) And in windows, is the host name the same as the netbios name? (c) Netbios name on the linux machine that would be the first part of the variation on localhost.localdomain? I've put all of them on the same workgroup name, I think. (d) The workgroup name would be the second part of the above reference variation? tia, -s Ps. Let me just post my lmhost & hosts files and see if they look right to you please. (I know something must be wrong somewhere.) I have four machines with one as a gateway and the samba server. /etc/lmhosts: 127.0.0.1 localhost 192.168.0.1 localmachine <-- mandrake gateway Burner'swork Burner'swork <-- windows machine Nightrunner Nightrunner<-- windows machine tuxmachine tuxmachine <-- mandrake workstation /etc/hosts: 127.0.0.1 localhost.localdomain localhost 192.168.0.1 localmachine.snetwork localmachine 192.168.0.3 Burner'swork.snetwork Burner'swork 192.168.0.4 Nightrunner.snetworkNightrunner 192.168.0.2 tuxmachine.snetwork tuxmachine thanks again.
Re: [newbie] Samba a no-go
--- s <[EMAIL PROTECTED]> wrote: > Hi all, > I know it's a long shot anyone being able to help on > such a project with so > many variables, but I need to try... > > I'm trying to configure it, but it just won't work. > I bascally followed the > plan layed out at: > http://www.linuxnewbie.org/nhf/intel/network/samba/samba1.html > with a little: > http://us1.samba.org/samba/docs/Samba-HOWTO-Collection.html#AEN209 > on the > side. > > However it's a no-go. Anyone seen errors like: > error connecting to > 127.0.0.1:139 (connection refused) when testing with > smbclient -L localhost > ? I have tripled checked the all files and such and > just can't eyeball the > problem. I reconfigured firewall using > BastilleInteractive and tried to > leave ports 137 & 139 open to internal interfaces. > So if course none of the > computers knows too much about the others existance, > other than returned ping > packets. > > I hate to lay out all the boring gory details right > off the bat. If this > rings any bells to anyone and need more info, I'll > gladly post it. I would > appreciate your help on this. > > As always, > TIA, > -s Ok without your config file (/etc/smb.conf) it's pretty difficult to tell what could be wrong. But maybe check to see if localhost is in /etc/lmhosts and check to see if your ip is in the host allow line in your smb.conf file. One more thing, and I know this sounds stupid but I've done it alot; After making changes to the config files make sure you run /etc/rc.d/init.d/smb restart (or start if it's not already running). Good luck and btw theres a really basic howto on mandrakeuser.org that has helped me notice the little thing before. The URL is http://www.mandrakeuser.org/docs/connect/csamba.html It spans about 5 pages but it normally take five minutes to skim through and check your files for any obvious errors you may have overlooked. __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
[newbie] Samba a no-go
Hi all, I know it's a long shot anyone being able to help on such a project with so many variables, but I need to try... I'm trying to configure it, but it just won't work. I bascally followed the plan layed out at: http://www.linuxnewbie.org/nhf/intel/network/samba/samba1.html with a little: http://us1.samba.org/samba/docs/Samba-HOWTO-Collection.html#AEN209 on the side. However it's a no-go. Anyone seen errors like: error connecting to 127.0.0.1:139 (connection refused) when testing with smbclient -L localhost ? I have tripled checked the all files and such and just can't eyeball the problem. I reconfigured firewall using BastilleInteractive and tried to leave ports 137 & 139 open to internal interfaces. So if course none of the computers knows too much about the others existance, other than returned ping packets. I hate to lay out all the boring gory details right off the bat. If this rings any bells to anyone and need more info, I'll gladly post it. I would appreciate your help on this. As always, TIA, -s
