wtaylor82
18-03-2007, 11:52
Hi guys,
I'm hoping people can help why i can't get hold of tech support.
My internet connection is running relatively slow. From a 10mb connection installed two weeks ago I am received around 1 to 3 Mb on average, with the max I have recorded at 5.5mb
I've tried the following:
1. unplug the cable modem for 30 secs
2. replug in the cable modem and run the speed test. connection via router
3. unplug the cable modem for 30 secs
4. replug in the cable modem and directly connect via pc
5. ran an exhaustive virus, spyware and all other un-nicety check via my virus scanner and online via trendmicro
6. ran a exhaustive spead check giving information just as packet loss. Results posted below.
7. connect to the root console of the ambit 250 cable modem and gathered logs to aid any support.
Could I point out that I am not a heavy user such as a p2p user, maybe a bit of online gaming, downloads from work, email, surfing etc.
Here is the details from my cable modem console, via 192.168.100.1
----
Boot Code Version : 2.1.6d
Software Version : 2.94.1010
Hardware Version : 1.19
Acquire a Downstream Channel 586750000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Downstream Lock : Locked
Downstream Channel Id : 1
Downstream Frequency : 586750000 Hz
Downstream Modulation : QAM64
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 4.8 dBmV
Downstream SNR : 37.0 dB
Upstream Lock : Locked
Upstream Channel ID : 4
Upstream Frequency : 46400000 Hz
Upstream Modulation : QPSK
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 47.0 dBmV
Upstream Mini-Slot Size : 2
Network Access : Allowed
Maximum Downstream Data Rate : 10240000
Maximum Upstream Data Rate : 512000
Maximum Upstream Channel Burst : 1600
Maximum Number of CPEs : 1
Modem Capability : Concatenation Enabled, Fragametation Enabled, PHS Disabled
First Time Last Time Counts Level ID Text
Time Not Established Time Not Established 24 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established 1 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 2 Critical(3) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC f...
Time Not Established Time Not Established 1 Critical(3) 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
---
Results of speedtest via cableforum
Sat, 17 Mar 2007 16:45:32 UTC
1st 512K took 1547 ms = 331 KB/sec, approx 2727 Kbps, 2.66 Mbps
2nd 512K took 922 ms = 555.3 KB/sec, approx 4576 Kbps, 4.47 Mbps
3rd 512K took 2484 ms = 206.1 KB/sec, approx 1698 Kbps, 1.66 Mbps
4th 512K took 1375 ms = 372.4 KB/sec, approx 3069 Kbps, 3 Mbps
Overall Average Speed = approx 3018 Kbps, 2.95 Mbps
---
Results of speedtest via altenative source
Speed Test Report 07/03/17 16:38 - Full test
Test conducted at: 17/03/2007 16:38:59
Test sequence: Full test
Please note that these results are a snapshot of this particular moment. Run the test a few times to ensure maximum accuracy. Although the test has been constructed to be highly accurate, no guarantees can be made to the level of accuracy experienced in everyday use.
Test 1: Ping times to UK servers
Ideally, you should get a result of around 30 ms (lower is better)
meto.gov.uk: 48.5 ms
clara.net: 29.8 ms
vantage.myby.co.uk: 49.5 ms
linx.net: 52.8 ms
This result is much poorer than expected and should be investigated.
Test 2: Ping times to European servers
Ideally, you should get a result of around 50 ms (lower is better)
eu.uu.net: 28 ms
tu-berlin.de: 62.8 ms
eu.uu.net: 36.3 ms
lycos.es: 52.5 ms
The results of this test indicate no problems.
Test 3: Ping times to east-coast USA servers
Ideally, you should get a result of around 120 ms (lower is better)
helios.dii.utk.edu: This test failed due to a server timeout or other error.
ftp-linux.cc.gatech.edu: This test failed due to a server timeout or other error.
aeneas.mit.edu: 126 ms
helios.dii.utk.edu: 441 ms
Your ping times are slightly poorer than expected.
Test 4: Ping times to west-coast USA servers
Ideally, you should get a result of around 160 ms (lower is better)
stanford.edu: 176.3 ms
mirrors.usc.edu: 161.8 ms
ucla.edu: 166 ms
ucla.edu: 169.8 ms
The results of this test indicate no problems.
Test 5: Ping times to east Asia servers
Ideally, you should get a result of around 300 ms (lower is better)
opensourcecommunity.ph: 432 ms
meisei-u.ac.jp: This test failed due to a server timeout or other error.
apache.cdpa.nsysu.edu.tw: 405.3 ms
meisei-u.ac.jp: This test failed due to a server timeout or other error.
The results of this test indicate no problems.
Test 6: Ping times to Australian servers
Ideally, you should get a result of around 350 ms (lower is better)
apache.planetmirror.com.au: 342 ms
planetmirror.com: 366.3 ms
apache.planetmirror.com.au: 353.7 ms
apache.ausgamers.com: 391 ms
The results of this test indicate no problems.
Test 7: Ping times to central Asian servers
Ideally, you should get a result of around 300 ms (lower is better)
apache.dnepr.net: 88.3 ms
oynasana.com: 88 ms
opensourcecommunity.ph: 414.7 ms
apache.rinet.ru: 78.8 ms
The results of this test indicate no problems.
Test 8: Download speeds from UK servers
Ideally, you should get a result of around 1000 Kb/s (higher is better)
mirrorservice.org: 1731 Kb/s
The results of this test indicate no problems.
Test 9: Download speeds from European servers
Ideally, you should get a result of around 1000 Kb/s (higher is better)
rediris.es: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 10: Download speeds from east-coast USA servers
Ideally, you should get a result of around 1000 Kb/s (higher is better)
mirrors.ccs.neu.edu: 665 Kb/s
This result is much poorer than expected and should be investigated.
Test 11: Upload speeds to the Speed Test Server
Ideally, you should get a result of around 500 Kb/s (higher is better)
Not conducted: You must register this software in order to perform this test.
Please click 'What's This?' for information on registering this software to enable this test.
Test 12: Packet loss en route to a UK server
Ideally, you should get a result of around 0 % (lower is better)
cardiff.ac.uk: 0 %
cardiff.ac.uk: 2 %
A small amount of packet loss has been detected. This should be investigated.
Test 13: Packet loss en route to a European server
Ideally, you should get a result of around 0 % (lower is better)
uni-kl.de: 0 %
univ-rennes1.fr: 0 %
The results of this test indicate no problems.
Test 14: Packet loss en route to an east-coast USA server
Ideally, you should get a result of around 0 % (lower is better)
mirrors.ptd.net: 16 %
mirrors.ptd.net: 18 %
An unacceptable level of packet loss has been detected which should be investigated.
End of testing.
This report was collated using Dan Elwell's Broadband Speed Test. For more information or to download, please visit www.broadbandspeedtest.net.
I'm hoping people can help why i can't get hold of tech support.
My internet connection is running relatively slow. From a 10mb connection installed two weeks ago I am received around 1 to 3 Mb on average, with the max I have recorded at 5.5mb
I've tried the following:
1. unplug the cable modem for 30 secs
2. replug in the cable modem and run the speed test. connection via router
3. unplug the cable modem for 30 secs
4. replug in the cable modem and directly connect via pc
5. ran an exhaustive virus, spyware and all other un-nicety check via my virus scanner and online via trendmicro
6. ran a exhaustive spead check giving information just as packet loss. Results posted below.
7. connect to the root console of the ambit 250 cable modem and gathered logs to aid any support.
Could I point out that I am not a heavy user such as a p2p user, maybe a bit of online gaming, downloads from work, email, surfing etc.
Here is the details from my cable modem console, via 192.168.100.1
----
Boot Code Version : 2.1.6d
Software Version : 2.94.1010
Hardware Version : 1.19
Acquire a Downstream Channel 586750000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Downstream Lock : Locked
Downstream Channel Id : 1
Downstream Frequency : 586750000 Hz
Downstream Modulation : QAM64
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 4.8 dBmV
Downstream SNR : 37.0 dB
Upstream Lock : Locked
Upstream Channel ID : 4
Upstream Frequency : 46400000 Hz
Upstream Modulation : QPSK
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 47.0 dBmV
Upstream Mini-Slot Size : 2
Network Access : Allowed
Maximum Downstream Data Rate : 10240000
Maximum Upstream Data Rate : 512000
Maximum Upstream Channel Burst : 1600
Maximum Number of CPEs : 1
Modem Capability : Concatenation Enabled, Fragametation Enabled, PHS Disabled
First Time Last Time Counts Level ID Text
Time Not Established Time Not Established 24 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established 1 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 2 Critical(3) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC f...
Time Not Established Time Not Established 1 Critical(3) 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
---
Results of speedtest via cableforum
Sat, 17 Mar 2007 16:45:32 UTC
1st 512K took 1547 ms = 331 KB/sec, approx 2727 Kbps, 2.66 Mbps
2nd 512K took 922 ms = 555.3 KB/sec, approx 4576 Kbps, 4.47 Mbps
3rd 512K took 2484 ms = 206.1 KB/sec, approx 1698 Kbps, 1.66 Mbps
4th 512K took 1375 ms = 372.4 KB/sec, approx 3069 Kbps, 3 Mbps
Overall Average Speed = approx 3018 Kbps, 2.95 Mbps
---
Results of speedtest via altenative source
Speed Test Report 07/03/17 16:38 - Full test
Test conducted at: 17/03/2007 16:38:59
Test sequence: Full test
Please note that these results are a snapshot of this particular moment. Run the test a few times to ensure maximum accuracy. Although the test has been constructed to be highly accurate, no guarantees can be made to the level of accuracy experienced in everyday use.
Test 1: Ping times to UK servers
Ideally, you should get a result of around 30 ms (lower is better)
meto.gov.uk: 48.5 ms
clara.net: 29.8 ms
vantage.myby.co.uk: 49.5 ms
linx.net: 52.8 ms
This result is much poorer than expected and should be investigated.
Test 2: Ping times to European servers
Ideally, you should get a result of around 50 ms (lower is better)
eu.uu.net: 28 ms
tu-berlin.de: 62.8 ms
eu.uu.net: 36.3 ms
lycos.es: 52.5 ms
The results of this test indicate no problems.
Test 3: Ping times to east-coast USA servers
Ideally, you should get a result of around 120 ms (lower is better)
helios.dii.utk.edu: This test failed due to a server timeout or other error.
ftp-linux.cc.gatech.edu: This test failed due to a server timeout or other error.
aeneas.mit.edu: 126 ms
helios.dii.utk.edu: 441 ms
Your ping times are slightly poorer than expected.
Test 4: Ping times to west-coast USA servers
Ideally, you should get a result of around 160 ms (lower is better)
stanford.edu: 176.3 ms
mirrors.usc.edu: 161.8 ms
ucla.edu: 166 ms
ucla.edu: 169.8 ms
The results of this test indicate no problems.
Test 5: Ping times to east Asia servers
Ideally, you should get a result of around 300 ms (lower is better)
opensourcecommunity.ph: 432 ms
meisei-u.ac.jp: This test failed due to a server timeout or other error.
apache.cdpa.nsysu.edu.tw: 405.3 ms
meisei-u.ac.jp: This test failed due to a server timeout or other error.
The results of this test indicate no problems.
Test 6: Ping times to Australian servers
Ideally, you should get a result of around 350 ms (lower is better)
apache.planetmirror.com.au: 342 ms
planetmirror.com: 366.3 ms
apache.planetmirror.com.au: 353.7 ms
apache.ausgamers.com: 391 ms
The results of this test indicate no problems.
Test 7: Ping times to central Asian servers
Ideally, you should get a result of around 300 ms (lower is better)
apache.dnepr.net: 88.3 ms
oynasana.com: 88 ms
opensourcecommunity.ph: 414.7 ms
apache.rinet.ru: 78.8 ms
The results of this test indicate no problems.
Test 8: Download speeds from UK servers
Ideally, you should get a result of around 1000 Kb/s (higher is better)
mirrorservice.org: 1731 Kb/s
The results of this test indicate no problems.
Test 9: Download speeds from European servers
Ideally, you should get a result of around 1000 Kb/s (higher is better)
rediris.es: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 10: Download speeds from east-coast USA servers
Ideally, you should get a result of around 1000 Kb/s (higher is better)
mirrors.ccs.neu.edu: 665 Kb/s
This result is much poorer than expected and should be investigated.
Test 11: Upload speeds to the Speed Test Server
Ideally, you should get a result of around 500 Kb/s (higher is better)
Not conducted: You must register this software in order to perform this test.
Please click 'What's This?' for information on registering this software to enable this test.
Test 12: Packet loss en route to a UK server
Ideally, you should get a result of around 0 % (lower is better)
cardiff.ac.uk: 0 %
cardiff.ac.uk: 2 %
A small amount of packet loss has been detected. This should be investigated.
Test 13: Packet loss en route to a European server
Ideally, you should get a result of around 0 % (lower is better)
uni-kl.de: 0 %
univ-rennes1.fr: 0 %
The results of this test indicate no problems.
Test 14: Packet loss en route to an east-coast USA server
Ideally, you should get a result of around 0 % (lower is better)
mirrors.ptd.net: 16 %
mirrors.ptd.net: 18 %
An unacceptable level of packet loss has been detected which should be investigated.
End of testing.
This report was collated using Dan Elwell's Broadband Speed Test. For more information or to download, please visit www.broadbandspeedtest.net.