[comp.sys.ncr] WIN-TCP / NFS &/or SLIP Available for Tower?

jdm@mbitow.UUCP (Jay D. Mumper) (03/02/91)

Does anyone know of NFS being available for the Tower series (specifically
a Tower 32/650 with UNIX 3.00.01 and WIN-TCP)?  I've heard some not-to-good
remarks about Wollongong's NFS (like it ignores the kernel file system
routines and interacts directly with the file system...), but that doesn't
mean it won't work with "normal" hardware.  Anyway, does it even exist for
the Tower anyway?

Okay, if not, how can I get NFS on the Tower?  (Sea Change, are you listening?)
My reasons are simply that I'd like to have some other non-NCR UNIX machines
be able to access the Tower drive in an NFS-like manner (remote mount, etc.) 
and perhaps do the reverse back to the tower with their disks as well.  And
yes I know RFS is there, but I'd prefer NFS, just because I can use PCNFS
on our PCs too....

Now what about SLIP?  Since WIN-TCP is so well documented :( , I can't 
imagine how I overlooked it if it's there...  Seriously, though, I'd 
like to be able to use it if it exists on this thing.  ANY pointers
on this one would be appreciated.

( NCR has already been flamed vigorously for the lack of documentation for
WIN-TCP, but hey, can't I add a little gasoline too!  A good set of manuals
would make this entire posting an RTFM error... )

--------------------------------
mbitow!jdm
Jay D. Mumper
Mold Base Industries, Inc.
Voice: (717) 564-7960

adk@csd4.csd.uwm.edu (Andrew D Kailhofer) (03/02/91)

I'm not sure about the 650, but I do have NFS on my 700.  It is from
TWG.  It performs relatively well, but I have had some problems with
the /etc/exports file.  I haven't been able to restrict an export to
anything other than a single host (i.e. I haven't been able to
restrict access to my config files to the two TowerViews on my net).
It's either just one host, or global access...

Anyone else notice this?

Andy Kailhofer
Ameritech Services, Inc.
414/678-7793
a907932@gus.wi.ameritech.com

TEMNGT23@ysub.ysu.edu (Lou Anschuetz) (03/03/91)

This isn't necessarily a direct followup, but our poster program
has temporarily vanished, and this is sort of related.  First, the
related stuff - I have heard that WIN-TCP has an NFS, but that if
you look up SLOW in the dictionary you would find a TWG NFS command
as the definition (over 2 minutes was the low estimate).  In light
of the not to speedy performance of WIN-TCP in general, I have not
pursued this so cannot verify that this is all true (though it has
that ring....)

Second, I am now sending everyone through a terminal server to my
tower since using HPSIO and modems is not real functional.  This
mostly works REAL well, except that at least once a day, WIN-TCP
decideds not to do anything anymore and quietly quits, thereby
allowing no more users to log in.  I am going to call this one in,
but I have NO error messages (WIN-TCP never writes to its syslog
file, and never reports errors - t'is like a c program, it dies
with no report of its death...).  There may well be a certain parameter
I need to tune, but have no idea what.  I do know that there are
usually about 14 users on board when it quits, though it has run
for 4 hours with this many users pounding away, so it is not
consistent.  Any help would be appreciated.  BTW, the terminal
server is fine during this time, but of course you can't do much
with it since it gets its software from the tower.  I never need
to reload or boot it when this happens.  HELP!  (Jeff at CODAR, look
for another strange call on Monday  :-)

As always, thanks in advance!

ian@ukpoit.co.uk (Ian Spare) (03/06/91)

In article <91061.205038TEMNGT23@ysub.ysu.edu> TEMNGT23@ysub.ysu.edu (Lou Anschuetz) writes:
>Second, I am now sending everyone through a terminal server to my
>tower since using HPSIO and modems is not real functional.  This
>mostly works REAL well, except that at least once a day, WIN-TCP
>decideds not to do anything anymore and quietly quits, thereby
>allowing no more users to log in.  I am going to call this one in,
>but I have NO error messages (WIN-TCP never writes to its syslog
>file, and never reports errors - t'is like a c program, it dies
>with no report of its death...).  There may well be a certain parameter
>I need to tune, but have no idea what.  I do know that there are
>usually about 14 users on board when it quits, though it has run
>for 4 hours with this many users pounding away, so it is not
>consistent.  Any help would be appreciated.  BTW, the terminal
>server is fine during this time, but of course you can't do much
>with it since it gets its software from the tower.  I never need
>to reload or boot it when this happens.  HELP!  (Jeff at CODAR, look
>for another strange call on Monday  :-)
>



We use terminal servers instead of HPSIO/621 since it gives better functionality
we even use them to allow telnet into no-netowrk towers/devices.

The 5.3 towers ( esp. 5.3.2 / 1.01.01 etc ) are especially talented at
silent deaths !! We find this on NFS , TCP ( this also relates to speed),
printers and modems !! Our problem ,and your's 'sounds' the same, is stream
tuning , check strstat ( from shell or crash ) and tune accordingly.

You may also not be aware that all tty tallies etc are now turned of, this
really doesn't apply in this case but is well worth knowing.

If you are running out a stream blocks you will get a silent death as you
describe. We have some 'specs' etc in to deal with the problem of not
being notified.

Hope this helps ( somebody :-) ) 

Ian

-- 
Ian Spare , iT , Barker Lane , CHESTERFIELD , DERBYS , S40 1DY , GREAT BRITAIN

   E-mail : ian@ukpoit.uucp - VOICE : +44 246 214296 - FAX : +44 246 214353