HDTenEightyP/NetNews huggingface dataset:
From: dhiltz@whsun1.wh.whoi.edu (David Hiltz)
Subject: Re: DNS with PC-NFS, ^p in Telnet
Reply-To: dhiltz@whsun1.wh.whoi.edu
Organization: NOAA - National Marine Fisheries
Date: Thu, 21 Jan 93 12:59:06 GMT

 I'm interested in the second part of your question.  If you find the 
 answer, post it or send me mail please.

 Thanks.

   David Hiltz
   NMFS, MA
   dhiltz@whsun1.wh.whoi.edu
   #####&@&####
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
From: "Bob Larribeau" <p00136@psilink.com>
Subject: Re: PC-NFS PPP Serial/ISDN driver wanted
Organization: Consultant
Date: Thu, 21 Jan 1993 16:01:40 GMT
X-Mailer: PSILink-DOS (3.3)

>Why would the ISDN/Ethernet bridge include an NT1? When you install the
>ISDN line, you install the NT1 as part of the Network Termination. 
>You don't have an NT1 in your ISDN phone, not in your ISDN fax, not in
>your ISDN BRI card for your PC. Why would a bridge include it?
>

In the U.S. (unlike most of the rest of the world) the NT1 is customer 
equipment and not network equipment.  It is the customer's 
responsibility to purchase and install the NT1.

The reason for having a U interace in the ISDN bridge is that it can 
reduce cost by eliminating the need for the U interface to T interface 
conversion and then the T interface to Ethernet conversion by converting 
directly from the U interface to Ethernet.

Note that this is not necessarily the same as integrating the bridge 
with an NT1.  NT1s have an S/T inteface and support the passive bus.  
The U interface bridge would not require this function.

The primary advantage of having an NT1 is that it permits support for 
passive bus and the ability to connect multiple devices on an ISDN line. 
However given the limitations of NI-1 in supporting B channel 
contention, this is not a strong reason.  These limitations are supposed 
to disappear with NI-2.

In the U.S. there are ISDN telephones and TAs with U interfaces.  It 
does represent the lowest cost for connecting to an ISDN line.  A voice 
only, U interface ISDN telephone is in the $200 price range.

		Bob Larribeau
		San Francisco
From: lwj@cs.kun.nl (Luc Rooijakkers)
Newsgroups: comp.protocols.nfs
Subject: Obtain PC-NFS serial over BOOTP?
Date: 21 Jan 93 15:42:51 GMT
Organization: University of Nijmegen, The Netherlands

I am looking for a program that uses BOOTP to obtain a PC-NFS
serial number and then patches it into the already loaded PCNFS.SYS
(which is easily found by walking the DOS device chain). This would
allow me to distribute identical boot floppies. I am using a packet driver.

Such a program could also construct a NETWORK.BAT and DRIVES.BAT from
the BOOTP info, so that PC-NFS does not need to RARP and access NIS for
this info.

So, I have several questions:

1) Does such a program exist?

2) If not, does a reasonably small BOOTP client program exist? Several
   packages are capable of using BOOTP, but they are all rather large.
   I could then easily add the functionality myself.

3) Is there a standard way of adding PC-NFS serial numbers, NIS domain,
   NIS server, etc to bootptab (i.e. what RFC1048 numbers are used?)

4) Is there a way to get NET INIT to read NETWORK.BAT and/or DRIVES.BAT
   from somewhere else then NFSPATH (e.g. stdin)? Or do I have to invoke
   all the NET commands myself (does NET INIT do anything more then reading
   NETWORK.BAT and DRIVES.BAT?)
   
--
Luc Rooijakkers                                 Internet: lwj@cs.kun.nl
Faculty of Mathematics and Computer Science     UUCP: uunet!cs.kun.nl!lwj
University of Nijmegen, the Netherlands         tel. +3180652271
From: geoff@tyger.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs
Subject: Re: PCNFS 4.0 not displaying boxes ! (also Re: DNS with PC-NFS, ^p in Telnet)
Date: 21 Jan 1993 21:48:15 GMT
Organization: SunSelect
Distribution: world
Reply-To: geoff@tyger.East.Sun.COM
NNTP-Posting-Host: tyger.east.sun.com


