[cifs-protocol] joining domain with IPv6 client

[tridge at samba.org]

Hi Hongwei,

I've hit a problem with joining a Windows2008r2 client to a Samba4
domain as a domain member, when the Windows client only has a IPv6
address (no V4 address).

The join completes, but then I get an error message:

 Changing the Primary Domain DNS name of this computer to ""
 failed. The name will remain "bludom.tridgell.net".
 The error was:
 The specified server cannot perform the requested operation.

I have taken a TTT trace, and I'd appreciate it if you could have a
look and see why Windows doesn't like the join. 

At the end of NetSetup.log I see the following:

06/08/2011 08:25:34:107 NetpChangeMachineName: from 'W2K8R2C' to 'w2k8r2c' using 'bludom.tridgell.net\administrator' [0x1000]
06/08/2011 08:25:34:107 NetpDsGetDcName: trying to find DC in domain 'BLUDOM', flags: 0x1010
06/08/2011 08:25:34:219 NetpDsGetDcName: found DC '\\BLU' in the specified domain
06/08/2011 08:25:34:219 NetpGetLsaPrimaryDomain: status: 0x0
06/08/2011 08:25:34:219 NetpGetDnsHostName: Read NV Domain: bludom.tridgell.net
06/08/2011 08:25:34:497 NetpLdapBind: ldap_bind failed on BLU: 81: Server Down
06/08/2011 08:25:34:497 NetpSetDnsHostNameAndSpn: NetpLdapBind failed: 0x3a
06/08/2011 08:25:34:497 NetpChangeMachineName: status of setting DnsHostName and SPN: 0x3a

I'm guessing that Windows is getting back an IPv4 address somewhere in
the join, and trying to use that to talk to the DCs LDAP
server. Unfortunately I can't find any place where we are
inappropriately returning an IPv4 address during the join.

I've put a TTT trace of lsass.exe, along with a network capture and
windows debug logs here:

  http://www.samba.org/tridge/ttt/IPv6/

In the trace, the samba server has addresses 10.0.0.1 and
fdb1:2726:40f9:b3b7::1. The w2k8r2 client has address
fdb1:2726:40f9:b3b7::16. 

Cheers, Tridge