From owner-freebsd-questions@freebsd.org Wed Jun 29 20:32:47 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 E777FB860DF for ; Wed, 29 Jun 2016 20:32:47 +0000 (UTC) (envelope-from btv1==988d1ff825d==noc@hdk5.net) Received: from spamfilter.netenterprise.net (relay1.netenterprise.net [64.29.90.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "spamfilter.netenterprise.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF5E020A3 for ; Wed, 29 Jun 2016 20:32:46 +0000 (UTC) (envelope-from btv1==988d1ff825d==noc@hdk5.net) X-ASG-Debug-ID: 1467232360-0a94c50eaab8dd0001-jLrpzn Received: from IMAIL5.netenterprise.net (imail5.netenterprise.net [64.29.90.135]) by spamfilter.netenterprise.net with ESMTP id gFthWcHuuXU8dIXu (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jun 2016 10:32:40 -1000 (HST) X-Barracuda-Envelope-From: noc@hdk5.net X-Barracuda-RBL-Trusted-Forwarder: 64.29.90.135 X-ASG-Whitelist: Client Received: from ponolei.intra.net [72.235.61.32] by IMAIL5.netenterprise.net with ESMTP (SMTPD-12.5.3.93) id b24f0003c1ed9209; Wed, 29 Jun 2016 10:32:40 -1000 Message-ID: <57743068.6010502@hdk5.net> X-Barracuda-Effective-Source-IP: udp017597uds.hawaiiantel.net[72.235.61.32] X-Barracuda-Apparent-Source-IP: 72.235.61.32 X-Barracuda-RBL-IP: 72.235.61.32 Date: Wed, 29 Jun 2016 10:32:40 -1000 From: al plant User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20071128 FreeBSD/i386 SeaMonkey/1.1.7 MIME-Version: 1.0 To: Polytropon CC: "freebsd-questions@FreeBSD.org" Subject: Re: network hook up for Win 10 laptop on Freebsd References: <5772D3C8.1050902@hdk5.net> <5772EB8A.5090908@hdk5.net> <19599.128.135.52.6.1467150299.squirrel@cosmo.uchicago.edu> <61537.76.193.17.2.1467174398.squirrel@cosmo.uchicago.edu> <20160629064410.dcd5b8ef.freebsd@edvax.de> X-ASG-Orig-Subj: Re: network hook up for Win 10 laptop on Freebsd In-Reply-To: <20160629064410.dcd5b8ef.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Barracuda-Connect: imail5.netenterprise.net[64.29.90.135] X-Barracuda-Start-Time: 1467232360 X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA X-Barracuda-URL: https://spamfilter.netenterprise.net:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 3159 X-Virus-Scanned: by bsmtpd at netenterprise.net X-Barracuda-BRTS-Status: 1 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 20:32:48 -0000 Polytropon wrote: > On Tue, 28 Jun 2016 23:26:38 -0500 (CDT), Valeri Galtsev wrote: > >> 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. >> > > There is another advantage, in case it should matter: > > You can have all your clients submit PS (using a generic Postscript > driver) and let the UNIX machine postprocess it into whatever format > is needed for the printer. Most normal printers speak PS, PCL and PDF > (or at least one of those), but if you're unlucky and your printer > doesn't, and maybe even worse, MICROS~1 decided your printer became > "too old" and there is no driver support anymore, this might be an > extendable solution: You got a new printer? No client-side change is > needed, just a different postprocessing filter on the server, which > is O(1) instead of O(n). ;-) > > > > many thanks for all the ideas put forward. We have an old b&w hp printer on the Freebsd server and have a wireless link to another color at least a few ways to go on this now. ~ Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 ~ Supporting FreeBSD - UNIX Computer O/S email: noc@hdk5.net email: alplant.att.net ."All that's really worth doing is what we do for others" - Lewis Carrol