Andrew, >> Andrew, >> >> Does this mean that you cannot duplicate the issue any more ?
>Correct. However, my original reporter still reproduces the issue. Could you explain a little bit more about this ? If you put everything back to original condition, you can still see the problem with XP ADCU. After some changes made to schema, the problem doesn't occur any more. Is my understanding right ? Should I still concentrate on the original condition under which we have a capture ? Is it possible for you to send us a network trace for the current successful condition so we can compare ? Thanks ---------------------------------------------------------- Hongwei Sun - Sr. Support Escalation Engineer DSC Protocol Team, Microsoft [EMAIL PROTECTED] Tel: 469-7757027 x 57027 ----------------------------------------------------------- -----Original Message----- From: Andrew Bartlett [mailto:[EMAIL PROTECTED] Sent: Monday, September 22, 2008 5:22 PM To: Hongwei Sun Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [cifs-protocol] RE: [Pfif] Microsoft Client tool expectatations On Mon, 2008-09-22 at 14:31 -0700, Hongwei Sun wrote: > Andrew, > > Does this mean that you cannot duplicate the issue any more ? Correct. However, my original reporter still reproduces the issue. > Can you give us some clarification at your earliest convenience ? > The only information I have been using for my investigation is > winxp-aduc-fail.cap attached in your original e-mail ? Is it still > relevant ? That shows the original failure - but as this could be any part of the whole schema that is incorrect, it is hard to tell what is wrong. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. http://redhat.com _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