[Three times in one day.... Oh well, probably easiest to post the info.]

To fix the control character and line drawing character bugs in PC-NFS 4.0
telnet, you need to get the PC-NFS 4.0a patch kit, which you can FTP from any of
	bcm.tmc.edu
	src.doc.ic.ac.uk
	ftpserver.massey.ac.nz

Geoff
---
Geoff Arnold, PC-NFS architect, Sun Select. (geoff.arnold@East.Sun.COM)

Xref: sparky comp.protocols.nfs:3182 comp.dcom.isdn:1196
From: cliff@garnet.berkeley.edu (Cliff Frost)
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
Subject: Re: PC-NFS PPP Serial/ISDN driver wanted
Date: 21 Jan 1993 19:44:46 GMT
Organization: University of California, Berkeley
Distribution: world
NNTP-Posting-Host: garnet.berkeley.edu

In article <2936706683.1.p00136@psilink.com>, "Bob Larribeau" <p00136@psilink.com> writes:
|> 
|> In the U.S. there are ISDN telephones and TAs with U interfaces.  It 
|> does represent the lowest cost for connecting to an ISDN line.  A voice 
|> only, U interface ISDN telephone is in the $200 price range.

And I'm finding the *best* price anyone will quote me for a 2B1Q compatible
NT1 and its power supply is in the range of $350.  Seems that both
Northern and AT&T upped their prices on these suckers in the last couple
of months.  These suckers appear to be priced to discourage vast segments
of the market.

I'd be happy to hear from anyone who is currently buying these NT1s at
better prices (in small volume).  I've followed up every lead I've seen
in this group (and other places), including calling Atlanta and Illinois
(from California, spitting distance from Silicon Valley), and not one
of the leads has turned up lower than $350.  It's depressing...

	Thanks,
		Cliff Frost
		UC Berkeley
From: ramsey@CERIS.Purdue.EDU (Ed Ramsey)
Newsgroups: comp.protocols.nfs
Subject: SUMMARY: PC/NFS Telnet (4.0a) wont connect to host from compaq286/mono
Keywords: pcnfs telnet
Date: 22 Jan 93 15:20:48 GMT
Organization: Center for Environmental and Regulatory Information Systems, Purdue University


John Gilbert and Paul Carroll both mentioned using the "-x" switch to telnet,
which tells telnet the pc is using an older BIOS that doesn't support
the extended keyboard functions.  This switch solved my problems.

Thanks to:

"John R. Gilbert" <gilbert@parc.xerox.com>
Paul.Carroll@east.sun.com (Paul Carroll - Sun PC Network Engineering)


Here was my question:

> I am in the process of upgrading all of our PCs from PC/NFS 3.5[bc] to
> PC/NFS 4.0a without any trouble until today.  We have a Compaq 286
> running a standard pc monochrome (non-compaq) monitor that works ok 
> using 4.0a (net print, screenprints, ftps, rshs) except that it wont
> telnet.
> 
> You can type "telnet" and play with the command mode of telnet, but when 
> you try to connect, or when you type "telent host" (where host is a real
> host in the PCs hosts file), something quickly flashes by and then you
> get nothing but a cursor on the beginning of line 4 or 5. CTL/ALT/DEL
> works fine but nothing else.
> 
> 3.5b telnet always did work fine. I commented almost everything out of the
> autoexec and config files and 4.0a telnet still wouldn't work.
> 
> Any fixes?  Anyone have this problem or a problem like it?  Any
> advice?

-Ed

-- 
Ed Ramsey ramsey@ceris.purdue.edu 317/494-0442 FAX/494-9727
CERIS (Center for Environmental and Regulatory Information Systems)
Network Services Manager/UNIX Systems Administrator
From: jcallaha@willamette.edu (John Callahan)
Newsgroups: comp.protocols.nfs
Subject: PC-NFS 4.0a Telnet VT100 Printer Escape (?)
Keywords: PC-NFS, telnet, printers, vt100
Date: 26 Jan 93 02:08:27 GMT
Article-I.D.: willamet.C1FvA3.1sC
Organization: Willamette University, Salem OR

