Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!execu!sequoia!balkan!wrangler!ssbn!bill
From: bill@ssbn.WLK.COM (Bill Kennedy)
Newsgroups: comp.sys.att
Subject: Re: LP as shared resource for 3B2s
Message-ID: <2003@ssbn.WLK.COM>
Date: 1 Feb 91 12:54:45 GMT
References: <30300001@inmet> <1991Jan31.020837.15416@eci386.uucp>
Reply-To: bill@ssbn.WLK.COM (Bill Kennedy)
Organization: W.L. Kennedy Jr. and Associates, Pipe Creek, TX
Lines: 28

> pcasey@inmet.inmet.com writes:
[ Paul Casey is trying to print across the network... ]
> woods@eci386.UUCP (Greg A. Woods) replies:
>
>If you can run UUCP over WIN3b, I'd suggest using one of the many
>remote_lp scripts which uux lp on the remote system.  You could also
>use remsh if it works.  RFS for this purpose is over-kill.
>-- 
>							Greg A. Woods

It's not overkill if it works IMHO.  I have both of my system printers
on an NCR Tower and both 386en and the Tower do just fine locally or
with remsh.  They also worked OK with the script I sent Paul using uux,
but the 3B2 (also WIN-TCP) refuses to cooperate.  If I run, by hand, the
same commands in my lp interface script, everything is hunky dory.  If I
try it through lp it claims to print but doesn't.

I also have TLI uucp working just fine among everyone but the 3B2.  The
NLS listener is OK because (other than what I complained about yesterday)
RFS works.  If I try to uucico -r1 I get an immediate EMT trap and any
inbound uucicos just fill the (remote) screen with imsg>'s.  I'm no
ethernet wizard, but the 3B2 is the least cooperative machine on the network.
I'm doubtful that I have made some really bone headed mistake because most
everything else seems to be working OK.  I think I need some email hand
holding if anyone has the time/patience.
-- 
Bill Kennedy  usenet      {att,cs.utexas.edu,pyramid!daver}!ssbn.wlk.com!bill
              internet    bill@ssbn.WLK.COM   or attmail!ssbn!bill