Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!newspump.sol.net!howland.erols.net!feed1.news.erols.com!netaxs.com!socko.cdnow.com!heller From: heller@socko.cdnow.com (A. Karl Heller) Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.solaris Subject: Re: named/Connection lags on Solaris.. Followup-To: comp.unix.bsd.freebsd.misc,comp.unix.solaris Date: 16 Oct 1996 17:52:24 GMT Organization: CDnow - The World's Largest Online Music Store http://cdnow.com Lines: 44 Distribution: inet Message-ID: <5437co$29h@netaxs.com> References: <540rpq$rhj@netaxs.com> <54133m$2fa@news1.radix.net> Reply-To: heller@cdnow.com NNTP-Posting-Host: socko.cdnow.com X-Newsreader: TIN [version 1.2 PL2] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:29360 comp.unix.solaris:86087 Lamar Hall (lsh@radixii.com) wrote: : In article <540rpq$rhj@netaxs.com>, : heller@socko.cdnow.com (A. Karl Heller) wrote: : : : : Strange topic to post here but its related... trust me.. : : : : : :I've got a Solaris 2.5.1 box that is running as a secondary name server : :to a FreeBSD 2.1.5 box primary name server. : : : : I'm experiencing connection lags to and from the solaris box to other : :machines. The connection eventually will go through but will sit for : :a very long time before connecting. It is also random ( or so ) and I : :can't reproduce it other than when someone screams why they can't get to : :some machine. : You might want to check if your system is running nscd (name service cache : daemon). We had name server problems when this was running on our system. I just did a ping -v from the bsd box to any other machine on the network and I get this: 64 bytes from solaris: icmp_seq=1 ttl=255 time=0.612 ms 64 bytes from solaris: icmp_seq=2 ttl=255 time=0.420 ms 81 bytes from solaris: Destination Port Unreachable Vr HL TOS Len ID Flg off TTL Pro cks Src Dst Data 4 5 00 0049 4a44 0 0000 40 11 f6d2 bsd solaris UDP: from port 53, to port 35819 (decimal) And this repeats... all the time. What is going on here? Is there a major bug in the networking code? ( doubtfull ) If I do a ping -v localhost I get the same messages but its only from bsd to solaris that the ports are unreachable. Even stranger is that sometimes the dst data is not to a local machine but to some IP out there on the internet that it can't reach. Do I need to tune something on the bsd side? Again, thanx for all the email responses.. I'm trying all of them. Karl