The documentation for PC-NFS V4.0/4.0a telnet mentions a "use printer"
option to direct output for vt100 printer escapes.  However, I can't seem
to get telnet to recognize the vt100 printer escape.

Has anyone else had any success with this?

Thanks in advance.

John Callahan
Network Manager
Willamette University
Newsgroups: comp.protocols.nfs
From: leeh7@fel.tno.nl (Ed van Leeuwen)
Subject: Re: Help!! NFS / MS-WIN3.1 Error ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
Organization: TNO Physics and Electronics Laboratory
Date: Thu, 21 Jan 1993 14:53:41 GMT

Brian.Milner@brunel.ac.uk (Brian D Milner) writes:


>I have a 486/33Mhz EISA tower attached to our net via PC-NFS. It'll run
>MS-Windows 3.1 *before* you attach to the network, but not after.

>The PC-NFS setup is absolutely standard - the same as for 100s of other
>PCs which can all first attach to the net, then run windows quite happily.

>I reinstalled windows - no go.
>I reinstalled PC-NFS  - no go.
>I ran the *network* rather than the *local* version of windows - same problem

>Originally the problem manifested as a System Error Message:

>                        Cannot Access H: Drive

>I noticed that the autoexec.bat said "SET TEMP=H:\". I reset this to C:, 
>and the message then read:

>                        Cannot Access J: Drive

>Nowadays it seems to lock up for a long time before displaying a message,
>so I don't usually wait for the System error box to appear. I posted to 
>the MS-Windows groups, but none of their suggestions worked.

>Any Ideas?

We have had similar problems with Win 3.0, not 3.1, but perhaps our
old solution works for you too.

We used the 'subst' command to let all unused (not mounted) drives
point to the C-drive. Example:
	subst h=c i=c
Note that you should give all the drives in one 'subst'-command
in stead of givoing each drive its own 'subst'-command.

If your environment changes often, this will nog give you a proper
solution, as you will have to change the command each time you
change the environment.



					Regards,

					Ed.

===============================================================================
Ed van Leeuwen                        |  Ed W.A. van Leeuwen
FEL-TNO                               |  TNO Physics and Electronics Laboratory
's-Gravenhage                         |  The Hague, the Netherlands
-------------------------------------------------------------------------------
Ed.van.Leeuwen@fel.tno.nl             |  Oops! Sorry, I am only a referee...
===============================================================================
From: ralf@wilma.physik.uni-stuttgart.de (Ralf Hirning)
Newsgroups: comp.protocols.nfs
Subject: PC-NFS with ULTRIX in ENHANCED security mode
Date: 25 Jan 1993 15:48:37 GMT
Organization: ITAP University of Stuttgart
Distribution: world
Reply-To: ralf@wilma.physik.uni-stuttgart.de (Ralf Hirning)
NNTP-Posting-Host: wilma.physik.uni-stuttgart.de
Keywords: PC-NFS, ULTRIX, kerberos, BIND/hesiod

We use SUN PC-NFS to serve a 1 GB Disk mounted on a
DEC-Station 5000 ( ULTRIX 4.2A ) for several users
on PCs. We have a cluster of seven DEC-Stations and distributed
accounts ( BIND/hesiod ).

The ncnfsd - daemon compares the given password with the entry in
/etc/passwd, but in enhanced security mode the is only a '*' there.

So a normal user cannot use the command
 net name user
to log into the system.

To make use of the disk I created a local account on the machine
where the disk is mounted and put an encrypted password in /etc/passwd
( instead of the '*' ). So users can use the disk, but they have all
the same uid.

Is there a patch for pcnfsd to run properly with ULTRIX?

==================================================

Ralf Hirning ( ralf@itap.physik.uni-stuttgart.de )
ITAP
University of Stuttgart
Pfaffenwaldring 57 VI
D-7000 Stuttgart 80
Germany

==================================================
Newsgroups: comp.protocols.nfs
From: markus@edfd.uucp (Markus Gruenkorn (MAGIC))
Subject: PCNFS 4.0 not displaying boxes !
Organization: EDAG, ENGINEERING + DESGIN AG, Fulda, FRG
Date: Thu, 21 Jan 1993 13:11:51 GMT

