Re: [Connectivity] Unstable Service once again? Latency+Packet l in Comcast HSI

Re: [Connectivity] Unstable Service once again? Latency+Packet l in Comcast HSI http://www.dslreports.com/forum/r20838457 en Wed, 11 Nov 2009 06:07:57 EDT Wed, 11 Nov 2009 06:07:57 EDT Re: [Connectivity] Unstable Service once again? Latency+Packet l http://www.dslreports.com/forum/remark,20838549 divinewind : Well, it isnt happening tonight yet so he cant really test to see what it is.... Said he will escalate it to see if the network admin in this area can sweep the main line for any problems etc. and if it happens again, just call back and hope they catch it]]> http://www.dslreports.com/forum/remark,20838549 Wed, 23 Jul 2008 19:17:42 EDT Re: [Connectivity] Unstable Service once again? Latency+Packet l http://www.dslreports.com/forum/remark,20838457 divinewind : Tech is here now. At the moment there is no loss of packets etc. He says since it has a pattern it is most likely not the modem, but something in the lines. And the fact that its the last hop on the line quality test that is having issues, he is out checking the box right now. wiring inside proved to be fine.]]> http://www.dslreports.com/forum/remark,20838457 Wed, 23 Jul 2008 19:04:23 EDT Re: [Connectivity] Unstable Service once again? Latency+Packet l http://www.dslreports.com/forum/remark,20828788 kingifnot : I'd recommend calling you're local office and verifying the service call the live chat rep scheduled has a work order showing on your account locally.]]> http://www.dslreports.com/forum/remark,20828788 Mon, 21 Jul 2008 23:55:38 EDT Re: [Connectivity] Unstable Service once again? Latency+Packet l http://www.dslreports.com/forum/remark,20828746 divinewind : staying connected at the moment.. talking with comcast support.. They will send a tech out hopefully during peak hours to test..

quote:
Sergi
The signal coming into your modem is slightly weak from what I can tell from my end which causes high ping times at some points. If you would like, I could definitely send a technician during the peak hours of this.

Casey
70% of the time when I restart the modem it gets stuck on upstream ranging or receiving the IP from the dhcp..

Sergi
That definitely coincides with the upstream signal quality I show on my end.

Sergi
It is likely that the signal coming into your home is degraded to such a point.

Sergi
This may be caused by the signal in general or possibly a splitter in the line. I will check technician availability now.

Sergi
I have a 1-5pm tomorrow however I do have a 4-7pm on Wednesday.

I chose the 4-7 for obvious reasons. I will update on wednesday as to what they find. If anything.]]> http://www.dslreports.com/forum/remark,20828746 Mon, 21 Jul 2008 23:46:37 EDT Re: [Connectivity] Unstable Service once again? Latency+Packet l http://www.dslreports.com/forum/remark,20828662 divinewind : Once(about the time the smokeping shows about 22:00) it was itself. Other than that it is me because I have absolutely no connectivity past my router]]> http://www.dslreports.com/forum/remark,20828662 Mon, 21 Jul 2008 23:28:04 EDT Re: [Connectivity] Unstable Service once again? Latency+Packet l http://www.dslreports.com/forum/remark,20828650 tshirt : 1970-01-01 00:00:346-NoticeM573.0Modem Is Shutting Down and Rebooting...

Did you force a reboot in those cases?
or are you getting spontanious reboots?]]> http://www.dslreports.com/forum/remark,20828650 Mon, 21 Jul 2008 23:25:37 EDT Re: [Connectivity] Unstable Service once again? Latency+Packet l http://www.dslreports.com/forum/remark,20828639 tshirt : I'd really like to see a tweak test, with you pingable.
something doesn't seem right about that upstream signal level, also the smokeping shows alot of loss close to you.
do all the tests with and without the router inline, and during the test DO Nothing, click start and wait (or walk away for a few) ANY computer activity CAN effect the results.]]> http://www.dslreports.com/forum/remark,20828639 Mon, 21 Jul 2008 23:23:19 EDT Re: [Connectivity] Unstable Service once again? Latency+Packet l http://www.dslreports.com/forum/remark,20828508 divinewind : Losing almost all packets... Keep rebooting to use the net for about 2 minutes before each time it d/cs.

»/r3/smokeping.···68e482d2

»i310.photobucket.com/albums/kk41···ecom.png is my PingPlotter results image. Still waiting on the line quality test.

Line Quality Test:

»/linequality/nil/2409829

Its something between my modem and the local node.. I assume?

Latest update to the log since that first cut-out that smokeping shows:

