HDTenEightyP/NetNews huggingface dataset:
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
Subject: Re: Low cost ether/isdn brouters (was PC-NFS PPP Serial/ISDN driver wanted)
Date: 22 Jan 93 20:47:54 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

In article <1993Jan21.224740.4259@gandalf.ca>, dcarr@gandalf.ca (Dave Carr) writes:
> ...
> Try a 5220.  And if you want a router with the same feature (data 
> compression, SNMP,...) for under $3000, wait a couple of months.  
>  ...

> Try the 5220i.  Not a misprint.  The 5200i can dial on demand, and only
> brings the link up when needed.  Shoot, it even looks at ARPs and IP
> addresses.  So tell me, is a router or a bridge.  
> ...

> The 5220i can dial different ISDN numbers to get to different IP 
> addresses.  Okay, it's a static router.  Some limitations apply.
> What's the equivalent CISCO box sell for?  What's that, you want
> compression.  Sorry.  We're Cisco, you don't need compression.
> ...

I mentioned cisco only to show what happened to the old style bridge
makers of years ago, who insisted on making dumb bridges and only
bridging.  Remember what the notion of "brouter" did to them?

$3000 would be expensive for a router.  Late last year you could buy a
T1 router (without CSU/DSU, but T1 and not measely 56K or 64K) for
about half of that.  Not (as far as I know) from Cisco, but then Cisco
is a big, mature company now.


> ..
> >Finally, I notice that you posted this to comp.protocols.nfs.  That
> >suggests you are thinking about running NFS over your ISDN boxes.  NFS
> >usually implies NIS.  NIS almost always involves broadcast packets.
> >How are you going to "eliminate these [broadcast] packets"?
> 
> Sure, why not.  After all, a bridge doesn't discriminate on the basis
> of protocol :-)
> 
> From what angle?  If bandwidth on the link is the problem, then I'll
> ask "How much information content is in a broadcast? In the second?"
> Know what compression does to these packets?
> 
> If your assuming that I am going to filter all broadcast and therefore
> NIS packets won't get through, that's a wrong assumption.  

I'm not sure what you're saying, but I think you should get some packet
traces of big networks.  There is much redundancy and so hope for
compression as I infer that you hope.  Unless the bridge is congesting
things, the broadcasts are not simply retransmissions of the same stuff
and so will not be compressed, at least not if your compression
dictionary (or whatever) adapts to traffic faster than every 30 sec.
(~2Mbit at 64Kbit/sec).

The corporate network I know tends to have a lot of broadcast and
multicast packets.  Besides ARP and NIS, there are games (~30 p/s/player)
and audio multicast streams.  No plausible compression will be enough.
You will have to filter by looking at higher layer protocols.

Still and all, products like your 5220* sound like efforts in the
right direction, so I'm not sure what we are arguing about.


Vernon Schryver,  vjs@sgi.com
Newsgroups: comp.protocols.nfs
From: lsidor@dres.dnd.ca (Lyle T. sidor)
Subject: Re: FAQ (sorry)
Organization: Defence Research Establishment Suffield
Date: Thu, 28 Jan 1993 17:13:48 GMT

In article <KAZ.93Jan28124340@haegar2.uni-paderborn.de> kaz@uni-paderborn.de (Kay Mueller) writes:

>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

This is from the README.TXT file that comes with PC-NFS 4.0:

**MICROSOFT WINDOWS SUPPORT**


USE PRINT MANAGER TO CONTROL PRINTING 

When configuring Printers to be used with PC-NFS software, it is
recommended that you use the Print Manager. You can do so by selecting 
"Use Print Manager" in Control Panel. Print Manager correctly handles 
output redirection to a local or remote printer. If you have problems 
printing to a local printer (i.e., one attached to your machine), go 
to Print Manager and verify that "Print Net Jobs Direct" is disabled. 
In Windows 3.1, select "Options" and then select "Network Settings." 
In Windows 3.0, select "Options" and then select "Network."
Newsgroups: comp.protocols.nfs
From: fr@eagle.mumath (Farid Rahmi)
Subject: Re : Drivers for other cards
Reply-To: fr@eagle.mumath
Organization: BIM sa,nv
Date: Tue, 26 Jan 93 18:59:14 GMT


Neil,

>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.

Start NFSCONF, choose NDIS from the adapter menu, you will be asked to insert
your first PCNFS floppy.

Next, take the third floppy (you know, the one with the weird name _QUIKNDIS_)
out of your PCNFS box, put it your floppy drive and type :

QUIKNDIS <Return>

From here on, NE2000 will appear in the list. Answer some obvious questions
and off you go.


Farid.
From: bigenwal@sun-valley.amcc.rochester.edu (Chris J. Bigenwald)
Newsgroups: comp.protocols.nfs
Subject: Re: FAQ (sorry)
Date: 28 Jan 93 18:35:40 GMT
Distribution: comp
Organization: University of Rochester (Rochester, NY)

Yes, I have the same problem when I run rtm.exe before loading Windows 3.1

- Chris
Newsgroups: comp.protocols.nfs
From: ramsey@CERIS.Purdue.EDU (Ed Ramsey)
Subject: PC/NFS Telnet (4.0a) wont connect to host from compaq286/mono system
Keywords: pcnfs telnet
Organization: Center for Environmental and Regulatory Information Systems, Purdue University
Date: Thu, 21 Jan 1993 23:12:05 GMT


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
Newsgroups: comp.protocols.nfs
From: jgr@ncn.UUCP (Jrn Grotnes)
Subject: Beeing nobody sometimes
Organization: Siemens Nixdorf A/S
Date: Wed, 27 Jan 1993 13:39:35 GMT
Summary: Printing problems; user ID suddely nobody 
X-Newsreader: Tin 1.1 PL4
Keywords: Printing, nobody, user ID, UID 

We have a problem in a ca.70 PC workstation network using PC-NFS 4.0a.
Sometimes, the printer jobs will hang (the servers spool directory
will contain the file but not append the .spl extension). Files written
atfter this on network disks will have the correct owner and group, but
when looking at the user information in the "network" part of the control
panel the user name will be "nobody", the domain will be nothing (not
"none" but plainly no entry, and UID and GID will be -1! (should be -2
or shouldn't it?). The error occurs intermittently, sometimes 4 times a day.
There is no known way to provoke it. Some PCs has never failed. When exiting to
DOS to check via "net name" the user information is correct. If the user
starts to log on to a server via telnet (or JSB i.e. a terminal emulator) 
the user information will be back to normal and printing will again be 
possible. (Old jobs will not be printed). This seems to be a problem on both 386SX and 486SX based systems, but happens much more often on the 486 systems.
This may be due to a higher level of user activity on these PCs. Both BICC
and WD (SMC) cards has been tested. 

On tip received already: this could happen after trying to log on to a server
which is not available. Does not seem to apply to the situation at hand, though.

Any further tips are wellcome :-)

Joern "No tag yet" Grotnes 		jgr@Siemens-Nixdorf.no
Newsgroups: comp.protocols.nfs,comp.dcom.lans.ethernet
From: bob@reed.edu (Robert Ankeney)
Subject: SOSS and mounting a PC filesystem problem
Organization: Reed College, Portland, OR
Date: Thu, 21 Jan 1993 20:23:26 GMT


     I have recently installed the SOSS NFS software on a couple of PC
systems.  The PC's are networked to a MicroVax system running Ultrix 4.2.
I can do a showmount on the PC successfully, but when I try to mount a
PC filesystem, I get the message:

     nfs_mount: tater:/c server not responding: RPC: Authentication error;
          why = Invalid client credential

Does anyone know what this means?  And how to get around it?

     Thanks,
     Robert

Newsgroups: comp.protocols.nfs
From: bubba@super.org (Paul Bublitz)
Subject: PCNFS 40a junk files
Organization: Supercomputing Research Center (Bowie, MD)
Date: Thu, 28 Jan 1993 20:32:19 GMT

I am running PCNFS ver 4.0a on our Sun network (SunOS 4.1.1) and
I am seeing some strange problems.  Has anyone else seen these?
What's the solution?

Problem 1:  
     When working with network mounted drive with PCNFS,
     trash files get left on the network directory.  If I 
     am working with a file named spp1_fmt.doc, a Word for
     Windows file, I will be left with a file called
     ~$p1_fmt.doc of 51 bytes.  There will alse be a
     lot of temporary files like ~doc0131.tmp left in
     the subdirectory.  These files do not get deleted
     by the system and I have been deleting them manually.

Problem 2:
     The ftp program that came with PCNFS version 4.0 and
     version 4.0a is EXTREEMLY slow:  it takes minutes to
	  transfer a 8K file.  My work aroud was to use the ftp 
	  program that came with version 3.4, it works fine under
	  version 4.0a.  I had the same problem with FTP Inc's
	  ftp program and I resolved it by changing its (ftp's)
	  default window size to 512 bytes from its default 
	  1024 byte size.  Is there a means to change the PCNFS
	  stuff?

Thanks for any help you can give me.

Paul Bublitz
Supercomputing Research Center
(301) 805-7594
bubba@super.org


Newsgroups: comp.protocols.nfs,comp.dcom.isdn
From: jbvb@vax.ftp.com  (James B. VanBokkelen)
Subject: Re: NFS via TCP services
Nntp-Software: PC/TCP NNTP
Keywords: TCP NFS
Reply-To: jbvb@ftp.com
Organization: FTP Software, Inc., North Andover, Massachusetts
Date: Mon, 25 Jan 1993 17:14:04

In article <23JAN199311452594@uc780.umd.edu> cm305b@uc780.umd.edu (CMIS 305 SECTION 5011) writes:

    I am interested in any work that is being done to have NFS use TCP
    services.

It isn't really at the level of papers anymore.  We've been shipping TCP
client capability with our OS/2 product for almost a year, and we're adding
it to our DOS product before the end of this quarter.  Sun's promised it
for some version of Solaris (not 2.1, I think).  TGV and Process Software
have it in their VMS TCP/IP packages.  Intercon demoed it for the Mac
in 1991, I don't know if it is productized yet.

James B. VanBokkelen		2 High St., North Andover, MA  01845
FTP Software Inc.		voice: (508) 685-4000  fax: (508) 794-4488

Newsgroups: comp.protocols.nfs,comp.dcom.isdn
From: dcarr@gandalf.ca (Dave Carr)
Subject: Re: Low cost ether/isdn brouters (was PC-NFS PPP Serial/ISDN driver wanted)
Organization: Gandalf Data Ltd.
Distribution: na
Date: Mon, 25 Jan 1993 14:22:06 GMT

In <1993Jan22.002029.27149@informix.com> johng@informix.com (John Galloway) writes:

>Educate me if you would, on just what is the difference (in function and use)
>of a TA Vs. an NT1.

An NT1 attaches directly to the TELCO lines.  On the other side, it provides
a passive bus for connection of the customers equipment.  Multiple devices
(TAs, phones,etc.) are basically multi-dropped on the passive bus.  The
TA provides conversion from the ISDN 2B+D to serial conversion (async or
sync) and the call control software.
>>
>I wasn't being really specific on RIP etc.  basically I just want a box
>that sits on my ethernet, and talks to my host(s) to get net info, configures
>itself and works.  I supply my IP addr, and a phone number and thats it.

Do you want the B-channels up permanently?  You probably want dial on
demand, with some intelligence at both ends to establish the link only
when required.  Given the choice between a standard bridge or router,
the router wins.  But is a full router necessary in this case?

I would argue that very little router code needs to be added to the 
bridge to gain this functionality.  By adding static routing to our bridge
I believe we have met your needs.

>>packet.  In terms of delay, the packet gets to the remote end sooner with
>>compression, even if retransmission is necessary (assuming >2:1).
>This is an area I am not clear on (in fact the biggest problem in
>interoperability between isdn vendors seems to be how they implemnt the
>2 B channels).  I assume "bonding" is some sort of synchronized action
>between the channels?

Bonding makes one 128K channel by interleaving at the data stream bit level.
It is necessary to account for the different delays between  the B channels.
The alternative is to run LAPB multilink protocol.  But you are right.
There is no standard yet on multilink. 
  It seems like running them seperatly would be
>a good idea, excpet for the degenerate case of some app wanting an
>ack after each packet and thus not being able to make use of the
>higher performnce (since a single tcp/ip -> ethernet packet would go
>entirely onto one channel), but that a stupid app.

With bonding you only have one channel.  With some software running on top
of multilink, you can split the packet in pieces and load balance. 
Fragmentation in this case is not done like a router, but similar to the
more bit in X.25.

Xref: sparky comp.protocols.nfs:3201 comp.dcom.isdn:1216
From: jcurran@nic.near.net (John Curran)
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
Subject: Re: Low cost ether/isdn brouters (was PC-NFS PPP Serial/ISDN driver wanted)
Date: 22 Jan 1993 22:40:21 -0500
Organization: New England Academic and Research Network
NNTP-Posting-Host: nic.near.net

In article <1jnj4tINN1io@nigel.msen.com> emv@msen.com (Edward Vielmetti) writes:
>
>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...

I concur.  While there might be many unique applications that will require
ISDN speaking remote bridges, one existing market (internet service providers)
will be looking for low-end BRI router with demand-dial, filtering, and 
remote maintenance capabilities.  Given the maximum link speed, performance
will not be a distinguishing capability, and that means that low-cost will 
be a major feature of the market winner.

/John
Newsgroups: comp.protocols.nfs,comp.sys.sun.admin
From: bob@cwi.com (Bob Parker )
Subject: NFS automounter problems
Organization: CaseWare Inc.
Date: Tue, 26 Jan 1993 21:36:00 GMT

I posted this before, and got no response, but we were having problems
with our news system, so I'll try again in case it never went out...


Does anyone have an elegent solution to coexisting with the automounter?

We have a software product that does 'pwd' and getwd() and uses 
that path for various things, sometimes the path is even passed to 
programs on other machines.  This is fine if both machines have the path 
NFS mounted normally, but the automounter really throws a monkey wrench 
into things.  

Since the path returned by getwd() is the 'real' path, you get /tmp_mnt/...
for automounted directories.  Since we use the getwd() path, we don't access
the files thru the automounter mapped pathnames, so the automounter is not
aware that we are accessing files under it's control.  Since the automounter
unmounts the files after a period of inactivity, the path that worked fine
becomes invalid, possibly at very inopportune times.

It seems like we need something like getwd() but that gives us the path
that is controlled by the automounter (so the automounter knows that the
files are being accessed), rather than the 'real' path.
Is there such a beast?

Any other ideas?

Thanks in advance for any help.

-- 
=======================================================
||  Bob Parker       ||                              ||        
||  CaseWare, Inc    || The floggings will continue  || 
||  bob@cwi.com      ||    until morale improves!    || 
Xref: sparky comp.protocols.nfs:3170 comp.dcom.isdn:1189
From: johng@informix.com (John Galloway)
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
Subject: Inexpensive isdn/ether brouters (was Re: PC-NFS PPP Serial/ISDN driver wanted)
Date: 21 Jan 93 08:05:16 GMT
Organization: Galloway Research

In article <5daf63a9.1bc5b@pisa.citi.umich.edu> Jim.Rees@umich.edu writes:
>In article <1993Jan20.034052.912@informix.com>, johng@informix.com (John Galloway) writes:
>
>  Given the couple of extra items (like a LANCE chipe set, and the NT1)
>  an isdn/ethernet bridge should cost a bit more than a modem.
>
>Why?  The isdn bridge/gateway is a simpler device.  It doesn't do any dsp,
>and it shouldn't do error correction or compression (those belong in the
>transport layer).  So it should be cheaper.
agreed here, bag error correction and compresion.

I don't see it.  Maybe if you were starting from scratch for both designs,
but even then both ethernet and isdn are more complex interfaces than are
a serial port and an analog line.  I agree you should be able to do without
the DSP, but is the transistor count of a DSP+CPU+MEM+SERAIL modem
more than a CPU+MEM+LANCE+ISDN brouter?  (transistor count seemed like the
most easily quantifiable measure of "simpler").  Even if all compponents
had similar price advantages from equal mass production, I would still
expect the brouter to be a bit pricier than the modem.
 
On the other hand if you think you can build one for to sell for $250, I'll
not only buy one, but fund their production! (now if I could just find those
lottery tickets...$-)

	-jrg

internet    jrg@galloway.sj.ca.us  John R. Galloway, Jr  795 Beaver Creek Way
internet    johng@informix.com     CEO...receptionist    San Jose, CA   95133
applelink   D3413                  Galloway Research     (408) 259-2490



-- 
internet    jrg@galloway.sj.ca.us  John R. Galloway, Jr  795 Beaver Creek Way
internet    johng@informix.com     CEO...receptionist    San Jose, CA   95133
applelink   D3413                  Galloway Research     (408) 259-2490
Newsgroups: comp.protocols.nfs
From: jpc@avdms8.msfc.nasa.gov (J. Porter Clark)
Subject: Printing problems from LifeLine Mail
Organization: NASA/MSFC
X-Newsreader: NN version 6.4.19
Distribution: na
Date: 27 Jan 93 14:19:07 GMT

I have one (and only one) user with this combination:

  LifeLine Mail 2.0
  PC-NFS 4.0a
  DOS 5.0
  Windows 3.1
  Qualitas 386MAX 6.02
  Generic 386DX hardware
  3Com 3C503 and NDIS drivers

He typically doesn't use LifeLine Mail from inside Windows, although
RTM is loaded.  LPT3: is redirected to a QMS PS-810 which is connected
via SunTOPS to a Sun 670MP server running SunOS 4.1.3 and the latest
rpc.pcnfsd from bcm.tmc.edu.  LPT2: is redirected to a printer directly
attached to the same server.  LifeLine Mail is set to print using "net
print %s lpt3:".  Both printers are in "raw" mode and are flushed out
using the printer hot-key.

When he tries to print from inside LifeLine Mail, the machine locks up
almost immediately and has to be power-cycled to recover.  The print
data does in fact get to the server.  When I reconfigure to use LPT2:
instead of LPT3: the results are the same.  Printing from outside
LifeLine Mail does fine.

After fooling around with it awhile, I made a script called netprt3.bat
which essentially does a "net print %1 lpt3:".  I set up LifeLine Mail
to print using "netprt3 %s".  Strange as it may seem, this works.
Until a couple of days ago.  Nobody can remember doing anything to
either the PC or the server to affect the operation of the printers.
Printing from outside LifeLine Mail still works.

Now he gets this message:

  net print PB66978C lpt3:
	  Queueing file [PB66978C] ...
  NFS210F : Error on network printer (code 1022):

I looked up the NFS210F error code in the Reference Manual, and it says
to dismount and remount the printer.  Tried it, to no avail.  Went back
to "net print %1 lpt3:" and got hangs again.  At this point, I tried
using LifeLine Mail from inside Windows, then printing.  It didn't
hang, but it didn't print either.  In all these cases the print data
did get to the server.

Nobody else has problems printing from inside LifeLine Mail, and to the
same printer at that.  Then again, nobody else has the same exact
combination.

I don't know where these network printer error codes are documented.
Are they errno + some number?

I sure wish rpc.pcnfsd would syslog more diagnostics.  Anybody else
feel the same way?
--
J. Porter Clark    jpc@avdms8.msfc.nasa.gov or jpc@gaia.msfc.nasa.gov
NASA/MSFC Flight Data Systems Branch
From: jr@bioch.ox.ac.uk (Jeremy Rowntree)
Newsgroups: comp.protocols.nfs
Subject: PC-NFS pcnfslpd generates extra form feed!!
Date: 26 Jan 93 18:14:35 GMT
Organization: Department of Biochemistry, University of Oxford
Originator: jr@frege.bioch

We have a small non-Internet linked network of 9 PCs running Sun PC-NFS 4.0a 
and served by a Sun IPX. One PC is configured as a dedicated print spooler.

We are trying to convert an Epson FX-100+ dot matrix printer from a local 
LPT1: to a PCNFSLPD shared PC printer. When connected via the network, the 
print job works but it is followed by a Form Feed which is absent when the 
same application (FoxPro) prints to the same printer via a local port.

Since the application is used to print labels, the repeated form feeds are a 
problem since the loss of several lines of labels per job is unacceptable. 
The same print share PC also spools for an HP LaserJet IIID which also 
produces a blank page at the end of every job.

We do not have the "-x" option enabled on pcnfslpd and file does not appear 
to have been modified by its passage from PC to Sun to PC, as judged by 
comparing the spool file found in the C:\nfs\spool\lpt2 directory with the 
original. We are mounting the printer with the "/fmt=raw" option to NET USE.

Has anyone seen similar behaviour?

Does anyone have any insight into whether the PCNFSLPD program may be 
appending a form feed after it has sent the spool file to the printer?

Thanks for any help.

----------------------------------------------------------------------
Jeremy Rowntree                            | E-Mail: jr@bioch.ox.ac.uk
Deputy Computer Manager, Biochemistry Dept | Voice : +44 865 275270
University of Oxford, England. OX1 3QU     | FAX   : +44 865 275259
----------------------------------------------------------------------

Relevant Info:-

PC we are printing from is a
386SX running Dos 5 and PC-NFS 4.0a
c:\nfs\drives.bat contains

NET USE LPT1: cherwell:lb /fmt=raw

Unix Box is a
Sun IPX running SunOS 4.1.2 and pcnfsd v2, dated 12.10.92
/etc/pcnfsd.conf contains no printer information
/etc/printcap contains

s3|S3|hplaser|lp|Hewlett Packard IIID for DOS:\
        :lp=:rm=windrush:rp=LPT1:\
        :sd=/var/spool/s3:
lb|LB|labels|Epson FX-100+:\
        :lp=:rm=windrush:rp=LPT2:\
        :sd=/var/spool/lb:

Print share PC is a
386SX running Dos 5 and PC-NFS 4.0a
PCNFSLPD.INI contains

PRINTER LPT1: s3
PRINTER LPT2: lb
DEDICATED
-- 
----------------------------------------------------------------------
Jeremy Rowntree                            | E-Mail: jr@bioch.ox.ac.uk
Deputy Computer Manager, Biochemistry Dept | Voice : +44 865 275270
University of Oxford, England. OX1 3QU     | FAX   : +44 865 275259
Newsgroups: comp.protocols.nfs