Results 1 to 8 of 8
Hello everyone,
I've got a problem with XP clients being able to write files to a SAMBA share running on Fedora Core 7. I've attached my smb.conf file and a ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-19-2010 #1Just Joined!
- Join Date
- Oct 2010
- Posts
- 4
SAMBA problem with XP clients
Hello everyone,
I've got a problem with XP clients being able to write files to a SAMBA share running on Fedora Core 7. I've attached my smb.conf file and a screenshot of what I get when I try to copy and paste any files to the share. By the way, I can create a file, as long as it stays empty, but as soon as I try to save it with any data, it says there's no space (which is obvious from the screenshot that there is plenty). Thanks for any help!
EDIT - Ok, I can't paste a link to it so if the next poster can, I would appreciate it. The address is: www . jarvistek . com/client/screenshots/error.bmp
#======================= Global Settings =====================================
Code:[global] # ------------------------- ZTAPE Options ------------------------- blocking locks = no local master = no block size = 4096 create mask = 0777 directory mask = 0777 csc policy = disable deadtime = 10 dfree cache time = 10 oplocks = False level2 oplocks = False # ----------------------- Netwrok Related Options ------------------------- # # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH # # server string is the equivalent of the NT Description field # # netbios name can be used to specify a server name not tied to the hostname # # Interfaces lets you configure Samba to use multiple interfaces # If you have multiple network interfaces then you can list the ones # you want to listen on (never omit localhost) # # Hosts Allow/Hosts Deny lets you restrict who can connect, and you can # specifiy it as a per share option as well # workgroup = workgroup server string = Samba Server Version %v # --------------------------- Logging Options ----------------------------- # # Log File let you specify where to put logs and how to split them up. # # Max Log Size let you specify the max size log files should reach # logs split per machine log file = /var/log/samba/log.%m # max 50KB per log file, then rotate, was 50 max log size = 50 # ----------------------- Standalone Server Options ------------------------ # # Security can be set to user, share(deprecated) or server(deprecated) # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. security = share passdb backend = ***** # --------------------------- Printing Options ----------------------------- # # Load Printers let you load automatically the list of printers rather # than setting them up individually # # Cups Options let you pass the cups libs custom options, setting it to raw # for example will let you use drivers on your Windows clients # # Printcap Name let you specify an alternative printcap file # # You can choose a non default printing system using the Printing option ; load printers = yes cups options = raw ; printcap name = /etc/printcap #obtain list of printers automatically on SystemV ; printcap name = lpstat ; printing = cups # --------------------------- Filesystem Options --------------------------- # # The following options can be uncommented if the filesystem supports # Extended Attributes and they are enabled (usually by the mount option # user_xattr). Thess options will let the admin store the DOS attributes # in an EA and make samba not mess with the permission bits. # # Note: these options can also be set just per share, setting them in global # makes them the default for all shares ; map archive = no ; map hidden = no ; map read only = no ; map system = no ; encrypt passwords = yes guest ok = yes guest account = root ; store dos attributes = yes #============================ Share Definitions ============================== [homes] comment = Home Directories browseable = no writable = yes ; valid users = %S ; valid users = MYDOMAIN\%S [printers] comment = All Printers path = /var/spool/samba browseable = no ; guest ok = no ; writable = No printable = yes [pictron-share] comment = Samba Share Folder path = /pictron-share writeable = yes guest ok = yes
Last edited by MikeTbob; 10-26-2010 at 11:55 AM. Reason: Added code tags
- 10-19-2010 #2
No idea what your problem is but you shouldn't make the guest account as root, very dangerous
- 10-19-2010 #3Just Joined!
- Join Date
- Oct 2010
- Posts
- 4
I know, but unfortunately this is how it was set up from the vendor (whom we're no longer dealing with). In either case root should work (I'll worry about securing the thing once it actually works, in the meantime this server is on a vlan that only talks to one computer all in a development sandbox).
- 10-22-2010 #4Just Joined!
- Join Date
- Oct 2010
- Posts
- 30
For my users I use the following under Share Definitions.
On the sever make sure the [smb_share] is owned by the group or user.Code:[smb_share] path = /home/smb_share force group = writable = yes create mask = 0770 directory mask = 0770 comment = Share Directory For All Users
I had funny read write errors with this.
Check the Samba group/user permission.
F1Last edited by MikeTbob; 10-26-2010 at 11:56 AM. Reason: Added code tags
- 10-25-2010 #5Just Joined!
- Join Date
- Oct 2010
- Posts
- 4
Ok, I tried that and still no go. I have expanded logging to level 3 and have a bunch of data, but don't know what it means. I did see in there is an "NT status disk full" error and I think that's where the problem lies. I've also added the smbstatus output in case that can help anyone in figuring out what I've got going on here.
Originally Posted by SAMBA Log
Originally Posted by smbstatus output
EDIT - I just tried this with one of our servers and it seems to have gotten further... I was able to copy and paste it, but the contents ended up being empty. So Win Server 2003 seems to be able to at least get past the NT_STATUS_DISK_FULL error, but then gets tied up elsewhere. I've pasted a log of that transaction as well below in order to give additional info.
Originally Posted by SAMBA Log from WinServer 2k3 Last edited by netninja2001; 10-25-2010 at 12:39 PM. Reason: added additional info
- 10-25-2010 #6Just Joined!
- Join Date
- Oct 2010
- Posts
- 30
Run testparm on the samba server.
Are you using quotas for your users?
(SMBwriteX) NT_STATUS_DISK_FULL
- 10-26-2010 #7Just Joined!
- Join Date
- Oct 2010
- Posts
- 4
I ran testparm and this was the output:
As for quotas, this was delivered to us by a vendor "pre-configured" so I didn't set any of the initial settings. As far as I know, there shouldn't be any quotas since this was supposed to be a massive store for video data.Code:[root@Pictron_Archive ~]# testparm Load smb config files from /etc/samba/smb.conf Processing section "[homes]" Processing section "[printers]" Processing section "[pictron-share]" Loaded services file OK. WARNING: You have some share names that are longer than 12 characters. These may not be accessible to some older clients. (Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.) Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions [global] server string = Samba Server Version %v security = SHARE passdb backend = tdbsam guest account = root log level = 3 log file = /var/log/samba/log.%m max log size = 50 deadtime = 10 local master = No create mask = 0777 directory mask = 0777 guest ok = Yes block size = 4096 cups options = raw blocking locks = No csc policy = disable oplocks = No level2 oplocks = No dfree cache time = 10 [homes] comment = Home Directories read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [pictron-share] comment = Samba Share Folder path = /pictron-share read only = No create mask = 0770 directory mask = 0770 [root@Pictron_Archive ~]#
EDIT - I also ran smbcquotas on the share and got this output:
I couldn't figure out what syntax to use to display "vfs default quota", but I don't think it would have been set.Code:[root@Pictron_Archive ~]# smbcquotas //***.***.***.***/pictron-share added interface ip=***.***.***.*** bcast=***.***.***.*** nmask=255.255.254.0 Password: Connecting to host=***.***.***.*** Connecting to ***.***.***.*** at port 445 Connecting to host=***.***.***.*** Connecting to ***.***.***.*** at port 445 rpc_pipe_bind: Remote machine ***.***.***.*** pipe \lsarpc fnum 0x7771 bind request returned ok. lsa_io_sec_qos: length c does not match size 8 Unix User\root : 0/ 0/ 0 [root@Pictron_Archive ~]#
Last edited by netninja2001; 10-26-2010 at 12:37 PM. Reason: additional info
- 10-26-2010 #8Just Joined!
- Join Date
- Oct 2010
- Posts
- 30
Your testparm does not show a workgroup. If this is on purpose that’s fine.
If your system is running VFS modules then vfs default quota will come into play.
“vfs default quota" stores Windows quota in samba.
There should be a line in smb.conf
Vfs objects =
Is your test user a member of a group?
If so what are your group permission?
They should be 0777 for a guest account directory.
Here my testparm shares output
[Z]
path = /home/z
force group = z
read only = No
create mask = 0770
directory mask = 0770
[RECOV]
path = /home/recov
force group = recov
read only = No
create mask = 0770
directory mask = 0770
[x]
path = /home/x
force group = z
read only = No
create mask = 0770
directory mask = 0770
all shares are listed by the group and owned by the group.
Aquarium:/# ls -la /home
total 44
drwxrwx--- 8 root recov 4096 2010-09-14 09:16 recov
drwxrwx--- 18 root z 4096 2010-10-26 14:45 x
drwxrwx--- 19 kids z 4096 2010-10-25 16:47 z
My best guess to your problem is quotas and or permissions.


Reply With Quote
