Samba 3 PDC/Win2K client: Roaming profile save problem: disk space
All:
I've got a Samba 3 server running as a PDC for a small network with Win2K clients. On each of the clients, I've recently been receiving the following error on logging off/shutting down the workstations: Windows cannot update your roaming profile. Contact your network administrator. DETAIL - There is not enough space on the disk. I've checked all of the obvious (and not so obvious) things I can think of: - I've got tons of disk space on all volumes (i.e. > 1 gig) - I've set the Samba log level to 2 for each machine, and see nothing out of the ordinary. - I've set permissions to 0777 to see if it was a read-only issue: no dice - I'm able to browse to the profile directories on the workstations, and all permissions appear correct. - Quotas have not been implemented (I've checked) - Network hardware issues (latency, etc.) don't appear in any tests. - My smb.conf is very straightforward - nothing fancy. I've seen a few posts on this issue, but never a resolution - any ideas? Thanks for your help. thr0ck |
Can you copy a file to the profile directory whilst logged in normaly?
|
All normal file operations from the Win2K boxes work fine - copy/paste/rename/delete, etc.
I'm playing around with some of the settings in my smb.conf file today (create mask, etc.) to see if that makes a difference - but since it worked initially then just started bombing recently, I doubt it'll make a difference... Thanks. thr0ck |
From the way you worded your first post it sounds like this is a recent occurance. Is that right?
Can you think of anything that has been changed on the server recently? I'm assuming it is a server issue if all the clients have the same problem. |
The only recent change to the server was (ironically) the addition of another 40 gb of drive space. That does lead me to a question, though: The profile-related (i.e. user-related) parts of my smb.conf file read as follows:
[netlogon] path = /etc/samba/netlogon guest ok = yes share modes = no [profiles] path = /etc/samba/profiles writeable = yes create mask = 0600 directory mask = 0700 [homes] comment = Home Directories browseable = no writeable = yes I don't have anything running from the netlogon directory (as far as I know, I don't need anything there). The interesting thing is that my profiles were stored in the home directories (/home/user1, /home/user2, etc.) and not in the /etc/samba/profiles directory as the conf would seem to indicate... This was the default behavior from when I set the box up, and I didn't see the need to fight it - think this might be related? Any way to "force" Samba or the Win2K boxes to write to the /profiles/ directory? |
try putting the "path" option in the "home" share.
|
Quote:
Have you tried setting "logon path" in the global section? |
OK - a lesson for those who hate dealing with their Win2K clients: check the contents/size of everything under your [Documents and Settings {username}] directory. A video-editing app had tucked 9 gigs worth of crap about 6 directory levels in in the user profile on one machine, with like results on other machines.
So, long and short of it is that Samba was right - there wasn't enough disk space there. My home partition isn't particularly big, since I generally try to limit the amount of junk there. Question: if I set a logon path to, say /etc/samba/profiles, will that force Samba to save the profiles to that directory? I've got tons of space there (and wouldv'e noticed when a Win2K box was pushing gigs of data to it). One final question: has anyone found a good source online of sample smb.conf files? I'm no newbie - to Linux or Samba - and even I found Samba a major trial-and-error pain to get running as a PDC the way it should. Would likely help a lot of people out there.... Thanks to all for your help. |
The best soruce for the configuration options can be found in the man page:
man smb.conf |
Sorry for borrowing your thread
I have problem storing the client's roaming profile onto the Samba server. I would like to confirm somethings.
1) useradd client account, smbpasswd -a account a - What group do we add them to? Does it matters? 2) Adding of machine account b - Whats the extra parameters to use? c - Do I need to use smbpasswd and passwd to add? d - Again, does it matter if what group i assign it to? Or both client and machine account must be in same group? 3) Do we need to create the directory/folder manually and assign the permission for profiles and netlogon folders? btw, I got the below message from my samba log file. get_domain_user_groups: primary gid of user [subaruwrx] is not a Domain group ! get_domain_user_groups: You should fix it, NT doesn't like that |
Re: Sorry for borrowing your thread
Quote:
|
up
|
All times are GMT -5. The time now is 05:42 AM. |