From owner-freebsd-questions@freebsd.org  Wed Jun 29 03:05:12 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D547BB86BF1
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Wed, 29 Jun 2016 03:05:12 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "wonkity.com", Issuer "wonkity.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 9979A219E
 for <freebsd-questions@freebsd.org>; Wed, 29 Jun 2016 03:05:12 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.15.2/8.15.2) with ESMTPS id u5T35A6S026178
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Tue, 28 Jun 2016 21:05:10 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u5T359Si026175;
 Tue, 28 Jun 2016 21:05:10 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
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
In-Reply-To: <19599.128.135.52.6.1467150299.squirrel@cosmo.uchicago.edu>
Message-ID: <alpine.BSF.2.20.1606282100030.22562@wonkity.com>
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>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (wonkity.com [127.0.0.1]); Tue, 28 Jun 2016 21:05:10 -0600 (MDT)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 03:05:12 -0000

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.