Hi guys !
One question !
We have different versions of PCNFS (3.5, 4.0).
With 3.5 if I telnet from a PC to a sun the line drawing characters are
displayed correctly. With 4.0 the PC shows q,x,l,j and not the vertical
and horizontal lines, or the corners . Why ? What can I do ?
Any information would be appreciated !

-- 
------ < MAGIC > ------
Newsgroups: comp.protocols.nfs
From: cm305b@uc780.umd.edu (CMIS 305 SECTION 5011)
Subject: NFS via TCP services
News-Software: VAX/VMS VNEWS 1.41    
Organization: University of Maryland, University College
Date: Sat, 23 Jan 1993 16:45:00 GMT

I am interested in any work that is being done to have NFS use TCP services.
I read recently that this was one of the future directions.  IS there any
papers/products out there that address this issue.  Thanks in advance.

Mike Alleman
University of Maryland University College

"Captain, the Beverly Hillbillies have taken over the United States!"
From: kaz@uni-paderborn.de (Kay Mueller)
Newsgroups: comp.protocols.nfs
Subject: FAQ (sorry)
Date: 28 Jan 93 12:43:40
Organization: Uni Paderborn FB 17 Informatik GERMANY
Distribution: comp
NNTP-Posting-Host: haegar2.uni-paderborn.de

Sorry for posting an FAQ:
Running PCNFS 4.0 with windows disables the local printer.
(the remote printer works fine)
What's wrong?

Thanx
Kay
Newsgroups: comp.protocols.nfs
From: fr@eagle.mumath (Farid Rahmi)
Subject: Re : Replace telnet in PC-NFS
Reply-To: fr@eagle.mumath
Organization: BIM sa/nv
Date: Thu, 21 Jan 93 19:10:07 GMT


>I am looking for a program which does the same in a SUN PC-NFS environment
>as "tnglas" does for PC-TCP from FTP. The program takes the INT 14 and
>send anything from your terminal emulator to a TCP - host.

There is an INT14.EXE bundled with Advanced Telnet 1.0 (an optional terminal emulat-
ion package sold by SunSelect). It's about 70KB and I used it to run non-standard
emulators from Persoft (e.g. Smarterm 470 to talk to a Data General). I guess it will
work with other software that catches interrupt 14.

Farid.

P.S.: I have a funny anecdote on INT14. A customer tried to get his Procomm Plus
      for Windows talking to a modem connected to his host. When he called DataStorm
      they told him "to go and find an INT14 for his Unix box :-)". Dos,dos,dos...

Newsgroups: comp.protocols.nfs,comp.dcom.isdn
From: mandrews@portal.hq.videocart.com (Mike Andrews)
Subject: Re: Re : Replace telnet in PC-NFS
Organization: VideOcart Inc.
Date: Tue, 26 Jan 1993 20:20:21 GMT

In article <1993Jan21.191007.28724@sunbim.be> fr@eagle.mumath writes:
>
>>I am looking for a program which does the same in a SUN PC-NFS environment
>>as "tnglas" does for PC-TCP from FTP. The program takes the INT 14 and
>>send anything from your terminal emulator to a TCP - host.
>
>There is an INT14.EXE bundled with Advanced Telnet 1.0 (an optional terminal emulat-
>ion package sold by SunSelect). It's about 70KB and I used it to run non-standard
>emulators from Persoft (e.g. Smarterm 470 to talk to a Data General). I guess it will
>work with other software that catches interrupt 14.
>
>Farid.
>

And Beame and Whiteside NFS includes a module called BWCOM14 that not only
sends INT14 I/O to a Unix host, but recognizes the AT (Hayes) command set!

Contact Beame and Whiteside at 416-765-0822.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=
Mike Andrews                                   VideOcart, Inc.
mandrews@hq.videocart.com                      Chicago, IL USA 
=-=- Madonna:  Andy Warhol called. Your 15 minutes are up.-=-=
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
From: emv@msen.com (Edward Vielmetti)
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
Subject: Re: Low cost ether/isdn brouters (was PC-NFS PPP Serial/ISDN driver wanted)
Followup-To: comp.protocols.nfs,comp.dcom.isdn
Date: 22 Jan 1993 01:37:11 GMT
Organization: Msen, Inc. -- Ann Arbor, Michigan
NNTP-Posting-Host: garnet.msen.com
X-Newsreader: TIN [version 1.1 PL8]

Dave Carr (dcarr@gandalf.ca) wrote:

: I made no such claim.  A bridge cannot replace a router.  But a router
: IS overkill for many applications.  Especially for replacing V.32 modems
: in a dialup application.  What do you want, a CISCO at home.  You must
: have a big net at home if you need BGP.  And I thought all you needed was
: OSPF at home.  

Dave, it's not at all unusual to have a router at home - most likely
it's a Unix box running SLIP or PPP over V.32bis modems.  Your ISDN
gear is not replacing anything more than that modem and (maybe) that terminal
server out there on the other end.

Talk to Sun or HP or NeXT or SGI (?) and build a box that will run as
a hub for the ISDN they are building onto their motherboards.  Talk to
Morning Star or their customers about what people are doing with PPP.
Pick up some clues as to what is actually out there in the field today
delivering Internet connections to people and build some gear that slides
in nicely...aim at the equipment that's going to squash V.fast before it
appears - 2B + NT1 in a single box, RS-232 or V.35, AT or V.25bis dialing,
ship it list $999 day 1 quantity 1. - get there before someone like Adtran
does...

  Edward Vielmetti, vice president for research, Msen Inc. emv@Msen.com
        Msen Inc., 628 Brooks, Ann Arbor MI  48103 +1 313 998 GLOB
From: long@vax.ox.ac.uk (Neil J. Long)
Newsgroups: comp.protocols.nfs
Subject: Drivers for other cards
Date: 22 Jan 93 13:06:59 GMT
Organization: Materials Department, University of Oxford

Hi
Could someone email me with any info on a site for drivers for cards other 
than the ones that come with the standard 4.0/4.0a distribution for PC-NFS.
In particular I am looking for a driver for an NE2000 (National 
Semiconductor board but Novell compatible) card which is used a lot in our 
department.
The packet driver method is quite sluggish!
thanks
Neil
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
From: ajb8886@ritvax.isc.rit.edu
Subject: Re: PC-NFS PPP Serial/ISDN driver wanted
Reply-To: ajb8886@ritvax.isc.rit.edu
Organization: Rochester Institute of Technology
Date: Sat, 23 Jan 1993 16:09:30 GMT

In article <CKD.93Jan20160821@loiosh.eff.org>, ckd@eff.org (Christopher Davis) writes:
>JG> == John Galloway <johng@informix.com>
>
> JG> Gee that would be nice, but I think unrealistic.  This would mean that
> JG> a single unit would likely sell for 160-200, which is less than a v.32
> JG> modem.  Given the couple of extra items (like a LANCE chipe set, and
> JG> the NT1) an isdn/ethernet bridge should cost a bit more than a modem.
> JG> So say 400-500 in singles and maybe 250-300 in quanity.  Or so it
> JG> seems to me.
>
>DSPs cost money, too; there's a LOT of computing power inside a V.32/bis
>modem, after all (probably more than the first multiuser system I used, and
>certainly more than the first computer I had to myself...).
>--

> * Christopher Davis * <ckd@eff.org> * <ckd@kei.com> * [CKD1] * MIME * RIPEM *

The CPU in a typical rockwell-based V.32bis modem runs at 20Mhz.  That should
give you a little bit of a picture.

Alex



Xref: sparky comp.protocols.nfs:3175 comp.dcom.isdn:1193 comp.protocols.ppp:1104
From: emv@msen.com (Edward Vielmetti)
Newsgroups: comp.protocols.nfs,comp.dcom.isdn,comp.protocols.ppp
Subject: Re: Low cost ether/isdn brouters (was PC-NFS PPP Serial/ISDN driver wanted)
Followup-To: comp.dcom.isdn,comp.protocols.ppp
Date: 21 Jan 1993 17:09:33 GMT
Organization: Msen, Inc. -- Ann Arbor, Michigan
NNTP-Posting-Host: garnet.msen.com
X-Newsreader: TIN [version 1.1 PL8]

Dave Carr (dcarr@gandalf.ca) wrote:

: Interesting.  Could you tell me more.  With ISDN, we are basically talking
: about a point-to-point link.  Our view is with the right software mods, you
: can get the desired performance out of a bridge.  The trickiest part is the
: handling of multicast and broadcast.  If we can eliminate these packets
: without doing the entire routing function, do we have what you need?

We are running people into a public network - for that reason we need
to do traffic isolation right away.  They typically have not one
host but 5 or 10 or 50 that are supported over a dial up line,
and they route traffic internally on their net.  These are connections
that want to do serious filtering and access limitations to their
net, and there is *no* way that they are going to bridge their net
to ours.

There is no way that a bridge works in this scenario - to get the
proper flows you'd need to wedge a router interface in there
somewhere anyways on each end.  So I suppose you could go
	router-ethernet bridge isdn isdn bridge ethernet-router
but that's just silly.

If you really have a point-to-point link then I'm going to run
PPP over it.  If you instead have a subnetwork of some sort then
I suspect that frame relay is the right frame of mind to take.
But a bridged ethernet really doesn't match the Internet network point 
of view.  (Not to say there aren't good places for it!  Just not
here!)

  Edward Vielmetti, vice president for research, Msen Inc. emv@Msen.com
        Msen Inc., 628 Brooks, Ann Arbor MI  48103 +1 313 998 GLOB
From: probert@fires1.uucp (Neal Probert)
Newsgroups: comp.protocols.nfs
Subject: Windows 3.1 locks up with PC-NFS 4.0a
Date: 22 Jan 1993 15:45:15 GMT
Organization: Scientific Research Labs, Ford Motor Company
Distribution: na
Reply-To: probert@fires1.srl.ford.com
NNTP-Posting-Host: fires1.srl.ford.com

When accessing a remotely mounted disk via PC-NFS 4.0a, no matter how I do it
(via COPY or DIR), Windows 3.1 locks up and I usually have to reboot.
The File Manager will lock up when trying access it too.  Or when running
one of the NFS utilities such as ping or telnet.  This happens
occasionally, not all the time.

Any ideas as to what is wrong?  I have some of the drivers loaded high.




-- 
    FORD       | Neal W. Probert   E3154 SRL    | probert@fires1.srl.ford.com
 SCIENTIFIC    | Ford Scientific Research Labs  | 313-845-8178 FAX 313-845-8202
RESEARCH LABS  | Dearborn, MI 48121-2053        | 
Newsgroups: comp.protocols.nfs
From: deg@kksys.com (Dan Germann)
Subject: Can I make NFS run over SCSI to share a disk?
Followup-To: deg@kksys.com
Keywords: NFS SCSI shared disk
Organization: K and K Systems
Distribution: na
Date: Mon, 25 Jan 1993 19:12:39 GMT

I have an off-the-wall question/idea.  A client of mine has a system that
gathers data and writes it off to disk.  It runs on a proprietary CPU
with a kludge-o-matic "operating system".  The problem is that they need
to be able to get at the data from their UNIX system, where they have
good application software to analyze the data.  Their system has a SCSI
interface to their proprietary CPU which could be used to communicate
between the UNIX box and the data acquisition box.  Their application also
needs to be able to delete the data files when it's done analyzing the
data and has printed the report.

My off-the-wall idea is to make the data acquisition box an NFS server and
share the internal disk with the UNIX box.  It makes things very easy on
the UNIX box end -- their report generators can access the files directly
and delete them when finished.  Obviously, it makes things harder in the
data acquisition box.  Not only do I have to implement NFS server software,
I also have to find a way to convince UNIX to talk NFS over a SCSI bus.

How unrealistic am I being?  Can I get NFS/RPC/XDR source code somewhere?
Any suggestions are welcome.  Please reply via email.

-Dan Germann
deg@kksys.com