home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.sysadmin
- Path: sparky!uunet!boulder!ucsu!spot.Colorado.EDU!dunbars
- From: dunbars@spot.Colorado.EDU (DUNBAR STEVEN THOMAS)
- Subject: printing on network problem
- Message-ID: <1992Jul27.024248.1941@ucsu.Colorado.EDU>
- Sender: news@ucsu.Colorado.EDU (USENET News System)
- Nntp-Posting-Host: spot.colorado.edu
- Organization: University of Colorado, Boulder
- Distribution: usa
- Date: Mon, 27 Jul 1992 02:42:48 GMT
- Lines: 36
-
- I have connected my NeXT to a network that has many different kinds of UNIX
- machines and Postscript printers.
-
- I have generated what appears to be a good printcap file, and I have
- niload'ed it properly. All the printers that I am interested in then
- appear in the PrintManager (but of course are not editable because of the
- niload) properly, and when I generate the test page, it also prints
- properly.
-
- When I generate postscript files with enscript or ptroff, they print
- fine.
-
- The PROBLEM is when I try to print from a NeXT Application, like WriteNow.
-
- I print to the printer, and then the document never makes to the printer.
- The lights on the printer never even blink.
-
- On our local ethernet, we have a centralized print server. Is the
- server possibly not understanding something?
-
- Does the postscript printers need to be told something about my NeXT?
-
- I have consulted NeXT's documentation, which seems to be abysmal unless you
- have NetInfo (which we are not running) or are attempting to attach a
- printer to your serial port (which I am not).
- I have also consulted the FAQ, but there is nothing there.
-
- Any help would be tremendously appreciated!
-
- Regards,
-
- Steve Dunbar
-
- sdunbar@mailbox.fwrdc.rtsg.mot.com
- dunbars@spot.colorado.edu
-
-