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

2011-06-08 Thread tridge
Thanks Hongwei, have a nice break! Edgar, let me know if you need any more traces. Cheers, Tridge > >Please go to this instruction point in the previous trace directly ( !tt > 3BB94041 ). It will directly take you to the beginning of the function > of querying Dns for IPv6 family

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

2011-06-08 Thread Hongwei Sun
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 t

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

2011-06-08 Thread tridge
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

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

2011-06-08 Thread tridge
Hi Hongwei, > " WSANO_DATA > 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

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

2011-06-08 Thread Hongwei Sun
Tridge, 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

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

2011-06-08 Thread tridge
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 re

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

2011-06-08 Thread 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

Re: [cifs-protocol] [REG:111060858976134] Deleted object removal

2011-06-08 Thread Edgar Olougouna
Matthieu, I am investigating this and will update you as soon as I have news. Regards, Edgar -Original Message- From: Bryan Burgin Sent: Wednesday, June 08, 2011 11:26 AM To: m...@samba.org; p...@tridgell.net; cifs-proto...@samba.org Cc: MSSolve Case Email Subject: [REG:111060858976134]

[cifs-protocol] [REG:111060858976134] Deleted object removal

2011-06-08 Thread Bryan Burgin
[dochelp to bcc] [adding case number and case mail] Hi, Matthieu, Thank you for your question. I created case 111060858976134 to track this. An engineer from the Protocol team will pick this up soon. Bryan -Original Message- From: Matthieu Patou [mailto:m...@samba.org] Sent: Wednesd

[cifs-protocol] Deleted object removal

2011-06-08 Thread Matthieu Patou
Hello doc help team, On a Windows 2008R2 server I joined and unjoined a Samba 4 domain controller and created users and groups and then deleted them. As the recycle bin is not activated this has resulted to ~ 100 of deleted objects. Most of this took place between march 2011 and mid may 2011

Re: [cifs-protocol] [REG:111051779565831] RE: dfs referral for sysvol and windows XP

2011-06-08 Thread Matthieu Patou
On 08/06/2011 02:01, Hongwei Sun wrote: Matthieu, I confirmed that there is a problem with the Netmon parser when displaying ReferralEntryFlag. The ReferralEntryFlags should be in little endian. In the packet, it should be parsed as 0x0004 that has TargetSetBoundary bit set for the first