Been getting lots of timeouts with different sites and everything is soooo slow! Just like the good old 56k days:(
Is it just me?
WB.
All fine here… Its you mate.
Ad Aware and Spydoctor run clean?
Seems fine for me as well Whiskey.
My ISP is BT.
:rolleye: WB broke teh interweb
Nope I see frequent timeouts when opening using multiple browser windows, I am on a 4.5mb/0.5mb line here. I blame all of the BBC I-player/watch again type services, and of course Radio online (which I am guilty of :o)
Could also be how many people you have locally (contention ratio), typically its between 30-50.
Classic makes a good point about BBC iplayer adding traffic as it has added interest for all the oldies/Richard and Judy mob, who previously thought tinterweb was only for geeks and pervs like you downloading pR0n… :roflmao:
Perhaps a listing of what sites are giving difficulties might help.
AAA, SAS, SimHQ, BBC News, Amazon, LloydsBank, Yahoo Mail, play.com
Some struggle then work OK others just won’t start.
My laptop seems to be having the same trouble so it’s probably not a PC issue. Perhaps it’s an ISP issue? I’m on BT and have had no problems with them so far. A router reboot doesn’t seem to have had any effect.
Firefox or IE make no difference although Firefox says address not found so I wonder if there’s a problem with a domain address server thingy somewhere
Strange.
WB.
ok, to eliminate the possibility of DNS failures try
That should bring up the Simhq apache server page near instantly if it doesnt, then DNS is not the issue, most likely a routing issue on BT’s part
go into a DOS window/CMD prompt and type:
tracert www.bbc.co.uk (or whatever site you’re having problems with)
Microsoft Windows [Version 6.0.6002]
Copyright © 2006 Microsoft Corporation. All rights reserved.C:\Users\Admin>tracert www.yahoo.com
Tracing route to www-real.wa1.b.yahoo.com [87.248.113.14]
over a maximum of 30 hops:1 6 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 21 ms 21 ms 21 ms 217.47.112.186
3 20 ms 20 ms 20 ms 217.47.112.161
4 21 ms 21 ms 20 ms 217.47.112.6
5 20 ms 19 ms 20 ms 217.41.175.25
6 20 ms 20 ms 20 ms 217.41.175.130
7 20 ms 19 ms 20 ms 217.41.219.42
8 19 ms 20 ms 20 ms 217.47.154.58
9 20 ms 20 ms 20 ms core1-pos7-0.bletchley.ukcore.bt.net [194.72.31.
145]
10 23 ms 22 ms 22 ms core3-pos0-8-0-10.ealing.ukcore.bt.net [62.6.201
.65]
11 21 ms 23 ms 22 ms core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.6
5.122]
12 22 ms 23 ms 23 ms 194.74.65.34
13 32 ms 32 ms 33 ms so-0-1-0.msr1.ird.yahoo.com [66.196.65.33]
14 34 ms 34 ms 33 ms gi-1-3.bas-b2.ird.yahoo.com [87.248.101.7]
15 34 ms 33 ms 32 ms f1.us.www.vip.ird.yahoo.com [87.248.113.14]Trace complete.
It’ll say how many hops its taking through the internet and which hop is causing the delay, providing the sites don’t have ICMP packets turned off.
It could be a DNS problem as well.
Did like Sporran says and the page was instant.
The tracert gave me a readout in a DOS Box like Keets’ quote above. However, there was anything from 2 to 7 to 20 secs between each step until eventually the dos box closed without completing the process?
WB.
Don’t use a CMD.exe prompt, should have made that clear.
Start -> Accessories -> Command Prompt
Do it for several of the sites and see if the long delay is common among the hops. Are you sure its seconds and not milli-seconds?
Seems to be OK now. Must have been an ISP glitch I reckon.
Cheers all,
WB.
Too many pornsurfers during lunchbreak around there, I’m afraid, WB…
Everyone watching the new Rammstein video. 