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

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

<channel>
<title>Cox HSI forum - dslreports.com community</title>
<link>http://www.dslreports.com/forum/coxhsi</link>
<description>Cox HSI forum current topics</description>
<language>en</language>
<copyright>Copyright 2007, dslreports.com</copyright>
<pubDate>Thu, 26 Nov 2009 02:06:41 EDT</pubDate>
<lastBuildDate>Thu, 26 Nov 2009 02:06:41 EDT</lastBuildDate>

<image>
<title>dslreports.com</title>
<url>http://i.dslr.net/bbrdisc1.gif</url>
<link>http://www.dslreports.com</link>
<width>19</width>
<height>18</height>
<description>bbr disc</description>
</image>

<item>
<title>[NV] Speed Upgrade</title>
<link>http://www.dslreports.com/forum/remark,22375154</link>
<description><![CDATA[Anyone hear about a speed upgrade this summer for Las Vegas? We're still @ 12 down while the people in Cali got 20 last year. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22375154</guid>
<pubDate>2009-05-12 01:08:53</pubDate>
</item>

<item>
<title>[LA] Slow speeds in 70560 (New Iberia)</title>
<link>http://www.dslreports.com/forum/remark,23368613</link>
<description><![CDATA[This was taken after midnight. I would have posted in the other topic about slow speeds, but I couldn't get the forum to load. 

Seems like I'm not the only one. Speeds are great in the day time. I have even had a tech come out and check the speeds here at the drop. 

New Iberia - 70560
  

Anyone know how well the DSL (AT&T right?) works down here?
--
Member of the US Air Force since May 7th, 2002 To March 29th, 2005
"You sneak up behind yourself and remove your pants before you realize what's going on." KOL]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23368613</guid>
<pubDate>2009-11-20 01:11:04</pubDate>
</item>

<item>
<title>Cox.net clerical error</title>
<link>http://www.dslreports.com/forum/remark,23389813</link>
<description><![CDATA[In a move that, for now at least, threatens e-mail marketers&#146; ability to communicate with a significant portion of their files during one of the most crucial Christmas shopping seasons in recent memory, someone at Cox Communications over the weekend apparently mistakenly added the Cox.net domain to the Federal Communications Commission&#146;s wireless domain list&#151;essentially, the equivalent of a do-not-call list for mobile domains: http://directmag.com/magilla/1124-cox-snafu-fcc-messup/]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23389813</guid>
<pubDate>2009-11-24 15:42:26</pubDate>
</item>

<item>
<title>[CA] Cox HSI dropping constantly, in a tech rut....help</title>
<link>http://www.dslreports.com/forum/remark,23336360</link>
<description><![CDATA[Hello,

Hopefully one of the keen Cox people can help a bit here. Thanks so much Cox gurus in advance.

I have the Premium plan, and when it works -- it works well for a very long time -- until something happens in the network.   I had one other issue 3 years ago -- and it took Cox 5 months to fix, it.    It took them this long to finally go across the street in a junction box where Taps are for all the houses immediately around me.   Apparently a cable was loose.   It was a bit maddening experience.

Well here I am again, and something in the Cox network has changed.   After 4 calls, 2 different visits I am no better off with any plan or methodology to do anything else.   Cox said my return signal is "not good" or is "failing" or "critical" .  However, my power levels appear to be good to them.  They sent out techs.  The first had no clue, and didnt really care to.  I showed him the numerous cable modem log errors of rebooting and SYNC troubles, and was promptly ignored while him looking at me in the face saying everything is fine.    

I had to call again to get another tech out, this one knew very little, and wasnt qualified to look into the phone box across the street (where my Tap issue was a couple years ago) to check connections in there.    He was very nice however, and clearly wanted to help -- but didnt know what to do.

I suggested leaving another cable modem, in absence of any suggestions from Cox, to see if that helps.    He had to call for approval, and got this.   

Cable modem is a Motorola SB5101.  The one I had before was the Ambit U10C018.   

The Motorola is certainly less verbose in the error logs, but when it loses connectivity it lasts sometimes much longer and reboots.  The Ambit had more errors logged, but when it looses connectivity, it lasts for seconds only and never seemed to reboot.       The first log I post below is an example of what is going on with the Motorola.  You can see it is rebooting itself (happens at least a couple times a day).       After this log I will post what the Ambit looked like when that was in the system:

Motorola Log:

009-11-12 11:51:18&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:23&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-12 11:50:37&#9;6-Notice&#9;M573.0&#9;Modem Is Shutting Down and Rebooting...
2009-11-12 11:50:37&#9;3-Critical&#9;R004.0&#9;Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-11-12 01:43:47&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:21&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:12&#9;3-Critical&#9;R002.0&#9;No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-12 01:43:11&#9;6-Notice&#9;E111.0&#9;SW download Successful - Via NMS
2009-11-12 01:42:37&#9;6-Notice&#9;E101.0&#9;SW Download INIT - Via NMS
2009-11-11 22:57:51&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:28&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 22:57:04&#9;6-Notice&#9;M573.0&#9;Modem Is Shutting Down and Rebooting...
2009-11-11 22:57:04&#9;3-Critical&#9;R004.0&#9;Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-11-11 21:14:59&#9;4-Error&#9;D103.0&#9;DHCP RENEW sent - Invalid DHCP option
2009-11-11 09:16:22&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 09:16:20&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
2009-11-11 09:16:18&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 09:16:12&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
2009-11-11 09:15:14&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:22&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 08:44:51&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:20&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 08:24:35&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:00:55&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:44&#9;3-Critical&#9;R004.0&#9;Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
1970-01-01 00:00:11&#9;3-Critical&#9;R002.0&#9;No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:00:06&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
2009-11-11 08:23:24&#9;6-Notice&#9;M573.0&#9;Modem Is Shutting Down and Rebooting...
2009-11-11 08:23:24&#9;3-Critical&#9;&Ocirc;7954.20&#9;Resetting the cable modem due to docsDevResetNow
2009-11-11 08:22:46&#9;6-Notice&#9;I401.0&#9;TLV-11 - unrecognized OID
1970-01-01 00:01:19&#9;3-Critical&#9;D003.0&#9;DHCP FAILED - Requested Info not supported.
1970-01-01 00:01:10&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
1970-01-01 00:01:09&#9;3-Critical&#9;R002.0&#9;No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:01:06&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
1970-01-01 00:01:04&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
1970-01-01 00:01:03&#9;3-Critical&#9;T001.0&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:26&#9;3-Critical&#9;T002.0&#9;SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:26&#9;3-Critical&#9;T001.0&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:24&#9;3-Critical&#9;T002.0&#9;SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:24&#9;3-Critical&#9;T001.0&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:06&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
1970-01-01 00:00:21&#9;3-Critical&#9;T001.0&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

Now below is the Ambit Logs from various prior days:

Wed Nov 11 05:55:26 2009&#9;Wed Nov 11 05:55:26 2009&#9;Critical (3)&#9;Started Unicast Maintenance Ranging - No Response received - ...
Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:19:02 2009&#9;Tue Nov 10 17:19:02 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:02 2009&#9;Tue Nov 10 17:19:02 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Nov 10 17:19:01 2009&#9;Tue Nov 10 17:19:01 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:01 2009&#9;Tue Nov 10 17:19:01 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Nov 10 17:19:00 2009&#9;Tue Nov 10 17:19:00 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:06:32 2009&#9;Tue Nov 10 17:06:32 2009&#9;Critical (3)&#9;Started Unicast Maintenance Ranging - No Response received - ...
Tue Nov 10 17:02:16 2009&#9;Tue Nov 10 17:02:16 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to receive MAC S...
Tue Nov 10 17:02:16 2009&#9;Tue Nov 10 17:02:16 2009&#9;Information (7)&#9;Downstream pulse failed
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:01:24 2009&#9;Tue Nov 10 17:01:24 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:01:24 2009&#9;Tue Nov 10 17:01:24 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:01:23 2009&#9;Tue Nov 10 17:01:23 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Authorized
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Registration complete!
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;We registered with a DOCSIS 1.1 config file!
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Received a REG-RSP message from the CMTS...
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Sending a REG-REQ to the CMTS...
Tue Nov 10 16:56:52 2009&#9;Tue Nov 10 16:56:52 2009&#9;Information (7)&#9;CableModem SNMP configure complete

 

Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:28:52 2009&#9;Tue Nov 10 17:28:52 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:28:48 2009&#9;Tue Nov 10 17:28:48 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:19:04 2009&#9;Tue Nov 10 17:19:04 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:19:02 2009&#9;Tue Nov 10 17:19:02 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:02 2009&#9;Tue Nov 10 17:19:02 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Nov 10 17:19:01 2009&#9;Tue Nov 10 17:19:01 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:19:01 2009&#9;Tue Nov 10 17:19:01 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Nov 10 17:19:00 2009&#9;Tue Nov 10 17:19:00 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 17:06:32 2009&#9;Tue Nov 10 17:06:32 2009&#9;Critical (3)&#9;Started Unicast Maintenance Ranging - No Response received - ...
Tue Nov 10 17:02:16 2009&#9;Tue Nov 10 17:02:16 2009&#9;Critical (3)&#9;SYNC Timing Synchronization failure - Failed to receive MAC S...
Tue Nov 10 17:02:16 2009&#9;Tue Nov 10 17:02:16 2009&#9;Information (7)&#9;Downstream pulse failed
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;locked and synced to rescue CMTS...all is well!
Tue Nov 10 17:01:25 2009&#9;Tue Nov 10 17:01:25 2009&#9;Information (7)&#9;Downstream sync ok
Tue Nov 10 17:01:24 2009&#9;Tue Nov 10 17:01:24 2009&#9;Information (7)&#9;Locked on the rescue CMTS ds. try to re-acquire ds sync...
Tue Nov 10 17:01:24 2009&#9;Tue Nov 10 17:01:24 2009&#9;Information (7)&#9;Downstream lock ok
Tue Nov 10 17:01:23 2009&#9;Tue Nov 10 17:01:23 2009&#9;Information (7)&#9;Downstream lock failed
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Authorized
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Registration complete!
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;We registered with a DOCSIS 1.1 config file!
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Received a REG-RSP message from the CMTS...
Tue Nov 10 16:56:53 2009&#9;Tue Nov 10 16:56:53 2009&#9;Information (7)&#9;Sending a REG-REQ to the CMTS...
Tue Nov 10 16:56:52 2009&#9;Tue Nov 10 16:56:52 2009&#9;Information (7)&#9;CableModem SNMP configure complete
Tue Nov 10 16:56:52 2009&#9;Tue Nov 10 16:56:52 2009&#9;Notice (6)&#9;TLV-11 - unrecognized OID]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23336360</guid>
<pubDate>2009-11-13 12:02:57</pubDate>
</item>

<item>
<title>[AZ] Slow Internet Access - Any suggestions or ideas? Thanks!</title>
<link>http://www.dslreports.com/forum/remark,23390093</link>
<description><![CDATA[Noticed a substancial drop in speed the last month when compared to previous months. As you can see from the attached speedtests, the speed is now typically about a 1/3 of what it was. I do realize that I'm supposed to get only 15Mbps (without powerboost), but we are not close to that any longer. 

Cox tech support helpline says the levels are right where they should be. We tried all the normal tech support techniques. (Unplug cablemodem/router/reboot pc/direct attach) No change.

I did notice the firmware is slightly out of date. There seem to be some forum posts about a new version. ( Software Version: SB5101-2.6.0.0-SCM00-NOSH )

DNS servers - changed to Cox - No change. Typically using OpenDNS.

Below are the answers to the typical questions. Any ideas or suggestions would be greatly appreciated! 

&#149; Motorola sb5101, Apple Airport Router, Buffalo Airstation, and direct attached tried. (No real speed difference.)
&#149; cox speed tier - Premier Package
&#149; Levels attached
&#149; No Splitters - Split outside of the house in Cox junction box for TV/Internet/phone. Using Cox phone, but not the version with the MTA inside the house. (It's the old style with the box attached to the outside  of our house.)
&#149; speed test attached, Speed test over time attached
&#149;  (&raquo;/tweaks) Ran test tools and tweaks not needed (OS/X) Snow Leopard
&#149; Called tech support and unplugged/replugged cable modem and router.. No change
&#149; Connect by Ethernet (gigabit). Used different Cat 6 cables.. No change.
&#149; speeds bypassing router? Yes, no difference. Tried multiple machines too. No change.
&#149; are other services such as phone or tv affected? TV seems fine. Don't watch it much, but all the channels seem to work. Phone seems fine too. 
&#149; I noticed the downstream frequency has changed from: Frequency 579000000 Hz, to 849000000 Hz. 

Happy Thanksgiving to all in a couple days.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23390093</guid>
<pubDate>2009-11-24 16:37:26</pubDate>
</item>

<item>
<title>[OK] New HD channels 31 December 2009</title>
<link>http://www.dslreports.com/forum/remark,23387448</link>
<description><![CDATA[From the FWIW department....

As posted on the HDTV in Oklahoma site by hdtver...

 quote:The December billing cycle statements list the following new channels under "News From Cox"

Tennis Channel HD on Channel 729
Investigation Discovery HD on Channel 761
BBC America HD on Channel 764

--
"When all else fails, read the instructions..."
MS-MVP Windows Desktop Experience]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23387448</guid>
<pubDate>2009-11-24 06:18:23</pubDate>
</item>

<item>
<title>[AR] slow speeds</title>
<link>http://www.dslreports.com/forum/remark,23381715</link>
<description><![CDATA[I am having slow speeds in alma arkansas here are my levals]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23381715</guid>
<pubDate>2009-11-23 01:38:38</pubDate>
</item>

<item>
<title>[CA] DOCSIS 3.0 coming to COX Orange County ?</title>
<link>http://www.dslreports.com/forum/remark,23381803</link>
<description><![CDATA[I'm wondering if there's any news on when south Orange County (Mission Viejo, Lake Forest, Newport Beach, Irvine Tustin, etc.) area might receive an upgrade to DOCSIS 3.0?  More and more people on other cable carriers are already on DOCSIS 3.0 and clocking over 120mb/s on speedtest.net -- can't wait!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23381803</guid>
<pubDate>2009-11-23 02:13:20</pubDate>
</item>

<item>
<title>[LA] Slow in Baton Rouge 70810</title>
<link>http://www.dslreports.com/forum/remark,21567818</link>
<description><![CDATA[Lately, my HSI has been very sluggish in the evenings. I just pinged the gateway (8:15 PM, 12/11/08), and I've copied the results below. It's not as bad during the day, and it improves late at night. I'm in Baton Rouge, zip code 70810.

Pinging 68.11.159.129 with 32 bytes of data:
Reply from 68.11.159.129: bytes=32 time=448ms TTL=254
Reply from 68.11.159.129: bytes=32 time=243ms TTL=254
Reply from 68.11.159.129: bytes=32 time=96ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=252ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=61ms TTL=254
Reply from 68.11.159.129: bytes=32 time=158ms TTL=254
Reply from 68.11.159.129: bytes=32 time=407ms TTL=254
Reply from 68.11.159.129: bytes=32 time=118ms TTL=254
Reply from 68.11.159.129: bytes=32 time=242ms TTL=254
Reply from 68.11.159.129: bytes=32 time=58ms TTL=254
Reply from 68.11.159.129: bytes=32 time=241ms TTL=254
Reply from 68.11.159.129: bytes=32 time=74ms TTL=254
Reply from 68.11.159.129: bytes=32 time=50ms TTL=254
Reply from 68.11.159.129: bytes=32 time=71ms TTL=254
Reply from 68.11.159.129: bytes=32 time=62ms TTL=254
Reply from 68.11.159.129: bytes=32 time=228ms TTL=254
Reply from 68.11.159.129: bytes=32 time=380ms TTL=254
Reply from 68.11.159.129: bytes=32 time=182ms TTL=254
Reply from 68.11.159.129: bytes=32 time=247ms TTL=254
Reply from 68.11.159.129: bytes=32 time=207ms TTL=254
Reply from 68.11.159.129: bytes=32 time=122ms TTL=254
Reply from 68.11.159.129: bytes=32 time=91ms TTL=254
Reply from 68.11.159.129: bytes=32 time=321ms TTL=254
Reply from 68.11.159.129: bytes=32 time=243ms TTL=254
Reply from 68.11.159.129: bytes=32 time=62ms TTL=254
Reply from 68.11.159.129: bytes=32 time=316ms TTL=254
Reply from 68.11.159.129: bytes=32 time=462ms TTL=254
Reply from 68.11.159.129: bytes=32 time=26ms TTL=254
Reply from 68.11.159.129: bytes=32 time=81ms TTL=254
Reply from 68.11.159.129: bytes=32 time=58ms TTL=254
Reply from 68.11.159.129: bytes=32 time=25ms TTL=254
Reply from 68.11.159.129: bytes=32 time=372ms TTL=254
Reply from 68.11.159.129: bytes=32 time=80ms TTL=254
Reply from 68.11.159.129: bytes=32 time=82ms TTL=254
Reply from 68.11.159.129: bytes=32 time=168ms TTL=254
Reply from 68.11.159.129: bytes=32 time=277ms TTL=254
Reply from 68.11.159.129: bytes=32 time=259ms TTL=254
Reply from 68.11.159.129: bytes=32 time=37ms TTL=254
Reply from 68.11.159.129: bytes=32 time=142ms TTL=254
Reply from 68.11.159.129: bytes=32 time=556ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=104ms TTL=254
Reply from 68.11.159.129: bytes=32 time=159ms TTL=254
Reply from 68.11.159.129: bytes=32 time=120ms TTL=254
Reply from 68.11.159.129: bytes=32 time=199ms TTL=254
Reply from 68.11.159.129: bytes=32 time=32ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=310ms TTL=254
Reply from 68.11.159.129: bytes=32 time=33ms TTL=254
Reply from 68.11.159.129: bytes=32 time=48ms TTL=254
Reply from 68.11.159.129: bytes=32 time=261ms TTL=254

Ping statistics for 68.11.159.129:
    Packets: Sent = 53, Received = 49, Lost = 4 (7% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 556ms, Average = 181ms
Control-C]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21567818</guid>
<pubDate>2008-12-11 21:21:00</pubDate>
</item>

<item>
<title>Attention Cox Customers in Orange County, CA &#x26;amp; Palos Verdes</title>
<link>http://www.dslreports.com/forum/remark,23383529</link>
<description><![CDATA[TiVo Inc. along with Cox Communications is pleased to announce the availability of a new device &#150; the Tuning Adapter -- which enables TiVo Series 3, TiVo HD and TiVo HD XL devices equipped with a CableCARD to tune to channels that are delivered via Switched Digital Video (SDV), a new interactive technology.  

The Tuning Adapters are currently only available in our Orange County, CA; Palos Verdes / San Pedro, CA; Arizona; Fairfax County, VA and Fredericksburg, VA service areas.  

Cox is constantly striving to provide customers with the best in entertainment and communications services.  To this end, Switched Digital Video is being utilized in select areas.  SDV allows maximization of network capacity, enabling additional HD channels and entertainment options to be offered to Cox customers.  To date, Digital Cable Ready (DCR) devices including TiVo Series 3 and TiVo HD devices equipped with a CableCARD have not been able to tune to channels delivered via SDV, as these devices permit only one-way communication to the cable network.

During the past several months however, Cox, along with the rest of the cable industry, has worked with TiVo to develop the Tuning Adapter, an external device that will allow TiVo Series 3 and TiVo HD digital video recorders to tune to channels delivered using SDV.

Tuning Adapters are now available and are being offered to Cox Orange County and Palos Verdes / San Pedro Digital Cable customers with a CableCARD in a TiVo Series 3, TiVo HD and TiVo HD XL digital video recorders at no charge.  

Tuning adapters are easy to install.  Self installation kits and Tuning Adapters can be picked up at our local retail centers, except our Queen Creek office.  Visit http://ww2.cox.com/aboutus/orangecounty/contact-us/cox-centers.cox
for Orange County locations and hours of operation or http://ww2.cox.com/aboutus/palosverdes/contact-us/cox-centers.cox for Palos Verdes / San Pedro locations and hours of operation.   
 
If you have any questions, would like to have a self install kit and tuning adapter mailed to you or would like to schedule a professional install, please call Cox at 1-888-246-3465.

Cox Communications ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23383529</guid>
<pubDate>2009-11-23 13:25:47</pubDate>
</item>

</channel>
</rss>