1970-01-01 00:00:183-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:00:113-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:00:346-NoticeM573.0Modem Is Shutting Down and Rebooting...1970-01-01 00:00:323-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:303-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:00:273-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:00:103-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:00:046-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:026-NoticeM571.4Ethernet link dormant - not currently active1970-01-01 00:01:166-NoticeM573.0Modem Is Shutting Down and Rebooting...1970-01-01 00:01:133-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:00:373-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:213-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:00:173-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:00:083-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets

]]> http://www.dslreports.com/forum/remark,20828508 Mon, 21 Jul 2008 22:57:57 EDT Re: [Connectivity] Unstable Service once again? Latency+Packet l http://www.dslreports.com/forum/remark,20828505 divinewind : I will attempt to run pingplotter and a new line quality test. Will post results here.

My Modem Signal at the moment is:

quote:
Downstream-
Signal To Noise Ratio - 38.7 dB
Power Level - 1.0 dBmV

Upstream-
Power - 33.0 dBmV

These tests will be with my computer directly connected to the modem for now. Will post results with router included in a bit.

May be a while, keeps coming in and out.]]> http://www.dslreports.com/forum/remark,20828505 Mon, 21 Jul 2008 22:57:08 EDT Re: [Connectivity] Unstable Service once again? Latency+Packet l http://www.dslreports.com/forum/remark,20824562 tshirt : What are your signal levels?
In fact you should probably provide all this info
»Comcast High Speed Internet FAQ »How To Get Help!]]> http://www.dslreports.com/forum/remark,20824562 Mon, 21 Jul 2008 11:21:07 EDT [Connectivity] Unstable Service once again? Latency+Packet loss http://www.dslreports.com/forum/remark,20824525 divinewind : As some of you know I had issues before.. And I still think its at least somewhat of a separate issue...

Before I had similar problems which were fixed by getting a new modem(Besides it having issues in the past, was the one being phased out).

I currently have

quote:
Software Version: SB5101-2.6.2.0-SCM00-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0

With a 1.5mbps Comcast Connection.

