Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

About a year ago, I successfully set up my LAMP server with some samba shares.

At that time, I have created a share that points to /media/data/www/clients/client1/web2/web. that folder has mode 710, because of my LAMP suPHP config, but despite that mode, I can share that folder and have write permission on it. I have created the share with usershare add command:

sudo net usershare add server /media/data/www/clients/client1/web2/web "" mgscr0_it:f guest_ok=n

The command created this file:


This is how it looks ls -la on that folder

drwx--x--- 29 web2 client1 4096 may 22 03:05 /media/data/www/clients/client1/web2/web

Today, I have created a new website, so I went to my server and created a new share to point it to my new site doc root /media/data/www/clients/client1/web6/web. I have used the very same usershare add command, but changing the folder and share name:

sudo net usershare add newsite /media/data/www/clients/client1/web6/web "" mgscr0_it:f guest_ok=n

The command created this file:


This is how it looks ls -la on that folder

drwx--x--- 3 web6 client1 4096 may 22 03:08 /media/data/www/clients/client1/web6/web

The issue is that I can access and modify my shared files on server shared folder but I can't even browse newsite shared folder.

I tryed changing mode on /media/data/www/clients/client1/web6/web to 770 and with that mode I can browse and edit files, but my server fails (suPHP complains about 770 mode).

I think I have added something to a user group but can't remember exactly what I have done before!

The question is ¿what I'm missing here?, because my previous shares are working ok.

Using Samba version 3.6.3 on ubuntu 12.04 completely updated.

This is my testparm output

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Press enter to see a dump of your service definitions

    workgroup = MGS
    server string = %h
    map to guest = Bad User
    obey pam restrictions = Yes
    pam password change = Yes
    passwd program = /usr/bin/passwd %u
    passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
    unix password sync = Yes
    syslog = 0
    log file = /var/log/samba/log.%m
    max log size = 1000
    name resolve order = wins lmhosts host bcast
    dns proxy = No
    usershare allow guests = Yes
    usershare owner only = No
    panic action = /usr/share/samba/panic-action %d
    idmap config * : backend = tdb

    comment = All Printers
    path = /var/spool/samba
    create mask = 0700
    printable = Yes
    print ok = Yes
    browseable = No

    comment = Printer Drivers
    path = /var/lib/samba/printers
share|improve this question

1 Answer 1

Well, I was shure I missed something that I didn't remember.

The issue was the user that access that new share. As this share is in another ISPConfig virtual host configuration, It's assigned another user, in this case was web6, si, to fix this, I have to create a new Shell user through ISPConfig.

After that, in my server box, I have to add that user to the samba users file with the very same password for the shell access, and at the end, create the sambashare for that user.

After doing that, my new share worked as expected, asking for password to browse and given read/write permission to the correct user only.

This time, I have written everything for future reference..jeje

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.