Network Printing Woes

I hope it's only a permissions issue because I've tried
many things to resolve this. I chmod 777 the spooling
directory for the "lp" queue, the default printer on my
setup. I just looked at /dev/lpt0 and it looks like this:

crw------- 1 root wheel 16, 0 Jan 11 18:21 /dev/lpt0

I assume the "c" means it's a device file. I'll have to admit
my lack of experience with device files. If I chmod the
device file and it doesn't work or something goes wrong,
can I chmod it back to it's original settings? I'd like to
hear some other opinions on this before I tinker with
the files in the /dev folder.


"Matt Payton" wrote in message

> Ditch Brodie wrote:
> > FreeBSD-4.9 with HP DeskJet 600 on lpt0. The filter
> > is the ifhp example for non-postcript printers from the
> > FreeBSD handbook.
> >
> > I can print to this printer using the command line. I can
> > also set it up as a share through Samba and print to it
> > with some Win2K workstations on the LAN. I want to
> > print to this printer from the LAN workstations without
> > using Samba.
> >
> > I have setup printers using TCP/IP and added the
> > printing for unix service, and set the printers to use
> > lpr, etc... but each time the jobs fail saying the printer
> > is busy or error.
> >
> > Here are my config files:
> >
> > /etc/printcap
> > -------------------------------------------------------
> > lp|HP DeskJet 600:\
> > :sh:\
> > :mx#0:\
> > :lp=/dev/lpt0:\
> > :sd=/var/spool/output/lpd/hpdj600:\
> > :lf=/var/log/lpd-errs:\
> > :if=/usr/local/libexec/hpif:
> > ---------------------------------------------------------
> >
> > I've added the IP address of the workstation trying to
> > print in the /etc/hosts.equiv and /etc/hosts.lpd files.
> >
> > Still I get "Printer busy or error." message.
> >
> > Any advice out there!
> >
> >
>
> I don't know if it matters, but have you restarted lpd after adding the
> entries to the hosts files ? I don't think you should have to, but
> maybe worth a shot ???
>
> Also, maybe you want to check the permissions on /dev/lpt0. I know I
> had to change them when I switched to lprng from the stock lpd.
>
> --
> - Matt -
 >> Stay informed about: Network Printing Woes 

On Tue, 13 Jan 2004 00:18:23 +0000, Ditch Brodie wrote:

> I hope it's only a permissions issue because I've tried
> many things to resolve this. I chmod 777 the spooling
> directory for the "lp" queue, the default printer on my
> setup. I just looked at /dev/lpt0 and it looks like this:
>
> crw------- 1 root wheel 16, 0 Jan 11 18:21 /dev/lpt0
>
> I assume the "c" means it's a device file. I'll have to admit
> my lack of experience with device files. If I chmod the
> device file and it doesn't work or something goes wrong,
> can I chmod it back to it's original settings? I'd like to
> hear some other opinions on this before I tinker with
> the files in the /dev folder.

Yes, you can change them back.
When I switched to LPRng I had to change the permissions on /dev/lpt0 to
get printing from remote hosts to work. IIRC, I used the checkpc utility
that comes with LPRng, which basically checks your config, and if run with
a certain option, will make the changes it thinks it should. In my case,
it changed the permissions on /dev/lpt0 to crw-rw-rw...And now printing
from remote hosts works.
If I wanted to change them back, a simple chmod would do the trick...

--
- Matt -
 >> Stay informed about: Network Printing Woes 

Ditch Brodie wrote:
> FreeBSD-4.9 with HP DeskJet 600 on lpt0. The filter
> is the ifhp example for non-postcript printers from the
> FreeBSD handbook.

Didn't you just post this question yesterday under another user name?
That's confusing and makes it more work for people trying to help you.

> I want to print to this printer from the LAN workstations without
> using Samba.

Okay.

> I have setup printers using TCP/IP

Not sure what you mean there...

> and added the printing for unix service,

You don't need that--it's only if you want to send lpr print jobs *to* a
Windows system.

> and set the printers to use lpr,

Again, it's hard to tell what you're saying. Do you mean you've set up
the software on the Windows system to print via lpr?

> etc... but each time the jobs fail saying the printer is busy or error.
>
> Here are my config files:
>
> /etc/printcap
> -------------------------------------------------------
> lp|HP DeskJet 600:\
> :sh:\
> :mx#0:\
> :lp=/dev/lpt0:\
> :sd=/var/spool/output/lpd/hpdj600:\
> :lf=/var/log/lpd-errs:\
> :if=/usr/local/libexec/hpif:
> ---------------------------------------------------------

