Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!kwe From: kwe@bu-cs.BU.EDU (kwe@bu-it.bu.edu (Kent W. England)) Newsgroups: comp.dcom.lans Subject: Re: Connecting printer to terminal server Summary: suspect postscript problems Message-ID: <26513@bu-cs.BU.EDU> Date: 8 Dec 88 17:29:21 GMT References: <608@wucs1.wustl.edu> Reply-To: kwe@buit13.bu.edu (Kent England) Followup-To: comp.dcom.lans Organization: Boston Univ. Information Tech. Dept. Lines: 20 In article <608@wucs1.wustl.edu> mike@wucs1.wustl.edu (Mike Ehlers) writes: > >We are attempting to connect a printer to a SUN over a LAN (ethernet) >using a MICOM-Interlan NTS/TCP (NTS100) terminal server. The printer >is an Apple Laserwriter II >The >problem is that it works intermittently, sometimes the file >successfully prints and other times nothing is printed, although data >is sent to the printer. Sounds to me like a postscript problem, not a serial comm problem. I have postscript files that often fail to print with no postscript error message. This is usually for postscript stuff I get over the net. We use a LaserWriter on LocalTalk as a printer for a sun system using the "papif" part of CAP, the Columbia AppleTalk Package. This works quite well, so your serial connection can be made to work if you can solve the postscript problems. I bet transcript is having a problem talking to the LW. Ask on comp.lang.postscript [?] and on comp.protocols.appletalk for details.