[Samba] changing server role = standalone server to 'member server'
steve
steve at steve-ss.com
Fri Apr 4 14:32:30 MDT 2014
On Fri, 2014-04-04 at 15:45 -0400, Carl Wilhelm Soderstrom wrote:
> In reference to this error:
>
> rpccli_netlogon_setup_creds: server AD.ad.example.com credential chain
> established.
> Bind RPC Pipe: host AD.ad.example.com auth_type 68, auth_level 6
> rpc_api_pipe: host AD.ad.example.com
> rpc_read_send: data_to_read: 72
> check_bind_response: accepted!
> seed 7fba58fe:dde64e56
> seed+time d2f95997:dde64e56
> CLIENT 414ca8a7:ca84cbce
> seed+time+1 d2f95998:dde64e56
> SERVER 5e528977:37d4889e
> rpc_api_pipe: host AD.ad.example.com
> rpc_read_send: data_to_read: 104
> libnet_Join:
> libnet_JoinCtx: struct libnet_JoinCtx
> out: struct libnet_JoinCtx
> account_name : NULL
> netbios_domain_name : 'EXAMPLEAD'
> dns_domain_name : 'ad.example.com'
> forest_name : 'ad.example.com'
> dn :
> 'CN=samba-4,CN=Computers,DC=ad,DC=example,DC=com'
> domain_sid : *
> domain_sid :
> S-1-5-21-3579304287-3829738268-3886208222
> modified_config : 0x00 (0)
> error_string : NULL
> domain_is_ad : 0x01 (1)
> result : WERR_OK
> Using short domain name -- EXAMPLEAD
> Joined 'SAMBA-4' to dns domain 'ad.example.com'
> added interface eth0 ip=192.XXX.XXX.30 bcast=192.XXX.XXX.255
> netmask=255.255.255.0
> ads_dns_lookup_ns: 2 records returned in the answer section.
> retrying DNS update with next nameserver after receiving
> ERROR_DNS_CONNECTION_FAILED
> retrying DNS update with next nameserver after receiving
> ERROR_DNS_CONNECTION_FAILED
> DNS update failed: NT_STATUS_UNSUCCESSFUL
> return code = 0
>
>
> On 04/04 01:36 , steve wrote:
> > bind or internal dns? the join only works with bind for Linux boxes.
>
> The server is a Windows AD server, which is responsible for the
> ad.example.com subdomain. (The example.com domain is served by a BIND
> server, which the AD server queries for domains other than ad.example.com).
>
> I use 'net ads join' on Samba v3 servers when joining them to a Windows AD
> server. (Admittedly it doesn't update the DNS entries for the Samba v3
> machines on the AD server either). Am I doing something wrong?
I can't reproduce the error against a windows AD but I can against a
Samba4 AD running bind dlz if I remove the localhost fqdn line
in /etc/hosts
Cheers,
Steve
More information about the samba
mailing list