To elaborate on the type of problems that we are experiencing,  
     netstat will take about 1/2 hour to an hour to complete for about 10 
     machines and one router.  TCP/IP sessions to our Sun DNS box always 
     fail, even though a route exists in the netstat.  However, it will 
     succeed to Linux, WinNT, and Win95 inside our sub-net.
     
     Kelly R. Bauman
     UW--Madison
     Academic Services LAN Administration


______________________________ Reply Separator _________________________________
Subject: Re: NetBSD and Sun OS 4.0.2
Author:  behind brown eyes <benji@haven.boston.ma.us> at IPNET
Date:    8/28/96 3:00 PM


According to Kelly BAUMAN:
>      We've got a Sun360 running NetBSD.  However, it doesn't seem to want 
>      to communicate with any Sun workstation either outside or inside of 
>      our sub-net.  Specifically, we want to use the 360 as a backup name 
>      server to our main name server, a Sun386i running SunOS 4.0.2.  Has 
>      anyone experienced similar problems, and how did you fix it?  Also, we 
>      seem to be getting very poor network access time.  Is this normal for 
>      a 360 running on the thin-net connection? Thanks in advance.
>      
Using a NetBSD box as a name server should work just fine, both my name 
servers here are NetBSD systems (albeit SPARCstations, and not 3/60s). Could 
you elaborate on what kind of problems your having, and what you mean when 
you say it "doesn't seem to want to communicate with any Sun workstation"?
     
I've got a 3/60, but I haven't put NetBSD on it yet, but I wouldn't expect 
it to have poor network access time. 
     
 benji
     
-- 
Benjamin R. Cline Large Furry Mammal  benji@haven.boston.ma.us
"No wrong, no right, I'm gonna tell you there's no black and no white, no 
 blood, no stain, all we need is one world wide vision. One flesh, one bone, 
 one true religion, one voice, one hope, Wowowowo gimme one vision." -- Queen