[Samba] problems writing to profile share when updating from samba 2.2.3a to 2.2.5

[Christian Storm]

Hi Ivan,

Thank U;
You'r right. My profiles share is in a different location as the homes share.
-- but --
The Problem is solved;

Look at the Thread
"For Those who have problems logging off and writing profiles with w2k"

I found a good documentation which was in front of my face 2 Months
"ARGHHH"

What did the "Godfather" say

Shit happens!

Chris ;-)


Am Donnerstag, 29. August 2002 17:37 schrieb Ivan Dimitrov:
> Hi Chris,
> I know that this is not relevant and you definitely know it but just in
> case... Does your profiles and users homes are under same dir on Samba
> server /i suppose they are not but just in case they are they should not be
> . "NT/2000 clients attempt to reuse the existing connection .. and in most
> circumstance
> new user may have not access to the profile ... " Gerald Carter/
>
> ivan
>
> At 19:55 28/08/2002 +0200, you wrote:
> >Am Mittwoch, 28. August 2002 18:55 schrieb Ivan Dimitrov:
> >Hi Ivan,
> >
> >Unfortunately this does not solve my ( our ) problem;
> >
> >here is the part of the smb.conf
> >
> >[profiles]
> >         comment = Benutzerprofile
> >         path = /windows/profiles
> >         read only = No
> >         create mask = 0775
> >         force create mode = 0775
> >         directory mask = 0775
> >         force directory mode = 0775
> >         browseable = Yes
> >
> >I've put the two "force.." - lines after the first (second, or 200987 )
> > test, but Windows tells me again that the file is open by another
> > process; Maybe the file to sync is open on windows not on the
> > samba-share??
> >
> >Another funny effect is that w2k does not hang at the same file.
> >Sometimes it can write the file, then another file causes the same
> > problem. This behaviour is not replicable ( sometimes a file causes the
> > problem 1 time;
> >sometimes 20 times ... )
> >
> >in the log occures ( debug level 3 ) the NT_STATUS_SHARING_VIOLATION
> >
> >
> >Chris ;-)
> >
> > > Hi Alexander and Christian i had the same problem and this is how i
> > > have managed to get around it :
> > >
> > > RH 7.3 upgrade to from 2.2.3a to 2.2.5 !!!
> > > fist of all my profile dir is outside homes dir say /tem/profiles
> > > i had to change few permissions  in this share :
> > >
> > > [Profiles]
> > >       comment = Roaming Profiles
> > >       path = /tmp/profiles
> > >       read only = no
> > >       browseable = yes
> > > # keep this one like this or profiles don't work !!!!
> > >       create mask = 0775
> > > # keep this permissions 0775 do not put them
> > >       directory mask = 0775
> > > # back to 0600 and 0700
> > >
> > >   When a new profiled is created in the /tem/profiles dir
> > > the permissions by default are 0700 !!!! You have to keep browseable to
> > > yes !!!
> > >
> > >
> > > Also all my users belong to group "users"  ... !!!! if you have normal
> > > users like user jhon group jhon /default in RH / it doesn't work !!!!
> > > I have only w2k sp 2 environment and i do use MMC to
> > > implement simple policy restriction on my workstations locally !!!!
> > >
> > > Hope this help if you need more info get in touch with me out of the
> > > list !!!
> > >
> > > Apologies  for my English :) !!!!
> > >
> > > Thanks
> > >
> > > ivan
> > >
> > > At 18:14 28/08/2002 +0200, you wrote:
> > > >Hi Alexander
> > > >
> > > >I've got the same problem after the update from 2.2.3a to 2.2.5 and
> > > > still no solution for it;
> > > >But i've encountered that the client does write on the Profiles-share;
> > > >( use the VFS-object audit.so on the share );
> > > >[profiles]
> > > >         ...
> > > >         vfs object = /usr/local/samba/lib/audit.so
> > > >
> > > >this logs in /var/log/messages ;-)
> > > >
> > > >It seem's that the Client
> > > >-connects
> > > >-writes ( a file prfXXX.tmp with size 0 )
> > > >-disconnects
> > > >for each file of the profile
> > > >
> > > >Why does Windoof create empty tmp-files??
> > > >
> > > >can this be this is a timing/oplock problem ???
> > > >
> > > >Does anyone else have a Solution
> > > >
> > > >A small solution can be to exclude the directories with MS
> > > >mmc.exe -> add/remove SnapIn -> Add -> Group-Policy
> > > >edit the User-Configuration -> Administativ Template -> System ->
> > > > Logon/Logoff
> > > >
> > > >Let me know, if you or anyone else solves this problem
> > > >
> > > >( Sorry for my poor english )
> > > >
> > > >Cheers Chris ;-)
> > > >
> > > > > Hi,
> > > > > we updated our samba 2.2.3a to 2.2.5 because of several printing
> > > > > problems. Now our Clients (win 2k & xp) can't write to their
> > > > > profiles share (the windows error-message was: "this file is used
> > > > > by another process", but there weren't any other processes from
> > > > > this user). In the samba logfile we can't see any write-attempt
> > > > > from the client.
> > > >
> > > >--
> > > >To unsubscribe from this list go to the following URL and read the
> > > >instructions:  http://lists.samba.org/mailman/listinfo/samba
> >
> >--
> >To unsubscribe from this list go to the following URL and read the
> >instructions:  http://lists.samba.org/mailman/listinfo/samba