We help IT Professionals succeed at work.

printing from Red Hat 7.2 to Win98 networked printer

phirephly
phirephly asked
on
I've an HP 932C deskjet printer. It is hooked to a computer called oscar which is running Win98. The printer is shared. We'll say the share is called //oscar/printer I can print to it from other Win98 machines on the network without problem. I want to print to it from my Red Hat 7.2 machine. I've been all over the place trying to find help online on webpages and stuff (Red Hat's site, linuxprinting.org, etc), but either what they're saying doesn't make sense or doesn't work. I need someone to very closely guide me through the setup and be able to explain what I'm doing and why so that I understand what I'm doing so I could do it again later. I think I've installed the latest drivers, but I'm not 100% sure. I think I may also need to reinstall ghostscript, but I'm not particularly sure how to do that either and don't want to mess up mixing 6.51 and 6.52 and lose the whole thing. I have more points if we really get into things.

Here's the link that I've been using as an install guide:
http://hpinkjet.sourceforge.net/install.php

Here's Red Hat's manual page about installing an SMB printer (which hasn't worked):
http://www.redhat.com/docs/manuals/linux/RHL-7.2-Manual/custom-guide/printconf-smb-printer.html

Here's a link that I think is supposed to be useful, but I don't know how:
http://www.linuxprinting.org/show_driver.cgi?driver=hpijs 

The page i'm using as an install guide asks for some diagnostics to see things working... here are the relevant outputs (in order):

hpijs -h:

Hewlett-Packard Co. Inkjet Server 1.0.2
Copyright (c) 2001, Hewlett-Packard Co.
(means I've got 1.0.2 installed correctly, right?)

gs -h:...
bjc880j lips4 lips4v escpage lp2000 npdl md50Mono md50Eco md1xMono hpijs
  DJ630 DJ6xx DJ6xxP DJ8xx DJ9xx DJ9xxVIP AP21xx hpdj md2k md5k stp lxm3200
...

there is no ijs entry in there. I think that's important, but have no idea what to do about it.

Hopefully this helps someone help me get this going! Thanks so much for your help!! ttyl,

mich
Comment
Watch Question

Author

Commented:
ok... I'm still working on this for better or worse even if there aren't any posts, so here's what I've been trying today:

I was working under the assumption that the ijs was installed correctly and I need to reinstall ghostscript. I got the RPM for both the versoin I have (6.51) and the latest version (6.51). Here's the first transaction I tried...

> rpm -U ghostscript-6.52-1.i386.rpm
error: failed dependencies:
       Omni is needed by ghostscript-6.52-1
       libpng.so.3   is needed by ghostscript-6.52-1
       libstdc++.so.4   is needed by ghostscript-6.52-1
So I found rpms to install Omni and libstdc++, but libpng isn't working. Here are my tries at that:

> rpm -i libpng-1.2.1-2.i386.rpm
file /usr/share/man/man5/png.5.gz from install of libpng-1.2.1-2 conflicts with file from package libpng-1.0.12-2

>rpm -U libpng-1.2.1-2.i386.rpm
error: failed dependencies:
       libpng = 1.0.12 is needed by libpng-devel-1.0.12-2
       libpng.so.2   is needed by gdk-pixbuf-0.11.0-8
       libpng.so.2   is needed by netpbm-progs-9.14-2
       libpng.so.2   is needed by imlib-1.9.10-2
       ...
       ...
       libpng.so.2   is needed by PyQt-2.4-1
       libpng.so.2   is needed by ghostscript-6.51-16
(note the bottom one is the package that I'm trying to upgrade past with this upgrade! how frustrating :(  

So then still doing this fails as expected:
rpm -U ghostscript-6.52-1.i386.rpm
error: failed dependencies:
       libpng.so.3   is needed by ghostscript-6.52-1

So I have no idea what's going on or what i'll do tomorrow... Hopefully something that someone suggests to help!  Again, if you need some kinda diagnostic info, let me know.

Here's where I've been finding the rpms I've been talking about:  http://www.rpmfind.net

thanks and ttyl,

mich
Commented:
I'm not a Linux wizard, but from the conflicts and dependencies you posted, it looks like you'll need to remove libpng-1.0.12-2 before installing libpng-1.2.1-2.  It also looks like libpng-devel-1.0.12-2 relies on that package, so you may need to remove that first.

Commented:
Also, there is a Linux Printing category under Operating Systems...  You might want to put a link to your question over there.

Author

Commented:
I do have a link in the linux printing category, also threw it in linux networking since it fits in there too. You're the only brave soul so far, shawn :) I haven't tried uninstalling and reinstalling libpng yet, but that's on my to do list for tonight. I'll post what happens! thanks for your comments... 'sok if you're not a wizard, I'll settle for a semi-wizard or less if (s)he can get my printer working! :p ttyl,

mich
BRONZE EXPERT

Commented:
listening ..
rid

Commented:
This may not be very helpful, as I'm not very well versed in Linux, but I get the impression you are into postscript country here. Is this a PS printer?
I have a similar setup, only it's win NT and an Epson inkjet. The setup was made using the printtool utility only; it works, but I cannot use the advanced features of the printer.
Can you even print an ASCII test page from printtool?
Regards
/RID

Author

Commented:
I don't think it's a PS printer (but I'm not sure, to be honest). I've used the printtool to try a bunch of different setups for the printer with no success. Neither the ASCII test page or the PS test page work from the printtool.

I've only got the printer to even appear to respond to me from an smb-client command line. I sent a print command directly to the printer from there. It proceeded to start printing pages with only one line of gibberish at the top, so I killed it.

So no... I'ven't seen anything useful come out of the printer from the RH box... at all.
Here are the errors I got when I tried uninstalling packages... Sorry I didn't do it last night. I ended up having plans... who knew?

rpm -e  libpng-devel;echo RESULT=$?
error: removing these packages would break dependencies:
     libpng-devel is needed by imlib-devel-1.9.10-2
RESULT=1

rpm -e  imlib-devel;echo RESULT=$?
error: removing these packages would break dependencies:
     imlib-devel is needed by gnome-libs-devel-1.2.13-16
RESULT=1

rpm -e  gnome-libs-devel;echo RESULT=$?
error: removing these packages would break dependencies:
     gnome-libs-devel is needed by control-center-devel-1.4.0.1-18
     gnome-libs-devel is needed by gdk-pixbuf-devel-0.11.0-8
     gnome-libs-devel is needed by libglade-devel-0.16-4
RESULT=1

yup. I followed the dependencies back three levels... Any more ideas? please?? :p I'ven't any idea where to go now.... thanks and ttyl,

mich

Author

Commented:
just thinking... should I force the uninstall or something?  if I were to install the updated rpms, would the dependencies be reestablished?  prolly not, right? ttyl,

mich
Commented:
Hi,

've only just followed the link that you did provide in
'Linux printing'  . . .
so here is a SAMBA setup link that successfully helped in the past:
http://www.linuxhelp.net/guides/janou/samba.shtml
it splits up even further to other helpful guides

You may even move up one level
http://www.linuxhelp.net/guides/

or two
http://www.linuxhelp.net

to decide for an other
document of
your choice.

Meanwhile I have another scan of
your postings to see if we've
missed anything crucial
but as far as the SMB printing
configurations side is concerned,
you have to stick to other means I'm afraid  ;-9  
 

Commented:
Back to you
phirephly,

Almost missed it at the beginning of your
question thread:

The Redhat site isn't a very good place to look for help with
the printconf-gui setup. Some of the manuals are not quite
clear & do have mistakes in them.
Anyway, I seriously recommend to use 'printconf-gui'
as an optimized tool for printing setup at your RH Linux box.
You have to use it rather than
modifying workable existing ghostscript files.
The 'printconf-gui' does have the printer definition files
& preconfigured setup options ready for your HP 932 C printer.
The 'hpijs' is within the list of selectable printer drivers, too.
So, no need to go for anything else.
Even worse, if trying to upgrade files on your system, which
are already integrated into a working complex of print automation
as it is with the RH print system, you'll likely spoil what
could be an easy task otherwise.

Please try to get your system back to how it was before you
ventured into ghostscript updates. Provided that you did a
standard workstation installation of your system, all you need
for your printer setup should be
existing there, preconfigured & definable with 'printconf-gui'.
Use the existing 'printconf-gui' as a stable point to start from.
I'll assist you with this to best of my knowledge but it shouldn't be
that difficult.
Above you mentioned that you already tried to get in with
'printconf-gui' , however to a point of frustration.
So please share to us your record of previous efforts
when using printconf-gui.

Regards,

xberry
 

Author

Commented:
the only thing I appear to be successful in at all altering on my computer was the hpijs driver. I updated that from 0.9x to the new 1.0.2. As I was writing earlier, I couldn't get anything in ghostscript to update because of error after error. Your samba page talks about setting up a server. That's not what I'm having trouble with. I want to print to a printer that's on a Win98 machine, not have a Win98 machine connect to me (I've done that successfully on other RH boxes). Most of the guides there are out there assume everything's all set to go. I think there's something not "all set to go" here. Need someone to help me diagnose what that is and get it installed.

This line "The ijs device supports the IJS interface. All other devices (hpijs DJ630 DJ6xx DJ6xxP DJ8xx DJ9xx DJ9xxVIP AP21xx) are supported through the old HPIJS interface." on this page http://hpinkjet.sourceforge.net/install.php is why I think there might be something wrong with ghostscript. But who knows, maybe I'm totally wrong. If I knew what I was doing, I'd be printing already. :p

Today, I printed off a test page from another Win98 box to be sure the printer was running properly. Then I went through ALL the drivers listed under 932C (just like I did before I originally posted the question): cdj550, cdj880, hpdj, hpijs, pcl3, and stp. I tried printing an ASCII text page, a postscript test page and GIF test image with each driver and none of them did a single thing. I also tried each driver with the two options both on and both off: "rerender postscript" and "convert text to postscript" just in case the postscript thing was messing things up. After all of these failed again, I also tried again the generic print queues at the top of the driver list: postscript printer, text only printer, and raw print queue with the same test pages. Still nothing at all has come out of the printer.

So actually, despite all the postings (including my own), I'm still exactly where I started with the hpijs upgraded (I guess). Hopefully this helps you help me out. thanks and ttyl,

mich

Author

Commented:
Alrighty. I've now also tried hooking the printer directly via a parallel cable and that didn't work either. I ran thru all the drivers and tried to print all three pages again. When the machine boots, I get this error message when it tries to start lpd: "cannot stat 'if' filter /usr/local/sbin/smbprint no file or directory" and it's stat not start, I didn't type it wrong. The file/directory it's talking about indeed doesn't exist, but I don't know who's trying to point at it or what to do about it.

I tried to go back and reinstall all the printer stuff just in case I could restore it, but the Red Hat upgrade thing won't let you touch that part of it. All I can mess with are the individual packages, and didn't see anything in there that appeared to be useful for what I wanted. Reinstalling the system is a very very very very very very distant option. 100% last shot. And I still don't think that will do anything since I don't think I've altered this one that much.

I was looking around my file structure and found a bunch of files that look like this in my /tmp directory:

-rw-------    1 lp       lp            216 Jan 30 16:54 gs_wYAg2z
-rw-------    1 lp       lp          82297 Jan 30 16:54 gs_XnOjLu
-rw-------    1 lp       lp            216 Jan 30 15:43 gs_yNZTr5
-rw-------    1 lp       lp            984 Jan 23 11:39 gs_YqEYKP
prw-------    1 lp       lp              0 Jan 30 16:54 hpijs_c2s_1018
prw-------    1 lp       lp              0 Jan 30 19:50 hpijs_c2s_1335
prw-------    1 lp       lp              0 Jan 30 15:37 hpijs_c2s_1354
prw-------    1 lp       lp              0 Jan 30 15:43 hpijs_c2s_1488
prw-------    1 lp       lp              0 Jan 23 11:34 hpijs_c2s_8343

They extend in both directions for a ways. These are queued jobs? Would they be interfering with my attempts to install the printer? If anybody's still out there, let me know! I'd prefer to have the printer on the Win98 box, but if getting it working locally will help, then we can work on that. I spose if we can get the Win98 boxes printing on the RH machine, that would be an acceptable alternative. But it's not a samba issue right now. It's a printer issue still. thanks and ttyl,

mich

Commented:
> I'd prefer to have the printer on the Win98 box

Up to now I took that your printer is sitting at the
win 98 box. It is difficult to help if I'm talking about different
things.

> It's a printer issue still.

This has been my idea, too.

Regarding the files in /tmp: Don't worry about them. The one
with the gs in front are temporary ghostscript test files from
your test printing, BUT whether the queue is blocked or not
anywhere you check with:

lpc status all

You can remove any 'old' print jobs, which likely block your printing
with the command

lprm -a all

I'm just working through your latest postings, so please give me some time.
Again, I wouldn't worry too much with what you got from sourceforge,
either.
Right now we need a point of stability there, so where is
your printer right now ?


 

Author

Commented:
Up until my last post, you were right. The printer was on the Win98 box. It was connected via USB. I hooked the parallel cable to the RH machine yesterday to see if I could get *anything* to work between the RH machine and the printer. I unhooked the USB connection to the Win98 machine just in case the printer couldn't handle both connections. I want the printer on the Win98 machine. If you don't think it will help the setup to put it on the RH box, I'll move it back. I thought it would help try to get things going by removing all the cross platform networking. At this very moment the printer is connected via parallel to the RH machine.

Did the lpc status all and it showed empty queues. One of them is a printer I deleted. I don't know why it's still on there. I did a lprm -a all just in case there was something I wasn't seeing. I still couldn't print after that, but I saw the queue (the right one, at least!) getting jobs. Then I deleted 'em since they weren't doing anything.

ttyl,

mich

Commented:
> At this very moment the printer is connected
                           via parallel to the RH machine.

Good idea, so we will be able to see if your RH systems print queuing, driver files & so on is
working ok with your printer & what might be necessary in order to have it working as
a local print device. It's now just a case of debugging to find where it still blocks.
Once it will do its job as a local printer then it is just a case to set
it back to your Windows 98 machine, giving it a share
& then at your Linux machine changing the queue
to Windows SMB type.

Ok, right now I'd just remove any existing queue setup
that you'd find listed in your printconfigutation.
Noting related to smbprint should come up any longer.
Then only build up a LOCAL queue for your printer
at /dev/lp0  (or lp1,. . .
chose your 'hpijs' from the
list of print drivers,
setup your driver options (A4 page size ! )
save your setup &
restart lpd
If everything is lined up ok
you should get a result with 'printing A4 postscript test page'

Author

Commented:
This is strange, and might be causing problems, I would imagine. When I add a print queue using printconf-gui, it shows up in the list when I do a lpc status all. But, even after I delete all the queues, one remains - and it's the remote one. Here's what it looks like:

Printer           Printing Spooling Jobs  Server Subserver Redirect Status/(Debug)
HP_Deskjet_on_Oscar@bigbird  enabled  enabled    0    none    none

This would seem like it's problematic, how do I remove this manually, I guess? Like what file do I need to edit? ttyl,

mich

Commented:
hm, don't see why it shouldn't disappear if you did save all your changes
in 'printconf-gui'.

So try again. Select your HP_Deskjet_on_Oscar entry, then
' Delete ', ' File > Save Changes ', ' File > Restart LPD '.

Additionally have a look in
/var/spool/lpd

there shouldn't exist any spool directories for your printer queue any longer. Else given, manually remove any content from there.

The only other reason why it still may find a queue for your
remote print setup is /var/spool/samba if it still does exist on
your system. Check it out.

Right, so when you built up your LOCAL printer then,
after having done the configurations, also first save your changes
before you restart your LPD. Then, if it still doesn't work, try this:

[root]# checkpc -f -P yourprinter

The checkpc is used to check for the existence & correct permissions
of entries & correct permissions of entries in the printcap database
(see man checkpc)

If your printer still doesn't work, then I suggest to do this
little test:

0.) lprm -a all
1.) In your root directory create a printfile
2.) [root]# lpr -Pyourprinter printfile
3.) If you didn't get a printout from your printer do
     [root]# checkpc -f
instantly after your lpr testprint & see if it does give you any error messages, which could be well an indicator for what's wrong there.




 


Commented:
hm, don't see why it shouldn't disappear if you did save all your changes
in 'printconf-gui'.

So try again. Select your HP_Deskjet_on_Oscar entry, then
' Delete ', ' File > Save Changes ', ' File > Restart LPD '.

Additionally have a look in
/var/spool/lpd

there shouldn't exist any spool directories for your printer queue any longer. Else given, manually remove any content from there.

The only other reason why it still may find a queue for your
remote print setup is /var/spool/samba if it still does exist on
your system. Check it out.

Right, so when you built up your LOCAL printer then,
after having done the configurations, also first save your changes
before you restart your LPD. Then, if it still doesn't work, try this:

[root]# checkpc -f -P yourprinter

The checkpc is used to check for the existence & correct permissions
of entries & correct permissions of entries in the printcap database
(see man checkpc)

If your printer still doesn't work, then I suggest to do this
little test:

0.) lprm -a all
1.) In your root directory create a printfile
2.) [root]# lpr -Pyourprinter printfile
3.) If you didn't get a printout from your printer do
     [root]# checkpc -f
