OK. I think I have tracked this problem down and have been able to
backout out the recommended changes below. Here is what I found.
Somehow through the PAM authentication modules the users home
directories were being mounted on top of themselves as NFS4 shares on
the Samba server (this server can
Volker, yes this "trick" worked for the current problems but agreed that
it is not a long term solution to the "locking" problem.
Thanks, Bob
--bs
On Tue, 2010-08-24 at 07:04 +0200, Volker Lendecke wrote:
> On Mon, Aug 23, 2010 at 11:34:21PM -0400, Robert W. Smith wrote:
> > OK, so far I now und
On Mon, Aug 23, 2010 at 11:34:21PM -0400, Robert W. Smith wrote:
> OK, so far I now understand that this is _NOT_ a general login issue
> _NOR_ is it a MS credentials file issue either. This appears to be a
> general locking issue in Samba and Linux. Here is a snippet of my
> workstation log with a
OK, so far I now understand that this is _NOT_ a general login issue
_NOR_ is it a MS credentials file issue either. This appears to be a
general locking issue in Samba and Linux. Here is a snippet of my
workstation log with another application that now no longer runs. The
SMB network transactions
I am running two Fedora 13 servers, one as a Samba PDC and the other as
a BDC. For the past week I have been tracing a series of issues which
may or may not be related to Samba 3.5.4. Here is one problem that I am
tracking and need help from the list with suggestions.
>From a wireshark trace betwe
