[Cialug] Network slowness

[Tom Sellers]

Not too basic in my opinion.  I am open to all suggestions.

The command you gave below does not seem to take as long as pings do.

Here is my resolv.conf
---------------------------------------------------------------------
# generated by NetworkManager, do not edit!

search globalccs.net


nameserver 69.63.8.74
nameserver 69.63.8.73

---------------------------------------------------------------------
and here is the result of a traceroute to google.


traceroute to www.l.google.com (74.125.95.103), 30 hops max, 40 byte packets
 1  10.1.1.254 (10.1.1.254)  14.228 ms  14.927 ms  15.992 ms
 2  ins-border11-ds1.kmrr.netins.net (167.142.64.9)  17.559 ms  13.184 ms  22.756 ms
 3  ins-h1-et-1-5-121.kmrr.netins.net (167.142.57.121)  32.231 ms  11.087 ms  16.443 ms
 4  ins-h2-et-1-20-130.desm.netins.net (167.142.57.114)  11.340 ms  16.785 ms  12.882 ms
 5  ins-c2-et-pc2-0.desm.netins.net (167.142.57.142)  16.415 ms  17.260 ms  23.399 ms
 6  gi1-1.ccr01.dsm01.atlas.cogentco.com (38.104.184.5)  23.633 ms  31.157 ms  24.366 ms
 7  te9-7.ccr01.ord01.atlas.cogentco.com (154.54.0.77)  23.254 ms  28.793 ms  33.948 ms
 8  te8-2.mpd01.ord03.atlas.cogentco.com (154.54.25.66)  26.764 ms vl3488.mpd01.ord03.atlas.cogentco.com (154.54.5.26)  46.530 ms te8-2.mpd01.ord03.atlas.cogentco.com (154.54.25.66)  20.376 ms
 9  google.ord03.atlas.cogentco.com (154.54.12.130)  23.834 ms  28.660 ms  20.499 ms
10  209.85.254.120 (209.85.254.120)  22.452 ms  30.384 ms  34.873 ms
11  209.85.241.22 (209.85.241.22)  39.512 ms  33.040 ms  90.571 ms
12  209.85.241.37 (209.85.241.37)  44.844 ms  39.225 ms 209.85.241.29 (209.85.241.29)  46.007 ms
13  209.85.240.45 (209.85.240.45)  42.560 ms  49.063 ms 72.14.239.193 (72.14.239.193)  58.871 ms
14  iw-in-f103.google.com (74.125.95.103)  56.835 ms  36.245 ms  38.277 ms
tsellers at bluto:~$



--- On Mon, 2/2/09, Jeff Chapin <chapinjeff at gmail.com> wrote:

> From: Jeff Chapin <chapinjeff at gmail.com>
> Subject: Re: [Cialug] Network slowness
> To: "Central Iowa Linux Users Group" <cialug at cialug.org>
> Date: Monday, February 2, 2009, 8:18 PM
> Forgive me for asking the obvious, but does nslookup return
> quickly?
> 
> $time nslookup www.yahoo.com
> 
> If this is slow, double check the file /etc/resolv.conf. It
> should have
> something like:
> $ cat /etc/resolv.conf
> # Generated by NetworkManager
> nameserver 192.168.1.1
> 
> only with the IP of your nameserver. I would compare to the
> settings on
> your windows box (*shudder*). If that file looks fine, I
> would go back
> to nslookup and test each nameserver and see if one is slow
> or timing out.
> 
> I would also try something like :
> $ traceroute www.yahoo.com
> and see if there are any particularly slow hops. Your name
> server may
> also be a good IP to traceroute ;-)
> 
> Again, forgive me if this is too basic, I would rather
> start with the
> 'obvious' though.
> 
> 
> Tom Sellers wrote:
> > I was wondering if anyone had experienced a problem
> such as this.
> >
> > When I ping a site such as www.yahoo.com it takes
> several seconds  for it to resolve.  This is true from the
> laptop that I have loaded with Debian, but if I perform the
> same ping function from a Windows workstation it responds
> almost immediately.  If I ping the IP address for
> www.yahoo.com directly from the Debian machine it responds
> quickly just as the Windows machine did while pinging by
> name.  
> >
> > I am connected to the network by an ethernet cable,  
> >
> > Is this some issue with the network setup of the
> Debian machine?  
> >
> > I found some information that indicated that being
> setup with IPV6 can cause such an issue.  I am not sure what
> the default setup for Debian 4.0 is.  
> >
> > Any thoughts or suggestions?
> >
> > The machine seems to be funtioning normally other than
> for the fact that name resolution takes exceptionally long.
> >
> >
> >       
> > _______________________________________________
> > Cialug mailing list
> > Cialug at cialug.org
> > http://cialug.org/mailman/listinfo/cialug
> >   
> 
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug