View Single Post
Unread 05-11-2016, 04:59 PM   #44
mrerick
Super Moderator - Patron
LugerForum
Life Patron
 
mrerick's Avatar
 
Join Date: Dec 2009
Location: Eastern North Carolina, USA
Posts: 3,900
Thanks: 1,372
Thanked 3,094 Times in 1,503 Posts
Default

From MarkBritt's post, it looks like something is getting lost withing the ISP's infrastructure at John D.'s end failing between their last router and John's premises.

When things work:

15 113 ms 118 ms 115 ms fttp07-pos0-0.cncdnh.fast.myfairpoint.net [64.222.166.71]
16 66 ms 61 ms 64 ms static-72-71-199-44.cncdnh.fast07.myfairpoint.net [72.71.199.44]

When things fail:

12 54 ms 53 ms 54 ms fttp07-pos1-0.cncdnh.fast.myfairpoint.net [64.222.166.111]
13 * * * Request timed out.

John , what kind of connectivity do you have to your ISP? It looks like Fairpoint provides a DSL connection?

Is your gateway/router showing high levels of Forward Error Correction (FEC) on it's status page?

It's possible that moisture or some other damage is increasing the signal to noise ratio and causing lost packets on the link from the DSlam to your gateway device (if DSL). With DSL the distance to the DSLAM makes a difference sometimes with reliability.

You can connect direct to these devices from within your internal network. Most have a "Status" page for the wide area network connection.

If you see high noise levels or high error levels, the ISP can and should repair this.

Marc
__________________
Igitur si vis pacem, para bellum -
- Therefore if you want peace, prepare for war.

Last edited by mrerick; 05-11-2016 at 07:36 PM.
mrerick is offline   Reply With Quote