Xref: utzoo comp.protocols.tcp-ip:11616 comp.protocols.misc:861 comp.protocols.nfs:989
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!samsung!emory!rsiatl!jgd
From: jgd@rsiatl.UUCP (John G. De Armond)
Newsgroups: comp.protocols.tcp-ip,comp.protocols.misc,comp.protocols.nfs
Subject: Dialup x.25 & nfs questions
Message-ID: <2747@rsiatl.UUCP>
Date: 7 Jun 90 19:48:59 GMT
Reply-To: jgd@rsiatl.UUCP (John G. De Armond)
Followup-To: comp.protocols.tcp-ip
Organization: Radiation Systems, Inc. (a thinktank, motorcycle, car and gun works facility)
Lines: 41


I have a couple of questions regarding the use of tcp/ip over x25 in
a dialup environment.

The environment is:

IBM RS/6000 320, Uninet SLAT, v.32 modems on one end and 

IBM 3081 with 3745 on the other.

Questions:

	Does anyone have any experience with a setup similiar to this?

	How does x.25 in a point-to-point environment compare to SLIP?

	How does x.25 and v.32 compare in performance to {slip,x.25,
	other protocols} and trailblazers?  Particularly in noisy environments.

	Any other general comments?


Second question.

From this same RS/6000, there is a need to connect a PC over ethernet.
PC-NFS has been proposed.  I have little experience with NFS in general
and no experience with PC-NFS in particular.  This connection will involve
an unmanned PC and therefore must be reliable.  Any comments positive
or negative would be appreciated.

I have to discuss these situations in the next few days so any comments
would be greatly appreciated.  E-mail prefered.

Thanks,
John

-- 
John De Armond, WD4OQC  | We can no more blame our loss of freedom on congress
Radiation Systems, Inc. | than we can prostitution on pimps.  Both simply
Atlanta, Ga             | provide broker services for their customers.
{emory,uunet}!rsiatl!jgd|  - Dr. W Williams |                **I am the NRA**