Subject: Re: What acts like an interupt problem...
To: None <netbsd-help@netbsd.org>
From: Christos Zoulas <christos@zoulas.com>
List: netbsd-help
Date: 11/24/1998 21:51:36
In article <wmn25gn94v.fsf@vyro-ingo.mesas.com> mhat@fundsxpress.com (Matt Knopp) writes:
>
>Okay.. To setup the problem: 
>
>I have two machines, the MB is by Asus (P2B), P2/350, 64M Ram, UDMA Disk, 
>4M Matrox Myst., a 10/100 Kingston (Dec chip), and a isa soundcard. 
>
>I have to use -current, because I need UVM. The BIOS configs for both machines
>are exactly the same. One machine had 1.3.2 installed on it, the other has 
>1.3H (the 'a' snap I got yesterday). Previous to that it was -current from 
>a month or so ago. They are both using a 1.3I kernel at the moment. 
>
>The problem is that the 1.3.2 box is the only one that can ever see the net. 
>Well thats not exactly correct, the 1.3.2 box is the only one that can do 
>anything more then arp. If i try to ping something from the -current box, 
>it waits ~60secords and then is able to ping that site (like its waiting for
>an interupt to clear). Oh, and did I mention that the -current machine was
>previously working just fine, but "stopped" when we moved, and no, the 
>hardware isnt damaged. (I'll get to that.) 

Actually it could be just that your dns is screwed up. 
Try 'ping -n ip-address'

christos