Jeremy Allison wrote:
Ok, you're probably running against a W2K3 SP1 DC in security=domain
mode. Can you confirm that ? There are some changes in SP1 that cause
schannel connections to become the anonymous user which prohibits lookups
on some of the pipes. Setting the auth user in winbindd
After considerable experimentation I'm forced to accept that Samba 3 has
problems with the combination of being a domain member, the 2.6 kernel,
and Dell 2850 hardware. It works fine on the 2.4 kernels but fails on
all the 2.6 versions I have avaialble for testing. I have one machine
that I
On Wed, Oct 12, 2005 at 10:22:16AM -0700, Stephen Carville wrote:
After considerable experimentation I'm forced to accept that Samba 3 has
problems with the combination of being a domain member, the 2.6 kernel,
and Dell 2850 hardware. It works fine on the 2.4 kernels but fails on
all the 2.6
Jeremy Allison wrote:
On Wed, Oct 12, 2005 at 10:22:16AM -0700, Stephen Carville wrote:
After considerable experimentation I'm forced to accept that Samba 3 has
problems with the combination of being a domain member, the 2.6 kernel,
and Dell 2850 hardware. It works fine on the 2.4 kernels but
Stephen Carville wrote:
After considerable experimentation I'm forced to accept that Samba 3 has
problems with the combination of being a domain member, the 2.6 kernel,
and Dell 2850 hardware. It works fine on the 2.4 kernels but fails on
all the 2.6 versions I have avaialble for testing. I
I upgraded to 3.0.20a (I'll get 20b as soon as it is available but I
_really_ needed to know samba would work on this machine)
I tried my previous configuration with the usual failure.
After a bit more head scratching, sniffer traces, and poring over the
arcane language of one of the Grand
On Wed, Oct 12, 2005 at 08:45:17PM -0700, Stephen Carville wrote:
I upgraded to 3.0.20a (I'll get 20b as soon as it is available but I
_really_ needed to know samba would work on this machine)
I tried my previous configuration with the usual failure.
After a bit more head scratching,
