I'm a very -slightly- advanced Samba user. I believe I know the basics of editing the smb.conf and I know to use smbpasswd to update the Samba users database.I have a group of identical shares.They are readOnly for the group @movies-play and they are (supposed to be) writeable by specific users. The readOnly group works great, no prob there, but I cannot get write access for the specified users. They are in the Samba user database using smbpasswd -a mark and neelix.Here is the share section in my smb.conf...
Code:
[movies-usb3]
path = /media/usb3/movies
guest ok = no[code]....
I have the workgroup and netbios info set. I have security=user set. The folder 'movies' in the path above is owned by 'mark' so it seems I should be able to write in it but I can't.I'm connecting to the share (it's on a server running Lucid) from my laptop (running Lucid. I added this mount info to fstab...
Code:
//spock/movies-usb3 /media/spockmovies3 cifs credentials=/home/mark/.smbpasswd 0 0
Of course spock in the hosts file so it resolves. I can see the share fine, just can't write.
I have this samba share for ghosting images to (backing up computers at work) and I can read the ghost images just fine from the share, but I am unable to write to the share. From any windows environment I have tried, I get a disk is full error. I have 200GB+ free space, so this is not the actual issue. I believe there is a write permission somewhere that I am overlooking. My setup basically lets me log in under the username samba from a client machine.
Here is my smb.conf file:
Code:
#======================= Global Settings ======================= [global] workgroup = discount.local server string = %h server (Samba, Ubuntu)
[code]....
I've tried chown on /media/Images to make it owned by samba, but it just reverts once I remount the partition. Either that or my eyes are playing tricks on me.
so after searching and reading, and searching some more, im stuck. i cant seem to get a mounted thumb drive to give write access. first thing to know is that, im using a seagate dockstar with a primary thumb drive[sda1] booting debian and samba.
i guess you could say im still in the testing phase, just trying to make sure files can be shared, mounted and accessed by users. the problem is stated as the title. i have successfully shared a folder in sda1 with rw access, but i cant do the same for the second drive[sdb1].
for sda1 with rw access, here are the smb.conf settings:
Code: [shared] path = share available = yes valid users = mark
I have a networked raid drive. Thecus 2100. Its running linux, and includes samba sharing. On that I have a folder shared. I can connect to and read and write from nautilus. No problems. However, I can't use other apps through that method. Its not really "mounting" that drive in the sense you'd normally think of (afaik).
If I try to mount the folder, no matter how I have tried so far (-t cifs, smbmount, etc), I can navigate the folders, but if I try to read any file I get a permission error. Looking at the permissions with 'ls -l', everything looks OK. The weird thing is, I can write a file, then read that file back as long as its the same session.
Just now I tried 'smbclient' with no special arguments. Just the server and path url. It asked for my password. Once I was in, I had no trouble getting files. I had a thread about this a while back and there were several links and all sorts of command line options to try, which I did, with no different outcome. I think its got to be something much simpler and more obvious. smbclient and nautilus seem to have no trouble. Anybody know what they're doing differently?
I have a Samba Share which is mounted on various linux systems throughout the network. Whenever any of my user access those files using vim, Gedit it works fine and get perfect permissions to read/write those files. but whenever they try to open with any php IDE (quanta plus, geany, eclipse-pdt) they get error while saving those files. I dont think it is a permission or samba issue because we are able to edit/save those files using normal editors..
i have setup a samba server and created samba shares on it, i have configured the samba server to authenticates users from a windows server 2003 DC,
i have 2 shares call IT and MYSHARE, I want to give read and write permissions to sevaral users to those two shares and read only permisson to all the other users.
i tried editing the smb.conf file with the following settings , but no one can write or modify the files in the shares including the users specified in the write list = cweerasinghe,njayarathna.
[IT] writeable = Yes browseable = yes public = no comment = IT share
[Code]....
how can i give access to the write list = cweerasinghe,njayarathna users to read, write and modify the files in the shares ??
I am using samba t share my files.I am sharing /media/MEDIA folder. it is a ntfs partition mounted with ntfs-3g with write/read access from linux.I can see and browse my shares and also create files in the root of this partition, ie /media/MEDIA, but in its subfolders i do not have write permissions.
another interesting thing is that i have permission to create directory and delete files everywhere and in any folder, subfolder but when trying to create files i get not enough free disk space error.by the way i dont know if this config file is correct, i find as template in internet.
I'm running Ubuntu 9.1 server on an PII Compaq. Read an article "Samba: How to share files for your LAN without user/password" [URL] and some others and can see and pull up files, can't change or delete. Here is my smb.conf:
# Sample configuration file for the Samba suite for Debian GNU/Linux. # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options most of which # are not shown in this example
# Some options that are often worth tuning have been included as # commented-out examples in this file. # - When such options are commented with ";", the proposed setting # differs from the default Samba behaviour # - When commented with "#", the proposed setting is the default # behaviour of Samba but the option is considered important # enough to be mentioned here .....
I'm pulling my hair out trying to figure out what is wrong with my Samba share. I have set up a directory /samba to serve up some movies, music, etc, on an Ubuntu 10.04 Server box. For now, I have given that directory 777 permissions, along with the subfolders:
Code: drwxrwxrwx 4 michal michal 4096 2010-06-22 18:02 Apps drwxrwxrwx 3 michal michal 4096 2010-06-22 19:02 Music drwxrwxrwx 3 michal michal 4096 2010-08-14 19:27 Pics drwxrwxrwx 5 michal michal 4096 2010-06-22 19:48 Video This is how my smb.conf file looks like for this particular share:
Code: [share1] comment = share1 browsable = yes path = /samba write list = michal Furthermore, I went ahead and mapped the Samba user to my Linux user account in /etc/samba/smbusers:
Code: michal = "michal" When I try to login from a Windows machine using michal as the username, I can see the folders, but I am unable to create new files on the share. Considering that the file system permissions are liberal on the share directory, I have no clue as to why I'm still getting denied write permission.
I've been reading for a while about samba but I haven't found a solution to my problem yet.I'd like to know if, the configuration I have in mind, is possible at all ("security = user" is what I'm using now).I want a directory to be: 1) read only for guests and some UNIX users; 2) write for some other UNIX users.
The advantage of this configuration would be that every single user in my LAN (with or without a UNIX account) would be able to read the content of the shared directory Music and I (UNIX user andrea) could manage the folder directly trough samba preserving the correct owner/group and permissions on the new files/folder created.
Notes about my configuration above: 1) as it is now every user gets authenticated by samba as nobody so even I (andrea) cannot write in it; 2) commenting out the line "guest ok = yes" I can authenticate as "andrea" and write in it but guest access is not possible any longer.
I just upgraded to jessie and now Samba won't let me log in anymore. I merged smb.conf manually. It now looks like this (removed comments):
Code: Select all[global] workgroup = WORKGROUP dns proxy = no bind interfaces only = no log file = /var/log/samba/log.%m max log size = 1000 syslog = 0
[Code] .....
With smbclient logs as follows: Code: Select allsmbclient -L 192...
Enter user's password: session setup failed: NT_STATUS_UNSUCCESSFUL
If I provide a wrong password, it raises NT_STATUS_LOGON_FAILURE, also if retry with the correct password.
Not sure about what resolved the issue. But after I purged samba, reconfigured it, added the users AND set www-data's shell to bash again (which was changed during the update), it now seems to work
Start>Run>\192.168.0.1storage gives me "The specified network password is not correct." It lists my domain as "ANTEC" which is the name of my computer, though I've changed the workgroup to WELLS. I've run:
I'm running ubuntu 10.04 and I need to set up samba. I haven't used samba since ubuntu 8.10 and I don't know if there have been changes that I'm not aware of. I remember it being a simple process that started with editing the configuration file, but I keep getting this message:
Code: /etc/samba/smb.conf': No such file or directory
Am I missing something? Has the configuration file changed names?
I am trying to use SWAT to better configure Samba.conf I have swat installed and working but it is missing the GLOBAL button which is its main configuration tool?
I'm getting some strange behavior when trying to create directories on an nfs share on a linux machine that I'm accessing from Mac OS X 10.4.
I can copy files but cannot create new files or directories. I've given every directory and file that's in the share directory rwx access for groups, users and owner and changed user to 777. The line I've added to my /etc/exports file is;
Code: /home/Music 10.1.1.1/24 (rw,async,no_subtree_check,insecure) how I can start trouble shooting this? If I can copy a file why can't I create a new file/directory?
Ive managed to install samba, I've shared a folder. I can access from a Windows 7 machine via \ubuntupublic. I can put files in the folder form the ubuntu machine and edit them on the windows box. I can put files in the folder/share from the Windows box but then I cannot edit them on the Ubuntu machine (they are read only and have a "Lock" over them). I can fix this by going to the properties of the file/folder in Windows and manually assigning "Everybody" full control (then the lock disappears and all is well.) I want read/write access to all the folders contents from both machines all the time (security is NOT a concern I WANT the permissions wide open) what am I doing wrong?
and I have share1 and its subfolder " subshare " the thing i have to do is that, i have 2 assign user1 and user2 to share1 that means user1 and user2 can only access share1 through password and user3 can access only its subfolder "subshare" i have done this upto first level permission of share1 not able to do for its subfolder "subshare"
I have installed ubuntu 10.10 and the Samba addon to configure my shares to my Windows terminals.This is what I got
Firewall off (utf disabled)
Internal Sata /dev/sda1 (EXT4 FS)
External USB HDD /dev/sdb1 mounted at /media/SG1500GB (EXT4 FS)
I have two shares
1. //home/test - Which I can see and access with no problems (can't write to it though even though I set the share as writable?, but, I can read from it). This is available to everyone. My windows terminal can see this folder and access it. This is on my main 80GB internal drive /dev/sda1.
2. //media/SG1500GB/Music. I set this up for everyone full access and I can see it at all my Windows machines but,I can't get into the folder. Windows keeps giving me an error stating network path not found.I also try to access it via the Nautilus (Places/Network/system/music) and get an error message "unable to mount location, Failed to mount windows share". This drive is mounted per the disk utility.
I have karmic on my laptop, and I can't access my windows network. I have had previous versions of ubuntu and managed to configure samba. However, since my last reinstall, I can't get it to work.
I am running Jaunty 9.0.4. I used system-config-samba (gui) to configure Samba. I put myself as a user and tried to map the drive from my local PC. I am unable to map the drive. On windows, I try to connect using a different user and when I select finish, it prompts me again and adds my workgroup before my user name.
When I create a new folder on my ubuntu machine and share it with my windows 7 machine using 'net usershare add <dir> <path>', I can't get write perms in Win 7. It keeps giving me a "You need permission to perform this action'. I've chmod the folder to 777 but still no luck.
The funny thing is, it was all working fine until I tried to add a new usershare yesterday (Can't think what I've changed). I use this sharing method to share all of my development /var/www/ folders so I can work on them from my win machine.
I have had a few problems with my samba smb.conf, and it nuked and rebuilt yesterday. I'm fairly new to the Linux game, and this permissions problem has me baffled.
I have mounted a samba share on my desktop from a remote server (with smb4k). There I created a symlink to "/". When I open the symlink with konqueror it opens the right one (the root directory of the server), but when i open this link with the shell (cd rootfs/), then it opens my local root directory (of my host)... Is it possible to open the right link with the shell?
My desktop is now dual boot, Xubuntu 10.10 has been added to WinXP. The attached parallel printer works fine with either OS. When running XP I can share the printer with my two XP laptops without problem. I cannot share it when the desktop is running Xubuntu. Neither laptop can see the printer. However, if I open the desktop Samba config application, change any parameter, retype in the original parameter, both laptops can see and connect to the shared printer - until I reboot the desktop