From owner-freebsd-questions@freebsd.org Wed Jun 29 04:26:39 2016 Return-Path: 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 D989AB85BBC for ; Wed, 29 Jun 2016 04:26:39 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.70.90]) by mx1.freebsd.org (Postfix) with ESMTP id AC5EF2F76 for ; Wed, 29 Jun 2016 04:26:39 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 6D75FCB8CAA; Tue, 28 Jun 2016 23:26:38 -0500 (CDT) Received: from 76.193.17.2 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Tue, 28 Jun 2016 23:26:38 -0500 (CDT) Message-ID: <61537.76.193.17.2.1467174398.squirrel@cosmo.uchicago.edu> In-Reply-To: References: <5772D3C8.1050902@hdk5.net> <5772EB8A.5090908@hdk5.net> <19599.128.135.52.6.1467150299.squirrel@cosmo.uchicago.edu> Date: Tue, 28 Jun 2016 23:26:38 -0500 (CDT) Subject: Re: network hook up for Win 10 laptop on Freebsd From: "Valeri Galtsev" To: "Warren Block" Cc: "Valeri Galtsev" , "al plant" , "freebsd-questions@FreeBSD.org" Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 04:26:39 -0000 On Tue, June 28, 2016 10:05 pm, Warren Block wrote: > 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. > I agree if you have one to 5 or so clients. If you have 100+ clients, you better don't let them print directly to the printer, and instead make them print through print server. One client acts up (say, hits consistently bug in postscript implementation of the printer that knocks printer out; and keeps re-sending print job every time you power cycle printer) - you will see the world of difference. You can pinpoint what comes from which client if all goes through print server. UNIX machine as print server will provide you with much more than brainless embedded system printers have inside. But for few clients, as you said, the effort is not worth it. Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++