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

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

<channel>
<title>Comcast HSI forum - dslreports.com community</title>
<link>http://www.dslreports.com/forum/comcast</link>
<description>Comcast HSI forum current topics</description>
<language>en</language>
<copyright>Copyright 2007, dslreports.com</copyright>
<pubDate>Sat, 04 Jul 2009 01:33:42 EDT</pubDate>
<lastBuildDate>Sat, 04 Jul 2009 01:33:42 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>SB6120 Connection Speed - LAN side</title>
<link>http://www.dslreports.com/forum/remark,22652390</link>
<description><![CDATA[So, I took the whole Comcast package a couple weeks back & they installed the SB6120.  The bottom LED (LAN) was orange meaning 10/100 Meg connection.  I updated my router to a Lynksys N with a Gig switch in it & the LED turned blue meaning 1 Gig LAN connection.  Two days ago Comcast had a fairly significant outage for a few hours and when things came back the LED is now orange again.  That makes no sense to me since it was a network outage, not something here.  Anyway, my speed tests still show the same speed I had after getting a Gig connection.  I don't see anything in the modem via a browser that tells me whether it's connecting at a Gig or not.  I have repowered both devices, but still the same results. 

Any way I can verify the LAN side connection speed other than the LED?

Thanks]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22652390</guid>
<pubDate>2009-07-03 23:54:55</pubDate>
</item>

<item>
<title>comcast email</title>
<link>http://www.dslreports.com/forum/remark,22652454</link>
<description><![CDATA[hey i just dont undestand comcast email here. i cant send emails from these.sites gmail yahoo  and hotmail . ive called at the customer service lines at comcast and the told me ? that i only have to use "comcast" email to send and rcvd. thats some thing else. with that can somebody ? tell me the " real truth here???? thanks..  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22652454</guid>
<pubDate>2009-07-04 00:19:30</pubDate>
</item>

<item>
<title>Connectivity &#x26;amp;raquo; SB5101 Online Light &#x22;Blinking&#x22;</title>
<link>http://www.dslreports.com/forum/remark,22652127</link>
<description><![CDATA[Hello - 
Internet was working fine in my house for years. Suddenly this afternoon it stopped working. TV signals are all fine. No wiring or additional equipment has been added or changed

When power is recycled / restarted I get solid greens for power - receive - send. "online" however is blinking. No connectivity. 

Can reach them modem via 192.168.100.1

On the status screen everything is listed or valued as "done" except for Cable Modem Status which is valued/listed as "offline"

Downstream Signal Levels - 
Signal To Noise : 38.6 dB
Power Level : .9 dBmV

Upstream Signal Levels - 
Channel ID - 1
Frequency - 23200000Hz
Power - 44.2 dBmV

Logs - 
2009-07-03 21:31:30&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
1970-01-01 00:03:33&#9;3-Critical&#9;R002.0&#9;No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:03:24&#9;3-Critical&#9;D001.0&#9;DHCP FAILED - Discover sent, no offer received
1970-01-01 00:01:25&#9;6-Notice&#9;M572.0&#9;Ds Lock Failed - Reinitialize MAC...
1970-01-01 00:01:25&#9;3-Critical&#9;T002.0&#9;SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:24&#9;6-Notice&#9;M572.0&#9;Ds Lock Failed - Reinitialize MAC...
1970-01-01 00:01:13&#9;3-Critical&#9;D001.0&#9;DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:02&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
1970-01-01 00:03:04&#9;6-Notice&#9;M572.0&#9;Ds Lock Failed - Reinitialize MAC...
1970-01-01 00:03:04&#9;3-Critical&#9;T002.0&#9;SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:03&#9;6-Notice&#9;M572.0&#9;Ds Lock Failed - Reinitialize MAC...
1970-01-01 00:02:12&#9;3-Critical&#9;D001.0&#9;DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:02&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
1970-01-01 00:03:20&#9;3-Critical&#9;R002.0&#9;No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:03:16&#9;3-Critical&#9;D001.0&#9;DHCP FAILED - Discover sent, no offer received
1970-01-01 00:03:01&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
1970-01-01 00:02:12&#9;3-Critical&#9;D001.0&#9;DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:02&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
1970-01-01 00:03:52&#9;3-Critical&#9;D002.0&#9;DHCP FAILED - Request sent, No response
1970-01-01 00:03:45&#9;3-Critical&#9;D001.0&#9;DHCP FAILED - Discover sent, no offer received
1970-01-01 00:03:29&#9;3-Critical&#9;R002.0&#9;No Ranging Response received - T3 time-out (US 4)
1970-01-01 00:03:25&#9;3-Critical&#9;D001.0&#9;DHCP FAILED - Discover sent, no offer received
1970-01-01 00:01:18&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
1970-01-01 00:01:15&#9;3-Critical&#9;D001.0&#9;DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:02&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active
1970-01-01 00:00:02&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
1970-01-01 00:00:11&#9;4-Error&#9;D004.3&#9;ToD request sent- No Response received
1970-01-01 00:00:04&#9;6-Notice&#9;M571.1&#9;Ethernet link up - ready to pass packets
1970-01-01 00:00:02&#9;6-Notice&#9;M571.4&#9;Ethernet link dormant - not currently active

Any ideas ?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22652127</guid>
<pubDate>2009-07-03 22:39:30</pubDate>
</item>

<item>
<title>What is DOCTORPING telling me here?</title>
<link>http://www.dslreports.com/forum/remark,22652012</link>
<description><![CDATA[http://www.dslreports.com/beta/doctorping?handle=248476e2dddd8b1e9cfe585b6b769c4f

"Sorry, 114 pings gave errors or timeouts. 64 from 103 IPs were reachable. - no record will be made."

Does this indicate a problem with my Internet? Or, is DoctorPing not fully functional?

Thanks!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22652012</guid>
<pubDate>2009-07-03 22:06:48</pubDate>
</item>

<item>
<title>New router need to notify Comcast?</title>
<link>http://www.dslreports.com/forum/remark,22650613</link>
<description><![CDATA[I haven't been using a router (Linksys WRT54GL) at all till now, only a cable modem. Do I have to notify Comcast if I begin to use one? Thanks.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22650613</guid>
<pubDate>2009-07-03 16:36:23</pubDate>
</item>

<item>
<title>New Comcast.net Web</title>
<link>http://www.dslreports.com/forum/remark,22616668</link>
<description><![CDATA[so I just got this email from Comcast announcing an all new website..  

anyone else get it?  

what's so new?
--
Webmaster - Steve
- - - - - - - - - - - -
http://www.1-gb.net
http://www.ppnstudio.com]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22616668</guid>
<pubDate>2009-06-26 16:05:37</pubDate>
</item>

<item>
<title>[Connectivity] Sudden spike in DCC&#x27;s, Schaumburg IL</title>
<link>http://www.dslreports.com/forum/remark,22604785</link>
<description><![CDATA[Beginning this Sunday, I have been seeing at least 3-4 DCC's (Dynamic Channel Change) a day. We've had D3 since October, and there were a few DCC's while it was being set up. Since Christmas, I only had one or two on one day, but it's been on the same channel otherwise.

I say 'at least' as I have an SB5120, which has a notoriously short log that also logs tons of junk.

I work from home (although I'm on vacation this week), and use both Skype and Vonage. The DCC's cause 10-15 second outages, which can really mess up a phone call, not to mention remote services like Citrix. I don't watch on-line videos or download/upload huge files. Speed-wise, the VPN to work is a T1, so that limits me to 1.5/1.5. Also, these changes are often occurring while everything is shut down.

Just wondering if anyone around here has also seen this. I don't want to buy a D3 modem just to avoid it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22604785</guid>
<pubDate>2009-06-24 17:43:44</pubDate>
</item>

<item>
<title>Comcast Call Center down?</title>
<link>http://www.dslreports.com/forum/remark,22564045</link>
<description><![CDATA[Got a call from Kiwi today.  He is fairly new to Comcast internet. He lives on the opposite side of town as me.  He said his video and internet were out.  He called the number and got the/a Call Center.  Perhaps Tennessee for us??
The person who answered said yes the service is down in your area but there is nothing they can do about it as the call center had been hit by a tornado.  Holy cow!

He asked "so how is one supposed to get a local support call through?"   I had assumed that if that call center was unable to handle calls perhaps they should have rerouted the call to another Call Center.  

I told him to post something here but for obvious reasons he can't!  lol  I got home late tonight so not sure of his status and if his problem has been fixed yet.

Just wondering if there is a way to call the local offices?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22564045</guid>
<pubDate>2009-06-17 01:44:20</pubDate>
</item>

<item>
<title>DOCSIS 3 upgrade in the area killed my Blast dl speed</title>
<link>http://www.dslreports.com/forum/remark,22629330</link>
<description><![CDATA[ Split from this topic -->  http://www.dslreports.com/forum/r20428169-Lets-keep-all-DOCSIS-30-Discussion-in-this-thread-please

~sorto' 

said by uid://1092082     :Well, it may be kind of "junky", but who is providing more than 4 channels to bond anyways? Give it time and they will come out with models that have 8 channels, but the provider must give 8 channels to bond. We haven't even been given upstream bonding yet, so, we have some time before anything more than 4 will be given on the download side.
 I just think it would have made more sense to drop equipment that could support 8 channels out of the gate.

Anyway, D3 is on in Lakewood... But its absolutely KILLED my downstream speeds and dropped me from 64QAM to 16 on upload.

They're still doing maintenance out here though so hopefully it gets fixed soon. My internet was out ALL last night and they told me that it would be up at 6:30... noticed my modem was flashing trying to get online when I woke up, unplugged it, plugged it back in, and I got all excited when I got the blue light... then I realized that my speed dropped dramatically. BOOOOOOOO!

http://www.speedtest.net/result/506455361.png

EDIT: Before anyone quotes my signal as the issue, this is the speedtest direct to the wall (-9 across the board):

  

They must be working on something because I can't pause 21Mbps...

--
** I am a Comcast employee. Posts on this site are my own, not my employer's **]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22629330</guid>
<pubDate>2009-06-29 15:54:28</pubDate>
</item>

<item>
<title>Packet Loss in Nashville TN</title>
<link>http://www.dslreports.com/forum/remark,22650554</link>
<description><![CDATA[How To Get Help! (#13965)
Please post the following information:

Answer these "6" questions first, then answer any of the following questions that are specific to your issue:

1)&#9;Your location: Nashville, TN

2)&#9;A description of the problem.  Major Packet Loss problem 

3)&#9;Is the issue intermittent, constant or does it occur at a specific time of day? Constant

4)&#9;Your modem make, model & firmware version. How to find firmware version: Access modem 

5)&#9;Describe any home networking if applicable. (i.e. routers, hubs, adapters, etc.) Netgear WPN824 Wireless Router

6)&#9;List any firewall and/or anti-virus software you have installed. Include what version you have. ESET Security 4.0

If you have an issue with slow or fluctuating speed:

&#149;&#9;What HSI Tier you are subscribed to: 6000/1000 Tier 



  

Downstream
 &#9;Freq/Power:&#9;693.000 MHz&#9;4 dBmV&#9; 
 &#9;Signal to Noise Ratio: &#9;37 dB&#9; 
 &#9;Modulation:&#9;QAM256&#9; 
Upstream
 &#9;Freq/Power:&#9;23.000 MHz&#9;44 dBmV&#9; 
 &#9;Channel Type:&#9;DOCSIS 2.0 (ATDMA)&#9; 
 &#9;Symbol Rate:&#9;5120 kSym/sec&#9; 
 &#9;Modulation:&#9;QAM16&#9; 

C:\Users\User>ping -t google.com

Pinging google.com [74.125.67.100] with 32 bytes of data:
Reply from 74.125.67.100: bytes=32 time=3411ms TTL=50
Reply from 74.125.67.100: bytes=32 time=40ms TTL=50
Reply from 74.125.67.100: bytes=32 time=41ms TTL=50
Request timed out.
Reply from 74.125.67.100: bytes=32 time=24ms TTL=50
Reply from 74.125.67.100: bytes=32 time=23ms TTL=50
Reply from 74.125.67.100: bytes=32 time=34ms TTL=50
Reply from 74.125.67.100: bytes=32 time=3450ms TTL=50
Reply from 74.125.67.100: bytes=32 time=2764ms TTL=50
Reply from 74.125.67.100: bytes=32 time=41ms TTL=50
Reply from 74.125.67.100: bytes=32 time=39ms TTL=50
Reply from 74.125.67.100: bytes=32 time=3192ms TTL=50
Request timed out.
Reply from 74.125.67.100: bytes=32 time=26ms TTL=50
Reply from 74.125.67.100: bytes=32 time=28ms TTL=50
Request timed out.
Reply from 74.125.67.100: bytes=32 time=22ms TTL=50
Reply from 74.125.67.100: bytes=32 time=25ms TTL=50
Reply from 74.125.67.100: bytes=32 time=23ms TTL=50
Reply from 74.125.67.100: bytes=32 time=30ms TTL=50
Reply from 74.125.67.100: bytes=32 time=21ms TTL=50
Reply from 74.125.67.100: bytes=32 time=28ms TTL=50
Reply from 74.125.67.100: bytes=32 time=26ms TTL=50
Reply from 74.125.67.100: bytes=32 time=45ms TTL=50
Reply from 74.125.67.100: bytes=32 time=24ms TTL=50
Reply from 74.125.67.100: bytes=32 time=34ms TTL=50
Reply from 74.125.67.100: bytes=32 time=3304ms TTL=50
Reply from 74.125.67.100: bytes=32 time=374ms TTL=50
Reply from 74.125.67.100: bytes=32 time=29ms TTL=50
Reply from 74.125.67.100: bytes=32 time=19ms TTL=50
Reply from 74.125.67.100: bytes=32 time=36ms TTL=50
Request timed out.
Reply from 74.125.67.100: bytes=32 time=44ms TTL=50
Reply from 74.125.67.100: bytes=32 time=23ms TTL=50
Reply from 74.125.67.100: bytes=32 time=26ms TTL=50
Reply from 74.125.67.100: bytes=32 time=24ms TTL=50
Reply from 74.125.67.100: bytes=32 time=23ms TTL=50
Request timed out.
Reply from 74.125.67.100: bytes=32 time=30ms TTL=50
Reply from 74.125.67.100: bytes=32 time=25ms TTL=50
Reply from 74.125.67.100: bytes=32 time=27ms TTL=50
Reply from 74.125.67.100: bytes=32 time=68ms TTL=50
Reply from 74.125.67.100: bytes=32 time=60ms TTL=50
Reply from 74.125.67.100: bytes=32 time=26ms TTL=50
Reply from 74.125.67.100: bytes=32 time=3570ms TTL=50
Reply from 74.125.67.100: bytes=32 time=45ms TTL=50
Reply from 74.125.67.100: bytes=32 time=30ms TTL=50
Reply from 74.125.67.100: bytes=32 time=296ms TTL=50
Reply from 74.125.67.100: bytes=32 time=3832ms TTL=50
Reply from 74.125.67.100: bytes=32 time=23ms TTL=50
Reply from 74.125.67.100: bytes=32 time=26ms TTL=50
Reply from 74.125.67.100: bytes=32 time=21ms TTL=50
Reply from 74.125.67.100: bytes=32 time=19ms TTL=50

Ping statistics for 74.125.67.100:
    Packets: Sent = 53, Received = 48, Lost = 5 (9% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 3832ms, Average = 528ms

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\User>ping -t comcast.net

Pinging comcast.net [76.96.38.13] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 76.96.38.13:
    Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\User>tracert 74.xxx.xxx.59

Tracing route to adsl-XXX-XXX-59.tys.bellsouth.net [74.xxx.xxx.59]
over a maximum of 30 hops:

  1    29 ms     4 ms     7 ms  192.168.1.1
  2    23 ms    27 ms    30 ms  73.230.21.1
  3    51 ms    20 ms    12 ms  ge-2-41-ur01.goodslettvll.tn.nash.comcast.net [6
8.86.151.73]
  4    39 ms    12 ms    11 ms  68.85.174.70
  5     *        *       13 ms  68.85.174.73
  6  1809 ms    42 ms    66 ms  te-9-1-ar02.nashville.tn.nash.comcast.net [68.86
.148.21]
  7    40 ms    30 ms    24 ms  te-9-2-ur01.goodslettvll.tn.nash.comcast.net [68
.86.148.61]
  8    17 ms    16 ms    19 ms  te-0-4-0-1-cr01.nashville.tn.ibone.comcast.net [
68.86.91.213]
  9    51 ms    29 ms    32 ms  pos-1-9-0-0-cr01.dallas.tx.ibone.comcast.net [68
.86.85.21]
 10    43 ms    53 ms    38 ms  Vlan549.icore2.DTX-Dallas.as6453.net [206.82.142
.5]
 11    74 ms  2266 ms   305 ms  Vlan6.icore1.DTX-Dallas.as6453.net [209.58.47.13
]
 12    44 ms    31 ms    25 ms  192.205.35.57
 13   202 ms    59 ms     *     cr2.dlstx.ip.att.net [12.122.138.106]
 14    66 ms    56 ms    55 ms  cr2.nsvtn.ip.att.net [12.122.28.65]
 15   107 ms    59 ms    66 ms  gar4.nsvtn.ip.att.net [12.123.129.105]
 16  3305 ms   724 ms    51 ms  65.83.238.145
 17    55 ms    65 ms    51 ms  65.83.238.99
 18   227 ms     *       65 ms  pxr00mia-so-1-0-0.bellsouth.net [65.83.236.20]
 19    81 ms    87 ms    65 ms  205.152.151.67
 20  3290 ms    65 ms    80 ms  ixc00tys-pos-7-0-0.bellsouth.net [65.83.239.102]

 21    64 ms    65 ms    75 ms  70.159.238.246
 22  1252 ms  1912 ms    85 ms  70.159.238.5
 23  1101 ms   100 ms     *     70.159.238.28
 24     *       74 ms    63 ms  70.159.238.26
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Sorry for such a long post.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22650554</guid>
<pubDate>2009-07-03 16:23:29</pubDate>
</item>

</channel>
</rss>
