samba - Jan 2011 - Strange problem - print_job_start: job start denied by time check

Hi,

Having a very odd problem with a printer that I've had up and running 
for over a year now with no previous issues.  There have been no 
software or hardware updates recently that should have affected it.  The 
printer is managed via CUPS and its details are loaded from the CUPS 
printcap.  At some point late on the afternoon of the 11th, samba 
started rejecting print jobs sent to it. Turning up logging details 
showed the following for a typical request:

[2011/01/12 01:29:19,  4] printing/nt_printing.c:print_access_check(5832)
   access check was SUCCESS
[2011/01/12 01:29:19,  3] printing/printing.c:print_job_start(2381)
   print_job_start: job start denied by time check
[2011/01/12 01:29:19,  3] smbd/error.c:error_packet_set(61)
   error packet at smbd/error.c(137) cmd=45 (SMBopenX) 
NT_STATUS_ACCESS_DENIED

This has happened quite a few times.  Since the problem started, I have 
been able to print successfully on one occasion.  This was a job that 
was sent to the printer at exactly 0100 GMT.  All other requests are 
denied with the time check message.

I have not configured any time restrictions on my printer, and accessing 
it via 'lpr' works fine.

smb.conf is reproduced below, with comments removed for brevity.  Samba 
version is 3.2.5 (debian package 3.2.5-4lenny13).

#########
[global]
    workgroup = meridiangrp
    server string = %h server

    dns proxy = no

    log file = /var/log/samba/log.%m
    log level = 4
    max log size = 1000
    syslog = 0
    panic action = /usr/share/samba/panic-action %d

    security = user
    encrypt passwords = true
    passdb backend = tdbsam
    obey pam restrictions = yes
    invalid users = root
    passwd program = /usr/bin/passwd %u
    passwd chat = *Enter\snew\sUNIX\spassword:* %n\n 
*Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .

    load printers = yes
    printing = cups
    printcap name = cups

    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

[homes]
    comment = Home Directories
    browseable = no
    writable = yes
    create mask = 0750
    directory mask = 0750
    valid users = %S

[www]
    comment = Websites
    writable = no
    locking = yes
    path = /work/www
    public = no

[printers]
    comment = All Printers
    browseable = yes
    path = /var/spool/samba
    printable = yes
    public = yes
    writable = yes
    guest ok = yes
    printer admin = jules

[print$]
    comment = Printer Drivers
    path = /var/lib/samba/printers
    browseable = yes
    read only = yes
    guest ok = no

###########
/etc/cups/printers.conf:

# Printer configuration file for CUPS v1.2.7
# Written by cupsd on 2008-08-07 13:30
<Printer EPSON_Stylus_Photo_R285_USB_1>
Info EPSON Stylus Photo R285
Location Local Printer
DeviceURI usb://EPSON/Stylus%20Photo%20R285
State Idle
StateTime 1218112240
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
</Printer>


/etc/printcap:

# This file was automatically generated by cupsd(8) from the
# /etc/cups/printers.conf file.  All changes to this file
# will be lost.
EPSON_Stylus_Photo_R285_USB_1|EPSON Stylus Photo 
R285:rm=vengeance.meridiandigital.net:rp=EPSON_Stylus_Photo_R285_USB_1:

On Wed, Jan 12, 2011 at 02:07:12AM +0000, Jules wrote:
> Hi,
> 
> Having a very odd problem with a printer that I've had up and
> running for over a year now with no previous issues.  There have
> been no software or hardware updates recently that should have
> affected it.  The printer is managed via CUPS and its details are
> loaded from the CUPS printcap.  At some point late on the afternoon
> of the 11th, samba started rejecting print jobs sent to it. Turning
> up logging details showed the following for a typical request:
> 
> [2011/01/12 01:29:19,  4] printing/nt_printing.c:print_access_check(5832)
>   access check was SUCCESS
> [2011/01/12 01:29:19,  3] printing/printing.c:print_job_start(2381)
>   print_job_start: job start denied by time check
This is caused by print_time_access_check() returning false.
That happens if the printer info stored in the printer tdb's
specifies a restricted print time range.

Take a look at this using the print manager on the client
I think.

Jeremy.