HDTenEightyP/NetNews huggingface dataset:
From: iceman@sequent.com (Ian Evans)
Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip.ibmpc
Subject: Looking for NDIS compliant version of NETBOIS
Date: 15 Dec 92 18:49:29 GMT
Article-I.D.: sequent.1992Dec15.184929.10927
Organization: Sequent Computer Systems Inc.

The title says it all.....

Are there versions of NETBIOS that work with NDIS??  Better yet is
there one that works with PC-NFS directly, not NDIS.

Thanks!!!

-- 
Ian C. Evans					Sequent Computer Systems Inc.
Senior Systems Administrator			15450 S.W. Koll Parkway
Architecture & Technology			MS=RHE1-895
iceman@sequent.com				Beaverton, OR  97006-6063
From: rcroger@svin01.win.tue.nl (Roger Beckers)
Newsgroups: comp.protocols.nfs
Subject: lifeline and windows 3.1
Date: 18 Dec 92 10:43:31 GMT
Reply-To: rcroger@win.tue.nl

Hello,

I'm trying to run lifeline in a dos window but as soon as i try to send a 
message windows crashess. Any suggestions?

Roger Beckers


Eindhoven University of Technology
Faculty of Mathematics and Computing Science, HG 6.05  
P.O.Box 513, 5600 MB Eindhoven, The Netherlands
Telephone +31 40 472802
Fax +31 40 436685
E-mail: rcroger@win.tue.nl
Newsgroups: comp.protocols.nfs
From: fr@eagle.mumath (Farid Rahmi)
Subject: Re: Need Help with PC-NFS/Windows 3.1 Dialog
Reply-To: fr@eagle.mumath
Organization: BIM nv
Date: Thu, 17 Dec 92 09:15:13 GMT


>Now, much as I would like "RTM" to mean "Read The Manual", I'm sure
>this is not what it means :-).  I've gone through the error messages
>in the Reference Manual, and could not find this message.

You were close though. Just behind the error section lives a thing called
Index which routes you to page 115 if you consult rtm.

The Manual : 

rtm - Load Resident Transport Module

	Description

			The resident transport module (RTM) is a TSR that provides
			transport services that allow an application to "talk" to
			the underlying network. The rtm command, used without any
			parameters, loads the RTM into memory.

			Before starting MS-Windows and the PC-NFS TSR, PCNFSLPD, you
			must load the RTM.


Farid
From: Bruce.Weinel@p1.f456.n632.z3.fidonet.org (Bruce Weinel)
Newsgroups: comp.protocols.nfs
Subject: NetWare and NFS - Coexistence.
Date: Fri, 18 Dec 1992 08:06:38

arifin@iti.gov.sg was heard in "The Pit" saying to  All

  ag> From: arifin@iti.gov.sg (Arifin Othman (JSAIC))
  ag> Organization: National Computer Board, Singapore
  ag> 
  ag> Would be interested if anyone who has attempted this to e-mail me
  ag> their success story.
  ag> 
  ag> Thank you in advance.

If you want a client (i.e. workstation) running Windows to have both NFS
access
and NetWare access then it can be done "out of the box" by using two products
from NetManage: Chameleon/NFS plus IPX/Link. The Chameleon/NFS product allows
the PC to be an NFS client and/or server. The IPX/Link product implements dual
protocol stacks (IPX and TCP/IP) for NetWare via a packet interface (its
actually
based on Spry Concurrent).

Note that this does _not_ address the issue of non-Windows clients nor does
it allow the NetWare server to "mount" an NFS drive (see Novell for their NFS
product for this) or vice versa (see your Unix vendor for NetWare/X).

 * Origin: Howls from "The Pit" BBS (03) 321-3295 (3:632/456.1@fidonet)
Newsgroups: comp.protocols.nfs,comp.sys.novell
From: chet@spock.retix.com (Chet Mazur)
Subject: NDIS/Packet driver
Organization: Retix, Santa Monica
Date: Mon, 14 Dec 1992 19:13:21 GMT

If there such a thing as a NDIS packet driver that can support a dual
stack over a single card??? can someone refer me to how to architect a
packet driver.. please reply via mail... thanks...
--

Chet Mazur (chet-mazur@retix.com)
Lambda Consulting
-- 

Chet Mazur (chet-mazur@retix.com)
Lambda Consulting
From: mirek@unixg.ubc.ca (Miroslaw Piaseczny)
Newsgroups: comp.protocols.nfs
Subject: PC-NFS and Oracle
Date: 17 Dec 1992 02:47:33 GMT
Organization: University of British Columbia, Vancouver, B.C., Canada
Distribution: world
NNTP-Posting-Host: unixg.ubc.ca

I would like to use PC as a terminal for the Oracle sqlforms30 application. 
I want to use telnet to connect to the host (sun), and run the runform30 
with vt100 resource file. 
 
Can anyone help me to configure telnet (?) to work for me?
 
I used PCNFS 3.0.1 some time ago and I don't recall having any problems, but
now, when we upgraded to 4.0, I'm getting Bs,Ds,etc instead of the form frame 
lines.
 
Is there any limitation on using 8 bit ASCII characters in version 4.0?
Do I need to buy the PC-NFS Advanced Telnet?
 
 
Thanks
 
 
Mirek Piaseczny
University of British Columbia


Newsgroups: comp.protocols.nfs
From: murray@msvu.ca (Murray Latter)
Subject: Re: 486-DX2-66 Brings a SS2 to its knees :(
Organization: Mount Saint Vincent University
Date: Mon, 14 Dec 1992 20:28:28 GMT

Xref: sparky comp.protocols.nfs:2986 comp.protocols.tcp-ip.ibmpc:7015
From: mjg@eng.cam.ac.uk (Michael Gray)
Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip.ibmpc
Subject: PC-NFS Telnet control character problems
Summary: PC_NFS mangles ^S, ^C, ^P
Keywords: PC-NFS, UNIX, character mapping, Emacs
Date: 15 Dec 92 11:49:48 GMT
Organization: cam.eng

I have just installed PC-NFS 4.0 to connect a PC to our workstation
network.  The NFS side works fine, but telnet is broken.

The control characters ^P, ^S, ^C get mangled in between the keyboard
and the UNIX host, about 4 times in 5.  This makes using Emacs and the
ksh command history particularly frustrating.

Is there an easy fix for this?

The PC is running DOS 5, Win 3.1, UK English settings for keyboard and
display.  No particularly strange drivers or TSRs are loaded.

Thanks in advance

Michael Gray                     Cambridge University Engineering Dept
mjg@eng.cam.ac.uk                Power & Machines Group
Newsgroups: comp.protocols.nfs
From: mathieu@ncrcis.stpaul.ncr.com (Tom Mathieu [7143])
Subject: Using LifeLine Backup, need help
Organization: NCR NPD Division
Distribution: usa
Date: Fri, 18 Dec 1992 15:08:49 GMT

We have PC-NFS 4.0 and want to use Lifeline's backup feature
to backup PC hard drives to tape. 

We have an EXB 8200 tape drive attached to one of our workstations
hung off our Sun 3/280.  When I stick a completely blank (i.e.,
never used before) tape in the Exabyte drive, I can get the PC
version of TAR to write files to the tape.  I can also restore the
PC hard disk from the tape.  The problem is, I can't "re-use" the
tape.  Once anything has been written on it, the PC TAR program
gives me a "write failed" message after the first few files get
written on the tape.  

I'd rather use the rput/rget/rlist functions, but I get the same
write failed message from those too.  

Is anybody using Lifeline backup?  If so, can you let me know how
you've got it configured?  Right now, we're using PCTOOLS to backup
our hard drives to a server file and tar to move it to tape.  This
works ok, but most people here don't know or want to know anything
about unix/tar.

Thanks



--
     _ _ /|
     \'o O'  mathieu@ncrcis.stpaul.ncr.com
     =(_._)=
        U
Newsgroups: comp.protocols.nfs
From: glad@daimi.aau.dk (Michael Glad)
Subject: Re: NFS cookies
Organization: DAIMI: Computer Science Department, Aarhus University, Denmark
Date: Mon, 14 Dec 92 09:04:44 GMT

krm@sdc.boeing.com (Keith Michaels) writes:

>Does anyone know what the practical limitations are for the 32 bit 
>NFS "cookie" that is used in the READDIR function?  Some servers use
>only printable characters in the cookie; this may be a concession to 
>clients that manipulate it with strcpy(), but if so it unnecessarily 
>limits the range of cookie values (only the zero byte must be avoided).
>Does the protocol sanction the use of unprintable cookies?

Many NFS implementations use file offsets into the directory file as
cookie values. The RFC states that cookies are 'opaque' meaning that
you can put whatever you want into them. DO NO DO THAT!! An example:
if you use all ones as an end-of-directory cookie, at least one
client nfs implementation will say 'oh: the directory has grown, lets better
cache the new size'. On 'ls -l' output, the directory will then appear
with size '-1' for some time. 

Let the cookie values live in the interval [0, (virtual) directory size].

>This is not just of theoretical interest! We have acually hit this problem 
>on recursive operations like find.  The result is duplicate files returned.

That's what may happen. I had the above problems with some SunOS release,
I think it was 4.0.3 or 4.1.1. I never saw the problem with HP-UX.

>Surely there's a more graceful -- more correct -- way of handling this!

I doubt so.

	-- Michael Glad, email: glad@daimi.aau.dk

Newsgroups: comp.protocols.nfs
From: rjberke@berke.itg.ti.com (Richard Berke)
Subject: NFS over TCP rather than UDP
Organization: Electronic Communications
Date: Fri, 18 Dec 1992 16:07:14 GMT

Which vendors offer their NFS able to use TCP?

I'll relay results I hear back to this group.

Thanks,
Richard Berke   RBRK   Richard.Berke@lobby.ti.com  (214) 575-2828
Texas Instruments      Plano, Texas
-------------------------------------------------------------------------
Newsgroups: comp.protocols.nfs
From: hoffman@tsla.noava.lisc.lockheed.com (John Hoffman)
Subject: Re: Sun PC-NFS performance (again)
Organization: LISC Noava
X-Newsreader: TIN [version 1.1 PL6]
Date: Fri, 11 Dec 92 21:31:56 GMT

I would also be interested in any type of caching program that would speed up
NFS performance.  We use PCNFS on our networks and also find that the
performance doesn't compare well to other protocol such as Novell.  

Wouldn't it be possible to cache stuff to your local hard drive as long as the
files you're opening are locked?  That would certainly improve performance.

Does anyone know of a DFS implementation for a PC?  I understand it caches a
lot of the data to your local hard disk.  This would certainly provide
excellent performance.

John
-- 
+-------------------------------------------------------------------------+
| The preceding is my personal opinion and not legally binding...         |
+-------------------------------------------------------------------------+
| John Hoffman     | Lockheed Integrated Solutions Company                |
| NOAVA/Engineering| Internet: jhoffman@lmsc.lockheed.com                 |
| 408/987-4693     | or: jhoffman@lisc.lockheed.com                       |
+-------------------------------------------------------------------------+
From: jkf87r@ecs.soton.ac.uk (Julian Field)
Newsgroups: comp.protocols.nfs
Subject: Re: QVTNET3.0 with PCNFS4.0
Date: 15 Dec 92 15:56:34 GMT

bob@prepress.com (Robert Crowe) writes:

> jkf87r@ecs.soton.ac.uk (Julian Field) writes:
>....
>>Yes, there is. QPC Software sell WinQVT/NFS for the same price as
>>WinQVT/Net, i.e. $40 per copy, 10% discount for every 10 copies bought
>>up to a maximum of 50%.

>Is WinQVT/NFS shareware, or do I have to buy it up front?  If it is 
>available from some ftp site, which site would that be?

As far as I can see, you have to buy it up front. I haven't seen it
on any ftp sites.

Jules.
From: koontz@cam.nist.gov (John E. Koontz X5180)
Newsgroups: comp.protocols.nfs
Subject: Any problems with PC-NFS Lifeline and POP3?
Keywords: POP3, PC-NFS Lifeline, email
Date: 14 Dec 92 17:10:52 GMT
Organization: National Institute of Standards and Technology, Gaithersburg, MD

I seem to remember that there are some pitfalls to using POP3 with 
the PC-NFS Lifeline mailer, but I can't find anything in my archived
email about it.  Can anyone recall something of this sort themselves?

----
John E. Koontz (koontz@bldr.nist.gov)

Disclaimer:  Views and recommendations, express or implied, are my own, and
do not reflect the opinion or policy of my employers.
Newsgroups: comp.protocols.nfs
From: fr@eagle.mumath (Farid Rahmi)
Subject: WinBatch and PCNFS
Reply-To: fr@eagle.mumath
Organization: BIM nv
Date: Thu, 17 Dec 92 16:18:38 GMT

In article 1g8e7jINNdo2@seven-up.East.Sun.COM, geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
>#Does any of the NFS implementations for PC, support an API to mount an UNIX 
>#file system to a DOS/Windows workstation?.
>#
>The easiest approach under Windows is simply to invoke the standard
>WNetAddConnection() API (see the Windows SDK doc for details).

WinBatch allows non-programmers (like me:-) to acces those routines from a batch
environment. Unfortunately, this does not seem to work :


WNetAddConnection(LPSTR lpszLocalNetpath,LPSTR lpszPassword, LPSTR lpszLocalName).

Yet, WNetAddConnection(ap1:/pcnfs/ap1.ma,,G) fails. Adding the password of the
user logged in does not help.


Same batch - with adapted host data - seems to work under LanMan. Also, I don't
see how to pass PCNFS-specific parameters (like /ms), or rather were all this is 
documented (I have a copy of the PCNFS PTK 4.0).


Farid
From: colh@lincoln.gpsemi.com (Colin Helliwell)
Newsgroups: comp.protocols.nfs
Subject: PC-NFS with NDIS Driver
Date: 15 Dec 92 17:24:48 GMT
Organization: GEC Plessey Semiconductors
X-Xxmessage-Id: <A753D55A430370B9@mac_oob5.lincoln.gpsemi.com>
X-Xxdate: Tue, 15 Dec 92 18:32:58 GMT
X-Useragent: Nuntius v1.1.1d12

I have a couple of old copies of Sun Microsystems PC-NFS (V3.0.1), but
the ethernet cards I have is not shown as a supported make. The cards are
DEC LC DE100 which come with their own NDIS driver. I am currently using
these to run DEC Pathworks software, where the server is a VAX.

As I'd like to change over to running PC-NFS served by a Sun, can anyone
tell me whether the NFS software can use the NDIS driver (if so, how?) or
do I need the latest version of PC-NFS (which the publicity blurb says
supports NDIS drivers).
I have a public domain driver (from Sun) which links PC-NFS to a Clarkson
packet driver, but I'd prefer to use the NDIS driver if possible, as this
will make it easier to switch back to DEC Pathworks if it is occasionally
needed.

Essentially, I'm trying to sort out how to run such things as telnet/ftp,
NFS (with Pathworks at the same time, if possible) and a mailer. The
difficulty is knowing whether to go with Packet Drivers or NDIS Drivers -
I'm not sure which is more commonly supported by the network applications
which are around.

Any guidance on what supports what would be most appreciated. An e-mail
reply would be preferrable - I can't always find the time to review the
postings here.
From: mathieu@ncrcis.stpaul.ncr.com (Tom Mathieu [7143])
Newsgroups: comp.protocols.nfs
Subject: Need help with LifeLine Backup
Date: 16 Dec 92 19:12:11 GMT
Distribution: usa
Organization: NCR NPD Division

We have an EXB8200 tape unit attached to a server workstation.
For some reason, the RPUT job doesn't seem to like the EXB tape
drive.  After I start up RPUT, a few files go off to tape, but then
I get a message LL011F: Write failed.  The manual says the tape
drive is write protected or otherwise unavailable.  (That's what
that message is supposed to mean).  However, if I use the PC version
of TAR to do the backup, I can write to the tape just fine.

Do I need to do something weird with some options to make RPUT work
with the EXB 8200 drive?  (The funny part is, RGET and RLIST work
just fine).

Thanks,

Tom Mathieu


--
     _ _ /|
     \'o O'  mathieu@ncrcis.stpaul.ncr.com
     =(_._)=
        U
Newsgroups: comp.protocols.nfs
From: travuri@novell.com (Tulasiram Ravuri)
Newsgroups: comp.protocols.nfs
Subject: Re: PC NFS Printing
Date: 16 Dec 92 23:43:24 GMT
Organization: Novell Inc., San Jose, Califonia

In article <1go5t3INNm0b@seven-up.East.Sun.COM> geoff@poori.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
>I could indeed post the analysis (how many pcnfsd's needed to print
>on multiple remote systems), but the description in the PC-NFS
>documentation is complete as it is.....
Controlling my temptations to respond.
>right now, and would prefer not to compose a long posting at
>this baud rate :-), let me ask this. Do you have a copy of PC-NFS?
Yes.
>If so, did you find the description inadequate - if so, cite
>chapter and verse and I'll remedy the deficiency (and file a bug report
>against the doc). Or do you not have a copy of PC-NFS (or any other
>product that uses pcnfsd)?
>
With reference to the PC_NFS Users'guide, chapter on 'Using Printers'
subsections 'Mounting a Network Printer' using nfscon/command line, there are
some examples on how  to map printdevices to different printers on
different hosts.  
     e.g  net use LPT1: popcorn:lwtr
          net use LPT2: curry:lw /end=h,/fmt=p
          net use LPT3: candy:laserw /end=m,/fmt=r
         
