First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 6247
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Guenther Deschner <gd@samba.org>
Hardware:
OS:
Version:
Priority:
Severity:
Target Milestone:
Reporter: Fabio Muzzi Frabetti <kurgan@kurgan.org>
Add CC:
CC:
QA Contact:
URL:
Summary:
Keywords:
Flags: Requestee:
  ()

Attachment Type Creator Created Size Flags Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 6247 depends on: 6099 Show dependency tree
Show dependency graph
Bug 6247 blocks:

Additional Comments:







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2009-04-05 13:21 CST
I have a Samba 3.3.2 member server, named mailbkp1, which I joined to a
Samba 3.3.2 domain controller.

At joining time, I got two consecutive identical errors on the domain
controller. I report here one of them:

[2009/03/31 14:08:47,  0]
rpc_server/srv_netlog_nt.c:_netr_ServerAuthenticate2(546)
  _netr_ServerAuthenticate2: netlogon_creds_server_check failed.
Rejecting auth request from client MAILBKP1 machine account MAILBKP1$   

After joining, users can logon properly, and everything seems to work,
but every time the member server gets a new connection, and contacts the
DC to authenticate the user, I get the same error again on the DC. 


I have also tried joining a 3.3.2 Samba server to a NT4 PDC, and while
the Samba member server still works properly, I get similar messages (the
machine failed to authenticate itself) in the Event Viewer of the NT4
PDC.


Fortunately this error seems not to be an issue, since everything seems to work
properly even if I get errors at every user logon on the member servers.

------- Comment #1 From Guenther Deschner 2009-04-06 05:39:21 CST -------
looking into this one.

------- Comment #2 From Guenther Deschner 2009-05-19 03:25:35 CST -------
Ok, this is the broken credential chain we used to have in some 3.3 and 3.2
releases. The fixes that are currently applied for bug #6099 will resolve these
issues.

------- Comment #3 From Karolin Seeger 2009-05-19 04:08:02 CST -------
Patches for bug #6099 will be included in 3.2.12 and 3.3.5.
Closing out bug report.
Please re-open if it's still an issue in these releases.

Thanks for reporting!

First Last Prev Next    No search results available      Search page      Enter new bug