Tridge, I am running out of time. I didn't get a chance to open the new trace. But I am not surprised that the problem is not fixed. The error is showing pretty clearly in the previous trace too. I believe that Edagr can continue to trace it down more deeply.
Edgar, Please go to this instruction point in the previous trace directly ( !tt 3BB940000041 ). It will directly take you to the beginning of the function of querying Dns for IPv6 family. This function is returning WSANO_DATA. From there, you can know where to set break points in the new trace. Thanks! Hongwei -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Wednesday, June 08, 2011 10:17 PM To: Hongwei Sun Cc: [email protected]; Edgar Olougouna Subject: RE: [REG: 111060784988397] RE: joining domain with IPv6 client Hi Hongwei/Edgar, > Is there a problem with the IPv6 record in DNS ? I've fixed the problem with returning 127.0.0.1 for IPv4. It was a bug where if we had no IPv4 addresses we defaulted to adding 127.0.0.1 in the provision code. I've now fixed that logic so we only return IPv6 addresses, but it hasn't fixed the join problem. I've taken a new trace, and put it here: http://www.samba.org/tridge/ttt/ipv6-3.zip The DNS replies in the network capture all look OK to me. We don't run a LLMNR server on Samba, so we don't reply to the LLMNR queries starting at frame 422, but all the normal port 53 DNS replies look OK to me. Can you look at this new trace and see if you can spot what DNS packet Windows doesn't like? Cheers, Tridge _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
