SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Smb4k has nothing to do with Samba v4, it stand for smb for kde, where smb is the Windows protocol name.
You can get a tgz package linuxpackages at this url: http://www.linuxpackages.net/pkg_details.php?id=8014
Download it and install with installpkg.
You need to su to root to chmod the two samba executables I mentioned. Do NOT chmod +s smbmount.
I've been playing with samba lately with my home network. While looking for some ideas for my own questions I ran across your thread. Here are some thoughts that might help:
1. The sample files are just that: samples. First thing to do is rename smb.conf-sample to smb.conf (without the -sample suffix).
2. Next copy smb.conf-sample~ to smb.conf-sample. The tilde (~) means the file is a backup file. You want to restore the original sample file for future reference.
3. With that said, the /etc/samba/smb.conf is for the samba server, not the samba client. That configuration file has nothing to do with using samba as a client to connect to a Windows box.
4. To use samba to connect to your windows box, use the smbmount command. You also should learn about the smbclient command to test your connections and network.
5. You do not need to execute/run the /etc/rc.d/rc.samba script to run the samba client tools.
If you are using the stock Slackware then you have all the packages and commands already installed to run samba.
I think ? ? that all you have to do is go into 'control panel' then 'local network browsing' and just put in your windows 'user name' and windows 'password' that you use on your lan and you should be fine. that is supposed to pass your log in's for you. This would of course require you to have the same username and pass on the various windows pc's that you have on your lan, which many people do, so maybe this will take care of your issue? gl.