Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!agate!bionet!csd4.milw.wisc.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!phri!roy
From: roy@phri.UUCP (Roy Smith)
Newsgroups: comp.protocols.nfs
Subject: Problems with PC-NFS
Message-ID: <3650@phri.UUCP>
Date: 13 Jan 89 16:19:09 GMT
Organization: Public Health Research Institute, NYC, NY
Lines: 31


	We've recently gotten PC-NFS runnng on a PC-AT and have noticed a
couple of problems.  One is that when I run NFSRUN, when it gets up to the
"NET START RDR", it hangs for a few seconds and then I get:

	Cannot send broadcast packet: unknown error
	NFS028W: unable to find a YP server for domain PHRI
	net: unable to get hostname by IP addr (128.122.136.101)

	The odd thing is that it then procedes to run through the rest of
the NFSRUN script and when it's done (almost) everything appears to work
just fine.  YP is obviously working since it's able to resolve hostnames
without any problem (and without a local hosts file).  NFS, Telnet, and NET
PRINT all work too.

	The second problem is that I can't seem to reliably talk to my Mt
Xinu 4.3BSD/NFS Vax using NFS.  I can mount a file system from the vax and
access it doing simple things (i.e. I can cd to it, do ls and cat, and copy
small files from the PC to the vax) but if I try to write a large (i.e.
Mbyte) file it eventually hangs.  I've never seen any problems with file
systems mounted from a Sun (SunOS-3.5.2) server.  The only thing I can
think of is that the vax has a problem with dealing with large block sizes.
All our suns mount the vax file systems with (rsize=2048,wsize=2048).  Is
it possible that I'm seeing the same problem with PC-NFS?  Is there any way
to change the block size PC-NFS uses?  Somehow, the idea of a PC sending
data too fast for a vax doesn't sound right, but that's all I can think of.
-- 
Roy Smith, System Administrator
Public Health Research Institute
{allegra,philabs,cmcl2,rutgers}!phri!roy -or- phri!roy@uunet.uu.net
"The connector is the network"