Bluehost.com Web Hosting $6.95

Re: [Samba] Setup of a new PDC with Samba 3.2.0]

This is a discussion on Re: [Samba] Setup of a new PDC with Samba 3.2.0] within the Samba forums, part of the Networking and Network Related category; I finally make it work. The problem was in my nss_ldap.conf file. I was missing a line indicating there ...


Go Back   Usenet Forums > Networking and Network Related > Samba

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 07-18-2008
devel@thom.fr.eu.org
 
Posts: n/a
Default Re: [Samba] Setup of a new PDC with Samba 3.2.0]

I finally make it work.

The problem was in my nss_ldap.conf file.

I was missing a line indicating there were "user" accounts in two
different OU : People and Machines. Once this was fixed, I could properly
check the trust account with winbindd.

in libnss_ldap.conf:

nss_base_passwd = ou=People,dc=mydomain,dc=fr
and after I added this line
nss_base_passwd = ou=Machines,dc=mydomain,dc=fr
It did work.

> Ok, so I could finally get the level 10 log out of winbindd.
>
> I started it with winbindd -S -F -i -d 10 > log.winbindd
>
> The complete log file is available at
> http://www.thom.fr.eu.org/log.winbindd
>
> By what I could see, it seem to get NT_STATUS_IO_TIMEOUT when trying to
> connect to MYSERVER (name resolving seems OK there) then it says Receiving
> SMB: Server stopped responding
>
> Any idea ?
>
>> On Sat, Jul 12, 2008 at 10:30:13AM +0200, devel@thom.fr.eu.org wrote:
>>> Ok,
>>>
>>> I just missed this part from the documentation (by the way, could
>>> anybody
>>> spot me to the place where this is specified. I could see in Samba
>>> Howto
>>> chapter 13, but this is not obvious).

>>
>> No, I think you're correct. This is where it's specified.
>> That's not really the right place.
>>
>> I'd like to take a look and fix this, but might take a
>> while to get to the docs update. Anyone else willing to
>> help ?
>>
>>> So I did successfully join the domain, and now I get the following
>>> error
>>> on wbinfo -t :
>>> MYSERVER:~# wbinfo -t
>>> checking the trust secret via RPC calls failed
>>> error code was NT_STATUS_DOMAIN_CONTROLLER_NOT_FOUND (0xc0000233)
>>> Could not check secret
>>>
>>> This looks like a resolver issue. I have
>>> wins server = 10.212.254.254
>>> wins proxy = Yes
>>> name resolve order = lmhosts wins host bcast
>>> in smb.conf, and my lmhost file says
>>> 10.211.254.253 MYDOMAIN
>>> 10.211.254.253 MYSERVER
>>> and anyway the nmblookup succeeds:
>>> tls-srv-01:~# nmblookup -R -U 10.212.254.254 MYDOMAIN#1b
>>> querying MYDOMAIN on 10.212.254.254
>>> 10.211.254.253 MYDOMAIN<1b>
>>> tls-srv-01:~# nmblookup -R -U 10.212.254.254 MYDOMAIN#1c
>>> querying MYDOMAIN on 10.212.254.254
>>> 10.211.254.253 MYDOMAIN<1c>

>>
>> Run winbindd -d10 and look at the core winbindd logs to
>> help find out why it can't find the DC.
>>
>> Jeremy.
>>

>
>
> --
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/listinfo/samba
>



--
François Legal


--
François Legal
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +1. The time now is 01:21 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0