Occasional (not all the time), they will go to print to their laser printer
on the HP Print Server (this is the 3 port model) and the print does not
come out. Sometimes it takes up to an hour, and lo and behold the job will
come out.
Printing from the workstations (PC's) directly to the laser on the print
server seem to work fine, only the UNIX box seems to have trouble seeing
the print server. The job just remains in the printer queue. The printers
are setup with the standard scoadmin utilities for the HP print server, and
work fine most of the time.
When this problem occurs, their Bay Networks network connection fires up,
giving the indication that someone gave a network address outside the local
network and the gateway is needed.
The HP Print Server is in the /etc/hosts file.
This system is setup with a local network address: 129.2.156.30/255.255.0.0
Not sure what other information would be helpful.
The Print Server is 129.2.156.37
Any ideas?
-> Bob Willey - b...@ccs.com <-
CCS Enterprises, Inc.
PO Box 35 Linkwood MD 21835
http://www.ccs.com Come Visit Us !!
http://www.intercom.net/user/consult
-> (410) 228-9211 -- FAX: (410) 901-1105 <-
> Occasional (not all the time), they will go to print to their laser printer
> on the HP Print Server (this is the 3 port model) and the print does not
> come out. Sometimes it takes up to an hour, and lo and behold the job will
> come out.
> Printing from the workstations (PC's) directly to the laser on the print
> server seem to work fine, only the UNIX box seems to have trouble seeing
> the print server. The job just remains in the printer queue. The printers
> are setup with the standard scoadmin utilities for the HP print server, and
> work fine most of the time.
> When this problem occurs, their Bay Networks network connection fires up,
> giving the indication that someone gave a network address outside the local
> network and the gateway is needed.
> The HP Print Server is in the /etc/hosts file.
> This system is setup with a local network address: 129.2.156.30/255.255.0.0
> Not sure what other information would be helpful.
> The Print Server is 129.2.156.37
> Any ideas?
Tough one. I'd start by turning on hpnpf debugging. Turn it
on in the interface script's 'wrapper' (in admins/lp/interfaces;
not model.orig) then looking in /tmp for files like *hp*, plus whatever
file you specified with '-l'.
-l logfile
Write verbose logging information to logfile. The logging messages
are detailed messages about what hpnpf is doing. Included in the
messages are how many bytes are read and written to the network
connection. hpnpf performs no logging if you omit this option.
-sw
If this is the case, you should see the JetDirects' LAN traffic light going
ape, and nothing happening. Disconnect printer 2 or 3 and connect to port 1,
and it will print on that port, not the one you sent it to.
Technology can be wonderful.
Dunc.
<swe...@scruznet.com> wrote in message
news:UEf44.1232$CA5....@typ11.nn.bcandid.com...