Hi there,
I have a 4mg connection with NTL and it has been running very slowly over the past few weeks on all of the computers on our network. I did the usual of rebooting the router and all the computers but it didn't make much difference. I called NTL and they tested the line and said there was no problem there. Then they tried to access my computer but couldn't as they said the firewall was on. I had turned off my Norton firewall and the Windows one was off.
I then tried on my boyfriend's computer, turned off his MacAffee firewall and made sure the windows firewall was off but NTL couldn't access it. They said that they couldn't help me further and that it was a problem with the firewalls on our computers (although it seems strange that the problem should be affecting all 5 computers and we use different firewalls. Anyway, I tried the computer in safe mode with networking and the internet seemed to be working fine.
I ran some broadband speed tests, here are the results:
Dan Elwell's Broadband Speed Test (unregistered)
Speed Test Report 06/10/11 10:01 - Full test
Test conducted at: 11/10/2006 10:01:21
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: 19.3 ms
bbc.co.uk: 17.5 ms
gold.ac.uk: 21.8 ms
broadbandspeedtest.co.uk: 14.5 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)
free.fr: 25 ms
uni-kl.de: 49.3 ms
eu.uu.net: 35 ms
tu-berlin.de: 45 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)
club.cc.cmu.edu: 101 ms
upenn.edu: 21.8 ms
rutgers.edu: This test failed due to a server timeout or other error.
dc.aleron.net: 203.3 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)
ucsb.edu: 203.5 ms
cybertrails.com: 203.3 ms
ucla.edu: 203.8 ms
cybertrails.com: 200.8 ms
Your ping times are slightly poorer than expected.
Test 5: Ping times to east Asia servers
Ideally, you should get a result of around 300 ms (lower is better)
zentek-international.com: 408 ms
apache.netsolutions.com.hk: 317 ms
apache-kr.org: 397.5 ms
apache.cdpa.nsysu.edu.tw: 370.5 ms
Your ping times are slightly poorer than expected.
Test 6: Ping times to Australian servers
Ideally, you should get a result of around 350 ms (lower is better)
apache.inspire.net.nz: 400.5 ms
mirror.pacific.net.au: 408.3 ms
froggy.com.au: 491.3 ms
froggy.com.au: 501 ms
Your ping times are slightly poorer than expected.
Test 7: Ping times to central Asian servers
Ideally, you should get a result of around 300 ms (lower is better)
opensourcecommunity.ph: 426.7 ms
apache.fresh.co.il: 280.3 ms
apache.rinet.ru: 69 ms
apache.rinet.ru: 68.5 ms
The results of this test indicate no problems.
Test 8: Download speeds from UK servers
Ideally, you should get a result of around 3072 Kb/s (higher is better)
mirrorservice.org: 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 3072 Kb/s (higher is better)
apache.crihan.fr: 580 Kb/s
This result shows serious problems with your downloads, and should be investigated.
Test 10: Download speeds from east-coast USA servers
Ideally, you should get a result of around 3072 Kb/s (higher is better)
csh.lkams.kernel.org: 841 Kb/s
This result shows serious problems with your downloads, and should be investigated.
Test 11: Upload speeds to the Speed Test Server
Ideally, you should get a result of around 300 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)
meto.gov.uk: 0 %
clara.net: 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)
univ-rennes1.fr: 0 %
belnet.be: 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: 10 %
club.cc.cmu.edu: 6 %
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 11/10/2006 10:01:21 using test version 3.0.316 - unregistered COPY
2:
Dan Elwell's Broadband Speed Test (unregistered)
Speed Test Report 06/10/11 10:10 - Full test
Test conducted at: 11/10/2006 10:10:29
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)
zeniiia.linux.org.uk: 203.8 ms
vantage.myby.co.uk: 13.5 ms
clara.net: 17.5 ms
gold.ac.uk: 19.3 ms
This result shows serious problems with your ping times, and should be investigated.
Test 2: Ping times to European servers
Ideally, you should get a result of around 50 ms (lower is better)
tu-berlin.de: 45.3 ms
belnet.be: 39 ms
sunsite.cnlab-switch.ch: 45.5 ms
tu-berlin.de: 46.3 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)
nyi.net: 85.5 ms
rutgers.edu: This test failed due to a server timeout or other error.
mirror.cc.vt.edu: 203.8 ms
ftp-linux.cc.gatech.edu: This test failed due to a server timeout or other error.
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)
ucsb.edu: 210.3 ms
redhat.netnitco.net: 203.5 ms
cybertrails.com: 203.5 ms
math.utah.edu: 208.3 ms
Your ping times are slightly poorer than expected.
Test 5: Ping times to east Asia servers
Ideally, you should get a result of around 300 ms (lower is better)
apache.oss.eznetsols.org: 491 ms
apache-kr.org: 407.7 ms
meisei-u.ac.jp: 326.7 ms
opensourcecommunity.ph: 422.3 ms
This result is much poorer than expected and should be investigated.
Test 6: Ping times to Australian servers
Ideally, you should get a result of around 350 ms (lower is better)
planetmirror.com: 408 ms
froggy.com.au: 510.8 ms
planetmirror.com: 468.7 ms
planetmirror.com: 412.3 ms
Your ping times are slightly poorer than expected.
Test 7: Ping times to central Asian servers
Ideally, you should get a result of around 300 ms (lower is better)
apache.rinet.ru: 69.5 ms
apache.fresh.co.il: 204.3 ms
apache.rinet.ru: 68.5 ms
apache.fresh.co.il: 200 ms
The results of this test indicate no problems.
Test 8: Download speeds from UK servers
Ideally, you should get a result of around 3072 Kb/s (higher is better)
mirrorservice.org: 2337 Kb/s
Your download speeds are slightly poorer than expected.
Test 9: Download speeds from European servers
Ideally, you should get a result of around 3072 Kb/s (higher is better)
cvut.cz: 911 Kb/s
This result shows serious problems with your downloads, and should be investigated.
Test 10: Download speeds from east-coast USA servers
Ideally, you should get a result of around 3072 Kb/s (higher is better)
apache.247available.com: 1433 Kb/s
This result shows serious problems with your downloads, and should be investigated.
Test 11: Upload speeds to the Speed Test Server
Ideally, you should get a result of around 300 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)
linx.net: 2 %
southwark.gov.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)
sunet.se: 0 %
univ-rennes1.fr: 2 %
A small amount of packet loss has been detected. This 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)
nyi.net: 0 %
dc.aleron.net: 20 %
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 11/10/2006 10:10:29 using test version 3.0.316 - unregistered COPY
3:
Dan Elwell's Broadband Speed Test (unregistered)
Speed Test Report 06/10/11 10:14 - Full test
Test conducted at: 11/10/2006 10:14:22
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)
cardiff.ac.uk: 41 ms
vantage.myby.co.uk: 15 ms
cardiff.ac.uk: 23.8 ms
f2s.com: 20.8 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)
gmd.de: 61.5 ms
club-internet.fr: 50.3 ms
eu.uu.net: 50 ms
tux.cprm.net: 97.5 ms
Your ping times are slightly poorer than expected.
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: 178 ms
cs.columbia.edu: 92.8 ms
upenn.edu: 23 ms
cs.columbia.edu: 88.3 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)
stanford.edu: 322 ms
limestone.uoregon.edu: 203.5 ms
limestone.uoregon.edu: 200.5 ms
oregonstate.edu: 203.5 ms
This result is much poorer than expected and should be investigated.
Test 5: Ping times to east Asia servers
Ideally, you should get a result of around 300 ms (lower is better)
opensourcecommunity.ph: 408.7 ms
meisei-u.ac.jp: 314 ms
apache.oss.eznetsols.org: 496.3 ms
meisei-u.ac.jp: 311.3 ms
Your ping times are slightly poorer than expected.
Test 6: Ping times to Australian servers
Ideally, you should get a result of around 350 ms (lower is better)
bondinet.com: 389 ms
mirror.pacific.net.au: 402 ms
apache.ausgamers.com: 363.3 ms
bondinet.com: 402 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)
sai.msu.su: 83.5 ms
apache.fresh.co.il: 218 ms
apache.rinet.ru: 70.3 ms
apache.rin.ru: 75.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 3072 Kb/s (higher is better)
apache.mirror.positive-internet.com: 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 3072 Kb/s (higher is better)
fr2.rpmfind.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 3072 Kb/s (higher is better)
apache.247available.com: 1167 Kb/s
This result shows serious problems with your downloads, and should be investigated.
Test 11: Upload speeds to the Speed Test Server
Ideally, you should get a result of around 300 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)
worcester.ac.uk: 2 %
vantage.myby.co.uk: 0 %
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)
lycos.es: 0 %
club-internet.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)
nyi.net: 0 %
ibiblio.org: 42 %
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 11/10/2006 10:14:22 using test version 3.0.316 - unregistered COPY
My computer is an Acer 5672WMLi
Network cards:
Broadcom Netlink ™ Gigabite Ethernet
Intel® Pro/Wireless 3945ABG Network Connection
Router: Netgear 54 Mbps Wireless Router WGR614v4 - latest firmware installed
It doesn't make any difference whether I'm using wireless or the ethernet cable.
If anyone could give me any advice on what to do it would be much appreciated.