> Mostly printing is fine. However once or twice a day printing stops. And 
> jobs are removed.

Do you configure your printer with DHCP?  And with a JetDirect config file 
(option 144 to the DHCP/BOOTP server)?

We've had problems with the following sequence of events:
        - TFTP server gets busy and stops listening for connections
        - printer DHCP lease renews
        - printer immediately tries to TFTP its config file
        - printer won't talk to anyone once this happens

The solution for us was to fix the TFTP server with the config files...the 
default inetd daemon under RedHat 6.2 would just loose a file descriptor while 
it was running, causing it to stop listening to TFTP traffic.  No such problem 
with xinetd under RedHat 7.1.  We didn't see any such problems with tftp/inetd 
daemons under Solaris, either.

-- 
============================================================================
   John Perkins                   |   University of Wisconsin-Madison
   Associate Researcher           |   Department of Computer Science
   [EMAIL PROTECTED]               |   1210 W. Dayton St.
   608-262-0438/608-262-9997 FAX  |   Madison, WI  53706-1685
============================================================================




-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to