An Update to my Samba headaches ...

[jeager]

First of all, I want to thank all who tried to lead me down the golden path to knowledge.

Now the update - I have Samba (smbd, nmbd, etc.) running correctly on my SuSe Linux machines- YEA!! Shares and all kinds of things!

DO NOT load another application that might grab port 139 on a machine before starting a samba install. Samba uses software port 139 in the /etc/services if it is not specifically changed. The other app (an intelligent client server) I load first, took control of port 139 and held it even though I started the two daemons for samba later. 'smbd' ended up in the bit bucket and not even in the background processes. 'nmbd' was listed in the 'ps' output.

I have some windoz98 machines that will not connect but that is a known problem to me. I know how to put in a work-around. I just haven't tried it yet.

Again, thanks to all.

[mcangeli]

YAY!!! Congrats jeager....

I gotta tell you though... in slackware, all you do during the install of the OS is select samba to start at boot. Then once you have your user created on the box, add him as a samaba user.

Piece of Cake.

[jeager]

Thank you mcangeli. It was a pain in the ass, but put to sleep for now.