Samba Questions-Only Half Working

Leonard Chatagnier lenc5570 at sbcglobal.net
Fri Feb 29 06:32:50 UTC 2008


--- NoOp <glgxg at sbcglobal.net> wrote:

> On 02/28/2008 04:31 PM, Leonard Chatagnier wrote:
> 
> > What I need to know is why two identical smb.conf
> > files, one on each machine, works on one but gives
> the
> > above listed errors on the other or some clue to
> > what's causing the errors. Found one hit(ubuntu)
> > listing the error that said it may be due to not
> > having setup user ID and password in NT lan
> manager or
> > workgroup or similiar but windows not even
> envolved as
> > both machines are on gutsy, one wifi connected and
> > one(that works) wired. Desperately needing some
> clues.
> > Thanks for any,
> 
Getting out of chronoligical order on answers. Have
been offline until now after rebooting a while ago
implementing you initial input.  Damn WMP54G wifi
card; ultimately had to pull it out again to get it
working.

> Small diagram would help; you indicated that one
> works (wired) and one
> doesn't wireless - I'm unsure just what that means.
> So please clarify &
> fill in the details:
> 
> Works (file sharing both directions)
> Wired:  Yes, can copy both ways but must do it from
wired machine,

> Wireless: No, can't see or connect anyway from this
machine. Doesn't matter if I use nautilus, smbclient
or mount command, I one doesn't work, none will, I'm
sure of this.

> 
> Works one way:
> Wire: If I understand what your asking, neither
machine works just one way. The above is best I can
explain

> Wireless:
> 
> I also assume that you've run sudo smbpasswd -a
> <username> on both
> machines.
> 
Of course, have actually been able to connect from
both machines using different smb.confs.  Earlier, I
could connect(in the beginning) from the wireless
only.  I could connect and share from the
wireless(copy both ways as long as done from wireless
mach).

> Regarding the wireless: have you configured the
> wireless router firewall
> to allow samba traffic on ports 137-139? Quite often
> these ports are
> properly blocked by default and you either have to
> turn them on, or do a
> port redirect so that the traffic can connect. Are
> you running anything
> like firestarter or other software firewall on
> either machine?
> 
No activated firewalls on either machine.  Since both
machines are fresh installs(gutsy), I don't know if
any firewalls are installed. Just know that in past,
had to activate them to get them working.
Have never played with 2Wire's firewall settings and
as mentioned above, each machine worked at some point
in past time but never both ways. I think this rules
out the firewall issue.  I did talk via email to
gateway about disabling the firewall and decided it
too much a burden likely screwing up my wifi
connection again. Open to suggestions though but I
think it will cause me a lot more misery due to that
flaky wifi card.
Well, just visited gateway.2wire.net again and after
clicking around in the firewall section for the wifi
one added a samba definition allowing the tcp ports
137-139. It seemed to be accepted. Hope nothing messed
up. Now to get back to your earlier reply.
Thanks,


Leonard Chatagnier
lenc5570 at sbcglobal.net




More information about the ubuntu-users mailing list