angryviper
join:2002-07-11
Chicago, IL
| Issues in Chicago
Been having issues in Chicago for the last 3 weeks. The modem lights will stay on but the internet connection drops. During the mornings/afternoons the connection usually comes back on within 5 minutes. In the evenings it gets longer and sometimes doesnt come back on until the morning.
So far had 1 sub-contractor tech, 1 advanced tech and 2 line techs come out and all have stated the issue is outside the residence with one of the junction boxes. It is not supplied enough power thus causing a flunctuating internet signal.
I have been patient with them for so long that I have no idea what else to do. I will be contacting the BBB if this ever gets fixed.
In the mean time, does anyone know of anyone in Comcast that actually has some brains beyond their binder? |
|
angryviper
join:2002-07-11
Chicago, IL
| Ill post my stats but like I said, I have intermittent service.
C:\Documents and Settings\Owner>tracert www.comcast.net
Tracing route to a1526.g.akamai.net [96.17.76.25]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 8 ms 9 ms ge-1-37-ur01.chicago301.il.chicago.comcast.net [
68.86.115.61]
4 12 ms 10 ms 12 ms ge-1-3-ar01.mishawaka.in.sbend.comcast.net [68.8
7.230.234]
5 10 ms 11 ms 12 ms ge-1-1-ar03.area4.il.chicago.comcast.net [68.87.
230.233]
6 36 ms 39 ms 35 ms pos-0-13-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.90.53]
7 37 ms 35 ms 36 ms a96-17-76-25.deploy.akamaitechnologies.com [96.1
7.76.25]
Trace complete.
Ping statistics for 96.17.77.155:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 43ms, Average = 35ms
Frequency 711000000 Hz Locked
Signal to Noise Ratio 39 dB
Upstream Value
Channel ID 7
Frequency 34400000 Hz Ranged
Power Level 32 dBmV |
|
angryviper
join:2002-07-11
Chicago, IL
| 1970-01-01 00:10:43 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:08:32 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:08:27 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:08:13 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:08:11 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:05:02 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:05:00 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:04:50 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:04:30 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:04:20 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:04:12 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:56 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:31 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:00:21 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:03:50 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:21 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:00:11 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:16 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:05 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:28 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:00:18 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-08-07 06:54:20 3-Critical I002.0 REG RSP not received
1970-01-01 00:01:05 3-Critical D002.0 DHCP FAILED - Request sent, No response
1970-01-01 00:00:59 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:22 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:00:12 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:03:47 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:03:37 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:03:16 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:06:59 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:06:52 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:06:38 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:06:38 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:06:38 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:06:36 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:03:22 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:03:17 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:05 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:08:13 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:06:57 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:06:43 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:06:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:06:43 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:06:41 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:08:04 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:08:02 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:07:52 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:07:34 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:07:24 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:07:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:07:02 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:07:02 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:07:02 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:07:00 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:03:37 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:03:23 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
2008-08-06 09:19:45 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-08-06 09:19:40 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:26 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:26 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:26 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:24 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:24 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:23 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:23 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:23 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:19 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:19 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:18 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:18 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:17 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:17 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:14 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:13 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:11 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:10 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:09 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:09 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:08 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:07 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:07 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:06 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:05 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:05 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:04 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:02 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:02 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:19:01 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:19:00 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:18:46 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:18:45 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:18:31 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:18:28 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-08-06 09:18:27 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-08-06 09:18:27 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing |
|
angryviper
join:2002-07-11
Chicago, IL | reply to angryviper
And by looking at
»/r3/smokeping.···b2&r=922
Notice how the connection just falls off. |
|
angryviper
join:2002-07-11
Chicago, IL
| reply to angryviper
So I send a email to comcast:
Comments:
I''ve tried phone support numerous times and all they do is send
out techs who acknowldge the problem exists outside and they refer it to
line techs but the issue does not get solved. I am hoping that someone
reading this email will be able to help me out.
Everyday for the last 3 weeks I have been having a intermintent
connections. The webpages load and than stop loading. The modem lights
are all on but once I powercycle the modem and restart the computer the
"online" light just flashes. During the day it takes about 5 minutes
for the connection to come back, but in the evenings it can take hours.
I called support and one person told me the issue is outside with a
junction box. The techs came out and acknowledged this.
Since this hasnt been fixed I will provide you with this link.
»/r3/smokeping.···c6b2&r'2
This link monitors my internet connection throughout the day. As you
notice I have a very high packet loss ratio and that the connections
just drop off during the day.
Please get this issued solve, I am growing very impatient.
And the GEM of a RESPONSE:
Dear Luke,
We apologize for the inconvenience you've experienced.
After reviewing your e-mail and your account, I see that there is not
currently an outage in your area causing your connection issues.
Sometimes it is necessary to completely shut down your cable modem
connection when something isn't functioning properly. This is similar to
rebooting your computer. For best results, the modem should be connected
directly to the wall power outlet and not to a powerstrip. You'll also
want to make sure that there are no splitters or filters on the cable
line between your cable modem and the wall cable outlet.
If the cable modem is spontaneously re-booting and there is no evidence
of signal-related problems, check the electrical conditions near to the
cable modem. Possible causes of causes of spontaneous re-booting are
wiring to the cable modem is faulty or intermittent; spikes arising from
other major users of electricity like vacuum cleaners, power tools,
heating thermostats, and refrigerator thermostats; electromagnetic
interference from mobile phones or local radio transmitters; or the
cable modem itself is faulty.
It is also important to know that most cable modems will only allow an
Ethernet connection or a USB connection but not both at the same time.
Please follow the instructions below for powercycling your cable modem.
Please follow the steps below to troubleshoot the issue.
If your cable modem is connected to one computer:
1. Shut down your computer
2. Unplug the power cord of your cable modem
3. Wait 2 minutes
4. Plug the power cord of your cable modem back in
5. Wait for the online or pc light to turn solid green (This can take up
to five minutes)
6. Restart your computer
If you have a router, please follow these steps:
1. Shut down your computers
2. Unplug the power cord of your cable modem
3. Unplug the power cord of your router
4. Wait 2 minutes
5. Plug the power cord of your cable modem back in
6. Wait for the online or pc light on the cable modem to turn solid
green (This can take up to five minutes)
7. Plug the power cord of your router back in
8. Wait 2 minutes
9. Restart your computers
I hope this resolves this issue to your satisfaction.
Thank you for choosing Comcast.
Sincerely,
Julio T
Comcast Customer Care Specialist
Are you fucking kidding me? |
|
angryviper
join:2002-07-11
Chicago, IL
| reply to angryviper
The internet was down all morning and the tech that was scheduled for 8am to 10am didnt show. I called Comcast and they told me the tech was scheduled for 8am till 8pm. Since when do techs make calls that late?
Well I have no clue on what to do anymore. Looking at the smoke ping you can see all the service interruptions. |
|
Quaoar
join:2004-08-11
Fort Collins, CO |
The upstream power level of 32dbmv is far too low: something like 40dbmv is a good number.
Q |
|
K Patterson
Premium,MVM
join:2006-03-12
Columbus, OH
 ·RoadRunner Cable
