Hello all, great forum I'm looking for some help here with my internet as comcast doesnt seem to know how to fix it. My internet has slow drastically in the last few weeks. I upgraded to the 12 meg service last month and never seen an increase in speed now it has slowed in the evening I cannot game at all ping in wow from 7p.m. to 10 p.m. is over 1100 constanly. Comcast tech came out today and checked and says everything is fine no packet loss but the 1st time he ran the test he looked puzzled and said it disconnected him then ran again and said it was fine. speedtest.net results are erratic anywhere from 300k to 10m all on the same server if i change severs same thing. I changed a couple of my cords and ran the optimizer and patch from here but same thing. Here are couple thing I have seen you guys ask for and I appreciate any help provided.
« SpeedGuide.net TCP Analyzer Results »
Tested on: 03.18.2009 16:11
IP address: 68.59.xx.xxx
Client OS: Windows Vista
TCP options string: 020405b40103030201010402
MSS: 1460
MTU: 1500
TCP Window: 65700 (multiple of MSS)
RWIN Scaling: 2 bits (2^2=4)
Unscaled RWIN : 16425
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 2628kbps (329KBytes/s)
BDP limit (500ms): 1051kbps (131KBytes/s)
MTU Discovery: ON
TTL: 50
Timestamps: OFF
SACKs: ON
IP ToS: 00100000 (32)
Precedence: 001 (priority)
Delay: 0 (normal delay)
Throughput: 0 (normal throughput)
Reliability: 0 (normal reliability)
Cost: 0 (normal cost)
Check bit: 0 (correct)
DiffServ: CS1 001000 (8) - class 1 (RFC 2474). Similar forwarding behavior to the ToS Precedence field.
C:\Users\User>tracert yahoo.com
Tracing route to yahoo.com [206.190.60.37]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 23 ms 14 ms 45 ms ge-1-10-ur01.panamacity.fl.pancity.comcast.net [68.86.181.81]
4 109 ms 33 ms 60 ms te-3-1-ar01.l3-mobile.al.northglf.comcast.net [68.86.181.17]
5 70 ms 58 ms 58 ms te-1-4-0-6-cr01.dallas.tx.ibone.comcast.net [68.86.91.61]
6 384 ms 60 ms 40 ms xe-5-1-0.edge3.Dallas1.Level3.net [4.71.198.41]
7 80 ms 67 ms 53 ms vlan79.csw2.Dallas1.Level3.net [4.68.19.126]
8 * 109 ms 162 ms ae-73-73.ebr3.Dallas1.Level3.net [4.69.136.157]
9 77 ms * 174 ms ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
10 88 ms * 111 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
11 75 ms 100 ms 109 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.1
30]
12 212 ms 73 ms 243 ms ae-11-69.car1.Washington1.Level3.net [4.68.17.3]
13 217 ms 78 ms 260 ms 4.79.228.2
14 90 ms 77 ms 139 ms ae2-p150.msr2.re1.yahoo.com [216.115.108.61]
15 195 ms 71 ms 179 ms te-9-3.bas-a1.re4.yahoo.com [216.39.49.3]
16 274 ms 66 ms 113 ms w2.rc.vip.re4.yahoo.com [206.190.60.37]
Trace complete.
C:\Users\User>
maybe someone can help
I would first ping -t http://www.comcast.com to see if there is any packet loss. Do the pings when you notice the internet is slowing down on you. Also type into your browser the IP address 192.168.100.1 to look at the modem signal levels. It is possible that you may have some type of fluctuation in signal. If you're experiencing more of a slow surf more in the evenings, there is a possibility that there is an issue called noise that can be interfering with the cable system and you will notice it by getting packet loss when you do a continuous ping. Ping the http://www.comcast.com server continuous because it is a reliable source.
You seem to be running Vista, so the Optimizer won't change anything, only the SG Vista TCP/IP patch: http://www.speedguide.net/downloads.php#vista
If your cable modem has a web interface (like the Motorola Surfboards), it may also be a good idea to check the signal levels to make sure they're within specs.
If your cable modem has a web interface (like the Motorola Surfboards), it may also be a good idea to check the signal levels to make sure they're within specs.
ok didn't notice packet loss pinging http://www.comcast.com. I let it run for 3-4 mins. I assume it would tell me or I would see one of the numbers besides the ping number change? The ping number changed alot anywhere from 50ms to 700ms. I have no idea what "in spec" would be for my modem here is the info from it. sorry if its to long.
Basic LAN
--------------------------------------------------------------------------------
RF Parameters
Downstream
Frequency 543 MHz Power 4 dBmV
Signal to Noise Ratio 36 dB Modulation QAM256
Upstream
Frequency 32 MHz Power 44 dBmV
Upstream Data Rate 2560 Ksym/sec Modulation QAM16
Status
System uptime 2 days 12h:22m:14s
Computers detected 2
CM Status Operational
WAN Isolation OFF
Time and Date Thu Mar 19 07:56:02 2009
Interface Parameters
Interface Name : LANCABLEUSBMTA
Provisioned Enabled State Up
Speed ------ MAC address 00-10-95-ff-ff-fe
Hardware Info
--------------------------------------------------------------------------------
System
HW Revision 2.0 VENDOR Thomson
BOOT Revision 2.1.7i SW Revision ST70.04.10
MODEL DHG535 Software Version ST70.04.10
Serial Number 00874813603123
MTA Hardware Information
Mta Serial Number 00874813603123
Software Build and Revisions
Firmware Name DHG535-70.04.10-081017-S-1C1.bin
Firmware Build Time 15:35:23 Fri Oct 17 2008
Event Log - DOCSIS
--------------------------------------------------------------------------------
DOCSIS PacketCable
--------------------------------------------------------------------------------
Date/Time Event ID Event Level Description
03/18/2009 21.50 82000500 03 Started Unicast Maintenance Ranging - No Response received - T3 time-out
03/18/2009 09.39 68000600 03 TFTP failed - configuration file NOT FOUND
03/18/2009 09.39 68000700 03 TFTP Failed - OUT OF ORDER packets
03/18/2009 09.39 68000600 03 TFTP failed - configuration file NOT FOUND
03/18/2009 09.39 68000700 03 TFTP Failed - OUT OF ORDER packets
03/18/2009 09.39 68000300 03 DHCP WARNING - Non-critical field invalid in response.
03/18/2009 09.39 84000100 03 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
03/18/2009 09.37 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
03/18/2009 09.30 82000500 03 Started Unicast Maintenance Ranging - No Response received - T3 time-out
03/18/2009 09.19 68000403 04 ToD request sent- No Response received
03/18/2009 09.19 68000300 03 DHCP WARNING - Non-critical field invalid in response.
03/18/2009 09.18 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
03/18/2009 09.13 68000300 03 DHCP WARNING - Non-critical field invalid in response.
03/18/2009 08.50 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
03/18/2009 08.44 68000300 03 DHCP WARNING - Non-critical field invalid in response.
03/18/2009 08.44 84000200 03 SYNC Timing Synchronization failure - Failed to acquire FEC framing
03/18/2009 08.41 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
03/17/2009 21.50 82000500 03 Started Unicast Maintenance Ranging - No Response received - T3 time-out
03/16/2009 20.04 68010300 05 DHCP RENEW WARNING - Field invalid in response
03/16/2009 19.33 2436694044 03 Resetting the cable modem due to docsDevResetNow
03/16/2009 19.15 2436694044 03 Resetting the cable modem due to docsDevResetNow
03/16/2009 19.03 82000500 03 Started Unicast Maintenance Ranging - No Response received - T3 time-out
03/16/2009 18.24 68000600 03 TFTP failed - configuration file NOT FOUND
03/16/2009 18.24 68000700 03 TFTP Failed - OUT OF ORDER packets
03/16/2009 18.24 68000600 03 TFTP failed - configuration file NOT FOUND
01/01/1970 00.00 68000700 03 TFTP Failed - OUT OF ORDER packets
01/01/1970 00.00 68000403 04 ToD request sent- No Response received
01/01/1970 00.00 68000403 04 ToD request sent- No Response received
01/01/1970 00.00 68000600 03 TFTP failed - configuration file NOT FOUND
01/01/1970 00.00 68000300 03 DHCP WARNING - Non-critical field invalid in response.
01/01/1970 00.00 68000403 04 ToD request sent- No Response received
01/01/1970 00.00 68000300 03 DHCP WARNING - Non-critical field invalid in response.
Cm State
--------------------------------------------------------------------------------
CM State Operational
Docsis-Downstream Scanning Complete
Docsis-Ranging Complete
Docsis-DHCP Complete
Docsis-TFTP Complete
Docsis-Data Reg Complete Complete
Telephony-DHCP Complete
Telephony-Security Complete
Telephony-TFTP Complete
Telephony-Reg with Call Server Complete
Telephony-Reg Complete Complete
Line 1 State on-hook
Line 2 State on-hook
Basic LAN
--------------------------------------------------------------------------------
RF Parameters
Downstream
Frequency 543 MHz Power 4 dBmV
Signal to Noise Ratio 36 dB Modulation QAM256
Upstream
Frequency 32 MHz Power 44 dBmV
Upstream Data Rate 2560 Ksym/sec Modulation QAM16
Status
System uptime 2 days 12h:22m:14s
Computers detected 2
CM Status Operational
WAN Isolation OFF
Time and Date Thu Mar 19 07:56:02 2009
Interface Parameters
Interface Name : LANCABLEUSBMTA
Provisioned Enabled State Up
Speed ------ MAC address 00-10-95-ff-ff-fe
Hardware Info
--------------------------------------------------------------------------------
System
HW Revision 2.0 VENDOR Thomson
BOOT Revision 2.1.7i SW Revision ST70.04.10
MODEL DHG535 Software Version ST70.04.10
Serial Number 00874813603123
MTA Hardware Information
Mta Serial Number 00874813603123
Software Build and Revisions
Firmware Name DHG535-70.04.10-081017-S-1C1.bin
Firmware Build Time 15:35:23 Fri Oct 17 2008
Event Log - DOCSIS
--------------------------------------------------------------------------------
DOCSIS PacketCable
--------------------------------------------------------------------------------
Date/Time Event ID Event Level Description
03/18/2009 21.50 82000500 03 Started Unicast Maintenance Ranging - No Response received - T3 time-out
03/18/2009 09.39 68000600 03 TFTP failed - configuration file NOT FOUND
03/18/2009 09.39 68000700 03 TFTP Failed - OUT OF ORDER packets
03/18/2009 09.39 68000600 03 TFTP failed - configuration file NOT FOUND
03/18/2009 09.39 68000700 03 TFTP Failed - OUT OF ORDER packets
03/18/2009 09.39 68000300 03 DHCP WARNING - Non-critical field invalid in response.
03/18/2009 09.39 84000100 03 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
03/18/2009 09.37 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
03/18/2009 09.30 82000500 03 Started Unicast Maintenance Ranging - No Response received - T3 time-out
03/18/2009 09.19 68000403 04 ToD request sent- No Response received
03/18/2009 09.19 68000300 03 DHCP WARNING - Non-critical field invalid in response.
03/18/2009 09.18 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
03/18/2009 09.13 68000300 03 DHCP WARNING - Non-critical field invalid in response.
03/18/2009 08.50 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
03/18/2009 08.44 68000300 03 DHCP WARNING - Non-critical field invalid in response.
03/18/2009 08.44 84000200 03 SYNC Timing Synchronization failure - Failed to acquire FEC framing
03/18/2009 08.41 82000400 03 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
03/17/2009 21.50 82000500 03 Started Unicast Maintenance Ranging - No Response received - T3 time-out
03/16/2009 20.04 68010300 05 DHCP RENEW WARNING - Field invalid in response
03/16/2009 19.33 2436694044 03 Resetting the cable modem due to docsDevResetNow
03/16/2009 19.15 2436694044 03 Resetting the cable modem due to docsDevResetNow
03/16/2009 19.03 82000500 03 Started Unicast Maintenance Ranging - No Response received - T3 time-out
03/16/2009 18.24 68000600 03 TFTP failed - configuration file NOT FOUND
03/16/2009 18.24 68000700 03 TFTP Failed - OUT OF ORDER packets
03/16/2009 18.24 68000600 03 TFTP failed - configuration file NOT FOUND
01/01/1970 00.00 68000700 03 TFTP Failed - OUT OF ORDER packets
01/01/1970 00.00 68000403 04 ToD request sent- No Response received
01/01/1970 00.00 68000403 04 ToD request sent- No Response received
01/01/1970 00.00 68000600 03 TFTP failed - configuration file NOT FOUND
01/01/1970 00.00 68000300 03 DHCP WARNING - Non-critical field invalid in response.
01/01/1970 00.00 68000403 04 ToD request sent- No Response received
01/01/1970 00.00 68000300 03 DHCP WARNING - Non-critical field invalid in response.
Cm State
--------------------------------------------------------------------------------
CM State Operational
Docsis-Downstream Scanning Complete
Docsis-Ranging Complete
Docsis-DHCP Complete
Docsis-TFTP Complete
Docsis-Data Reg Complete Complete
Telephony-DHCP Complete
Telephony-Security Complete
Telephony-TFTP Complete
Telephony-Reg with Call Server Complete
Telephony-Reg Complete Complete
Line 1 State on-hook
Line 2 State on-hook
I have replaced all the cables now and unplugged the modem for 15 mins tonight. check my awesome speed tonight.
comcast told my wife they see the internet is slow but it takes 1-3 weeks to get someone to come check the node. I bet if I get on the phone and act like a jerk they will get someone out quicker but I hate to have to do that. I will if need be I'm not waiting 3 weeks.
comcast told my wife they see the internet is slow but it takes 1-3 weeks to get someone to come check the node. I bet if I get on the phone and act like a jerk they will get someone out quicker but I hate to have to do that. I will if need be I'm not waiting 3 weeks.
If you don't see a lot of packet loss, you may want to have customer service to check to make sure that your account isn't capping your internet at the 1 MEG package offered with comcast. The modem levels that you specified are in specs. Also, you may want to verify that your modem isn't on the retirement list for the DOCSIS version used by Comcast.
Try another tracert to yahoo.com. Noticed hop 2 on your original shows request timed out. All the rest have irregular times.
C:\Users\User>tracert yahoo.com
Tracing route to yahoo.com [206.190.60.37]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 23 ms 14 ms 45 ms ge-1-10-ur01.panamacity.fl.pancity.comcast.net [68.86.181.81]
4 109 ms 33 ms 60 ms te-3-1-ar01.l3-mobile.al.northglf.comcast.net [68.86.181.17]
5 70 ms 58 ms 58 ms te-1-4-0-6-cr01.dallas.tx.ibone.comcast.net [68.86.91.61]
6 384 ms 60 ms 40 ms xe-5-1-0.edge3.Dallas1.Level3.net [4.71.198.41]
7 80 ms 67 ms 53 ms vlan79.csw2.Dallas1.Level3.net [4.68.19.126]
8 * 109 ms 162 ms ae-73-73.ebr3.Dallas1.Level3.net [4.69.136.157]
9 77 ms * 174 ms ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
10 88 ms * 111 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
11 75 ms 100 ms 109 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.1
30]
12 212 ms 73 ms 243 ms ae-11-69.car1.Washington1.Level3.net [4.68.17.3]
13 217 ms 78 ms 260 ms 4.79.228.2
14 90 ms 77 ms 139 ms ae2-p150.msr2.re1.yahoo.com [216.115.108.61]
15 195 ms 71 ms 179 ms te-9-3.bas-a1.re4.yahoo.com [216.39.49.3]
16 274 ms 66 ms 113 ms w2.rc.vip.re4.yahoo.com [206.190.60.37]
Trace complete.
C:\Users\User>
Philip, mccoffee;
Would that indicate possible problem with the line from modem to comcast?
C:\Users\User>tracert yahoo.com
Tracing route to yahoo.com [206.190.60.37]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 23 ms 14 ms 45 ms ge-1-10-ur01.panamacity.fl.pancity.comcast.net [68.86.181.81]
4 109 ms 33 ms 60 ms te-3-1-ar01.l3-mobile.al.northglf.comcast.net [68.86.181.17]
5 70 ms 58 ms 58 ms te-1-4-0-6-cr01.dallas.tx.ibone.comcast.net [68.86.91.61]
6 384 ms 60 ms 40 ms xe-5-1-0.edge3.Dallas1.Level3.net [4.71.198.41]
7 80 ms 67 ms 53 ms vlan79.csw2.Dallas1.Level3.net [4.68.19.126]
8 * 109 ms 162 ms ae-73-73.ebr3.Dallas1.Level3.net [4.69.136.157]
9 77 ms * 174 ms ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
10 88 ms * 111 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
11 75 ms 100 ms 109 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.1
30]
12 212 ms 73 ms 243 ms ae-11-69.car1.Washington1.Level3.net [4.68.17.3]
13 217 ms 78 ms 260 ms 4.79.228.2
14 90 ms 77 ms 139 ms ae2-p150.msr2.re1.yahoo.com [216.115.108.61]
15 195 ms 71 ms 179 ms te-9-3.bas-a1.re4.yahoo.com [216.39.49.3]
16 274 ms 66 ms 113 ms w2.rc.vip.re4.yahoo.com [206.190.60.37]
Trace complete.
C:\Users\User>
Philip, mccoffee;
Would that indicate possible problem with the line from modem to comcast?
Sorry for the long time between my replies (long week at work) 2nd tech came out today and said same thing it was the node. Then later in the day a network engineer came by and said they think they fixed it and left. I get home and check the internet it is not even working so call comcast and they say they will reactivate it and did but it is not fixed friggin 4.8mb on speedtest.net, anyway here is the new trace you asked for
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\User>tracert http://www.yahoo.com
Tracing route to www-real.wa1.b.yahoo.com [69.147.76.15]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 25 ms 10 ms 9 ms ge-1-10-ur01.panamacity.fl.pancity.comcast.net [
68.86.181.81]
4 14 ms 13 ms 14 ms te-3-1-ar01.l3-mobile.al.northglf.comcast.net [6
8.86.181.17]
5 38 ms 29 ms 30 ms te-1-4-0-6-cr01.dallas.tx.ibone.comcast.net [68.
86.91.61]
6 29 ms 35 ms 106 ms xe-11-2-0.edge3.Dallas1.Level3.net [4.71.198.13]
7 32 ms 34 ms 35 ms vlan79.csw2.Dallas1.Level3.net [4.68.19.126]
8 38 ms 35 ms 35 ms ae-73-73.ebr3.Dallas1.Level3.net [4.69.136.157]
9 * * * Request timed out.
10 75 ms 72 ms 72 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
11 74 ms 71 ms 71 ms ae-71-71.csw2.Washington1.Level3.net [4.69.134.1
34]
12 78 ms 89 ms 65 ms ae-21-79.car1.Washington1.Level3.net [4.68.17.67
]
13 73 ms 74 ms 74 ms 4.79.228.2
14 97 ms 96 ms 78 ms ae2-p140.msr1.re1.yahoo.com [216.115.108.57]
15 78 ms 84 ms 83 ms te-9-4.bas-a2.re1.yahoo.com [66.196.112.203]
16 74 ms 75 ms 79 ms f1.http://www.vip.re1.yahoo.com [69.147.76.15]
Trace complete.
C:\Users\User>
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\User>tracert http://www.yahoo.com
Tracing route to www-real.wa1.b.yahoo.com [69.147.76.15]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 25 ms 10 ms 9 ms ge-1-10-ur01.panamacity.fl.pancity.comcast.net [
68.86.181.81]
4 14 ms 13 ms 14 ms te-3-1-ar01.l3-mobile.al.northglf.comcast.net [6
8.86.181.17]
5 38 ms 29 ms 30 ms te-1-4-0-6-cr01.dallas.tx.ibone.comcast.net [68.
86.91.61]
6 29 ms 35 ms 106 ms xe-11-2-0.edge3.Dallas1.Level3.net [4.71.198.13]
7 32 ms 34 ms 35 ms vlan79.csw2.Dallas1.Level3.net [4.68.19.126]
8 38 ms 35 ms 35 ms ae-73-73.ebr3.Dallas1.Level3.net [4.69.136.157]
9 * * * Request timed out.
10 75 ms 72 ms 72 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
11 74 ms 71 ms 71 ms ae-71-71.csw2.Washington1.Level3.net [4.69.134.1
34]
12 78 ms 89 ms 65 ms ae-21-79.car1.Washington1.Level3.net [4.68.17.67
]
13 73 ms 74 ms 74 ms 4.79.228.2
14 97 ms 96 ms 78 ms ae2-p140.msr1.re1.yahoo.com [216.115.108.57]
15 78 ms 84 ms 83 ms te-9-4.bas-a2.re1.yahoo.com [66.196.112.203]
16 74 ms 75 ms 79 ms f1.http://www.vip.re1.yahoo.com [69.147.76.15]
Trace complete.
C:\Users\User>
Uneven ping times at hop 3. As hop 2 is timed out, the uneveness may have started here.Bigray13 wrote: 1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 25 ms 10 ms 9 ms ge-1-10-ur01.panamacity.fl.pancity.comcast.net [
68.86.181.81]
4 14 ms 13 ms 14 ms te-3-1-ar01.l3-mobile.al.northglf.comcast.net [68.86.181.17]
Make sure your modem is not placed near to any other electrical device. Keep it a few feet away from the router or cordless phone set.
"Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon
I moved the router tonight just to try it again I had done this last week when someone suggested it. Nothing really around it but I even tried putting it in the middle of the bed and power cycled everything but same thing SLOW. Tracert tonight shows the same thing. Timed out on jumps 2 and 9 weird again tonight.