[mdlug] Network Slowdown Troubleshooting/Netgear WNDR3700 Free To Good Home

[Peter Bart]

On Sat, 26 Nov 2011 12:49:18 -0500
Stan Green <Stan at mcomputersolutions.com> wrote:

> I don't think you have a latency issue ( See for more on latency: 
> http://en.wikipedia.org/wiki/Latency_(engineering)

	I did look before I posted, but it doesn't make a lot of sense
	yet.
> 
> Also, I'm not clear on what you mean by "my router would stop the
> downloads". The router only knows packets, it does not know what is a
> download and what is an email. (Other than they are on different
> ports.) It is the client program that is performing the download. It
> may timeout if it is not getting a response from the server.

	Ok, I'm guessing it's a timeout issue. What happens is the
	packets are happily coming to me at a good rate as indicated by
	the various browsers I tried. Then the rate slows and stops
	dead. Also I get a lot of timeout complaints from Claws mail.
	This happens when I connect wirelessly, to the router and to
	the switch. 
> 
> Since all is fine when you plug into the modem directly, this would
> suggest the DSL is fine. You stated you have a router and a switch,
> so did you try plugging directly into the router? If that works fine,
> then the issue may be your switch.  If plugging directly into the
> router show the same download issue, I would suspect the router is
> the issue.  You can test the switch my pluggin it directly into the
> modem.  If plugging directly into the router show the same download
> issue, I would suspect the router is the issue. 

	I agree. My setup is the modem first, then the router and then
	the switch. Plugging into the switch yields the same result a
	plugging into the router because the switch itself is plugged
	into the router. I have not tested plugging the switch into the
	modem. I think I found at least one problem with my router, so
	I'm going to try and narrow it down from there. I have an old
	Linksys that was good when I stored it, I'm going to put it
	back as my main router and see what happens.
> 
> The bottom line is good troubleshooting is about isolating to smaller
> components in order to find the one that is not working.
> 
> HTH
> Stan
> 
	I agree again. I've done most of what you suggest, it does help
	thanks. The new Netgear router I have has known issues, I went
	a little to close to the bleeding edge with that one.
-- 
Best Regards,

Peter The Plumber
<petertheplumber at att.net>