Netgear DG834G V4 - websites taking longer to load

hi changed my netgear DG834G v3 today for the version v4 as should be better for my line.

At the moment websites are taking longer to load than on the v3. the v4 as sycned higher. ip profile still the same at the moment , what could be causing this.


i have done a factory reset then updated the v4 to the latest firmware, no luck

one thing that did look odd to me in the router page , then router status (left hand side) , under the main heading router status, sub heading modem, it says modem firmware version A2pB023b.d20e.

Under the main heading router status says The firmware version is V5.01.16

As it is syncing higher it is possible you are getting an increased number of errors that it is having to deal with.

Or possibly a DNS issue? Had you changed DNS servers on the old one but not on the new?

gets the dns from the isp , some websites take ages to load other will not load at all

If you swap back to the v3, is everything all right? We just need to check it isn't a problem elsewhere .

is the MTU set the same on both old a new router?

( i have now logged in , could not remember my details yesterday )

the same is happening on the v3 as the v4, the MTU are the same (1458)

edit 8.10 pm also the same on my dlink router also having random problems to other sites like isp review , moneysaving expert, there must be a problem on the network?

since yesterday morning i am having problems loading. the following

www.bbc.co.uk/news
www.ebay.co.uk
https://login.yahoo.com/config/mail?&.src=ym&.intl=uk

sometimes they have loaded ok other times completely timed out, took 30 seconds to load or loaded on a refresh.

when i do i speed i get around 2.8mb (3000 profile) , xbox live working fine , iplayer , 4od , sky player all working .

i have the same problem on my pc and laptop

here are trace route to www.bbc.co.uk , www.ebay.co.uk, www.yahoo.co.uk ,
it will not let me do a trace route for sub pages like www.bbc.co.uk/news, comes back with
"Unable to resolve target system name www.bbc.co.uk/news."

C:\Users\Home User>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:

1 10 ms 2 ms 2 ms www.routerlogin.com [192.168.0.1]
2 34 ms 29 ms 30 ms 217.47.110.58
3 29 ms 28 ms 28 ms 217.47.110.161
4 28 ms 30 ms 28 ms 217.47.73.170
5 29 ms 28 ms 29 ms 217.47.73.35
6 28 ms 29 ms 28 ms core1-pos12-3.sheffield.ukcore.bt.net [217.32.17
1.249]
7 35 ms 34 ms 35 ms core1-pos0-14-5-0.ealing.ukcore.bt.net [62.172.1
03.109]
8 35 ms 34 ms 34 ms peer2-xe2-0-0.telehouse.ukcore.bt.net [109.159.2
54.106]
9 35 ms 34 ms 35 ms 194.74.65.42
10 34 ms 34 ms 34 ms 212.58.238.153
11 37 ms 36 ms 36 ms te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
12 39 ms 38 ms 39 ms 212.58.255.12
13 36 ms 37 ms 39 ms bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]


C:\Users\Home User>tracert www.yahoo.co.uk

Tracing route to any-rc.a01.yahoodns.net [77.238.178.122]
over a maximum of 30 hops:

1 20 ms 2 ms 2 ms www.routerlogin.com [192.168.0.1]
2 29 ms 29 ms 32 ms 217.47.110.58
3 29 ms 28 ms 29 ms 217.47.110.161
4 29 ms 28 ms 28 ms 217.47.73.170
5 29 ms 28 ms 29 ms 217.47.73.58
6 31 ms 28 ms 29 ms core1-pos12-2.sheffield.ukcore.bt.net [217.32.17
1.241]
7 * * * Request timed out.
8 35 ms 35 ms 69 ms peer1-xe0-0-0.telehouse.ukcore.bt.net [109.159.2
54.96]
9 34 ms 36 ms 35 ms ge-1-1-0.pat1.the.yahoo.com [195.66.224.129]
10 49 ms 110 ms 49 ms UNKNOWN-66-196-65-X.yahoo.com [66.196.65.17]
11 48 ms 47 ms 47 ms ae-1.msr1.ird.yahoo.com [66.196.67.231]
12 48 ms 51 ms 49 ms te-7-4.bas-b2.ird.yahoo.com [87.248.101.105]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


C:\Users\Home User>tracert www.ebay.co.uk

Tracing route to www.intl.ebay.com [66.135.200.182]
over a maximum of 30 hops:

1 9 ms 2 ms 2 ms www.routerlogin.com [192.168.0.1]
2 52 ms 28 ms 29 ms 217.47.110.58
3 28 ms 27 ms 29 ms 217.47.110.161
4 30 ms 29 ms 28 ms 217.47.73.170
5 29 ms 29 ms 28 ms 217.47.73.59
6 30 ms 29 ms 28 ms core1-pos12-3.sheffield.ukcore.bt.net [217.32.17
1.249]
7 * * * Request timed out.
8 39 ms 38 ms 38 ms core2-te0-5-0-0-1.ealing.ukcore.bt.net [194.74.6
5.138]
9 35 ms 34 ms 34 ms core2-pos1-0-0.telehouse.ukcore.bt.net [62.6.201
.86]
10 37 ms 37 ms 36 ms t2as2-tge4-3.uk-lon1.eu.bt.net [166.49.214.145]

11 35 ms 36 ms 35 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.17]
12 125 ms 119 ms 120 ms 195.66.224.130
13 116 ms 114 ms 119 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
14 134 ms 134 ms 134 ms 207.88.14.62.ptr.us.xo.net [207.88.14.62]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


does anything appear to be wrong my ISP is postoffice

Edited by deleted (Wed 26-Oct-11 20:12:08)

Looks like DNS. What servers are you using? Try google or OpenDNS servers.

It's unlikely to be the ISP as it's just a white-labelled BT network.

obtaining automatically from isp , is it safe to use google and open dns servers for things like banking and shopping online? i assume best to change within the router rather than each pc?

Edited by deleted (Wed 26-Oct-11 20:32:09)

Yes, quite safe but you may as well change them on a PC first to see if that's what the problem is.

i will change the dns tomorrow , ty for your help

if its the DNS , how should the post office be sorting this?

You could look up the IP addys of the slow websites, say by ping or tracert, and put these into your browser. If they now load faster then it is certainly a DNS issue and you are advised to change them as previously advised.

If it's any help to anyone, i am on P.O. but not seeing any browsing issues here.
The P.O. DNS seems to be working fine for all those sites mentioned,

I am on a different gateway to you (your first hop after router), though not too far away.

My eBay trace also fails at that point, but no problems at all browsing the site, very fast

I am using the standard P.O. DNS:

Primary DNS: 194.74.65.69
Secondary DNS: 62.6.40.178


The ping to your first hop looks a little on the high side, perhaps interleaving has been switched on for your line?

all seems to be back to normal now.

at about 10.10 pm last night i decided to try one last thing ( after having 3 routers on the line) i changed the adsl cable and all sites that i could not load all started working again , not sure if that was coincidence or had something to do with it ? , many thanks

edit i now have the netgetgear dg834g v4 on my line instead of the v3, stats from v4

ADSL Link Downstream Upstream
Connection Speed 4800 kbps 448 kbps
Line Attenuation 39.0 db 20.5 db
Noise Margin 9.1 db 20.0 db


before i had problems ( getting to some websites ) the v4 stayed synced at 48000 for over 24hrs best could get on the v3 was 3900 , if i can get my snr down to 6db should i be able to get a bit more from my line.

i have interleaving turned on, is my line stable enough to have it turned off.

Edited by deleted (Thu 27-Oct-11 15:17:46)