samba - Jan 2012 - issues with printing

We have recently started having an odd problem with printing via samba (3.6.1).
Samba is joined via security = ads to our domain. We do not use winbind on this
system. Our account usernames are provided via openldap.

User starts system (generally windows 7 64bit, but we've seen it on 32bit
windows 7 and XP), sometimes they can print, sometimes they can't. If they
reboot, they can almost always print.

I've turned the logging up to level 3 and have noticed repeated errors like

[2012/01/04 09:10:32.252107,  2] auth/auth.c:319(check_ntlm_password)
  check_ntlm_password:  Authentication for user [MACHINENAME$] ->
[MACHINENAME$] FAILED with error NT_STATUS_NO_SUCH_USER
[2012/01/04 09:10:32.252212,  3] smbd/error.c:81(error_packet_set)
  error packet at smbd/sesssetup.c(124) cmd=115 (SMBsesssetupX)
NT_STATUS_LOGON_FAILURE

Which I suspect has to do with the lack of winbind and not having machine names
in our ldap service.

I should note that this all worked perfectly up until a few weeks ago and then
just started breaking randomly.. Isn't that always the case?

I appreciate any pointers.

Thanks.

Tom

On 1/4/12 9:13 AM, "Tom Ryan" <tomryan at camlaw.rutgers.edu>
wrote:
>We have recently started having an odd problem with printing via samba
>(3.6.1). Samba is joined via security = ads to our domain. We do not use
>winbind on this system. Our account usernames are provided via openldap.
>
>User starts system (generally windows 7 64bit, but we've seen it on
32bit
>windows 7 and XP), sometimes they can print, sometimes they can't. If
>they reboot, they can almost always print.
>
>I've turned the logging up to level 3 and have noticed repeated errors
>like
>
>[2012/01/04 09:10:32.252107,  2] auth/auth.c:319(check_ntlm_password)
>  check_ntlm_password:  Authentication for user [MACHINENAME$] ->
>[MACHINENAME$] FAILED with error NT_STATUS_NO_SUCH_USER
>[2012/01/04 09:10:32.252212,  3] smbd/error.c:81(error_packet_set)
>  error packet at smbd/sesssetup.c(124) cmd=115 (SMBsesssetupX)
>NT_STATUS_LOGON_FAILURE
>
>Which I suspect has to do with the lack of winbind and not having machine
>names in our ldap service.
>
>I should note that this all worked perfectly up until a few weeks ago and
>then just started breaking randomly.. Isn't that always the case?
>
>I appreciate any pointers.
>Thanks.
>
>Tom
I've included a full log from a failed print session here:

http://pastebin.com/WBA4PEnG

Thanks for any consideration.

Tom