SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm sure I'm opening myself to rtfm, but I have tried and failed...
I have one machine running 10.2, another newly loaded with 11.0 and yet another with windoze 2000. I did have samba running quite fine on the 10.2 machine, but I did something that broke it, and now I can't get it to work on either one. (That something was upgrading W2000 and finding that it no longer allowed a 2 letter workgroup, and thinking it was something wrong with samba and messing with it. That may teach me something.)
The symptoms are: I can see either machine on the Windows network, and when I try to open them I see folders for homes and Printers. However, when I try to open the homes folder from windows, I get 'homes is not accessible the network name cannot be found', and when I try to do the same from either SW box I get 'The file or folder smb://radio2/homes does not exist'.
testparm gives the following result:
cr@radio2:~$ testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
workgroup = CRCOM
server string = Samba Server
log file = /var/log/samba.%m
max log size = 50
acl compatibility = winnt
server signing = auto
preferred master = No
domain master = No
ldap ssl = no
hosts allow = 192.168.1., 127.
[homes]
guest ok = Yes
case sensitive = No
strict locking = No
msdfs proxy = no
I am not sharing printers on any machine, and the configuration on the 11.0 machine is similar.
I hate to admit it, but I can't remember - I messed around....
I thought that when I did the new install on the other machine using 11.0 it would all work again and I'd be able to fix the first one, but that didn't happen.
here is how to set it up
first copy this in your /etc/samba/smb.conf
[global]
workgroup = yourworkgroup
netbios name = machinename
encrypt passwords = Yes
log file = /var/log/samba/%m.log
LOG LEVEL = 0
max log size = 10000
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
os level = 164
preferred master = True
dns proxy = No
wins support = Yes
unix charset = ISO8859-1
dos charset = 850
[homes]
comment = Home Directories
valid users = %S
read only = No
create mask = 0664
directory mask = 0775
browseable = No
[DATA]
comment = publicly available share
path = /data
create mask = 0777
directory mask = 0777
public = yes
writable = yes
only guest = Yes
then bee sure to have a windows user in your win2k machine with password
add the same user in your slackware box with (adduser)
then do smbpasswd -a theusernameofwin2kuser
it will ask for password use the same as win2k box
test config with testparm to be sure there is no spelling probs
restart samba with: /etc/rc.d/rc.samba restart
et voila! you should be able to go to homes directories with your windows box.
Last edited by slackwareserver; 10-18-2006 at 08:43 PM.
In the future, save yourself a lot of hassle by editing /etc/inetd.conf, and uncommenting the line for 'swat', then issuing `killall -HUP inetd`. From this point on you can configure Samba using SWAT by pointing your browser at http://localhost:901.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.