network printing/printcap file

[Loonygirl]

Sorry....
Really silly question!
I've searched but can't find an answer....

I had two printers printing off one print server (had to keep swapping the cables). This wasn't ideal, so I bought two new print servers. I've changed the IP address on the print servers to 192.168.44.15 and 192.168.44.19.

I've changed the hosts and printcap file, and I've restarted the printers(via scoadmin), but they still aren't printing. I think my printcap file is wrong!!

Old printcap file:
lineprinter: :lp=:rm=netport1:ex:rp=LPT1:sd=/usr/spool/lpd/lineprinter:
invoice: :lp=:rm=netport1:ex:rp=LPT1:sd=/usr/spool/lpd/invoice:

new printcap file:
invoice: :lp=:rm=invoice:rp=invoice:sd=/usr/spool/lpd/invoice:mx#0:

lineprinter: :lp=:rm=lineprinter:rp=lineprinter:sd=/usr/spool/lpd/lineprinter:mx#0:

I think the rp bit is wrong?? And I don't know what the :mx#0 is? Can I edit these bits via "vi"??

Old hosts files:
192.168.44.15 netport1

New hosts file:
192.168.44.15 lineprinter
192.168.44.19 invoice

Thanks,

Sarah

 

[Loonygirl]

I should have said before...
I added the printer using rlpconf

I can ping the IP, but cannot ping the name of the printer:

ping: wrote lineprinter 64 chars, ret=-1
ping: sendto: Host is down
ping: wrote lineprinter 64 chars, ret=-1
ping: sendto: Host is down

 

[itfellow]

Hey Loony,

I'm not a complete expert on this, but I've been doing a lot of work with this vey thing recently and I've gotten mine to work. Your printcap entries should be as follows:
rm=<the name of your print server>
rp=<the name of your printer>

If you used rlpconf to set these up, then when you are asked for the printer name, you enter a value such as Printer1, specify that it is a remote printer, and when prompted for the name of the remote host that it is attached to, enter the print server name.

I'm not sure if it is possible to call the print server and the printer by the same name without problems, but try it with different names first.

Meanwhile, the print server name and IP should be correct in hosts. You will not be able to ping the printer itself, just the print server.

 

[Loonygirl]

Thanks for that.
I actually got around it by adding the printers via rlpconf and then using the editor vi to edit the bits which were wrong in my printcap file.

Unfortunately, didn't check each time I made a change, and one of the configs works....I'm just not sure which one....lol

Ahh well...I won't do it again ;o)

 

[stanhubble]

I can ping the IP, but cannot ping the name of the printer:
"

since you have changed it in your /etc/hosts file, check /etc/resolv.conf for your "host resolution order"

eg
hostresorder local bind /nis

this tells the system to check the hosts file first then your DNS and not to check nis. your configuration may differ. I think that it checks dns first by default.

 

[aarne]

Hi Sarah

I'm glad that it's working for you.
Anyway, about that mx#0 at the end of the line. I don't know what it means for sure, but if you don't have it, long prints will brake in the midle.

Here are some lines of my printcap, where iolb5 is a matrix-printer connected to terminal server (port 5) called iolb and hpjet2 is a laser-printer with it's own called hpjet2.

iolb5: :lp=:rm=iolb:rp=iolb5:sd=/usr/spool/lpd/iolb5:mx#0:
hpjet2: :lp=:rm=hpjet2:rp=hpjet2:sd=/usr/spool/lpd/hpjet2:mx#0:

So it works also when you call them (printer and server) by the same name.

br. aarne

 

[Loonygirl]

Just for anyone else who reads this....mx#0 on the end of each line means there is no limit on the size of the print job.

Sarah