Your "if=" line is sending everything that is received through the HP
filter. But if you've told Windows that it's an HP printer, the data is
already formatted, and you're just trying to reinterpret it.

Try removing the if= line and the continuation backslash on the line
above it. You don't have to restart lpd, IME.

This would also explain why it works from the command line. That data
would be text, not graphic data, so it needs to be converted to graphics
by the filter.

--
Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes 

Sorry about the dual names guys, but I'm desperate to find a solution and
posted from a friends computer as well as mine.

Here's what I've got so far. The goal is to setup network printing to the
HPDJ600 in lpt0 of the FreeBSD server from the Win2K workstations on the
network WITHOUT using Samba.

I made a new entry in /etc/printcap which does not use any kind of filter
like so:

rdj|DeskJet 600:\
:sh:\
:mx#0:\
:lp=/dev/lpt0:\
:sd=/var/spool/output/lpd/hpdj600:\
:lf=/var/log/lpd-errs:

I then added a new printer on one of the Win2K workstations using the
HPDJ600 drivers and set it to use an LPR port which points to the IP address
of the FreeBSD server (192.168.100.254) and uses the queue name of "rdj". I
should mention that I tried using an LPR port and standard TCP/IP port.
Nothing works so far.

Any detailed advice would be appreciated. Thanks.



"Warren Block" wrote in message

> Ditch Brodie wrote:
> > FreeBSD-4.9 with HP DeskJet 600 on lpt0. The filter
> > is the ifhp example for non-postcript printers from the
> > FreeBSD handbook.
>
> Didn't you just post this question yesterday under another user name?
> That's confusing and makes it more work for people trying to help you.
>
> > I want to print to this printer from the LAN workstations without
> > using Samba.
>
> Okay.
>
> > I have setup printers using TCP/IP
>
> Not sure what you mean there...
>
> > and added the printing for unix service,
>
> You don't need that--it's only if you want to send lpr print jobs *to* a
> Windows system.
>
> > and set the printers to use lpr,
>
> Again, it's hard to tell what you're saying. Do you mean you've set up
> the software on the Windows system to print via lpr?
>
> > etc... but each time the jobs fail saying the printer is busy or error.
> >
> > Here are my config files:
> >
> > /etc/printcap
> > -------------------------------------------------------
> > lp|HP DeskJet 600:\
> > :sh:\
> > :mx#0:\
> > :lp=/dev/lpt0:\
> > :sd=/var/spool/output/lpd/hpdj600:\
> > :lf=/var/log/lpd-errs:\
> > :if=/usr/local/libexec/hpif:
> > ---------------------------------------------------------
>
> Your "if=" line is sending everything that is received through the HP
> filter. But if you've told Windows that it's an HP printer, the data is
> already formatted, and you're just trying to reinterpret it.
>
> Try removing the if= line and the continuation backslash on the line
> above it. You don't have to restart lpd, IME.
>
> This would also explain why it works from the command line. That data
> would be text, not graphic data, so it needs to be converted to graphics
> by the filter.
>
> --
> Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes 

Ditch Brodie wrote:
> Here's what I've got so far. The goal is to setup network printing to the
> HPDJ600 in lpt0 of the FreeBSD server from the Win2K workstations on the
> network WITHOUT using Samba.
>
> I made a new entry in /etc/printcap which does not use any kind of filter
> like so:
>
> rdj|DeskJet 600:\
> :sh:\
> :mx#0:\
> :lp=/dev/lpt0:\
> :sd=/var/spool/output/lpd/hpdj600:\
> :lf=/var/log/lpd-errs:

That looks okay. Does /var/spool/output/lpd/hpdj600 exist?
('chkprintcap' should complain if there is a problem, too.)

Do you have lpd_enable="YES" in /etc/rc.conf?

What does 'lpc status all' display?

Can you print on FreeBSD--'lpr -Prdj /etc/printcap'?

> I then added a new printer on one of the Win2K workstations using the
> HPDJ600 drivers and set it to use an LPR port which points to the IP address
> of the FreeBSD server (192.168.100.254) and uses the queue name of "rdj". I
> should mention that I tried using an LPR port and standard TCP/IP port.

"Standard TCP/IP Port" is Windowese for "HP JetDirect". It's a port
9100 connection, rather than lpr. You are correct in using lpr.

--
Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes 

1. Yes the sd: does exist and I've got it wide open at 777, and it's
"chowned by root:deamon"

2. chkprintcap comes back clean

3. lpd_enable="YES" is in the rc.conf as well as I often stop and restart
lpd from the console

4. output of "lpc status all"
-----------------------------
lp:
queuing is enabled
printing is enabled
no entries in spool area
printer idle

