Find the answer to your Linux question:
Results 1 to 9 of 9
Ok not sure if I should be posting this here or in Linux newbie section only been using Linux for less than a week. So bare with me please. I ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Sep 2006
    Posts
    6

    Samba issues can't connect to share


    Ok not sure if I should be posting this here or in Linux newbie section only been using Linux for less than a week. So bare with me please.

    I installed fedora core 5 and trying to set up samba so that my winxp boxes can have a general shared folder.

    right now I am able to see the share on one of my xp boxes but I can not access the share gives me the standard.

    "file is not accessible you might not have permissions to use network resource. contact..... the network name can not be found"

    not sure where I went wrong but any help or pointer would be great.

    if more infromation is need please let me know.

    here is my smb.conf file

    [global]
    netbios name = FILESERVER
    server string = fserver
    username map = /etc/samba/smbusers
    log file = /var/log/samba/%m.log
    max log size = 50
    load printers = No
    show add printer wizard = No
    os level = 2
    preferred master = No
    local master = No
    domain master = No
    dns proxy = No
    ldap ssl = no
    hosts allow = 192.168.1.0/255.255.255.0
    cups options = raw

    [printers]
    comment = All Printers
    path = /usr/spool/samba
    printable = Yes
    browseable = No

    [Family files]
    path = /home/fshare/
    valid users = @cooper
    read only = No
    case sensitive = No
    strict locking = No
    wide links = No
    msdfs proxy = no

    Thanks in advance

    Ganther

  2. #2
    Super Moderator Roxoff's Avatar
    Join Date
    Aug 2005
    Location
    Nottingham, England
    Posts
    3,878
    I believe your problem is caused by security system differences between samba and windows.

    What you need to do is:

    - Add a line 'workgroup = <workgroup_or_domain_name>' to your [global] section in smb.conf. This must match the domain or workgroup name applied to the windows machines. If they all use windows xp home, then I think it's fixed at 'workgroup' for those machines (I could be wrong, though, and I'm sure someone will point it out if I am).

    - Add a line which says 'encrypt passwords = yes' to your [global] section of smb.conf.

    - Make sure each windows user has a username an password on their local windows machine(s).

    - Use the 'smbpasswd' command on the linux machine to add samba users that exactly match the windows logon credentials your set up in the previous step (check the manpage for it but it should be as simple as 'smbpassword -a <username>'.

    - If any windows user name is different to the linux username on the server, then set up a mapping between the linux name and the windows name in the /etc/samba/smbusers file.

    - Restart samba and test. Dont forget that windows users will have to log-on correctly before they get access to any of the services, and make sure your unix groups (particularly the 'cooper' group) are set up correctly in /etc/groups.
    Linux user #126863 - see http://linuxcounter.net/

  3. #3
    Linux Enthusiast KenJackson's Avatar
    Join Date
    Jun 2006
    Location
    Maryland, USA
    Posts
    510
    Also, there is no security line in [global]. Although the default is security = user, so it may not be a problem.

    From 'man smb.conf', way down at line 5382:
    If your PCs use usernames that are the same as their usernames
    on the UNIX machine then you will want to use security = user.
    If you mostly use usernames that don't exist on the UNIX box
    then use security = share.

    You should also use security = share if you want to mainly setup
    shares without a password (guest shares). This is commonly
    used for a shared printer server. It is more difficult to setup guest
    shares with security = user, see the map to guestparameter for
    details.

  4. #4
    Super Moderator Roxoff's Avatar
    Join Date
    Aug 2005
    Location
    Nottingham, England
    Posts
    3,878
    Quote Originally Posted by KenJackson
    Also, there is no security line in [global]. Although the default is security = user, so it may not be a problem.

    From 'man smb.conf', way down at line 5382:
    Whoops; yes, thanks Ken, I missed that - but like you said, 'security = user' is the default.
    Linux user #126863 - see http://linuxcounter.net/

  5. #5
    Just Joined!
    Join Date
    Sep 2006
    Posts
    6
    Started from scratch restored smb.conf, deleted shared dir, deleted group, recreate dir, created group, added users to group added group to share changed permission to rwxrwx---

    Used swat to screate samba share, I can see my home directory and the share, I can access my home directory but not my share I get the attached error.

    I have a feeling my permissions are not set right.


    # Samba config file created using SWAT
    # from 127.0.0.1 (127.0.0.1)
    # Date: 2006/09/08 23:00:35

    [global]
    workgroup = workgroup
    netbios name = FILE SERVER
    encrypt password = yes
    server string =
    log file = /var/log/samba/%m.log
    max log size = 50
    os level = 2
    dns proxy = No

    [homes]
    comment = Home Directories
    read only = No
    browseable = No

    [share]
    path = /home/samba/share/
    valid users = @cooper
    write list = @cooper
    read only = No
    hosts allow = 192.168.1/255.255.255.0
    case sensitive = No
    strict locking = No
    msdfs proxy = no
    Attached Images Attached Images

  6. #6
    Just Joined!
    Join Date
    Apr 2005
    Posts
    62
    did you add that certain user that belongs to a group cooper to smbpasswd database...?

    root:
    Code:
    smbpasswd -a certain-user

  7. #7
    Just Joined!
    Join Date
    Sep 2006
    Posts
    6
    checked the smbpasswd database users were already there but did the command again. restarted samba and still get the same error message when trying to access the one share.

  8. #8
    Linux Enthusiast
    Join Date
    Dec 2004
    Posts
    637
    Under the global section, insert the following:

    security = user

    Then, restart smb and see what happens.

  9. #9
    Just Joined!
    Join Date
    Sep 2006
    Posts
    6
    Thanks everyone for your input and help.. Figured out the issue turned out to be an issue with the permissions for the group on a parent folder that was causing the problem. Again thanks for all the help

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •