> Was it complaining that they are read only or that after saving a file
> that existed it word claimed that it could not save the file? I am
> asking as after I upgraded from samba-3.0.22 to samba-3.0.23 on gentoo
> I had these symptoms and the fix was very easy.
Do you have a hint / link for th
John Drescher wrote:
> On 2/2/07, Ole Holm Nielsen wrote:
> > We run samba-3.0.23c on some Redhat RHEL4 servers, and Samba used to
work
> > like a charm. But then a couple of days ago we upgraded the kernel
> > on the Samba servers to kernel-smp-2.6.9-42.0.8.EL. All of a sudden
> > our Windows u
Yes, they're the solo PDC in the lan and we haven't had an problems, but
that does clear it up for me. At most, we connect our W2k3 servers to
our Samba PDC's, that's working fine.
Aaron Kincer wrote:
> If they are working great as PDC's, I wouldn't worry too much. As a file
> server in an Active
If they are working great as PDC's, I wouldn't worry too much. As a file
server in an Active Directory environment, the Red Hat version of Samba
on RHEL4 is, in my opinion, unacceptably broken. It's little things like
file locking not working right and strange other quirks that I can't
remember
On 2/2/07, Ole Holm Nielsen <[EMAIL PROTECTED]> wrote:
We run samba-3.0.23c on some Redhat RHEL4 servers, and Samba used to work
like a charm. But then a couple of days ago we upgraded the kernel
on the Samba servers to kernel-smp-2.6.9-42.0.8.EL. All of a sudden
our Windows users could not use
Ole Holm Nielsen wrote:
>> Looks like a kernel issue to me. Have you reported this to Red Hat ?
>
> No, because I run samba-3.0.23c in stead of the RHEL4 Samba 3.0.10
> which is broken wrt. workgroup master browsers. Your recent Samba
> versions solve the problems, but I'm sure Redhat won't accep
Hi Don,
What are the details (OS/type, etc.) of the NFS server that you are
mounting these resources from? Is it possible that you are mounting an
older 32 bit NFS service from a system that is evidently 64 bit capable?
Samba server: RHEL4 (32-bit Intel Xeon 2.4 GHz).
NFS server: RHEL3 (32-
Jeremy Allison wrote:
...
Fortunately I found this article
http://lists.samba.org/archive/samba/2006-October/126638.html
where Jeremy recommends to use "posix locking = no", and indeed
this fixes the problem !
Hopefully these observations can help others, but a real solution
to the problem wo
On Fri, Feb 02, 2007 at 04:45:08PM +0100, Ole Holm Nielsen wrote:
> We run samba-3.0.23c on some Redhat RHEL4 servers, and Samba used to work
> like a charm. But then a couple of days ago we upgraded the kernel
> on the Samba servers to kernel-smp-2.6.9-42.0.8.EL. All of a sudden
> our Windows us
Olm,
What are the details (OS/type, etc.) of the NFS server that you are
mounting these resources from? Is it possible that you are mounting
an older 32 bit NFS service from a system that is evidently 64 bit capable?
-D
At 09:45 AM 2/2/2007, Ole Holm Nielsen wrote:
We run samba-3.0.23c on
We run samba-3.0.23c on some Redhat RHEL4 servers, and Samba used to work
like a charm. But then a couple of days ago we upgraded the kernel
on the Samba servers to kernel-smp-2.6.9-42.0.8.EL. All of a sudden
our Windows users could not use Microsoft Office with files on the
Samba shares :-(
Ou
11 matches
Mail list logo
