From owner-freebsd-questions  Wed Dec 24 15:22:21 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA08337
          for questions-outgoing; Wed, 24 Dec 1997 15:22:21 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from gdi.uoregon.edu (cisco-ts12-line10.uoregon.edu [128.223.150.142])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA08329
          for <freebsd-questions@FreeBSD.ORG>; Wed, 24 Dec 1997 15:22:16 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id PAA10212;
          Wed, 24 Dec 1997 15:22:09 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Date: Wed, 24 Dec 1997 15:22:09 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Chris Sagar <csagar@iterated.com>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: network problems
In-Reply-To: <349FF1A3.2169@iterated.com>
Message-ID: <Pine.BSF.3.96.971224152127.10003c-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 23 Dec 1997, Chris Sagar wrote:

> I have installed ver. 2.2.5 on IBM Thinkpad using 3C589D PCMCIA card. 
> I am using the Thinkpad as a server for a Dec Network Computer. I have a
> similar setup using Gateway 486/66DX2 as server and it works flawlessly. 
> However, my Thinkpad has network connectivity problems serving files to
> the NC. The NC uses TFTP to download boot image, then uses NFS to access
> root and usr filesystems on Thinkpad. TFTP seems to be OK, but NFS part
> flakes out. I get the following errors:
> 
> /kernal: nfsd send error 55
> (repeated many times)
> 
> Also, pinging other UNIX boxes on my network gets this error:
> ping: sendto: No buffer space available

Hm.  Check your routing, the packets are getting stalled out trying to
figure out where to go.

You should have a default route pointing at your router or gateway.  That
should take care of it.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major