![]() |
Slow in Guildford
I'm on the supposed 1.5mb service (213.107.72.***)
For the last 3 weeks its been really slow 128-200k I put it down to this big upgrade did the 'broadband medic' chat to a tech 3 nights ago and they diagnosed a cable fault in my area. was told to give it 24hrs gave it 36 and followed up with a 'real' tech support person he just didnt have a clue rang again the following day and got fobbed off again rang this afternoon and spoke to a Karthik who seemed a step up from recent people he emailed me some info on poor connections incl a link to Dan Ellwells speed test Nearly fainted at paying £10 but surprise surprise it says I've got a very slow connection and should contact tech support. " Test 8: Download speeds from UK servers Ideally, you should get a result of around 1024 Kb/s (higher is better) mirror.ac.uk: 149 Kb/s This result shows serious problems with your downloads, and should be investigated. Test 9: Download speeds from European servers Ideally, you should get a result of around 1024 Kb/s (higher is better) heanet.ie: This test failed due to a server timeout or other error. Too many server errors occurred therefore this test is inconclusive." Now that seems like a few circles I've been round a few times what should I do? David M Wicker Admin Edit: Last bit of IP removed (Paul) |
Re: Slow in Guildford
hi and :welcome: to the site , is this thru sacm or stb ??????? , can you tell us what tier you are on thru diagnostics ???????? :)
|
Re: Slow in Guildford
its the standard cable modem
but I dont recognise your other acronyms |
Re: Slow in Guildford
Quote:
when you say standard cable modem do you mean the silver ntl badged type ??????? , stb = set top box :) |
Re: Slow in Guildford
silver, with the bit around the lights being black and marked ntlhome
|
Re: Slow in Guildford
have now spoken to another tech at ntl
apparently they're all in india! have they closed down the cardif office? they say there's something wrong with my pc as a ping to the modem, disconnected from the pc, was much faster than pinging the pc ???? |
Re: Slow in Guildford
Quote:
start with the usual - full av scan using an up to date virus scanner, also try scanning for spyware. If you run p2p then make sure this is completely disabled. i wouldn't recommend speed tests as such as they can be unreliable, there is however a good one on robin walkers site http://homepage.ntlworld.com/robin.d...speedtest.html another good way of testing your connection is to try downloading a file from www.tucows.com using a good uk mirror. |
Re: Slow in Guildford
Quote:
As you have the NTL Home Modem type this into the browser address bar - http://192.168.100.1/ The user id and password will normally be - root and root You can then if you wish post the results back here at the time the connection is failing/poor. :) Ps I have asked a passing Mod to edit your IP from your first post as it is not a good idea to post your full IP address on a public forum. :D |
Re: Slow in Guildford
thanks very much guys
first, response to carlingman results of config Type : Ambit ETH/USB Combo Cable ModemCable modem : Ambit Cable ModemMAC address : **:**:**:**:**:**IP address : 10.247.183.***Downstream Receive Power Level : 3.59 dBmvDownstream SNR : 23.35 dBUpstream Transmit Power Level : 33.00 dBmv Operation Configuration Network Access : EnabledMaximum Downstream Data Rate : 1536000 bpsMaximum Upstream Data Rate : 256000 bpsMaximum Number of CPEs : 1Software Upgrade File Name : C2403225.cprSoftware Upgrade AdminStatus : allowProvisioningUpgradeSoftware Upgrade OperStatus : completeFromProvisioningDownstream Status Downstream Lock : LockedDownstream Frequency : 402750000 HzDownstream Modulation : 64 QAMDownstream Receive Power Level : 3.84 dBmvDownstream SNR : 23.68 dBCable Modem StatusUpstream Statusis that enough info? |
Re: Slow in Guildford
[QUOTE=threadbare]when the techs run their tools it may have shown latency on the PC but not on the modem. Indicating a possible problem with viruses, spyware, p2p (take your pick) or simply something installed on your PC using the connection. This is not conclusive proof in itself but a possible incicator of a problem.
start with the usual - full av scan using an up to date virus scanner, fine, done using nod32 also try scanning for spyware. did y/day with adaware and spybot, which I run frequently, nothing found If you run p2p then make sure this is completely disabled. stay clear of p2p i wouldn't recommend speed tests as such as they can be unreliable, there is however a good one on robin walkers site http://homepage.ntlworld.com/robin.d...speedtest.html tried this The connection is so slow, that after 5 mins, nod advised that there was a further estimated 40 mins to download, so posted back without this result earlier this evening, I did an easynews trace, which showed speed less than 60 k 64Kb/sec---ISDN40Kb/sec---56K20Kb/sec--- many thanks for your help guys what do you think I should do now? (now 1am uk time, will post back tomorrow) |
Re: Slow in Guildford
|
Re: Slow in Guildford
Results from Dan Elwell's BB Test
Dan Elwell's Broadband Speed Test Speed Test Report 04/11/21 01:30 - Full test Test conducted at: 21/11/2004 01:30:56 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) clara.net: 22.5 ms zeniiia.linux.org.uk: 28.7 ms gnu.teleglobe.net: 33 ms zeniiia.linux.org.uk: 39.3 ms The results of this test indicate no problems. Test 2: Ping times to European servers Ideally, you should get a result of around 50 ms (lower is better) belnet.be: 16.3 ms club-internet.fr: 22 ms rediris.es: 57 ms sunet.se: 57 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) dulug.duke.edu: 109.3 ms unet.brandeis.edu: 114 ms helios.dii.utk.edu: 134.8 ms unet.brandeis.edu: 112 ms The results of this test indicate no problems. Test 4: Ping times to west-coast USA servers Ideally, you should get a result of around 160 ms (lower is better) mirrors.tds.net: 113.5 ms limestone.uoregon.edu: 170.8 ms redhat.netnitco.net: 172 ms mirror.ats.ucla.edu: 162.3 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) apache-kr.org: 335 ms meisei-u.ac.jp: 259.3 ms opensourcecommunity.ph: 454.5 ms meisei-u.ac.jp: 261.5 ms 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: 339 ms mirror.pacific.net.au: 445.5 ms apache.planetmirror.com.au: 338 ms froggy.com.au: 452 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.rinet.ru: 73.5 ms apache.fresh.co.il: 88.3 ms apache.fresh.co.il: 89.7 ms oynasana.com: 79.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 1024 Kb/s (higher is better) apache.rmplc.co.uk: This test failed due to a server timeout or other error. Too many server errors occurred therefore this test is inconclusive. Test 9: Download speeds from European servers Ideally, you should get a result of around 1024 Kb/s (higher is better) oleane.net: 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 1024 Kb/s (higher is better) 64.12.168.21: This test failed due to a server timeout or other error. Too many server errors occurred therefore this test is inconclusive. Test 11: Upload speeds to the Speed Test Server Ideally, you should get a result of around 256 Kb/s (higher is better) broadbandspeedtest.net: This test failed due to a server timeout or other error. Too many server errors occurred therefore this test is inconclusive. Test 12: Packet loss en route to a UK server Ideally, you should get a result of around 0 % (lower is better) gnu.teleglobe.net: 10 % gnu.teleglobe.net: 16 % An unacceptable level of packet loss has been detected which 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) belnet.be: 24 % rediris.es: 24 % An unacceptable level of packet loss has been detected which should be investigated. Test 14: Packet loss en route to an east-coast USA server Ideally, you should get a result of around 0 % (lower is better) mirror.cc.vt.edu: 6 % club.cc.cmu.edu: 10 % 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. Generated 21/11/2004 01:30:58 using test version 3.0.316 - registered copy |
Re: Slow in Guildford
Quote:
:D PS I have * out your mac address and IP and asked a Passing Mod to remove it from your original post as it is not a good idea to post either on a public forum. :D |
Re: Slow in Guildford
Quote:
|
Re: Slow in Guildford
thanks carlingman for your help
I'll give them a call this lunchtime when it might be less busy did a download from tucows uk 4.07mb in 23min 20sec ie 2.98kb/sec this would normally have taken a few secs |
| All times are GMT +1. The time now is 12:23. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum