"Looking Up/Contacting" Slow when switching between webpages.

[Rik]

Let me know how your Mac goes with the switch, will you?

[merlin]

if you are using vista, and recently changed to AVG version 8, this will introduce a 15 second delay on web pages ,

the problem is in vista ,and the patch for it is KB929547, although looking at other forums ,this patch is difficult to install, it certainly wants microsoft validation first.

it seem most people with this situation have gone back to AVG 7.5

suggest you google KB929547, it will explain it better than i.

[Rik]

Thanks for that, Bob. 

[net91]

if you are using vista, and recently changed to AVG version 8, this will introduce a 15 second delay on web pages ,

the problem is in vista ,and the patch for it is KB929547, although looking at other forums ,this patch is difficult to install, it certainly wants microsoft validation first.

it seem most people with this situation have gone back to AVG 7.5

suggest you google KB929547, it will explain it better than i.

The Windows Vista machine I have been using still has AVG 7.5 installed on it.

[net91]

Let me know how your Mac goes with the switch, will you?

I have changed the DNS setting on my router to the ones IDNET suggested I use. I have been browsing the web on my mac machine since I have done this and have not came across the problem so far. I will test it tomorrow some more to ensure the connection is ok with these settings.

Thanks
net91

[madasahatter]

if you are using vista, and recently changed to AVG version 8, this will introduce a 15 second delay on web pages ,

the problem is in vista ,and the patch for it is KB929547, although looking at other forums ,this patch is difficult to install, it certainly wants microsoft validation first.

it seem most people with this situation have gone back to AVG 7.5

suggest you google KB929547, it will explain it better than i.

that's strange - I've updated to AVG 8 on both my desktop and lappy - both run Vista, and neither have such a problem 

Would seem that this issue only affects in certain circumstances.

[merlin]

that's strange - I've updated to AVG 8 on both my desktop and lappy - both run Vista, and neither have such a problem 

Would seem that this issue only affects in certain circumstances.

HOOBS GET ALL THE LUCK !!!

[Rik]

I've had the results of IDNet's testing through, the graph can be seen at:

http://www.idnet.net/misc/resolvertimes/stats.html

The first graph (resolver0.idnet.net) is 212.69.36.3 and the second graph is 212.69.40.3. The last two graphs are OpenDNS.

The tests were run from a personal linux box over a regular max premium ADSL line, ie not within the IDNet infrastructure.

From IDNet:

"If changing details has improved things for people I would guess its either their windows dns cache has got messed up and
changing has forced it to rebuild or there are other reasons they are having problems. Manually specifying dns details on individual machines will always help anyway. resolver1.idnet.net as mentioned is in same rack as our ADSL connections terminate so is always going to be very slightly quicker to respond.

Also it depends on how they were doing their testing, the testing we have done is done on scientific principles i.e. all the variables are the same, the client is a raw client (does no fancy graphics or anything else that could affect the results) and there is no local caching anywhere (dns resolvers are, by design, caches of the dns of the whole internet).

If anyone with a linux box wants to duplicate my tests Hobbit can be downloaded and installed easily and the config needed to add to the bb-hosts file is as follows:

212.69.36.3   resolver0.idnet.net # conn dns ssh
212.69.40.3   resolver1.idnet.net # conn dns ssh
212.69.36.2   ns0.idnet.net       # conn dns ssh
212.69.40.2   ns1.idnet.net       # conn dns ssh
208.67.222.222 resolver1.opendns.com # conn dns
208.67.220.220 resolver0.opendns.com # conn dns

Mandriva - urpmi hobbit
Ubuntu   - http://packages.ubuntu.com/hardy/net/hobbit
General  - http://hobbitmon.sourceforge.net/docs/install.html"

[Steve]

So are we supposed to use 40.3 as the primary or 36.3 on the local machine? It confirms the relative sluggish ness of open dns

[Rik]

