Haven't been able to log into SM for a few days now has anything been changed with the server setup?
This is affecting quite a few of us here on different ISPs.
This is affecting quite a few of us here on different ISPs.
*SM Access problem in Australia*
- Thread starter IJ.
- Start date
naaa, ive been logging on fine, maybe it is that part of the backbone of the net.
i've been hearing something about a certain company that got pissed at another company and closed part of their backbone for a while, but just a guess.
have you tried clearing ur cache for ur browser? and do u use mozilla, FireFox.
i've been hearing something about a certain company that got pissed at another company and closed part of their backbone for a while, but just a guess.
have you tried clearing ur cache for ur browser? and do u use mozilla, FireFox.
IJ. said:Mario: Yep tried all the usual "tricks"
did it just know like start working?
and can you log onto anything else, other forums? or email?
SM is the only site affected
I can't access it at all unless I route through http://anonymouse.org/
and doing it this way it's slow as ....
I can't access it at all unless I route through http://anonymouse.org/
and doing it this way it's slow as ....
then something is blocking you from SM, check and see if like windows firewall (i assume ur using windows? and its either Xp or 2k) is blocking it, i have had this problem before, for some reason windows randomly blocks stuff.
also what browser are u useing?
also what browser are u useing?
Using IE and it's not just me or my system there's a bunch of us here in Australia all on different ISP's that can't access SM!
(it's a conspiricy I'm sure of it! hang on there's been a chopper flying overhead the last few nights I wonder if it's black? now where's that tinfoil I need to make a hat)
(it's a conspiricy I'm sure of it! hang on there's been a chopper flying overhead the last few nights I wonder if it's black? now where's that tinfoil I need to make a hat)
Mike has been talking about moving us to another server... I hadn't checked to see if the IP has changed, but that might be it. I could see the DNS servers updating slower over there - especially if the change started in the US.
well their's your missing factor!
and use plastic rap for the inside of the helmet, it helps cause the tin foil will start to bother you.
and use plastic rap for the inside of the helmet, it helps cause the tin foil will start to bother you.
Dave: Can you check the IP please?
(mine is trying for 208.186.130.196)
Mario: Check got it plastic liner for tinfoil hat!
(mine is trying for 208.186.130.196)
Mario: Check got it plastic liner for tinfoil hat!
That's the correct IP address for the current server.
I have no idea why you cannot connect, I don't think it's anything on our end...
I was having the same problem myself actually, but with Supraforums, a couple weeks ago... it lasted for about 7-8 days until it finally started working normally again.... weird.
I have no idea why you cannot connect, I don't think it's anything on our end...
I was having the same problem myself actually, but with Supraforums, a couple weeks ago... it lasted for about 7-8 days until it finally started working normally again.... weird.
Hi Jeff,
Just received this from my ISP minutes ago>>
Dear Ian,
Thank you for your enquiry.
There appears to be a block against OptusNet IP addresses accessing the website.
As this block is not on the OptusNet network our Engineers will not be able to resolve this issue, only the website administrator or hosting provider of the domain can do this.
Kind Regards,
Ben
OptusNet Cable Support
Tel: 1300 300 693
Just received this from my ISP minutes ago>>
Dear Ian,
Thank you for your enquiry.
There appears to be a block against OptusNet IP addresses accessing the website.
As this block is not on the OptusNet network our Engineers will not be able to resolve this issue, only the website administrator or hosting provider of the domain can do this.
Kind Regards,
Ben
OptusNet Cable Support
Tel: 1300 300 693
Mario: LOL they've blocked all of Australia as the 2 biggest competing ISP's both don't work !
Jeff thanks it'd be nice to have SM back!
(A mate's been blocked for a month now)
! Jeff thanks it'd be nice to have SM back
!(A mate's been blocked for a month now)
IJ. said:
Heh, that's me! Using mezzy.com to get to the site so I can post this. This might help you admin types a bit (and if you need anything else, just let me know). Here is a trace from my machine at work (took the first few hops out to protect security) and one from Optus' own we traceroute utility, and finally, one from an unaffected link here in Australia. So that's Comindico (kinda peer with Telstra and my own Telstra checks from home are identical), Optus and Connect. I'll point out the differences shortly.
COMINDICO/SPTcom/Telstra:
Tracing route to www.supramania.com [208.186.130.196]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ********
2 2 ms 2 ms 1 ms ********
3 7 ms 3 ms 2 ms ********
4 3 ms 1 ms 1 ms ********
5 2 ms 2 ms 2 ms ********
6 2 ms 1 ms 1 ms ge6-2.cor01-dryb-mel.comindico.com.au [203.194.56.61]
7 14 ms 14 ms 14 ms pos2-2.cor02-kent-syd.comindico.com.au [203.194.1.1]
8 14 ms 14 ms 14 ms ge3-1.bdr02-kent-syd.comindico.com.au [203.194.25.41]
9 15 ms 16 ms 15 ms unknown.net.reach.com [134.159.123.245]
10 174 ms 174 ms 173 ms i-1-3.paix-core01.net.reach.com [202.84.249.33]
11 174 ms 174 ms 175 ms i-3-1.paix04.net.reach.com [202.84.251.20]
12 * * * Request timed out.
13 177 ms 176 ms 177 ms p7-0.cr01.sntd.eli.net [207.173.114.137]
14 176 ms 176 ms 176 ms srp3-0.cr02.sntd.eli.net [208.186.21.34]
15 186 ms 185 ms 185 ms p9-0.cr01.lsan.eli.net [207.173.114.53]
16 188 ms 186 ms 186 ms srp3-0.cr02.lsan.eli.net [208.186.20.210]
17 196 ms 193 ms 193 ms p9-0.cr01.lsvl.eli.net [207.173.114.33]
18 193 ms 192 ms 193 ms ge1-1.gw01.lsvg.eli.net [207.173.114.74]
19 * * * Request timed out.
The rest are all "Request timed out" from here on
OPTUS:
Performing trace to www.supramania.com...
1 FastEth8-1-0.sb1.optus.net.au (192.168.34.2) 0.895 ms 0.496 ms 0.511 ms
2 203.208.148.101 (203.208.148.101) 158.617 ms 159.068 ms 154.654 ms
3 203.208.173.82 (203.208.173.82) 159.843 ms 159.924 ms ge-0-3-0.plapx-ar3.ix.singtel.com (203.208.168.114) 158.515 ms
4 * * *
5 p7-0.cr01.sntd.eli.net (207.173.114.137) 158.995 ms 160.294 ms 155.488 ms
6 srp3-0.cr02.sntd.eli.net (208.186.21.34) 160.538 ms 160.326 ms 155.259 ms
7 p9-0.cr01.lsan.eli.net (207.173.114.53) 169.313 ms 169.358 ms 167.838 ms
8 srp3-0.cr02.lsan.eli.net (208.186.20.210) 168.168 ms 164.493 ms 168.109 ms
9 p9-0.cr01.lsvl.eli.net (207.173.114.33) 177.034 ms 176.930 ms 172.019 ms
10 ge1-1.gw01.lsvg.eli.net (207.173.114.74) 172.165 ms 172.227 ms 177.032 ms
11 * * *
Times out from here on out
CONNECT:
traceroute to www.supramania.com (208.186.130.196), 30 hops max, 40 byte packets
1 fastethernet9-0-0.bdr2.syd.connect.com.au (192.189.54.55) 1.34 ms 0.885 ms 0.761 ms
2 ge-0-1-0.bdr5.syd.connect.com.au (203.63.11.202) 1.041 ms 0.971 ms 0.923 ms
3 p5-0.sybr3.global-gateway.net.nz (203.96.120.121) 0.975 ms 1.618 ms 2.237 ms
4 p1-1.sjbr1.global-gateway.net.nz (202.37.247.82) 159.223 ms 158.26 ms 158.673 ms
5 * * *
6 sl-st20-pa-6-2.sprintlink.net (144.223.243.49) 159.508 ms 158.945 ms 159.493 ms
7 sl-st20-pa-1-0.sprintlink.net (144.232.20.171) 159.291 ms 159.684 ms 159.23 ms
8 sl-eleclight-16-0.sprintlink.net (144.223.243.6) 154.229 ms 154.431 ms 155.365 ms
9 p7-0.cr02.sntd.eli.net (207.173.114.141) 160.314 ms 160.231 ms 161.46 ms
10 p9-0.cr01.lsan.eli.net (207.173.114.53) 169.639 ms 169.864 ms 169.554 ms
11 srp3-0.cr02.lsan.eli.net (208.186.20.210) 170.239 ms 169.794 ms 170.316 ms
12 p9-0.cr01.lsvl.eli.net (207.173.114.33) 178.768 ms 178.379 ms 177.806 ms
13 ge1-2.gw01.lsvg.eli.net (207.173.114.78) 176.74 ms 177.155 ms 177.236 ms
14 host.bard.net (208.186.130.196) 177.202 ms 177.08 ms 177.049 ms
Now for the important stuff - the routes on the links that don't work vs the one that does are completely different. In fact the second to last hop is probably the culprit. Sounds like that router has an advertised route that isn't correct. The could be physically different routers or different interfaces on the same device, either way, when packets come to that IP, the either don't come back or never reach the SM server.
Hope that helps!