[NBLUG/talk] why is Samba so bloody awful

Bob Blick bobblick at covad.net
Mon Nov 17 15:13:00 PST 2003


Walter Hansen said:
>      To avoid pulling hairs out use the web interface. You have to do
> some
> minor setup, but it seems to make a lot more sense in between the
> year or so that I change my samba setup.

SWAT is working, I get no errors in the smbd or nmbd log files.
LinNeighborhood shows the shares on the local machine, and if I change
things in smb.conf and restart it, those changes do take place.

It really acts almost as if there's no network cable between the two
machines, but that is not the case, vnc, ssh etc all work fine. ports
137-139 are open.

If I try to force a connection from a windows machine(NET USE..), it is
acknowledged but it won't authenticate. Looking in the log.smbd on the
linux machine, it says the user is not found in passdb. But I've run
smbadduser, the user exists and there's a password, so I guess it's just
one of those things that doesn't work because it doesn't want to.

This gets back to the original subject, "why is Samba so bloody awful"?
Neither smbd nor nmbd seem to be working properly. I've both created an
smb.conf file by hand and also let SWAT do it.

I'm open for any suggestions.

Thanks,

Bob





More information about the talk mailing list