Thread View: comp.sys.next.sysadmin
2 messages
2 total messages
Started by DUNBAR STEVEN THOMAS
Mon, 27 Jul 1992 02:42
printing on network problem
Author: DUNBAR STEVEN THOMAS
Date: Mon, 27 Jul 1992 02:42
Date: Mon, 27 Jul 1992 02:42
35 lines
1730 bytes
1730 bytes
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
printing on network problem
Author: Jeremy Thomas James
Date: Mon, 27 Jul 1992 22:34
Date: Mon, 27 Jul 1992 22:34
45 lines
2632 bytes
2632 bytes
(DUNBAR STEVEN THOMAS) writes: |> 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 am having a similar problem which I need some help with. I am trying to use the Local_Printer with an alias. The printer used to work fine both locally and remotely. I have set up the hosts and printcap files with the niload utility and it seems to be set up properly. When I type lpq to see if the print queue is enabled, it tells me : lpq: Local_Printer: displayq unknown printer The same message comes up with lpr. I can't figure out what might have changed. What can I check?? -- What I say isn't necessarily the opinion of the organization I belong to! =============================================================================== Jeremy T. James University of Michigan Medical Center, ITN B1911 CFOB, Ann Arbor, MI 48109-0704 Phone:313-747-2778 blackp@med.umich.edu "Even if your on the right track, you'll get run over if you're there too long" -------------------------------------------------------------------------------
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads