On 03/12/11 17:32, Matthieu Patou wrote:
Steve
Beware that on your machine where samba 4 DC is running file / folders
needs to have guid/uid of your AD users not your linux users.
Did you read this ^.
Did a git pull ./configure.developer make and make install about an
hour ago.
And, well,
Hi Steve,
the last configuration is the correct one.
However you may have to set LD_LIBRARY_PATH to the
directory containing libsamdb.so.0 (or other libraries it may complain
about during startup).
Bye,
Marcel
Von: samba-boun...@lists.samba.org
Hi Marcel
Thanks for the confirmation. It narrows down the problem.
I can confirm:
/usr/local/samba/modules/bind9/dlz_bind9.so
is there OK.
However:
hh3:/home/steve # echo $LD_LIBRARY_PATH
hh3:/home/steve # export LD_LIBRARY_PATH=/usr/local/samba/modules/bind9/
hh3:/home/steve # echo
Hi
I had a go at resara (resara.org), mainly because it looks like they
have written a GUI to manage AD under Linux.
I got the source code since I don't have enough resources for their
virtual machine. The documentation is poor, but I managed to compile and
install from source on Ubuntu
Hi Steve,
it's quite likely, that bind running in chroot is the cause of
the problem. You can easily test it by disabling chroot for
named on SuSE systems by editing /etc/sysconfig/named
NAMED_RUN_CHROOTED=no
If the problem is still there, try running named using strace,
and have a look at all
On 04/12/11 14:19, Marcel Ritter wrote:
Hi Steve,
it's quite likely, that bind running in chroot is the cause of
the problem. You can easily test it by disabling chroot for
named on SuSE systems by editing /etc/sysconfig/named
NAMED_RUN_CHROOTED=no
If the problem is still there, try running
First, you had better understand Windows domain trustrelationship
before working on Samba issue. Then you will understand what to be
done.
I've set up trust between domains. Users from windows domain can
access shares on Samba PDC but not on other machines in samba domain.
That is the puzzling
On 04/12/11 09:04, steve wrote:
On 03/12/11 17:32, Matthieu Patou wrote:
Steve
Beware that on your machine where samba 4 DC is running file / folders
needs to have guid/uid of your AD users not your linux users.
Did you read this ^.
Did a git pull ./configure.developer make and make
Hi Steve,
as 2 of the 3 queries did succeed, are you sure the hostname
of your dc was correctly detected during provision?
Does hostname -f return samba.hh3.site?
You may also try samba-tool / ldbsearch to get info about
the DNS entries stored by samba.
(Please replace 192.168.1.6 with the IP
