Why not use CUPS?, with the CUPS LPD daemon, works like a charm for us. Just enable RAW and LPR Byte accounting on your Windows XP hosts. When configuring the CUPS printer again choose a RAW device to ensure straight pass through from your Windows PC to the printer.

I seem to remember a problem when I was setting up the same scenario as you using FreeBSD. When trying to print from a Windows host using LPR/LPD the FBSD LPD daemon expects connections from a certain TCP/IP port on the connecting host, but Windows doesn't use the said port for it's LPR connections. Hence the connections are being rejected. This may not apply to OBSD's LPD implementation but you never know.

Sorry I can't remember more it was along time ago before CUPS became really useful.

Try googling.

Greg Thomas wrote:

On 12/2/05, Fred Crowson <[EMAIL PROTECTED]> wrote:
Greg Thomas wrote:
Ok, I decided to switch from using a little Linksys 802.11b parallel
print server to using my OpenBSD box for printing to my one printer.
Printing locally works fine but I'm having trouble printing from XP.

[EMAIL PROTECTED]:/home/ethant# cat /etc/printcap
#       $OpenBSD: printcap,v 1.4 2003/03/28 21:32:30 jmc Exp $
#
lp|:\
:sh:sf:lp=/dev/lpt0:sd=/var/spool/output:lf=/var/log/lpd-errs:

[EMAIL PROTECTED]:/home/ethant# lpq
Warning: no daemon present
Rank   Owner      Job  Files                                 Total Size
1st    ethant     9    Test Page                             0 bytes

[EMAIL PROTECTED]:/home/ethant# ps waux |grep lpd
daemon    7435  0.0  0.9   180   556 ??  Ss    10:22PM    0:00.03 /usr/sbin/lpd

[EMAIL PROTECTED]:/home/ethant# sudo lprm 9
cannot dequeue dfA009LOCUST
cfA009locust.2fortheroad.net dequeued

And I get a bunch of these in /var/log/lpd-errs until I rm everything
in /var/spool/output:

Dec  1 22:31:06 grits lpd[15269]: locust.2fortheroad.net
Dec  1 22:31:06 grits lpd[15269]: link tfA009locust.2fortheroad.net
cfA009locust.2fortheroad.net: File exists
Dec  1 22:31:14 grits lpd[5050]: locust.2fortheroad.net
Dec  1 22:31:14 grits lpd[5050]: link tfA009locust.2fortheroad.net
cfA009locust.2fortheroad.net: File exists
Dec  1 22:31:22 grits lpd[21910]: locust.2fortheroad.net
Dec  1 22:31:22 grits lpd[21910]: link tfA009locust.2fortheroad.net
cfA009locust.2fortheroad.net: File exists
Dec  1 22:31:30 grits lpd[17060]: locust.2fortheroad.net
Dec  1 22:31:30 grits lpd[17060]: link tfA009locust.2fortheroad.net
cfA009locust.2fortheroad.net: File exists
Dec  1 22:31:38 grits lpd[23270]: locust.2fortheroad.net
Dec  1 22:31:38 grits lpd[23270]: link tfA009locust.2fortheroad.net
cfA009locust.2fortheroad.net: File exists

I saw a similar message on misc back in August but no resolution.
What am I doing wrong?

Thanks,
Greg

Hi

Have you tried using samba to share the printer with XP?


No, I'll just go back to running the wireless print server before I
bother with samba.  I just wanted to reduce the number of devices
here.  The little print server runs lpd so I don't know why I'm having
problems with XP and OpenBSD's lpd.

Thanks,
Greg

Reply via email to