slow internet connections
in [Setup]
|
Prev: FTP Setup
Next: ESX hardware configuration
From: The Natural Philosopher on 14 Apr 2010 07:40 Nico Kadel-Garcia wrote: > On Apr 14, 4:43 am, Matt Giwer <jul...(a)tampabay.rr.com> wrote: >> On 04/13/2010 10:07 PM, GrailKing wrote: >> >>> I have extremely slow cable connections, Comcast sent a tech but all he >>> did was replace the modem and check levels at the GB. >>> I ping my router, local host all computers connected to the router and >>> all the pings come back the pings ranged from .05 ms for LH to 15 ms for >>> the computers connected to the router. >>> I ping the primary DNS and I get real long wait periods for the pings to >>> come back with any where from 2 to for packets not returned, I ping >>> different sites: cnn, fox, astra news and they all come back with lost >>> packets and long times. >>> 1. what else can I check on my end? >>> 2. Is this a problem in the main lines and ComCast has to come back? >> Annoying problems are they not? >> >> The one thing you have not checked is your router for outbound connections. I >> have no idea how routers are designed but worth checking simply as a standard >> trouble shooting procedure. Can you borrow one from a neighbor? >> >> Also to check, is modem you were given new or an old model? I do not see it >> losing packets no matter how old but a defective spare the serviceman carried >> is not out of the question. So can you borrow the neighbor's modem also? >> >> Actually losing packets is the mystery. >> >> If you can get the CNN numerical address, ping that instead. That will >> eliminate the DNS computer. Is that dig? I haven't done this in a while. If >> the number works the server is the problem. >> >> Looking at the man page try -w and -W to see if the packets will return >> eventually. Slow is not lost. I have no idea what to do with this information >> but it is a data point. >> >> Did you show the visiting technician the problem? Why not? He should have had >> a router as part of his trouble shooting inventory. > > Comcast is infamous, in my book for a number of fascinating issues. > One is trying the easy fix that's on the top of the list of > procedures, seeing that it passes their diagnostics, and assuming > they're done. Another is ignoring reports of intermittent problems and > assuming that because it works during their test, it was working > earlier. Another is that they've bought up a lot of smaller ISP's and > cable companies over the years, and wound up with weird mish-moshes of > equipment, some of which is hard to test or monitor. > > That said, I wonder if your entire home network is zombie and virus > free. Can you test with one machine on your home network turned on at > a time, and be sure that this occurs for all of them individually? One > machine running Bittorrent quietly in the background can suck a *lot* > of bandwidth, and it's easy not to notice. The other classic is to be using an MTU that breaks some routers in the link between you and the target. Or some giant windows that do similar. try setting MTU to something really low like 512bytes, and check on 'giant frame' issues with some Linux implementations. There has been a tendencey for Linux to assume the internet actually conforms to TCP/IP specifications. Large parts of it do not, and are arguably broken and should be fixed, however this is of little consolation to those condemned to use them.
From: Sidney Lambe on 14 Apr 2010 07:47 On comp.os.linux.setup, Matt Giwer <jull43(a)tampabay.rr.com> wrote: > On 04/13/2010 10:07 PM, GrailKing wrote: > >> I have extremely slow cable connections, Comcast sent a tech >> but all he did was replace the modem and check levels at the >> GB. I ping my router, local host all computers connected >> to the router and all the pings come back the pings ranged >> from .05 ms for LH to 15 ms for the computers connected to >> the router. I ping the primary DNS and I get real long wait >> periods for the pings to come back with any where from 2 >> to for packets not returned, I ping different sites: cnn, >> fox, astra news and they all come back with lost packets and >> long times. 1. what else can I check on my end? 2. Is this a >> problem in the main lines and ComCast has to come back? > > Annoying problems are they not? > > The one thing you have not checked is your router for outbound > connections. I have no idea how routers are designed but worth > checking simply as a standard trouble shooting procedure. Can > you borrow one from a neighbor? > Why not just connect a computer directly to the cable modem, bypassing the router? If the router is the problem they'll vanish... [delete] Sid
From: GrailKing on 14 Apr 2010 15:17 On Wed, 14 Apr 2010 04:43:52 -0400, Matt Giwer wrote: > On 04/13/2010 10:07 PM, GrailKing wrote: >> I have extremely slow cable connections, Comcast sent a tech but all he >> did was replace the modem and check levels at the GB. I ping my >> router, local host all computers connected to the router and all the >> pings come back the pings ranged from .05 ms for LH to 15 ms for the >> computers connected to the router. I ping the primary DNS and I get >> real long wait periods for the pings to come back with any where from 2 >> to for packets not returned, I ping different sites: cnn, fox, astra >> news and they all come back with lost packets and long times. >> 1. what else can I check on my end? >> 2. Is this a problem in the main lines and ComCast has to come back? > > Annoying problems are they not? > > The one thing you have not checked is your router for outbound > connections. I > have no idea how routers are designed but worth checking simply as a > standard trouble shooting procedure. Can you borrow one from a neighbor? > > Also to check, is modem you were given new or an old model? I do not > see it > losing packets no matter how old but a defective spare the serviceman > carried is not out of the question. So can you borrow the neighbor's > modem also? > > Actually losing packets is the mystery. > > If you can get the CNN numerical address, ping that instead. That will > eliminate the DNS computer. Is that dig? I haven't done this in a while. > If the number works the server is the problem. > > Looking at the man page try -w and -W to see if the packets will return > eventually. Slow is not lost. I have no idea what to do with this > information but it is a data point. > > Did you show the visiting technician the problem? Why not? He should > have had > a router as part of his trouble shooting inventory. He was over my shoulder, I can get a spare router from work. been a long time since I had to deal with this stuff.
From: GrailKing on 14 Apr 2010 21:26 On Wed, 14 Apr 2010 13:47:20 +0200, Sidney Lambe wrote: > On comp.os.linux.setup, Matt Giwer <jull43(a)tampabay.rr.com> wrote: > >> On 04/13/2010 10:07 PM, GrailKing wrote: >> >>> I have extremely slow cable connections, Comcast sent a tech but all >>> he did was replace the modem and check levels at the GB. I ping my >>> router, local host all computers connected to the router and all the >>> pings come back the pings ranged from .05 ms for LH to 15 ms for the >>> computers connected to the router. I ping the primary DNS and I get >>> real long wait periods for the pings to come back with any where from >>> 2 to for packets not returned, I ping different sites: cnn, fox, astra >>> news and they all come back with lost packets and long times. 1. what >>> else can I check on my end? 2. Is this a problem in the main lines and >>> ComCast has to come back? >> >> Annoying problems are they not? >> >> The one thing you have not checked is your router for outbound >> connections. I have no idea how routers are designed but worth checking >> simply as a standard trouble shooting procedure. Can you borrow one >> from a neighbor? >> >> > Why not just connect a computer directly to the cable modem, bypassing > the router? If the router is the problem they'll vanish... > > [delete] > > Sid I did that but forgot to mention it, I was running at 2mbs this afternoon and now at 8pm it's a crawl and I'm dropping packets to the primary and secondary DNS this is looking like a broken stinger or short connector in the lines, I'm changing the outside connectors and GB tomorrow and will see what happens tomorrow night. GK
From: Sidney Lambe on 14 Apr 2010 22:24
On comp.os.linux.setup, GrailKing <grailking(a)invalid.net> wrote: > On Wed, 14 Apr 2010 13:47:20 +0200, Sidney Lambe wrote: > >> On comp.os.linux.setup, Matt Giwer <jull43(a)tampabay.rr.com> >> wrote: >> >>> On 04/13/2010 10:07 PM, GrailKing wrote: >>> >>>> I have extremely slow cable connections, Comcast sent a tech >>>> but all he did was replace the modem and check levels at the >>>> GB. I ping my router, local host all computers connected >>>> to the router and all the pings come back the pings ranged >>>> from .05 ms for LH to 15 ms for the computers connected to >>>> the router. I ping the primary DNS and I get real long wait >>>> periods for the pings to come back with any where from 2 >>>> to for packets not returned, I ping different sites: cnn, >>>> fox, astra news and they all come back with lost packets and >>>> long times. 1. what else can I check on my end? 2. Is this a >>>> problem in the main lines and ComCast has to come back? >>> >>> Annoying problems are they not? >>> >>> The one thing you have not checked is your router for >>> outbound connections. I have no idea how routers are designed >>> but worth checking simply as a standard trouble shooting >>> procedure. Can you borrow one from a neighbor? >>> >> >> Why not just connect a computer directly to the cable modem, >> bypassing the router? If the router is the problem they'll >> vanish... >> >> [delete] >> >> Sid > > I did that but forgot to mention it, I was running at 2mbs this > afternoon and now at 8pm it's a crawl and I'm dropping packets > to the primary and secondary DNS this is looking like a broken > stinger or short connector in the lines, I'm changing the > outside connectors and GB tomorrow and will see what happens > tomorrow night. > > GK It's probably irrelevant, but I have been noticing a _lot_ of brief DNS lookup failures lately. For the last couple of weeks. Luck, Sid |