Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
using samb version 3.0.10 or something close to that.
Just setting up a simple share for all the users on my box just a test I have severl smb.conf's most have lots of stuff in them but I always get stuck on the same part. when I try and access any share I get a message on the windows box saying
\\servername\homes is not accessible.
The network name cannot be found
here is the most basic stripped down smb.conf I have tried.
[global]
workgroup = workgroup
server string = Samba is fantastic
security = share
encrypt passwords = Yes
[homes]
comment = Home Directories
read only = No
create mask = 0750
Also just to add detail.
When I open My Computer and type in the address \\eagle I get prompted for a password I type in the username and the password and it accepts it and then it show me a list of the shares, then when I click on the share thats when I am getting this message.
Here is my smb.conf that I use at home. The home share works and the data share works.
[global]
workgroup = mydomain
server string = myserver
security = user
hosts allow = 192.168.0. 127.
load printers = yes
log file = /var/log/samba.%m
max log size = 10000
socket options = TCP_NODELAY
local master = yes
os level = 65
preferred master = yes
wins support = yes
dns proxy = no
[homes]
comment = Home Directories
browseable = no
writable = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
[data]
comment = Shared Data
path = /pub/data
valid users = bob tom sam
write list = bob tom
read list = sam
public = no
writable = yes
printable = no
create mask = 0775
It is set to be the master browser and WINS server. It is setup to allow access to 192.168.0.0/255.255.255.0 network only.
Not sure what it was, but I wasn't able able to access the home directories. was very odd. but I just made a new directory in the /home and it works just fine. So I think my problem is fixed.
Where is the standard place to store shares? in var or pub? like if I wanted to make a directory called smbshares and then put a bunch f directories below that which are shared?
Where is the standard place to store shares? in var or pub? like if I wanted to make a directory called smbshares and then put a bunch f directories below that which are shared?
I think that is a personal prefference thing. I prefer to make a partition and name it /pub. I seen some distros use /usr/share/pub and /var/pub. A common file stystem hierarchy is one of the things that I would like to see all distro adopt. I know some would argue, but it would make it easier on users and programmers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.