I did'nt come across any mention of having to have PCNFSD
running on all the different hosts, which is confusing because on the PR_INIT
protocol there is no hostname field.  Am I to understand that PC NFS Client is
sendig the PR_INIT request to the host mentioned in the net use command,
implying that PCNFSD is to be running on all the hosts?

-- Tulasi
Newsgroups: comp.protocols.nfs
From: backman@vaxeline.ftp.com  (Larry Backman)
Subject: Re: PC-NFS 4.0 and Windows for Workgroups
Nntp-Software: PC/TCP NNTP
Organization: FTP Software, Inc., Wakefield, MA
Date: Tue, 15 Dec 1992 09:46:26

In article <1g2ci9INN9g1@seven-up.East.Sun.COM> geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:

 >> I don't know who you spoke  with at Sun, but this description
 >> is inaccurate in almost every respect.
 >> 
 >> 
 >> There are a number of incompatibilities between PC-NFS and W4W.  On the
 >> PC-NFS side, we had to rework our emulation of the DOS Int21 5F02
 >> (GetRedirList) call - our original code was legal as defined by the DOS
 >> Tech.Ref, but W4W is picky and won't allow "gaps" in the index list.
 >> However there is also a bug in W4W (specifically in the W4WNET.DRV
 >> driver) which Microsoft has to fix. We've been working with MS on this,
 >> and our testing is substantially complete. (It would be unwise to infer
 >> from this that the fix is ready to be released, since it's possible
 >> that there are additional changes that MIcrosoft needs to make to
 >> W4WNET.DRV.)

 Agree with Geoff.  There is a bug in the WfWNet.drv; there is also
 one in the vredir.386 Vxd that is worse :-).  We were broken also
 by WfW; we had to write a quick and dirty WFWFTP.386 Vxd to work
 around the WfW bugs.

 >> There would be little point in our releasing a patch to PC-NFS until
 >> we've had a chance to test against the final version of W4WNET.DRV (and
 >> any other changes in W4W). As soon as both PC-NFS and W4W fixes are
 >> ready, we'll announce the fact.

 Again; I agree with the competition; we too are working with our friends
 in the Northwest to make WfW a better neighbor to all other redirectors.

 >> PS For obvious reasons, I usually prefer not to go into this level of
 >> detail about multivendor problems in a public forum such as this - it
 >> tends to obscure/obstruct/cloud the issues we're trying to solve - but
 >> I felt that it was important to set the record straight. While it would
 >> obviously have been preferable if these incompatibilities could have
 >> been resolved during W4W beta testing, I would like to emphasize that
 >> we've had excellent cooperation with Microsoft in working on the
 >> resolution of the matter. No finger pointing please; we'll get things
 >> fixed as quickly as we can.

 Again; agreement from FTP; Microsoft has been very helpful in getting
 us information and the help needed to resolve the incompatibilities
 quickly.

 Larry Backman
 FTP Software
