Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!rpi!bu.edu!inmet!pcasey
From: pcasey@inmet.inmet.com
Newsgroups: comp.sys.att
Subject: LP as shared resource for 3B2s
Message-ID: <30300001@inmet>
Date: 25 Jan 91 16:07:00 GMT
Lines: 36
Nf-ID: #N:inmet:30300001:000:1407
Nf-From: inmet.inmet.com!pcasey    Jan 25 11:07:00 1991



Hello,

I need some system administration type help.

I am trying to set up a laser printer connected to a 3b2 as
a shared resource so another 3b2 on the network can use it.
From what I have read, the Remote File Sharing Utilities (RFS) are
what is needed to accomplish this. Unfortunately, the documentation
is pretty vague if you aren't using STARLAN as your "transport
provider", which I'm not. Our 3b2s have Wollongong TCP/IP WIN3B
networking software, which I assume would be considered the machines
transport provider.

Where I am getting stuck is in setting up the Network Listener
Service, which RFS requires to be up and running. A call to
nlsadmin shows no listener service existing, and I'm not sure
what to specify as the network specifier in /dev, since it isn't 
starlan. Also, I am not sure what to specify as the network address
for my network, as the documentation is again vague outside of the 
STARLAN format. ( I have come across a routine in the Wollongong
package called rfsaddr which converts an ip address to rfs format,
is this it?).

The 3b2s are networked on a standard ethernet LAN, and the
Wollongong TCP/IP software is up and running correctly, if this
information is any help. The 3b2s are running System V 3.1.x.

If anyone can shed some light on my problem, it would be greatly
appreciated.


Paul Casey              pcasey@inmet.inmet.com
Intermetrics, Inc.
Cambridge, MA