similar to: Documentation on Displaying Quotas

Can anybody explain why SOME Windows XP applications have trouble writing files larger than 2 GB (or sometimes larger than 4 GB) to Linux Samba shares, when OTHER Windows applications on the same machine do not have difficulty writing large files to the same Samba share? And when the underlying Linux filesystem supports very large files? I have sometimes even found that a SINGLE Windows

Hi, We use XFS, Samba and Quotas. Until now, we haven't had any issues with Samba versions up to 3.0.13. But we are testing Samba 3.0.22 and noticing that when we set group quotas on XFS volumes, the quotas are NOT getting reflected on Windows XP workstations when you look at the "Properties" of a Samba share. With 3.0.13 and below, the group quotas come through fine. In both

I wrote into the list a few days ago about XFS Group Quotas not working in Samba 3.0.21c and 3.0.22. I have confirmed that if I uninstall 3.0.22 and reinstall 3.0.13, when I change an XFS group quota on Linux and mount a share that belongs to that group, if I look at the "Properties" for that share in Windows, Windows tells me that the "size" of the share is equal to the

Hi, Does anybody know why Windows clients can see shares that are defined by the "include=/etc/samba/smb.%U.conf" option in but Mac OS X and Linux Samba clients cannot see those shares? In other words, I have a bunch of users. Each user has a set of his/her own unique shares on my Linux server that are defined in files called: /etc/samba/smb.User1.conf /etc/samba/smb.User2.conf

Hi, I have an Ubuntu Linux server where I use Sticky Bits to help enforce specific permissions on Samba shares: -- Each Samba share is associated with a unique Linux group -- Only members of the group can access the share -- All members of the group can create new files and directories in the share -- SGID is set on all directories. -- The "creator" of any new file will be the

Do anyone have any experience using 10 Gigabit Ethernet connections with Samba? Specifically, if you have had such an experience, can you share what sorts of optimizations you made to get the maximum data transfer between server and workstation? I am just experimenting with this kind of setup myself and I see a huge GULF between the raw TCP/IP transfers that I can make between two

Hi. I'm running Samba 3.0.2 (a?) on Linux. For the most part, it's working great. I have set up Samba as a PDC and also just as a workgroup server. However, under both scenarios I'm seeing a troublesome behavior with Windows XP machines that have many users who frequently log on and log off. If User A logs off Windows XP and User B logs on 30 or 40 seconds later, sometimes

I recently upgraded from Samba 3.0.2a to Samba 3.0.11. I didn't change anything in my smb.conf file. But Now, when a user logs on to my Linux server and access a Samba share, in the log file for that machine there is always a message repeated twice: [2005/03/16 05:40:23, 0] printing/print_cups.c:cups_cache_reload(85) Unable to connect to CUPS server localhost - Connection refused As

I have spent most of the past 24 hours reading various samba docs and searching google for help -- but can't find a solution. Suggestions and solutions would be appreciated. I have set up a Linux Box (Samba 3.02) as a PDC with roaming profiles. (I haven't upgraded, because this box is a model for over 100 other boxes in the field). I can add XP users to the domain and their roaming

Hi, Is there a simple way to set up Samba so that users ONLY see the shares that belong to them? I'm not talking about the user's HOME directory. But lets say I have 60 shares in my smb.conf file. To make it less confusing for users when they access the Samba server from Windows, I want the users to ONLY see the shares that belong to them. So, I want to set up each share so that

Can somebody tell me how to get samba to ask me for a username and password when I click on my Samba server in Windows XP Explorer? When I click on another computer on the network (Workstation A) from a workstation (Workstation B) where I'm NOT logged in with a username:password that Workstation A recognizes as having an account, I get a dialog box asking me for a username and password.

I have Samba 3.0.0 installed on Mandrake 9.2. I also have Samba 2.8.8a installed per instructions from Mandrake -- but I do NOT start Samba 2.8.8a automatically. In fact, I don't use it at all. Maybe I should uninstall the Samba 2.8.8a rpm??? I will update to 3.0.1 as soon as an rpm is available from Mandrake. Anyway, I have a problem when I try to add a new share to my smb.conf file. I

Hi, I have a weird problem with a Linux Server acting as a PDC with Samba 3.02. If I map a particular Samba share as the "Z" drive -- and I use roaming profiles with a logon.bat script -- the share will NEVER automatically reconnect when logging on again. This happens 100 percent of the time. And now the same thing seems to be happening for any shared mapped as the

Hello, Samba 3.0.23d PDC on CentOS 4.4, smbpasswd backend, Windows XP clients. I recently took over the administration of a small LAN (~35 hosts). The shared drives had been implemented in a hurry and the configuration had never been revisited. Linux groups had been enabled for different shares, but this had never been enforced on the file server. I have implemented linux group quotas on the

Does somebody know if the Samba Client in MAC OS X (10.3.4 and 10.3.5) has problems looking at Linux-based Samba shares that are larger than 2 TB? I have Samba 3.0.2 running on my Linux box. I have never had any difficulty with the Mac seeing a 2 TB RAID array on the Linux box, but when the Mac looks at the 4 TB array, it can see all the contents and create folders but it can't create

Begin forwarded message: > From: Kimball Larsen <kimball at miridiatech.com> > Date: February 2, 2010 7:58:49 PM MST > To: Andy Liebman <andyliebman at aol.com> > Subject: Re: [Samba] OS X Clients Can't Create Sub-Directories > > > On Feb 2, 2010, at 6:53 PM, Andy Liebman wrote: > >> >> Kimball Larsen wrote: >>> I'm running

Hi, I'm setting up a Linux machine to use as a file server for a small group of windows machines. Like many of the folks who write to this list, I'm having all kinds of difficults getting the Windows machines to be able to access the Linux shares. In my case, the most frustrating thing is that all of my Windows machines and users can access the Linux shares SOMETIMES. But

Does anybody have any insight into what could be causing this strange problem? I have Samba 3.02 (sorry, can't upgrade right now). My Linux box is running Mandrake 10 Official. I have Samba configured as a PDC. I can successfully add machines to my Domain -- and log on as ANY user from ANY machine. However on a SINGLE MACHINE, when I log on as USER_1 and access that user's roaming

A question about capturing videos to a Samba share... When Apple's Final Cut Pro captures video files, it pre-allocates file space on the destination volume. If you capture to a local volume that's physically attached to a Macintosh, or if you capture to a network volume via AFP (Apple File Sharing Protocol), you can see that Final Cut instantly creates a file of the

I have written to this list several times. I purchased the Officia SAMBA 3 How-To and Reference Guide (and read much of it). But I can't get a good answer to my question. I'm trying to figure out the difference between "inherited permissions" and "force/create mask/directory", and other actions like "force user" and "force group" (it seems I