<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>TWGandalf, a response in Charter HSI/CATV</title>
<link>http://www.dslreports.com/forum/r8542117</link>
<description></description>
<language>en</language>
<pubDate>Fri, 27 Nov 2009 14:05:23 EDT</pubDate>
<lastBuildDate>Fri, 27 Nov 2009 14:05:23 EDT</lastBuildDate>

<item>
<title>Re: TWGandalf, a response</title>
<link>http://www.dslreports.com/forum/remark,8543131</link>
<description><![CDATA[<A HREF="/useremail/u/900178"><b>bigbearr</b></A> : Yeah, that looks ok. From the troubleshooting you have already done, I didnt think it was your signal.<br><br>I dont know what all you have accumulated, but the infro from the previous traceroute/post and what I had done, it seems it is ATT, not charter, causing the problem. But you may have more info avalible to you.<br><br>If you are having trouble with the call center, you may need to escalate your case further up the chain until someone recognizes or states the problem they are having. Im sure you are not the only one.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,8543131</guid>
<pubDate>Tue, 18 Nov 2003 23:27:30 EDT</pubDate>
</item>

<item>
<title>Re: TWGandalf, a response</title>
<link>http://www.dslreports.com/forum/remark,8543005</link>
<description><![CDATA[<A HREF="/useremail/u/900883"><b>TWGandalf</b></A> : Dumb Dumb me. I found it. I followed the link you kindly put in your post. LOL!<br><br>Downstream  Value <br>Frequency 555000000 Hz Locked <br>Signal to Noise Ratio 37 dB <br>QAM 64 <br>Network Access Control Object ON <br>Power Level 11 dBmV The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading  <br> <br><br>Upstream  Value <br>Channel ID 3 <br>Frequency 23984000 Hz Ranged <br>Ranging Service ID 180 <br>Symbol Rate 2.560 Msym/s <br>Power Level 47 dBmV  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,8543005</guid>
<pubDate>Tue, 18 Nov 2003 23:14:49 EDT</pubDate>
</item>

<item>
<title>Re: TWGandalf, a response</title>
<link>http://www.dslreports.com/forum/remark,8542988</link>
<description><![CDATA[<A HREF="/useremail/u/900883"><b>TWGandalf</b></A> : Thank You for starting a new thread. Yes, it is the Kingsport area that is in Charters domain. At hop 5 is where all my problems always begin. I have got lots of saved trace routes to show that saved. I have been keeping a Charter Log on Word for the past 2 months. Saving all the goodies because when I do get hold of tech support on the phone they deny it like anything or just say we are experiencing temporary difficulties. 2 months is way more than "temporary" difficulties.<br>I do not know how to do a signal strength test. Could you please explain to me how to do that.<br>I would love to be able to play MOHAA again on my server that I pay for.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,8542988</guid>
<pubDate>Tue, 18 Nov 2003 23:12:02 EDT</pubDate>
</item>

<item>
<title>Re: TWGandalf, a response</title>
<link>http://www.dslreports.com/forum/remark,8542531</link>
<description><![CDATA[<A HREF="/useremail/u/507346"><b>sparky9</b></A> : It's what you might call an overloaded network lol.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,8542531</guid>
<pubDate>Tue, 18 Nov 2003 22:24:35 EDT</pubDate>
</item>

<item>
<title>Re: TWGandalf, a response</title>
<link>http://www.dslreports.com/forum/remark,8542500</link>
<description><![CDATA[<A HREF="/useremail/u/555338"><b>volntn</b></A> : WinMTR Statistics<br><CENTER>WinMTR statistics</CENTER><br> <br>Host % Sent Recv Best Avrg Wrst Last<br>10.173.48.1    0    5    5    0    9   16   16<br>midtn-24-159-64-129.chartertn.net    0    5    5   15   28   32   31<br>midtn-24-159-64-1.chartertn.net    0    5    5   16   28   32   31<br>midtn-24-159-64-34.chartertn.net    0    4    4   15   27   31   31<br>kcm-edge-02.inet.qwest.net    0    4    4   31   42   47   47<br>kcm-core-02.inet.qwest.net    0    4    4   32   43   47   47<br>dal-core-02.inet.qwest.net    0    4    4   46   46   47   47<br>dal-brdr-02.inet.qwest.net    0    4    4   46   46   47   46<br>205.171.1.14    0    4    4   46   46   47   47<br>tbr1-p013802.dlstx.ip.att.net    0    4    4   47   54   78   47<br>tbr2-cl1.attga.ip.att.net    0    4    4   78   78   78   78<br>gbr1-p20.attga.ip.att.net    0    4    4   78   78   78   78<br>gar1-p360.attga.ip.att.net    0    4    4   78   78   78   78<br>gw-er1kngtn.chartertn.net    0    4    4  203  211  219  203<br><br><br>  A reverse trace from down the road in Cleveland ,Looks like it is a charter issue with the Kingsport router.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,8542500</guid>
<pubDate>Tue, 18 Nov 2003 22:21:52 EDT</pubDate>
</item>

<item>
<title>Re: TWGandalf, a response</title>
<link>http://www.dslreports.com/forum/remark,8542348</link>
<description><![CDATA[<A HREF="/useremail/u/900178"><b>bigbearr</b></A> : K, unfortunatly I missread the post and thought that you were in my area, but I have done some investigating and cameron119 is correct, the issue is related to ATT service.<br><br>We can detect this by doing as Sparky had suggested and I can traceroute to the IP provided and notice that the ATT hop is the problem.<br><br>When TWGandalf posted his traceroute, it shows that its almost the same IP causing the issue. Its off by 1 number.<br><br>1,10.16.x.x,9ms,None,----<br>2,24.217.x.x,15ms,charter-stl.com,----<br>3,24.217.63.193,16ms,None,----<br>4,12.124.129.97,14ms,None,----<br>5,12.123.25.30,17ms,gbr6-p40.sl9mo.ip.att.net,----<br>6,12.122.11.125,19ms,tbr2-p013601.sl9mo.ip.att.net,----<br>7,12.122.10.90,36ms,tbr2-cl6.dlstx.ip.att.net,----<br>8,12.122.9.161,28ms,tbr1-p013601.dlstx.ip.att.net,----<br>9,12.122.2.90,42ms,tbr2-cl1.attga.ip.att.net,----<br>10,12.122.12.34,43ms,gbr1-p20.attga.ip.att.net,----<br>11,12.123.21.1,42ms,gar1-p360.attga.ip.att.net,----<br>12,12.124.59.114,210ms,None,----<br>13,24.158.96.230,211ms,gw-swc2kngtn.chartertn.net,----<br>14,24.158.109.161,213ms,gw-cr1kngtn.chartertn.net,----]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,8542348</guid>
<pubDate>Tue, 18 Nov 2003 22:07:24 EDT</pubDate>
</item>

<item>
<title>Re: TWGandalf, a response</title>
<link>http://www.dslreports.com/forum/remark,8542246</link>
<description><![CDATA[<A HREF="/useremail/u/507346"><b>sparky9</b></A> : bigbearr, would you please run a tracert to 24.158.109.161 and post results. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,8542246</guid>
<pubDate>Tue, 18 Nov 2003 21:58:39 EDT</pubDate>
</item>

<item>
<title>Re: TWGandalf, a response</title>
<link>http://www.dslreports.com/forum/remark,8542199</link>
<description><![CDATA[<A HREF="/useremail/u/730814"><b>cameron119</b></A> : I haven't seen anything showing you have packet loss on any of your first hops.  Could you post your modem's signal levels anyway?  &raquo;<A HREF="http://192.168.100.1" >192.168.100.1</A>  If the signals are out of spec that can cause some issues.  Granted, I highly doubt there is anything we can do since the issue is beyond Charter control on AT&T's backbone.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,8542199</guid>
<pubDate>Tue, 18 Nov 2003 21:55:04 EDT</pubDate>
</item>

<item>
<title>TWGandalf, a response</title>
<link>http://www.dslreports.com/forum/remark,8542117</link>
<description><![CDATA[<A HREF="/useremail/u/900178"><b>bigbearr</b></A> : Hey, your other thread got locked, so I needed to respond this way.<br>I have not noticed much of a latency issue in the area, but Ill check on a few things on my own using my own connection.<br><br>I just wanted to start another thread so you know someone is assisting you and you can post more info.<br><br>P.S. no one troll this thread too.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,8542117</guid>
<pubDate>Tue, 18 Nov 2003 21:48:26 EDT</pubDate>
</item>

</channel>
</rss>
