I got an email from Cajun saying that its something to do with Xtra's servers not communicating with the site and that he hoped to have it sorted today.
I got a similar call from Telecom, so hopefully this should be fixed later today.
I got an email from Cajun saying that its something to do with Xtra's servers not communicating with the site and that he hoped to have it sorted today.
I got a similar call from Telecom, so hopefully this should be fixed later today.
Before you judge a man, walk a mile in his shoes. After that, who cares? ...He's a mile away and you've got his shoes
same thing for me too been 3 days.
we all know if something was wrong, the KB tech team will have it sorted in no time
BUT
being an xtra problem well to use the statment "Christmas is comming" maybe over-rated
Thanks to Cajun & his tech know-how information
followed by another call to xtra, they revealed they are looking into their problem
asked Mom if I was a gifted child ... she said they certainly wouldn't have paid for me.
I'm on Xtra, and haven't had any problems.....
"It would be spiteful, to put jellyfish in a trifle."\m/ o.o \m/
A few of us are having issues when logged in by our user IDs but no issues as anonymous or by another user ID on the same computer and internet connection. Seems to be pretty ramdom and not one specific ISP looking at the above posts.
Last edited by Bonez; 8th December 2008 at 16:56.
i went to work and that fixed the problem
Well....still doesn't work at home.... grumble mutter etc![]()
Before you judge a man, walk a mile in his shoes. After that, who cares? ...He's a mile away and you've got his shoes
Connected via www.grandproxy.com seems ok this way,xtra sux at times.
Hello officer put it on my tab
Don't steal the government hates competition.
Restarted the server. If that helps I'll be surprised.
If anyone is talking to Xtra ip banning was disabled along time ago so it's nothing to do with the server. Only real possibilities are that Xtra's routing from certain ip blocks is rooted or one of the hops along the way is being blocked/sending everything to the internet black hole.
It would be handy to know ip's for people having problems so if everyone having problems could pm me their ip address it'd help. Ta.
You get your ip address by doing:
- Start menu
- Run...
- cmd
- ipconfig
That won't be useful for some people (as pointed out below), ie those whose ip numbers start with 192.168. or 10., so a tracert would be useful as well:
- Start menu
- Run...
- cmd
- tracert www.kiwibiker.co.nz
Zen wisdom: No matter what happens, somebody will find a way to take it too seriously. - obviously had KB in mind when he came up with that gem
Artificial intelligence is no match for natural stupidity
Won't work if you're behind a router.
I'll PM you a tracert when I get home, and the router IP.
Originally Posted by skidmark
Originally Posted by Phil Vincent
Seems to be leaving Telecom OK
C:\Documents and Settings\Owner>tracert www.kiwibiker.co.nz
Tracing route to www.kiwibiker.co.nz [216.237.127.134]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.123.254
2 3 ms 2 ms 2 ms 192.168.1.1
3 28 ms 16 ms 13 ms 219-89-49-1.dialup.xtra.co.nz [219.89.49.1]
4 * * * Request timed out.
5 14 ms 15 ms 15 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.2
44.221]
6 17 ms 18 ms 13 ms xe0-0-0-2.akbr4.global-gateway.net.nz [202.50.23
2.77]
7 22 ms 20 ms 18 ms so1-2-0.tkbr9.global-gateway.net.nz [203.96.120.
74]
8 140 ms 139 ms 168 ms so0-3-1.labr5.global-gateway.net.nz [202.50.232.
254]
9 141 ms 142 ms 138 ms so-1-0-0.lebr6.global-gateway.net.nz [202.50.232
.237]
10 144 ms 142 ms 135 ms gi1-3.mpd01.lax05.atlas.cogentco.com [154.54.13.
121]
11 171 ms 173 ms 175 ms te4-2.mpd01.lax01.atlas.cogentco.com [154.54.6.2
29]
12 174 ms 171 ms 182 ms te4-1.mpd01.sjc01.atlas.cogentco.com [154.54.6.3
0]
13 180 ms 264 ms 177 ms te4-3.mpd01.sjc05.atlas.cogentco.com [154.54.6.7
4]
14 180 ms 172 ms 175 ms infortech-corp.demarc.cogentco.com [38.104.134.5
0]
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 * 182 ms * 216-237-127-134.infortech.net [216.237.127.134]
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.
Originally Posted by Albert
Talking to Telecom Technical Support about it, but they say they have only had one complaint about this. If more people call Telecom and log a fault, then they'll give it more attention and will also be able to track the problem better.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks