randy@ux1.cso.uiuc.edu (06/12/90)
I'm cross posting here from comp.protocols.nfs in hopes of reaching a
wider interested audience...
/* Written 1:47 am Jun 12, 1990 by randy@ux1.cso.uiuc.edu in ux1.cso.uiuc.edu:comp.protocols.nfs */
/* ---------- "PC-NFS and Novell revisited" ---------- */
Hello all,
I sent out a note yesterday regarding running PC-NFS and Novell con-
currently. Basically, I couldn't get it to work, though one is
"supposed to" be able to get it to work using Geoff Arnold's latest
pktd.sys driver that allows for PC-NFS to use the packet driver *and*
allows concurrent Novell access. I spent hours upon hours testing out
different setups, but haven't yet succeeded. I have heard rumours that
it *has* been done, and I'm sure Geoff has done it at least once 8-}.
This would be a very nice setup for me to be able to backup our Novell
servers to an optical disk NFS exported from our NeXT machine. The idea
is NFS mount the optical disk on the NeXT as drive g: or something and
then mount the Novell volume as drive h:, say. Then you use pkzip to
archive the Novell volume to the optical disk by typing "pkzip -arp
-whs h:\*.* g:\server.zip", and away you go, no messy cumbersome tapes,
no waiting around to flip cartridges, etc (you could use tar too). Not
to mention that it's a zero cost solution. Here are the details of my
travails using an ni5010 card in an AT... Geoff, are you listening?
This is a detailed bug report. Does anyone have any tips? There are
more comments after this lengthy report.
---------------------------------------------------------------------------
PC-NFS v 3.0
(side question: If it's 3.01, does it say so on the package? or is that an
update that's shipped seperately? what's the difference between 3.0 and
3.01 anyway?)
ni5010 card.
interrupt:3
i/o address:0x340
config.sys:
shell=c:\command.com /e:1024/p
buffers=37
files=20
device=ansi.sys
device=c:\nfs\pcnfs.sys /m
device=c:\nfs\sockdrv.sys
device=pktd.sys
autoexec.bat:
echo off
cls
set TZ=CST6CDT
ni5010 0x60 3 0x340
set nfsdrive=c
\nfs\network
\nfs\network.bat:
net start rdr mrc2 * (mrc2 is the PC's name)
net subnet 255.255.255.0 (we are on a class B subnet)
net route gw (gw is our gateway)
===========================================================================
case 1:
packet driver v6.0
pktd.sys dated May 24, 1990 (size:8619) from sun.soe.clarkson.edu in
~ftp/pub/packet-drivers:
behavior: Crash at boot-time during device driver installation.
===========================================================================
case 2:
Same situation as above, this time using a previous pktd.sys dated Aug 7, 1989
(size:4928), originally from sun.soe.clarkson.
behaviour: machine boots ok, but.....
nfsping of known nfs server (mrcnext) results in:
NO answer from mrcnext
ftp connection to known ftp server mrcnext results in:
ftp: connect: Unknow error.
telnet connection to know telnet server mrcnext results in:
NFS104F: telnet: Unable to open connection
mount attempt of known exported file system ("net use g: \\mrcnext\micro")
results in:
NFS036F : Server mrcnext is not responding.
NFS008F : Drive g: has not been mounted.
==============================================================================
case 3:
Same situation as case 2, using yet another version of pktd.sys dated
Feb 21, 1990 (size:5264), from sun.soe.clarkson.edu in
~ftp/pub/packet-drivers/pktd.tar.Z (dated March 27, 1990: size:56135)
behavior is precisely the same as in the previous case.
==============================================================================
case 4:
Now, using case 3 configuration, but with ni5010 packet driver v5.0 instead
of v6.0....
nfsping mrcnext:
mrcnext is alive!
ftp functions normally.
telnet functions normally.
"net use g: \\mrcnext\micro" crashes the machine hard (forces power down).
=============================================================================
case 5:
now, switching back to the Aug. 7, 1989 pktd.sys, leaving the packet driver
version at 5.0...
nfsping mrcnext:
mrcnext is alive!
ftp functions normally.
telnet functions normally.
"net use g: \\mrcnext\micro" mounts our NeXT on drive g: like a charm.
=============================================================================
Now, as you can see, I *have* been able to get PC-NFS to work via packet-
driver, but only with an old version of pktd.sys that doesn't support
concurrent use of Novell packets. What's a net admin to do?
Does anyone have any pointers on how I can get this to work? Has anyone
got it to work with a different card, say, an ni5210, an ni9210, a wd8003e
or wd8003eb, a 3c501, a 3c523, an NE1000 or NE2000? If I could get it to
work with any one of these cards, I would be truly happy for the rest of
the week (that's saying a lot, believe me).
Till later..
Randy Cotton
Computing Services Office
University of Illinois at Urbana/Champaign.
/* End of text from ux1.cso.uiuc.edu:comp.protocols.nfs */