The suggestion is that 36.3, the primary, is showing as consistently faster in testing (which is ongoing, btw), and that it should be used in the normal order given.

[Steve]

Thanks Rik,

[madasahatter]

HOOBS GET ALL THE LUCK !!!

Want to come join us then? 

[net91]

The suggestion is that 36.3, the primary, is showing as consistently faster in testing (which is ongoing, btw), and that it should be used in the normal order given.

Does this mean that this problem is not caused by IDNET's dns servers?

[Rik]

They can't see a problem with them, based on the testing so far.

[net91]

Ok, so do we just see how things go with the dns servers swapped?

[Rik]

For the time being, or contact support with specific examples if you continue to have problems.

[net91]

Ok thanks.

[Sebby]

I don't know if this has been mentioned, but perhaps a DNS resolver cache flush will work. From a command prompt in Windows, type ipconfig /flushdns and hit enter.

[Rik]

Certainly worth a try, Sebby. 

[Mark_Mac]

Just to add to this slowness conversation, I too have experience a real drop in web responses over the last couple of days.  An example is Digital Spy (www.digitalspy.co.uk) gets timed out, some sites do response but MUCH slower than normally.  Weird thing is a few sites are responding completely fine.

Clearly this problem is affecting certain 'internet routes' (correct term?) rather than everything.

I am connected to the Sheerness exchange in Kent.

Looking at Rik's advice from earlier on, I have changed the DNS on my router from auto to 208.67.222.222 and 208.67.220.220.  However I haven't noticed any difference.

PS I'm on a Intel iMac running Leopard with an Netgear ADSL router.

Cheers in advance for any advice.

Mark

[net91]

Just to add to this slowness conversation, I too have experience a real drop in web responses over the last couple of days.  An example is Digital Spy (www.digitalspy.co.uk) gets timed out, some sites do response but MUCH slower than normally.  Weird thing is a few sites are responding completely fine.

Clearly this problem is affecting certain 'internet routes' (correct term?) rather than everything.

I am connected to the Sheerness exchange in Kent.

Looking at Rik's advice from earlier on, I have changed the DNS on my router from auto to 208.67.222.222 and 208.67.220.220.  However I haven't noticed any difference.

PS I'm on a Intel iMac running Leopard with an Netgear ADSL router.

Cheers in advance for any advice.

Mark

That problem does sound exactly like mine. It also sounds like we have very similar set ups; I also have a Intel iMac running Leopard with a Netgear ADSL router. Altough I am in Lincolnshire so I doubt we are going through the same exchange (I'm not sure what one I'm on).

Those DNS addresses are Open DNS's which I am running on my mac machine at the moment and they seem to be fine. Are you also running ok with these?

[Sebby]

This is very odd. I visit Digital Spy almost daily and haven't noticed any slowness. I'm using OpenDNS, by the way. The only slowness I've noticed is on this forum, but that's believed to be something else.

Perhaps it's a Mac thing? Can you flush the DNS cache? (No idea how to do it on a Mac!)

[Mark_Mac]

Hi

Thanks for quick replies.

Yep I am using OpenDNS (although I'm not sure which way the values go in - Primary and Secondary). However I have tried both ways and the result is the same, no response from Digital Spy, slowness on some sites, absolutely fine on other sites.

Not sure how to flush DNS on Mac, I'm guessing via Terminal.

PS - just found this (http://www.tech-faq.com/flush-dns.shtml) that includes Mac support.  Didn't work on my Terminal even when using 'sudo' command (root/super user). Got a 'dnscacheutil: command not found' response. If anyone reading this and is an network expect on Mac, please help.

Cheers

Mark

[lozcart]

To clear the cache on your Mac running Leopard launch Terminal (in your utilities folder) type
dscacheutil -flushcache and hit return.

Mark, it might also be worth you entering the OpenDNS servers into your network settings on the computer.

[Simon]

Hi Mark, seems we missed your welcome Karma point, so