[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Odd Networking problem



on Tue, May 15, 2001 at 05:10:24AM -0700, Hamma Scott (scott_hamma@yahoo.com) wrote:
> --- "Karsten M. Self" <kmself@ix.netcom.com> wrote:
> > on Sun, May 13, 2001 at 04:33:12PM -0400, Sunny
> > Dubey (dubeys@voyager.bxscience.edu) wrote:
> > > Hi, 
> > > 
> > > I've got a bunch of computers on my network here, and I've got one
> > > really odd problem.
> > > 
> > > For some odd reason, its takes _forever_ for me to connect to
> > > another computer.  If I try to ssh from one to another, it will
> > > take me about a minute just to make the connection, and for some
> > > odd reason everything is fine afterwards. (this applies to just
> > > about any service, ftp, httpd, etc)
> > > 
> > > Anyone have any ideas as to why this happens?
> > > Thanks
> > > 
> > > Sunny Dubey
> > 
> > Disable reverse DNS lookups (not sure how to do this) or straighten
> > out your local DNS server.
> > 
> > I recently got the kinks worked out of a locally-run DNS server
> > (caching for the world, authoritative for the LAN plus a few
> > favorite ad-serving sites).  Once I got that all ironed out, both
> > internal (LAN-to-LAN) and external lookups got a lot faster.

> I'm pretty new to this whole GNU/Linux thing, but when I had my
> ethernet card enabled on my motherboard, it was pausing for a long
> time before it timed out. Is there any service that is timing out on
> you or a service your system expects, but isn't there?

Please:

  - Reply to list mail on list.  Response to list, Reply-to set to list.
    This is for your good, not mine.  Your liable to get a faster, more
    accurate response from the list.  This reply's been sitting at the
    bottom of a stack of rxvt's all day.

  - Post your reply below quoted material.

  - Fix your line wrap.  64 - 72 characters is generally acceptable,
    indicated by rules below.

----------------------------------------------------------------
------------------------------------------------------------------------

At what point in boot is the card timing out?  Is it during the initial
boot phase and detection, usually accompanied by a line or lines similar
to:

    Linux NET4.0 for Linux 2.2
    Based upon Swansea University Computer Society NET3.039
    NET4: Unix domain sockets 1.0 for Linux NET4.0.
    NET4: Linux TCP/IP 1.0 for NET4.0
    Initializing RT netlink socket

...or is it at some point later when services start?

If the former, you're going to want to change module or autoprobe
behavior.  If the lattter, you're going to want to look at your SysV
init scripts and disable the misbehaving service.

Cheers.

-- 
Karsten M. Self <kmself@ix.netcom.com>    http://kmself.home.netcom.com/
 What part of "Gestalt" don't you understand?       There is no K5 cabal
  http://gestalt-system.sourceforge.net/         http://www.kuro5hin.org

Attachment: pgpZiiHX6l0Bz.pgp
Description: PGP signature


Reply to: