This is non-NeXT-network-printing in view mode; [Up]
Date: Sun 30-Dec-1991 16:10:00 From: dweissman@amarna.gsfc.nasa.gov (WiseGuy) Subject: non-NeXT network printing I have successfully attached an HP Laserjet II w/ postscript cart. to our NeXTstation. From the NeXT I can select the printer from the Print window, use both lpr -PHPLJ and enscript -PHPLJ from the Terminal with no problems.. No matter what I do though, an entry for a NeXT 400dpi printer with the name Local_Printer always seems to get generated. 2 questions: How do I get rid of the self-creating entry for the NeXT printer? I added a printcap entry on our Sparc that points at the NeXTstation's printer but I cannot remote print anything from there.. A valid lpd request message never appears for it and the Sun writes a message about not being able to open a queue. Both printcap entries look right so what am I doing wrong? ================================================================================ Dave Weissman - Broadband and FDDI LAN Operations Group Snail mail: NeXTmail - weissman@trust.gsfc.nasa.gov Code 543.8 Internet - dweissman@amarna.gsfc.nasa.gov Goddard Space Flight Center SPRINTnet's X.400 - Greenbelt, Maryland 20771 (C:USA,A:TELEMAIL,P:GSFC,FN:DAVID,SN:WEISSMAN)
Date: Sun 31-Dec-1991 09:54:05 From: root@panther.cosy.sbg.ac.at (Bernhard Nocker (Operator)) Subject: Re: non-NeXT network printing In article <30DEC199111103337@amarna.gsfc.nasa.gov> dweissman@amarna.gsfc.nasa.gov (WiseGuy) writes: > I have successfully attached an HP Laserjet II w/ postscript cart. to > our NeXTstation. From the NeXT I can select the printer from the Print > window, use both lpr -PHPLJ and enscript -PHPLJ from the Terminal with no > problems.. No matter what I do though, an entry for a NeXT 400dpi printer > with the name Local_Printer always seems to get generated. > > 2 questions: > > How do I get rid of the self-creating entry for the NeXT printer? > > I added a printcap entry on our Sparc that points at the NeXTstation's > printer but I cannot remote print anything from there.. A valid lpd > request message never appears for it and the Sun writes a message about > not being able to open a queue. Both printcap entries look right so > what am I doing wrong? > Nothing to worry about. The first question is simple to answer: It's impossible. I think that the only way to remove the Local_Printer entry is to remove it with the NetInfoManager and never reboot! The second problem on how to allow remote machines access to a printer attached to the NeXT can be solved with two further entries under printers/HPLJ in NetInfoManager. Click on the last item in that directory and choose "Append property". Name it sharedAs. Choose "New value" and name it lp (like the entry in the remote machines printcap). Append another new property and name it sharedTo. Name the new value /. This means that everybody can print within your domain. Well, PrintManager should allow you to do the same things much easier. In fact it seems to be impossible to export a printer to a local domain which you always have in a NonNetinfoNetwork. So you always get a message: "Printer cannot be exported to this same computer". So I worked around and made the entries with NetInfoManager. It works great. In our domain Suns and Tektronics and even PCs print on the NeXTLaser. Best regards, Bernhard. ************************************************************************* Bernhard Nocker, University of Salzburg's Department of Computing Studies (beware root :-) ************************************************************************* Greetings Bernhard.
Date: Sun 01-Jan-1992 00:03:28 From: hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) Subject: Re: non-NeXT network printing <1991Dec31.095405.22824@milton.u.washington.edu> Bernhard Nocker's solution is unduly complicated. The simplest solution is an /etc/hosts.lpd with a list of hosts from which print requests are accepted on your NeXT. On the host, depending on the OS, you use either lpadmin for lp (or sam, for HP-UX) to configure a remote printer with the correct name on the NeXT, or add an appropriate printcap entry if you are using lpr. It works nicely, even over dialupip. Prosit Neujahr, Bernhard! Happy New Year to the rest of the world! Hardy ----- Meinhard E. Mayer, Department of Physics, UC Irvine
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.