From: tyen@cs.utexas.edu (Anthony Yen)
Newsgroups: comp.protocols.nfs
Subject: Need Help with PC-NFS/Windows 3.1 Dialog
Date: 17 Dec 92 02:23:25 GMT
Organization: Coffee R Us
NNTP-Posting-Host: peaches.cs.utexas.edu


I have a dialog box that appears whenever I try to start a MS-Windows
3.1 on a new PC-NFS 4.0a installation:

	Dialog Title:  PC-NFS Network

	Message:  The network software has not been installed.
	          You must have the RTM module loaded
	          before starting Windows.
	          Network options will not be enabled.

	Checkbox: Disable warning when network not running.

	Button: OK

Now, much as I would like "RTM" to mean "Read The Manual", I'm sure
this is not what it means :-).  I've gone through the error messages
in the Reference Manual, and could not find this message.  Nor was
there any helpful information in the section about MS-Windows.  Could
someone please let me know what this message means?

-- 
 ____     tyen@cs.utexas.edu.....Kowabunga!...
  /ony -- Claimer: Views expressed here == mine && only mine.  Sail tough.
Newsgroups: comp.protocols.nfs
From: vaisanen@joyds2.joensuu.fi (Jarmo Vaisanen)
Subject: PC-NFS locking don't work - HELP!
Reply-To: vaisanen@joyds2.joensuu.fi (Jarmo Vaisanen)
Organization: University of Joensuu, Computer Center
Date: Mon, 14 Dec 1992 12:08:05 GMT

