"Looking up..." Delay

[net91]

I've tried the test router a little on Friday and I think there was an improvement, although due to the intermittent nature of the problem I can't really be sure. Anyway I'm going to compare my router and the test router all day today, seems it needs to be sent back tomorrow. I'll post how it goes here.

[Simon]

Cheers, Dan! 

[Rik]

Dan, make sure that you don't force more than 10 re-syncs in an hour by swapping the routers, or you are likely to trigger an increase in your d/s noise margin.

[net91]

I've just put IDNET's router in place of mine so it's connected to everything mine was (except I've left a spare ethernet cable from it for a laptop to be connected to it in place of the wireless on my router) and I'm going to leave it there all day now to test it thouroughly. I've also swapped the filter and RJ11 cable that connects to it just to rule that out.

In a way I sort of hope I find I can blame my router because then I can just replace it and finally solve this issue. What is the average life of a router (mine is about a year old)?

[Sebby]

It would certainly be better if it was the router.

[Lance]

My Linksys started causing problems after only a year, which is when I moved to the wonderful 2700HGV!

[Sebby]

I've never liked Linksys routers...

[net91]

How long have you been using your 2700HGV Lance?

[Lance]

I've never liked Linksys routers...

Me neither!

How long have you been using your 2700HGV Lance?

I've just had a look back at the thread I started when I got it, and it was the 18th July, last year! I've since gone from the old hardware to the newer (dual SSID) hardware, but both are as reliable as each other.

[net91]

Thanks Lance. It's something to think about since I may be replacing my router soon.

[Rik]

Another 2700 fn here, Dan. Faster sync, less noise susceptibility, far more reliable.

[net91]

It would seem that it was my router causing the problem as I've not run into any major delays while using the router from IDNet over yesterday and this morning.

There where a few sites I had slight problems with, but due to previous problems with them (see previous posts on this thread), I think it is down to those sites. I did notice that I didn't have the issue if I visited the sites again shortly after. The sites and ping results for them are below;
(They're all all links from the Google News page.)




<sub>http://news.xinhuanet.com/english/2008-08/04/content_8953161.htm

Ping has started ...

PING a1051.g.akamai.net (84.53.137.34): 56 data bytes
64 bytes from 84.53.137.34: icmp_seq=0 ttl=59 time=24.215 ms
64 bytes from 84.53.137.34: icmp_seq=1 ttl=59 time=23.723 ms
64 bytes from 84.53.137.34: icmp_seq=2 ttl=59 time=29.572 ms
64 bytes from 84.53.137.34: icmp_seq=3 ttl=59 time=23.615 ms
64 bytes from 84.53.137.34: icmp_seq=4 ttl=59 time=33.924 ms
64 bytes from 84.53.137.34: icmp_seq=5 ttl=59 time=22.966 ms
64 bytes from 84.53.137.34: icmp_seq=6 ttl=59 time=23.421 ms
64 bytes from 84.53.137.34: icmp_seq=7 ttl=59 time=24.610 ms
64 bytes from 84.53.137.34: icmp_seq=8 ttl=59 time=23.851 ms
64 bytes from 84.53.137.34: icmp_seq=9 ttl=59 time=30.203 ms

--- a1051.g.akamai.net ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 22.966/26.010/33.924/3.601 ms




http://www.teletext.co.uk

Ping has started ...

PING www.teletext.co.uk (213.165.3.20): 56 data bytes

--- www.teletext.co.uk ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss




http://www.enews20.com/news_Almost_150_Dead_In_Temple_Stampede_In_India_10057.html

Ping has started ...

PING www.l.enews20.com (83.246.75.249): 56 data bytes

--- www.l.enews20.com ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss</sub>



Anyway I think this leaves me with a simple solution to the problem - get a new router.



Thanks to everyone who has helped with this.

 

[Simon]

Good news, Dan! 

[Rik]

Glad you got there, Dan. 

[Lance]

Great stuff, Dan! 

[Sebby]

Goods news. It's certainly easier when it's the router that's to blame.

[net91]

Yes I'm glad I can just replace my router, it's a nice simple solution.

Again thanks to everyone.