The main things I think it might be right now(doesnt narrow down much eh? heh:
Modem
Router
NIC

Started yesterday(well for a few days have had extremely varying latency/packet loss which coincides with peak hours so im not concerned about the past week really).
Around 2200 MDT(mountain, -2 EDT, +1 PDT) my connection started to get very choppy. Was constantly having to refresh because of timeouts etc. After restarting I had a variety of problems, which I will list below in my troubleshooting steps.

1. Checked my computer for anything that may be causing it.
Using programs like x-netstat and hijackthis I couldnt find any localized reason for the trouble.

2. Pinged various addresses.
To the router and modem seemed fine at the time. To google was at 45ms for 3 packets, fourth packet lost. At this point I chose the next step.

3. Restarted router and modem multiple times.
Will explain more about the modem results below. The reason I think it may be the router or NIC: router page loaded very slow compared to normal. Had previously been downloading torrents(never caused this before) but my open connections and half-open connections list was quite short, shorter than it has been in the past(I have a similar problem with things like google maps filling my local ports and taking a minute or more to close before I can even access my router page)

Now, expanding on number 3 since that is where I noticed a larger issue than I expected.. (See modem log at the bottom as a reference if you need)

At first it would just send out a DHCP discovery packet and receive no response from the server. About 70% of the time rebooting it would stop at this stage.

A couple of times it would get stuck at Upstream Ranging(when it was stuck on this, signal page showed upstream power between 33 and 58).

After about 5 or more reboots I gave up. I left it unplugged overnight and this morning it seems to be working fine(with steady latency levels like when I first got the new modem). I have been running a smokeping test for the last 6 days or so(Did a 24hr and a 3-day before, dont have saved results of those though).
My current results as of this post(since the smokeping page will expire 12 hours after its complete, so any future viewers wont see it, I am using images)

Smokeping Statistics
Linked for quicker page loading

California Server 1 3 Hour
»i310.photobucket.com/albums/kk41···-3HR.png

California Server 1 30 Hour
»i310.photobucket.com/albums/kk41···30HR.png

California Server 2 3 Hour
»i310.photobucket.com/albums/kk41···-3HR.png

California Server 2 30 Hour
»i310.photobucket.com/albums/kk41···30HR.png

New York Server 3 Hour
»i310.photobucket.com/albums/kk41···-3HR.png

New York Server 30 Hour
»i310.photobucket.com/albums/kk41···30HR.png

California Server 1 6 Day
»i310.photobucket.com/albums/kk41···-6DY.png

Modem Log
Note: Most recent report is on top. Last entry is the first entry from the first reboot at about 2300 MDT. You can see how long it was up before each reboot by the timestamps(HH:MM:SS).

1970-01-01 00:00:153-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:00:123-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:05:406-NoticeM572.0Ds Pulse Failed - Reinitialize MAC...1970-01-01 00:05:406-NoticeM572.0Ds Pulse Failed - Reinitialize MAC...1970-01-01 00:05:406-NoticeM572.0Ds Lock Failed - Reinitialize MAC...1970-01-01 00:05:353-CriticalR002.0No Ranging Response received - T3 time-out (US 2)1970-01-01 00:05:233-CriticalR002.0No Ranging Response received - T3 time-out (US 1)1970-01-01 00:05:023-CriticalR003.0Init RANGING Critical Ranging Request (17) Retries exhausted1970-01-01 00:05:023-CriticalR002.0No Ranging Response received - T3 time-out (US 4)1970-01-01 00:04:013-CriticalR003.0Init RANGING Critical Ranging Request (17) Retries exhausted1970-01-01 00:04:013-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:02:576-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...1970-01-01 00:02:573-CriticalU001.0No UCD's Received - Timeout1970-01-01 00:02:463-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 00:02:373-CriticalR002.0No Ranging Response received - T3 time-out (US 2)1970-01-01 00:02:093-CriticalR002.0No Ranging Response received - T3 time-out (US 1)1970-01-01 00:02:053-CriticalR003.0Init RANGING Critical Ranging Request (17) Retries exhausted1970-01-01 00:02:053-CriticalR002.0No Ranging Response received - T3 time-out (US 4)1970-01-01 00:01:073-CriticalR003.0Init RANGING Critical Ranging Request (17) Retries exhausted1970-01-01 00:01:073-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:00:046-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:036-NoticeM571.4Ethernet link dormant - not currently active1970-01-01 00:03:556-NoticeM573.0Modem Is Shutting Down and Rebooting...1970-01-01 00:03:493-CriticalR002.0No Ranging Response received - T3 time-out (US 2)1970-01-01 00:03:273-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:00:093-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:06:136-NoticeM573.0Modem Is Shutting Down and Rebooting...1970-01-01 00:06:123-CriticalR002.0No Ranging Response received - T3 time-out (US 2)1970-01-01 00:06:063-CriticalR002.0No Ranging Response received - T3 time-out (US 1)1970-01-01 00:06:023-CriticalR002.0No Ranging Response received - T3 time-out (US 4)1970-01-01 00:05:583-CriticalR003.0Init RANGING Critical Ranging Request (17) Retries exhausted1970-01-01 00:05:583-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:05:126-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...1970-01-01 00:05:123-CriticalU001.0No UCD's Received - Timeout1970-01-01 00:05:023-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 00:05:013-CriticalR003.0Init RANGING Critical Ranging Request (17) Retries exhausted1970-01-01 00:05:013-CriticalR002.0No Ranging Response received - T3 time-out (US 1)1970-01-01 00:04:203-CriticalR003.0Init RANGING Critical Ranging Request (17) Retries exhausted1970-01-01 00:04:203-CriticalR002.0No Ranging Response received - T3 time-out (US 2)1970-01-01 00:03:243-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:00:073-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:00:066-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:026-NoticeM571.4Ethernet link dormant - not currently active1970-01-01 00:04:306-NoticeM573.0Modem Is Shutting Down and Rebooting...1970-01-01 00:04:303-CriticalR002.0No Ranging Response received - T3 time-out (US 2)1970-01-01 00:04:203-CriticalR003.0Init RANGING Critical Ranging Request (17) Retries exhausted1970-01-01 00:04:203-CriticalR002.0No Ranging Response received - T3 time-out (US 1)1970-01-01 00:03:333-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:00:103-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:143-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:036-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:163-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:113-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:00:163-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:01:333-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:01:313-CriticalD002.0DHCP FAILED - Request sent, No response1970-01-01 00:01:193-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:01:066-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...1970-01-01 00:01:063-CriticalU001.0No UCD's Received - Timeout1970-01-01 00:00:553-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing1970-01-01 00:00:403-CriticalR004.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o1970-01-01 00:00:073-CriticalR002.0No Ranging Response received - T3 time-out (US 3)1970-01-01 00:00:046-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:026-NoticeM571.4Ethernet link dormant - not currently active

]]> http://www.dslreports.com/forum/remark,20824525 Mon, 21 Jul 2008 11:14:34 EDT