RE: [ActiveDir] 675 Pre-Authentication failure errors

2005-02-15 Thread Free, Bob
@mail.activedir.orgSubject: RE: [ActiveDir] 675 Pre-Authentication failure errors Just to close the loop on this issue, we have a QFE package that resolves this issue and stops the flood of events. Call PSS and ask for Q888612. This need only be applied to win2k SP4 servers, the issue does not exist anywhere

RE: [ActiveDir] 675 Pre-Authentication failure errors

2005-01-26 Thread Eric Fleischman
Of Eric Fleischman Sent: Monday, January 17, 2005 10:47 AM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] 675 Pre-Authentication failure errors I should have been more clear. The issue is on the server with the app, not the DC logging the events. So the dependency is not DC side

RE: [ActiveDir] 675 Pre-Authentication failure errors

2005-01-17 Thread Dave Lamberty
this fix when it becomes available? Thanks! --Dave -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric FleischmanSent: Sunday, January 16, 2005 23:27To: ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] 675 Pre-Authentication failure errors

RE: [ActiveDir] 675 Pre-Authentication failure errors

2005-01-17 Thread Eric Fleischman
@mail.activedir.org Subject: RE: [ActiveDir] 675 Pre-Authentication failure errors Hello Eric, We are experiencing the same problem, although it has not (to this point) kept users from accessing resources. Our logs simply fill with 675 errors. Can you tell me if this patch

RE: [ActiveDir] 675 Pre-Authentication failure errors

2005-01-17 Thread Eric Fleischman
Fleischman Sent: Monday, January 17, 2005 10:03 AM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] 675 Pre-Authentication failure errors Without confirmation as to whether or not we have properly fixed the issue, it would be premature to answer that question. ~Eric From

RE: [ActiveDir] 675 Pre-Authentication failure errors

2005-01-16 Thread Eric Fleischman
I have been involved in this very issue behind the scenes here at MS. It is a known issue, with the root of the issue identified. We have a fix we are currently testing, and anticipate success in the test over the next few days. We are comfortable with it internally, waiting only on a