| reply to angryviper
Well, it would appear that you are on a low-value tap, and that is why your upstream is so low. Nothing wrong with a 32 upstream. The upstream is ALWAYS the correct value to produce the desired power level at the CMTS, and is set by instructions from the CMTS.
It looks like there is simply a loose connection somewhere out in the Comcast plant. I'm assuming that the reconncections shown on your smokeping are happening automatically and not as a result of a manual reboot which you initiated.
To give the agent his due, a nosiy electrical environment will also produce the problem. Try shutting of as much as possible in the house and see if things improve. You don't have fish, do you? Aquarium heaters are regular radio transmitters. |
|
angryviper
join:2002-07-11
Chicago, IL | reply to angryviper
No the modem is not rebooted by me, everything happens on its own. Besides the router, there is nothing else near my modem. |
|
EG
The wings of love
Premium
join:2006-11-18
Union, NJ
1 edit | reply to K Patterson
said by K Patterson  :Well, it would appear that you are on a low-value tap, and that is why your upstream is so low. Nothing wrong with a 32 upstream. The upstream is ALWAYS the correct value to produce the desired power level at the CMTS, and is set by instructions from the CMTS. While I agree with Kip that there may be "nothing wrong with a 32 upstream". I'll disagree with a general statement such as "The upstream is ALWAYS the correct value to produce the desired power level at the CMTS" simply because even though this is technically correct, when we are referring to what an end user sees in their modem's signal stat figures, that does not take in to account any individual and unique attenuation (or a lack thereof) conditions that may exist on an end user's line.
All due respect to Kip here and only posted in case there are any possible clarity concerns. |
|
tech4044
join:2008-08-10
Chicago, IL | reply to angryviper
since your internet is down so much it should be an easy fix when the tech comes out he should see that the modem is down and be able to see the problem with his meter and fix the problem |
|
angryviper
join:2002-07-11
Chicago, IL | reply to angryviper
internet worked fine for 2 weeks, recently connection dropped 1-2 times every 2 days. Back to the same issue where the internet connection drops. In the last 30 hours it dropped 11 times. |
|
antiteam
| reply to angryviper
Where are you in Chicago? I'm in the West Loop and I've been having this exact problem. I've been running PingPlotter and when I'm experiencing service issues PingPlotter shows a loss of connection that can last up to a minute, then the connection returns for a minute or so only to have the process repeat. It's incredibly frustrating.
Comcast has told me that everything looks fine on their end. A tech was supposed to come out Saturday between 1PM and 4PM. He was a no-call-no-show and when I called Comcast to see where he was at I was told that the tech canceled my visit because I wasn't home (which couldn't be farther from the truth). Their customer service is driving me up a wall. |
|
AlienRendel
@spcsdns.net
| reply to angryviper
I have been having the same problem for the last bunch of weeks - random dropping of connection and rebooting the modem does not necessarily help, I just have to wait for the connection to come back up. I am just a bit west of the Logan Square area.
As of 2:30 pm yesterday, my connection has been completely down (no phone service either, obviously). I've called Comcast twice and been told that there is a node outtage affecting the greater Chicago area with no ETA for a fix.  |
|
Chaldo
join:2008-03-18
West Bloomfield, MI
| reply to angryviper
they are fucking with there throttling system .. just happend to me 5 min ago and went on for about 2 min but isnt the first time last night my friend had 10 hours on a game ready to hit 11 and they cut him off too for about a half a hour.. its there throttling stuff i bet you it is. |
|
antiteam
| reply to angryviper
I've been getting an intermittent connection here in the West Loop for 4 hours now, since around 11:45 this morning. Awful. |
|
angryviper
join:2002-07-11
Chicago, IL | reply to angryviper
issue seems to be worse during the evening hours. |
|
angryviper
join:2002-07-11
Chicago, IL | reply to angryviper
Oh and I live on the northwest side of Chicago. I spoke with a supervisor for the last 2 weeks and he told me the issue was fixed today, but clearly it has not. I will continue to bug him in the morning. |
|
angryviper
join:2002-07-11
Chicago, IL | reply to angryviper
Spoke with a supervisor and he stated there is an issue on the entire block or whatever. Says to give him couple days to fix it. Lets see what happens. |
|
antiteam
| reply to angryviper
Well, I've figured out a solution to my intermittent connection problems (which are still ongoing). I've called up AT&T and signed up for DSL. So long, Comcast! |
|
