Date: Tue, 28 Jun 2016 21:05:09 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Valeri Galtsev <galtsev@kicp.uchicago.edu> Cc: al plant <noc@hdk5.net>, "freebsd-questions@FreeBSD.org" <freebsd-questions@freebsd.org> Subject: Re: network hook up for Win 10 laptop on Freebsd Message-ID: <alpine.BSF.2.20.1606282100030.22562@wonkity.com> In-Reply-To: <19599.128.135.52.6.1467150299.squirrel@cosmo.uchicago.edu> References: <5772D3C8.1050902@hdk5.net> <alpine.BSF.2.20.1606281452450.57984@wonkity.com> <5772EB8A.5090908@hdk5.net> <19599.128.135.52.6.1467150299.squirrel@cosmo.uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 Jun 2016, Valeri Galtsev wrote:
> They didn't change anything. You can create two kind of ports (at least
> two). Namely: you can create "raw" port, and give there IP address of the
> printer. This printer has to listen to "jetdirect" port (9100) for this to
> work. The other way is if printer listens to LPD ("spooler") port (port
> number 515) (or better: print server, - I usually set up all printer to
> only accept print jobs from print server - easier to manage especially if
> something is wrong with some client). In this case, you need to enable two
> services on Windows side (through "turning on features"): UNIX printing
> related: "LPD Print Service" and "LPR Port Monitr". This teaches Windows
> talk UNIX printing language, you then create local port of type LPD (and
> put remote LPD server's IP there). I found this to be the most robust way
> of having Windows printing to UNIX print queues.
I've used raw port 9100 printing to HP JetDirects many times. It's nice
because it has no other dependencies.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1606282100030.22562>