Hi! Thanks!
Version is 3.5.4, primary dns is AD server. AD is Win2003 server sp2.
Domain functional level is "windows server 2003", forest functional
level is "windows 2000". I think even 3.0.37 did use DNS (judging by
network traffic it made).
It's a pitty that there's no instructions how
Which version of Samba? I had more trouble with Samba 3.5.x. And I
have never managed to get Samba to compile with sun cc. I figured
Samba was written with gcc in mind.
The "failed to lookup DC info for domain 'mydomain.COM' over rpc: Logon
failure' " message is interesting - not sure if
Hi!
First of all, thanks for replies to all ;)!
Using GCC was a fail for me - too much errors and 2 additional things
must be compiled (tdb & talloc) . I only managed to compile using Sun's
cc and gmake and will stick to them. I'm a bit further now. Now I don't
get PKCS 11 erros, when trying
Compiled 3.5.4 successfully, but new binaries seem to be defective or
missing something. I get errors about PKCS 11 library calls when trying
to join domain. I've seen these errors with "original" Samba 3.0.37 in
"log.winbindd" and "log.wb-DOMAIN", but besides that, 3.0.37 worked and
could join
0n Thu, Jul 15, 2010 at 12:26:05AM +0300, M??rcis Lielturks wrote:
>Can anybody share experience on compiling samba on OpenSolaris? What's the
>most painless way? I'm considering to use latest 3.5.5 but maybe I should
>use same version Sun (Oracle) is using - 3.0.37? I have to se
I compiled Samba 3.4.x on Solaris 10.(I have a Samba 3.4.x pdc with
two Samba 3.0.x BDC's.) Samba 3.0.x DC"s will not support Windows 7
clients (don't have any yet but it is probably inevitable) and doesn't
seem to support trusts with Windows 2003 Native domains (at least it
didn't for me.
On 15 July 2010 00:28, Jeremy Allison wrote:
> On Thu, Jul 15, 2010 at 12:26:05AM +0300, Mārcis Lielturks wrote:
> > Thanks, machine wont provide NFS or ssh login services, so fiddling with
> max
> > groups should do no harm!
> >
> > I googled a bit at found that samba should be recompiled to tak
On Thu, Jul 15, 2010 at 12:26:05AM +0300, Mārcis Lielturks wrote:
> Thanks, machine wont provide NFS or ssh login services, so fiddling with max
> groups should do no harm!
>
> I googled a bit at found that samba should be recompiled to take advantage
> of new NGROUPS_MAX. "./configure" logs also
Thanks, machine wont provide NFS or ssh login services, so fiddling with max
groups should do no harm!
I googled a bit at found that samba should be recompiled to take advantage
of new NGROUPS_MAX. "./configure" logs also suggested that NGROUPS_MAX is
evaluated only at compile time.
Can anybody s
Here is the catch (at least for some people.)
This can break NFS stuff.On my PDC I made a similar change. Home
directories are not on the PDC. This fixed the problem of people
getting login failures when logging into windows if they had more than
16 groups. But if a user tries to ss
Hi!
Running OpenSolaris snv_134 with Samba 3.0.37. Samba is successfully
joined to AD domain. AD user "user1" is member in 17 AD groups including
"group1", but he cannot access Samba share which have read permissions
for "group1". If user account is modified and "group1" becomes users
primary
11 matches
Mail list logo