instantly after your lpr testprint & see if it does give you any error messages, which could be well an indicator for what's wrong there.




 


Commented:
load 'webmin' ( available from www.webmin.com ) its a web based admin tool which is totally easy to use.

Make sure you have samba loaded, then logon via browser to your server via port 10000 ( eg, http://servername:10000 )

goto printer configuration option, create new and then select windows printer and point to the server in question.

You may have to put the win98 machine in the hosts file to reference the name-ip

Commented:
I'm going to be a real pain here but I think we are going to have to try to narrow down the problems one by one. Some questions spring to mind. Are the print jobs arriving at the Doze box. do they appear in the printer queue on that box (however briefly <g>) (flood the thing with jobs incase they pop up and are discarded to fast to see) emph Not do they print but do they arrive. They probably won't print cause the device isn't supported by you're installed version of ghostscript. quote

gs -h:...
bjc880j lips4 lips4v escpage lp2000 npdl md50Mono md50Eco md1xMono hpijs
  DJ630 DJ6xx DJ6xxP DJ8xx DJ9xx DJ9xxVIP AP21xx hpdj md2k md5k stp lxm3200. end quote in your previous post.
...
but let's see if they turn up first <g>
If they are arriving but not printing we can eliminate a samba problem. If they aren't arriving then we have to look at samba. smbprint can be a funy b******r sometimes <g>.

Commented:
You're remote queue is still there cause samba is setting it up, it's not going to cause any probs and you'll need it later when the problems are sorted. We are going to have to deal with the problem one step at a time. The printing process for a remote printer is
1. gs produces printable copy.
2. this is sent to the print queue for the remote printer.
3.the job is sent to the machine which connects to the remote printer.
4. the remote machine recieves and queues the job.
5. the job is sent to the printer.

So far we cannot establish stage 1. When the printer is connected locally phir still cannot print!!

Commented:
so let's sort out the ghostscript problem first
Asta CuTechnical consultant & graphic design
BRONZE EXPERT
Top Expert 2004

Commented:
Have you been helped here or is more needed?

If you've been helped, please convert that Expert's comment to the Accepted Answer to grade and close this.

If more is needed, please tell us.  I am willing to help you here, but not if this is no longer a need.

If Asker does not respond in 7 days, Experts, please post closing recommendations.

If you found/posted your own solution, please post that solution here and request a refund/PAQ in the Community Support with a zero point question (include this link).

Thanks,
":0) Asta

Commented:
I am assuming that when you set up your network you switched the localhost to your computer name?  Now when your printcap looks for localhost it is not defined. Easyfix: Go into your network setting and put in a new host in your list

you can use gui but in the location where you add all the hosts in your network add

ip 127.0.0.1
name localhost
alias $YOURCOMPUTERNAME$

That might work
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:
[split points between shawn313 and xberry ]
Please leave any comments here within the next four days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!

[MRFIXITPC]
EE Cleanup Volunteer

Explore More ContentExplore courses, solutions, and other research materials related to this topic.