SpankMe - KB server timing out problem? 22/1/07

**crashe** · 22nd January 2007, 17:49

Originally Posted by KB

The connection has timed out

The server at www.kiwibiker.co.nz is taking too long to respond.

* The site could be temporarily unavailable or too busy. Try again in a few moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

SpankMe,

This has been happening alot this afternoon and this evening.....

I even shut the comp down and restarted it up to see if that would sort it out.

No other websites that I am browsing is having this problem.

Im just bringing it to your attention...... so that it can be sorted out.

Cheers.

PS: I am on Dial up but that should not be a issue to this problem.

**Blairos** · 22nd January 2007, 17:55

No problems here!

**SpankMe** · 22nd January 2007, 17:58

Server has been running fine all day. More likly to be one of the gateway servers between you and the KB server.

As an example, here is how many servers I have to go through to get to the KB server from my XTRA connection.

[root]$ traceroute kiwibiker.co.nz
traceroute to kiwibiker.co.nz (216.237.127.130), 30 hops max, 38 byte packets
1 * * *
2 210-55-64-64.adsl.netgate.net.nz (210.55.64.64) 46.772 ms 45.032 ms 44.558 ms
3 210.55.205.189 (210.55.205.189) 79.427 ms 128.361 ms 157.489 ms
4 fid-int.tkbr4.global-gateway.net.nz (202.50.245.198) 53.831 ms 99.777 ms 100.849 ms
5 vlan-283.tkbr4.global-gateway.net.nz (202.50.245.197) 58.018 ms 55.748 ms 58.370 ms
6 * * *
7 so3-0-0.akbr3.global-gateway.net.nz (203.96.120.193) 73.278 ms so-0-2-0.akbr3.global-gateway.net.nz (202.50.232.33) 53.710 ms 202.50.232.165 (202.50.232.165) 55.737 ms
8 p2-0.sjbr1.global-gateway.net.nz (203.96.120.202) 233.855 ms p6-3.sjbr1.global-gateway.net.nz (203.96.120.82) 234.119 ms 231.730 ms
9 so-3-0-0.pabr3.global-gateway.net.nz (210.55.202.194) 233.518 ms 234.766 ms 235.931 ms
10 206.111.12.141.ptr.us.xo.net (206.111.12.141) 233.991 ms 232.755 ms 237.900 ms
11 p5-2-0.RAR2.SanJose-CA.us.xo.net (65.106.5.177) 235.387 ms 237.683 ms 234.507 ms
12 p0-0-0.MAR2.Fremont-CA.us.xo.net (65.106.5.138) 236.352 ms 236.594 ms 235.395 ms
13 p15-0.CHR1.Fremont-CA.us.xo.net (207.88.80.182) 234.467 ms 235.642 ms 238.082 ms
14 207.88.3.58.ptr.us.xo.net (207.88.3.58) 237.289 ms 236.191 ms 235.448 ms
15 core-01.ge-6-8.sjc1.gni.com (69.80.192.49) 237.930 ms 238.164 ms 238.415 ms
16 69.80.192.90 (69.80.192.90) 247.963 ms 281.761 ms 323.868 ms
17 216-237-127-130.infortech.net (216.237.127.130) 330.058 ms !<10> 280.492 ms !<10> 331.833 ms !<10>
[root]$

Only takes one of them to be playing up.

**crashe** · 22nd January 2007, 18:07

cheers SpankMe...... no idea what all that means

But it has taken me, 5 goes, to get back into this thread again since you posted up on it.... I even had to open up another KB browser to attempt to get in here...... as it kept on 'timing out' all the time.

Blardy frustrating....... !

It was working fine this morning........

**onearmedbandit** · 22nd January 2007, 18:20

He's saying it not's KB's problem, nor your computer. The problem probably lies with one of the 'gateway' servers your particular connection goes through to get to KB.

**crashe** · 22nd January 2007, 21:52

Ta, I realise that.......

Just saying how blardy frustrating it is...

I turned the comp off for a few hours...... came back and still having probs....

So will try again tomorrow........

**onearmedbandit** · 22nd January 2007, 21:58

Not a KB issue though.

**crashe** · 22nd January 2007, 22:10

yep guys I realise it aint a KB issue once SpankMe expained it... in his post above..

Im one of the non comp geek's that dont fully understand the jibber jabber words when he showed the routes used to get throu all the servers etc......

but I did understand what he meant......

There are just times when you want to throw the comp out the window.....