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

Hongwei Sun hongweis at microsoft.com
Wed Jun 8 19:34:56 MDT 2011


  I  can see the error condition from the trace so this is the correct trace.   After some quick debugging,  I found that the error is returned from the DNS lookup for the host name "BLU".   Windows will automatically detected if IPv4 or IPv6 stacks are installed and then do the IPv4 or IPv6 lookup accordingly.  In this case , both stacks are installed so both A and AAA records are looked up.    When looking up for IPv4, the error returned is 11001(WSAHOST_NOT_FOUND),   this is understandable since only Ipv6 address is registered for the host as you indicated.  When looking up for IPv6, the error returned is 11004 (WSANO_DATA),  this may be the problem.   The following is the description for this error:

Valid name, no data record of requested type. 
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record-indicating the host itself exists, but is not directly reachable."

  Is there a problem with the IPv6 record in DNS ?


-----Original Message-----
From: tridge at samba.org [mailto:tridge at samba.org] 
Sent: Wednesday, June 08, 2011 6:54 PM
To: Hongwei Sun
Cc: cifs-protocol at samba.org; Edgar Olougouna
Subject: [REG: 111060784988397] RE: joining domain with IPv6 client

Hi Hongwei,

 >     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.

I've redone the trace with the lanmanworkstation process (pid 1004), and have uploaded the trace to:


the zip file also contains the network capture, and the logs from c:\windows\debug

 >    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.

ok, sounds good, thanks!

Cheers, Tridge

More information about the cifs-protocol mailing list