Problem adding a printer in UNIX.


We have configured a jet direct card on our network.  It has been given a hostname in DNS.  We can ping the card and it appears to be configured correctly.   However,  when we add the printer to UNIX it shows a status of "UNKOWN" and doesn't allow you to print to the printer.  

1.  We can ping the hostname oft he jet direct and it pings back fine.   This tells me that the cabling and jet card are fine
    and that it is configured correctly.
2.  We have swapped the jet direct several time with the same problem.
3.  We can ping the device directly from the UNIX box.

Any ideas on this problem???? Thansks for any help.
TargetuserAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
moduloConnect With a Mentor Commented:
PAQed with points refunded (500)

modulo
Community Support Moderator
0
 
gheistCommented:
What kind of UNIX you use ??? (uname -a)
What printing protocol you chose ???
Is there a firewall involved ???
0
 
TargetuserAuthor Commented:

There is not a firewall beween the UNIX box and the Jet direct card.

The UNIX is AIX version.

It prints using the TCP/IP.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
yuzhCommented:
You need to add the printer to /etc/hosts, eg

10.5.6.123 photocopy-room

then use " smit " to create a a remote queue

          smit queue
           add a print queue
           remote

then
   lp -dRemotequeue printfile

Please have a look at the following docs to learn more details:
http://nscp.upenn.edu/aix4.3html/aixbman/printrgd/init_prt_config.htm
http://www.interex.org/tech/9000/Tech/aix_hpux_interop_v2/chap08_print.html
0
 
gheistCommented:
First ensure that qmanager is running - add one printer using "smitty spooler" , and remove it.
You will need LaserJet backend and some printer driver ( install all of them from CD and patch to your ML)
Anyway - AIX print system will treat "Out Of Paper" as fatal condition, so you will need to bring queue(s) back up once in a hour or so.
0
 
gheistCommented:
More about /etc/hosts;

create file named /etc/netsvc.conf with one line
hosts = local,bind4

for /etc/hosts to precede DNS lookup

And make sure that all your systems's IP interfaces resolve fine in both directions like this:
$ host localhost
localhost is 127.0.0.1
$ host 127.0.0.1
127.0.0.1 is localhost
0
 
GnsCommented:
The UNKNOWN state simply inform you that the "spooler protocol" and ipaddress/hostname you've chosen isn't replying;-).

The clincher here is to _not use REMOTE_ when defining the queue (since this implies everything from (BSD) LPD to SysV lp etc... Not socket/port 9100 that jetdirect uses) in "smitty print"->"Add a Print Queue", but (as gheist very aptly states) install/use both the printer.* packages and HpJetDirect support package from install media (just install every darned printer it knows about:). Once you have that it's rather easy to define a print queue that'll fully support the printserver and printer capabilities.... Do the add bit, select HpJetDirect, choose specific printer etc etc...

-- Glenn
0
 
gheistCommented:
telnet or browse to jetdirect, do whatever it takes to enable lpd/lpr printing, direct mode on port 9000 is supported by AIX-s JetDirect attachment only (not installed by default).
0
 
RobnhoodCommented:
The default port on a jetdirect is 9100 not 9000
0
 
pyschesCommented:
dont print to the jd via port 9100, it has a few problems from Unix systems.

best bet is to enable lpd, which should be on as default, and then point the lpd queue on the AIX box to the ip address..


just use the standard spooler it should work fine..

0
 
RobnhoodCommented:
pysches

Really?  I have been doing it for years without issue.
0
 
GnsCommented:
If you're refering to the risk of lost jobs on timeouts/resets (of the JetDirect device), you run that with LPD too... The defualt state of LPD support varies (at least to my experience). Since modern JetDirect support a wide range of thing... IPP, 9100, LPD, FTP(!) ... you could hack up you own strange printermanagement scripts... But why bother when someone already has, and has made them to fit nicely with the AIX spooler?

-- Glenn
0
 
pyschesCommented:
the devices will actually connect fine via 9100 port and as Gns states there are various other ways to connect to a jetydirect card..

but from a unix box unless you have a HP tool to configure and connect to the pritners (which they only make for Solaris and HPUX) i really would advise using the lpd spooler on the aix box..

also the risk of timeouts is not what i was referring to, its the connection from the aix machine which may vary, unless you have some other management tool.

also set the pritner up as a local lpd queue, as the jd will act as a queue itself just point it to the ip not the hostname.

and if your really stuck, you can always use ftp to print to the jd.

the command is bin to change to binary mode then

put (filename and path)

this should send the job ok..



0
 
RobnhoodCommented:
Why not just load the HP Jetdirection stuff off of the AIX CD's?

Craig Anteman
<advertizing removed by CetusMOD per http:help.jsp#hi106 and http:help.jsp#hi99>
0
 
GnsCommented:
Um. No phyches, the Jetdirect support is solid, no need to do silly hoops (even though you can:-). At least that's my experience.
As to management... Who cares about JetAdmin these day? You can set everything you need via telnet or http... The printers/jd are even a bit more stable if you restrict what protocols they will will support. Again, that's my experience at least.

-- Glenn
0
 
yuzhCommented:
Glenn is right !

I have a lot of HP LaserJet printers, and I never have to worry about
to use JetAdmin.
0
 
gheistCommented:
Either you choose jetdirect or lpd, the AIX spooler will misunderstand the "out of paper"condition as permanent fatal error, and you will need to bring queues back up by hand or by cron time after time.
0
 
TargetuserAuthor Commented:
I'm not sure about this one.  They readded the printer several times and it worked.

Not sure of the cause.
0
 
GnsCommented:
.... And what did they end up with? A "pure LPD" or "JetDirect" printer queue?

-- Glenn
0
 
TargetuserAuthor Commented:

Pure LPD
0
 
GnsCommented:
Ok. Simply "got it right" whilst frobbing then perhaps?-) Or someone enabled LPD support on the HP side... Or ....:-)

Sounds like the issue for this Q is solved, so... You should perhaps try to decide on who (or whom) to bestow the points on, or even have it refunded (if you deem our help worth... naught at all:-).

-- Glenn
0
 
pyschesCommented:
jsut a quick question..

what type of jetdirect do you have and what is the firmware version on it???

0
 
TargetuserAuthor Commented:
I'll have to check on that.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.