rdj:
queuing is enabled
printing is enabled
no entries in spool area
printer idle
-----------------------------

5. YES, I can print to it using 'lpr -Prdj /etc/printcap'

And don't forget that if I startup Samba and add a new printer to the Win2K
workstation to point to this share in Samba, I can print then also. Call me
a purist, call me irresponsible... but I really want a Samba-less setup for
this. They tell me it works but I can't seem to crack the code just yet.
Thanks for your assistance, if you have any other advice I'd appreciate it.


"Warren Block" wrote in message

> Ditch Brodie wrote:
> > Here's what I've got so far. The goal is to setup network printing to
the
> > HPDJ600 in lpt0 of the FreeBSD server from the Win2K workstations on the
> > network WITHOUT using Samba.
> >
> > I made a new entry in /etc/printcap which does not use any kind of
filter
> > like so:
> >
> > rdj|DeskJet 600:\
> > :sh:\
> > :mx#0:\
> > :lp=/dev/lpt0:\
> > :sd=/var/spool/output/lpd/hpdj600:\
> > :lf=/var/log/lpd-errs:
>
> That looks okay. Does /var/spool/output/lpd/hpdj600 exist?
> ('chkprintcap' should complain if there is a problem, too.)
>
> Do you have lpd_enable="YES" in /etc/rc.conf?
>
> What does 'lpc status all' display?
>
> Can you print on FreeBSD--'lpr -Prdj /etc/printcap'?
>
> > I then added a new printer on one of the Win2K workstations using the
> > HPDJ600 drivers and set it to use an LPR port which points to the IP
address
> > of the FreeBSD server (192.168.100.254) and uses the queue name of
"rdj". I
> > should mention that I tried using an LPR port and standard TCP/IP port.
>
> "Standard TCP/IP Port" is Windowese for "HP JetDirect". It's a port
> 9100 connection, rather than lpr. You are correct in using lpr.
>
> --
> Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes 

Ditch Brodie wrote:
> 1. Yes the sd: does exist and I've got it wide open at 777, and it's
> "chowned by root:deamon"

It doesn't need to be 777, lpd runs as root. And that should be
"daemon".

> And don't forget that if I startup Samba and add a new printer to the Win2K
> workstation to point to this share in Samba, I can print then also. Call me
> a purist, call me irresponsible... but I really want a Samba-less setup for
> this. They tell me it works but I can't seem to crack the code just yet.
> Thanks for your assistance, if you have any other advice I'd appreciate it.

What method of printing do you have Samba using?

When you create the lpr port on Windows, do you give it the FreeBSD
system's IP address or hostname? (I'm thinking DNS...)

You said earlier that you can print from the Windows command line,
right? Using the Windows lpr, right?

--
Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes 

You're right, it is daemon... my typo there! and 777 was just to to be sure
there were no permission issues with that directory.

As for the method of printing in Samba, I'm not sure I know. I just have the
printer listed as one of the shares in the smb.conf file. It does work this
way as I've printed from Word and printed test pages to it.

When I create the port in Windows I give it the IP address of the FreeBSD
server, 192.168.100.254. I used to run my own DNS but now use the ISP's
servers. Anything beyond that I add entires to /etc/hosts on FreeBSD or the
hosts file on the Windows machines.

And no, it was the FreeBSD command line that I can print from. If I try to
run lpr from the windows machine like this:

lpr -S 192.168.100.254 -P rdj c:\autoexec.bat

I get "Printer did not accept request. Job aborted."

That's why I keep thinking permissions or something. But I'm still stumped.
Thanks again for your insightful information.


"Warren Block" wrote in message

> Ditch Brodie wrote:
> > 1. Yes the sd: does exist and I've got it wide open at 777, and it's
> > "chowned by root:deamon"
>
> It doesn't need to be 777, lpd runs as root. And that should be
> "daemon".
>
> > And don't forget that if I startup Samba and add a new printer to the
Win2K
> > workstation to point to this share in Samba, I can print then also. Call
me
> > a purist, call me irresponsible... but I really want a Samba-less setup
for
> > this. They tell me it works but I can't seem to crack the code just yet.
> > Thanks for your assistance, if you have any other advice I'd appreciate
it.
>
> What method of printing do you have Samba using?
>
> When you create the lpr port on Windows, do you give it the FreeBSD
> system's IP address or hostname? (I'm thinking DNS...)
>
> You said earlier that you can print from the Windows command line,
> right? Using the Windows lpr, right?
>
> --
> Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes 

Ditch Brodie wrote:

