[EMAIL PROTECTED] wrote:
> 
[problem description deleted]
> 
> Oh my oh my oh my...  I have a funny feeling I know what the problem is.
> 
> Question 1:  what are these printers?

They are an HP LaserJet 4000 and an HP 4SiMX (in two documented cases so
far).

> Question 2:  are you using the Appsocket protocol?

In one documented case, the printer to which the job was sent and the
one which got the job were AppSocket printers, and in another, the
printer to which it was sent was an AppleTalk printer (using NetAtalk)
and the one which received it was an AppSocket printer.

> Question 3:  are you running a DNS server on the spooler? Is it in caching mode?

No, and therefore, no.

> Question 4:  do you use DHCP?  and are your DNS entries being updated?

No. And our DNS entries are up to date and only change every three
hours.

> 
> I hate to say this,  but I think this is a network/DNS/TCP-IP problem...

The above instance where the original printer was an AppleTalk printer
makes me doubt that. In addition, when an incorrect print job comes out
of a printer, it follows a different persons banner page (I don't know
if this is also happening on printers where there is no banner page
printed - it may be and I just haven't heard about it) whose job never
comes out (it could come out somewhere else - again, I'm not sure). If
it were a DNS problem, that should be persistent enough to cause this
issue for longer than that. This will happen with one print job that
follows a good job and which is followed by another.

> 
> Patrick
> 
> Patrick Powell                 Astart Technologies,
> [EMAIL PROTECTED]            9475 Chesapeake Drive, Suite D,
> Network and System             San Diego, CA 92123
>   Consulting                   858-874-6543 FAX 858-279-8424
> LPRng - Print Spooler (http://www.astart.com)
> 
> -----------------------------------------------------------------------------
> 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.
> -----------------------------------------------------------------------------

-- 
                        Bill Knox
                        Senior Operating Systems Programmer/Analyst
                        The MITRE Corporation

-----------------------------------------------------------------------------
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