[cifs-protocol] [REG: 111060784988397] RE: joining domain with IPv6 client

[Hongwei Sun]

+Edgar,

Tridge,

    I didn't find the code path in the trace as shown in the Netsetup.log.   Then I realized that this is a workstation domain join and not DC promo.   It happens in workstation service.  Please use the following instruction to capture a TTT trace.

1.  Use tasklist to find the process ID for workstation service. 

     c:> tasklist /SVC

     Look for the svchost.exe instance that contains the service "lanmanworkstation".   Save the process ID#

2.  Use TTTracer -attach <pid>  -dumpFull    to start the tracing as usual

   If I don't have a chance to check the new trace tonight,   Edgar will continue working with you while I am away.  I also captured a trace for Windows client to join to a Windows DC, so we compare while we are investigating it.

Thanks!

Hongwei

--------------------------------------------------------------------
Hongwei  Sun - Sr. Escalation Engineer
DSC Protocol  Team, Microsoft
hongweis at microsoft.com
Tel:  469-7757027 x 57027

Exceeding your expectations is my highest priority.  If you would like to provide feedback on your case you may contact my manager at allisong at microsoft.com.
---------------------------------------------------------------------




-----Original Message-----
From: tridge at samba.org [mailto:tridge at samba.org] 
Sent: Tuesday, June 07, 2011 6:32 PM
To: Hongwei Sun
Cc: cifs-protocol at samba.org; Interoperability Documentation Help
Subject: joining domain with IPv6 client

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