Help!


I would like to share common data files under MS Windows with other users
using PC-NFS network.  It seems to me that UNIX lockd could support this.
Our server machine is Sun so I had to patch SunOS kernel so that locking
would work (if I've had another UNIX I haven't had to do this :-).

What should I do now to get locking effective?  I do have lockd, statd and
pcnfsd running.  I have mounted server directory with "must share".

Should my Windows programs eg. Windows Write use locking now (it doesn't
seem to work :-(  Should I also run DOS SHARE?  What about other Windows
software like Excel or Ami Pro?  Or should I obtain network versions of 
these programs to get these working?


HELP I'm lost!


regards,
	Jarmo

-----------------------------------------------------------------------
Jarmo Vaisanen          vaisanen@joyds2.Joensuu.FI      (Internet)
University of Joensuu   JVAISANEN@FINUJO                (EARN, BITNET)
Computer Center
Newsgroups: comp.protocols.time.ntp
From: ramey@csc.ti.com (Joe Ramey)
Subject: should distance be this large for a local clock?
Originator: ramey@jello
Reply-To: ramey@csc.ti.com
Organization: Texas Instruments
Date: Sat, 12 Dec 1992 22:10:43 GMT

I am trying to bring up xntp3 on my Sun4.  The other NTP systems on my
network all run version 2 of NTP.  I specified version 2 in the
ntp.conf file for the peers and servers that I configured, but I could
never get xntpd to sync up.

Looking into things further I discovered that it was discarding the
packets because the `distance' field of the packets it received was
too large (0x140000 > 0x100000).  Here is some output from ntpq
looking at our stratum 1 server:

------------------------------------------------------------------------------
/usr/local/etc/ntpq sunspot.hc.ti.com
ntpq> pe
     remote           refid      st  when poll reach  delay  offset   disp
==========================================================================
*127.127.1.0     .LCL.            0    43   64  377  5000.0    0.00    0.0
ntpq> readlist
status=0033 leap_none, sync_unspec, 3 events, event_sync_chg
system="UNIX", leap=00, stratum=1, distance=20000.0, dispersion=0.0,
peer=46196, refid=LCL,
reftime=aed4dce9.4e11c000  Sat, Dec 12 1992 15:49:29.304,
clock=aed4dd18.19abe000  Sat, Dec 12 1992 15:50:16.100, hold=0,
phase=0.00, freq=0.00, compliance=0.00
ntpq>
------------------------------------------------------------------------------

The delay (5000) and the distance (20000) seem awfully large to me.
Does it look like this server is working properly or not?
Newsgroups: comp.protocols.time.ntp