> And no, it was the FreeBSD command line that I can print from. If I try to
> run lpr from the windows machine like this:
>
> lpr -S 192.168.100.254 -P rdj c:\autoexec.bat
>
> I get "Printer did not accept request. Job aborted."

Your FreeBSD system is working. The problem is on the Windows side, or
possibly on the network. On XP, check the Advanced tab of the network
connection properties to see if the firewall is enabled. Otherwise,
could you have some other firewall between the Windows and FreeBSD
systems?

--
Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes 

I believe you when you say it's on the windows side, but it's certainly not
a firewall. I run IPFW on the freebsd machine but it's wide open for
internal IP addresses and just to be sure I opened it wide up for my testing
for IP from any to any....

I also run Win2K not XP but a similar setup at my office where I do run XP
is giving me the same BS.

Thanks for your assistance... I'll keep trying.!

"Warren Block" wrote in message

> Ditch Brodie wrote:
>
> > And no, it was the FreeBSD command line that I can print from. If I try
to
> > run lpr from the windows machine like this:
> >
> > lpr -S 192.168.100.254 -P rdj c:\autoexec.bat
> >
> > I get "Printer did not accept request. Job aborted."
>
> Your FreeBSD system is working. The problem is on the Windows side, or
> possibly on the network. On XP, check the Advanced tab of the network
> connection properties to see if the firewall is enabled. Otherwise,
> could you have some other firewall between the Windows and FreeBSD
> systems?
>
> --
> Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes 

Ditch Brodie wrote:
> I believe you when you say it's on the windows side, but it's certainly not
> a firewall. I run IPFW on the freebsd machine but it's wide open for
> internal IP addresses and just to be sure I opened it wide up for my testing
> for IP from any to any....
>
> I also run Win2K not XP but a similar setup at my office where I do run XP
> is giving me the same BS.

"Personal firewall" (ha) software on Windows? Some type of ad-blocker,
perhaps?

Can you telnet to the FreeBSD lpr port (515) from Windows?

Maybe a Windows virus already running on that port? (Only half kidding.)

Hmm... Do you have CUPS installed on the FreeBSD system?

--
Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes 

Dude, you're never going to believe me when I tell you what I stumbled
across. The /etc/hosts file needed an entry for the hosts wanting to print.
The /etc/hosts.lpd file also needed an entry. Without this, nothing was
working.

I got loads of hints from reading docs on the /etc/hosts.lpd but nothing
clued me into the /etc/hosts entry until I tried this from a command window
on the Win2K machine:

lpq -S192.168.100.254 -Prdj -l

The -l switch sets verbose and there it was. A small little hint that said
"Print services are not available to your host." That set me onto adding the
Win2K machine into the /etc/hosts file and bingo, it works. I've got it
working without the filter and it prints fine. Even got the form feeds
suppressed to stop wasting paper....But,

Now there is just one more issue. I have two entries in my /etc/printcap but
when I run

lpc status all

I see that the second printer has it's queuing turned off. I can only assume
that I did that when I was tinkering around with webmin. I'd like to turn it
back on but without using webmin. How do I do that?


"Warren Block" wrote in message

> Ditch Brodie wrote:
> > I believe you when you say it's on the windows side, but it's certainly
not
> > a firewall. I run IPFW on the freebsd machine but it's wide open for
> > internal IP addresses and just to be sure I opened it wide up for my
testing
> > for IP from any to any....
> >
> > I also run Win2K not XP but a similar setup at my office where I do run
XP
> > is giving me the same BS.
>
> "Personal firewall" (ha) software on Windows? Some type of ad-blocker,
> perhaps?
>
> Can you telnet to the FreeBSD lpr port (515) from Windows?
>
> Maybe a Windows virus already running on that port? (Only half kidding.)
>
> Hmm... Do you have CUPS installed on the FreeBSD system?
>
> --
> Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes 

Ditch Brodie wrote:
> Dude, you're never going to believe me when I tell you what I stumbled
> across.

..post-top don't Please

> The /etc/hosts file needed an entry for the hosts wanting to print.
> The /etc/hosts.lpd file also needed an entry. Without this, nothing was
> working.

Your DNS was broken, and you used something that required DNS.

> Now there is just one more issue. I have two entries in my /etc/printcap but
> when I run
>
> lpc status all
>
> I see that the second printer has it's queuing turned off. I can only assume
> that I did that when I was tinkering around with webmin. I'd like to turn it
> back on but without using webmin. How do I do that?

I think I understand now why you think FreeBSD docs are lacking, as you
said in your other post--you haven't experienced man pages! (Windows
doesn't have them, just those terrible /? things.)

man lpc

Search through that (with "/") for "queue". For more information on
searching and viewing, see the man page for less.

--
Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Network Printing Woes