@ Brett - did you try to reset your accesspoint, router and switch
I worked with Brett on this when he was having the problem a few days ago. What we found was that he could tracert all the way to the last hop (tinyclr.com). I could connect and when comparing my tracert to his the last 3-4 hops were identical except that I could reach the final IP. To me it sounds like a firewall issue that is either rejecting his IP or perhaps because heās across the pond the time to arrive is too long and perhaps you have something that is thinking his request may have been tampered with? Iām no network expert but we did prove that his route is definitely getting him to your server and the server is rejecting him.
What if Brett is a member of Annonymous trying to bring down TinyCLR servers?! Since he canāt get thru he tries to convince you to lower down your security level! 
@ Garlin
You joking right?
Iāve been called Random before, but never anonymous ![]()
I canāt repro the tracert path right now (Iām running on a 3g connection tethered through my phone and the telco has a transparent proxy that is blocking ICMP packets).
Hereās the tracert output when I was on my home ADSL:
[quote]Tracing route to tinyclr.com [207.58.176.213]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms home.gateway [192.168.2.254]
2 42 ms 44 ms 43 ms lns20.syd7.internode.on.net [150.101.199.219]
3 42 ms 47 ms 43 ms te3-3.cor2.syd7.internode.on.net [150.101.195.13]
4 201 ms 198 ms 200 ms gi6-0-0-104.bdr1.syd7.internode.on.net [150.101.197.113]
5 223 ms 224 ms 222 ms po3-0-0.bdr1.sjc2.internode.on.net [203.16.213.158]
6 225 ms 224 ms 224 ms ge13-1.br02.sjo01.pccwbtn.net [206.223.116.48]
7 273 ms 274 ms 278 ms servint.tenge10-3.br01.rst01.pccwbtn.net [63.218.125.22]
8 273 ms 274 ms 273 ms sc-smv2206.servint.net [209.50.237.198]
9 * * * Request timed out.
10 ^C
C:\Users>tracert www.tinyclr.com
[/quote]
As you can see, Iām on Internode ADSL service, it navigates over into the Servint.net network, and then times out. Iāll dump a trace from a different network that shows the last hops in the working scenario (it wonāt be from an internode network but you can see the ingress into the datacentre shows the same).
@ Gus, I havenāt forced a restart on my ADSL infrastructure, but I will tonight; the evidence I see today however does seem like the issue isnāt in my network - itās been a few years since I did my IP networking MCSE exam but I think when a trace gets that close to the host, the host and final steps in the datacentre are the most likely problem areas.
@ noob123 - You never know 
[quote]Tracing route to tinyclr.com [207.58.176.213]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 2 ms 2 ms 2 ms 053.016.dsl.syd.iprimus.net.au [210.50.54.53]
4 3 ms 3 ms 3 ms irb-5.bsr01.equ.iprimus.net.au [210.50.143.163]
5 139 ms 146 ms 139 ms xe-0-3-0.bsr01.sjc.iprimus.net.au [203.134.2.138]
6 139 ms 139 ms 142 ms xe-5-3-0.sjc12.ip4.tinet.net [173.241.128.13]
7 139 ms 140 ms 139 ms tenge10-3.br02.sjo01.pccwbtn.net [63.218.179.53]
8 215 ms 215 ms 215 ms servint.tenge10-3.br01.rst01.pccwbtn.net [63.218.125.22]
9 216 ms 216 ms 216 ms sc-smv2206.servint.net [209.50.237.198]
10 227 ms 225 ms 225 ms server.ghihost.com [207.58.176.213]
Trace complete.[/quote]
So everything is same-same once it hits this device:
servint.tenge10-3.br01.rst01.pccwbtn.net [63.218.125.22]
From home, still failing.
[quote]Tracing route to tinyclr.com [207.58.176.213]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms home.gateway [192.168.2.254]
2 48 ms 85 ms 80 ms lns20.syd7.internode.on.net [150.101.199.219]
3 46 ms 63 ms 42 ms te3-3.cor2.syd7.internode.on.net [150.101.195.13]
4 198 ms 198 ms 208 ms gi6-0-0-104.bdr1.syd7.internode.on.net [150.101.197.113]
5 224 ms 220 ms 220 ms po3-0-0.bdr1.sjc2.internode.on.net [203.16.213.158]
6 223 ms 237 ms 223 ms ge13-1.br02.sjo01.pccwbtn.net [206.223.116.48]
7 309 ms 621 ms 312 ms servint.tenge10-3.br01.rst01.pccwbtn.net [63.218.125.22]
8 273 ms 271 ms 278 ms sc-smv2206.servint.net [209.50.237.198]
9 * * * Request timed out.
10 * * * Request timed out.[/quote]
So, looks like my forum hours are numbered !
Edit: thatās after a total reet and restart on all the ADSL networking gear.
Weāre looking into it Brett.
@ josh - FYI, since Brett canāt check this thread to see your posts, you can usually get him on Twitter (@ brettpound).
Thanks
Today I have forum access problem. I see that problem here is the server s7.addthis.com where probably are sent some post from forum serverā¦
Josh, I hope you got my tweet reply. Donāt have a direct email for you and was āofflineā as Ian said. Iām temporarily able to access the site (via work). To get my fix over the weekend I think Iām going to have to go via work proxies 
Hey guys, another aussie got in touch with me and get canāt to your site(s). Rob Mawtson email is rmawston at live dot com dot au. Iām sure he would love to hear from GHI to try some troubleshooting.
Oh Rob, nice⦠Hey Rob, if you can see this ! Iāl lping you offline to talk about our access problems to see if theyāre similar.
Iām still in limbo; Running off a wifi hotspot again this morning. Josh, ping me if you have any thoughts (tweet me), I will probably be around most of the day.
Edit: just a reminder; this seems to be affecting the whole GHI web presence, including the catalog page, so I canāt buy anything 
Reached out to Rob to chat about this. Thereās not much in common Iām afraid.
[ Right now Iāve set myself up to work via a work proxy server, and that seems fine (while ever I can reach it via VPN/Direct Access). ]
Robās scenario is somewhat different. He connects from a single PC, and can access the site via a 3g network (as can I; weāre both using Telstra 3g service) but this fails via his home broadband.
Hereās his trace from 3g that works:
[quote]Tracing route to tinyclr.com [207.58.176.213]
over a maximum of 30 hops:
1 60 ms 172 ms 70 ms 172.18.211.19
2 54 ms 50 ms 46 ms 172.18.67.158
3 70 ms 55 ms 58 ms 172.18.240.233
4 76 ms 167 ms 71 ms Bundle-Ether10.win24.Melbourne.telstra.net [110.
142.226.41]
5 70 ms 83 ms 81 ms Bundle-Ether6.win-core1.melbourne.telstra.net [2
03.50.11.58]
6 174 ms 67 ms 58 ms Bundle-Pos3.ken-core4.Sydney.telstra.net [203.50
.11.12]
7 116 ms 67 ms 71 ms Bundle-Ether1.pad-gw2.Sydney.telstra.net [203.50
.6.29]
8 83 ms 65 ms 80 ms 203.50.13.118
9 280 ms 197 ms 211 ms i-0-1-0-0.paix-core01.bx.telstraglobal.net [202.
84.140.117]
10 210 ms 226 ms 211 ms i-2-1.paix01.bi.telstraglobal.net [202.84.251.10
1]
11 363 ms 418 ms 394 ms te4-5.mpd01.sjc04.atlas.cogentco.com [154.54.11.
157]
12 200 ms 221 ms 308 ms te0-0-0-6.mpd21.sfo01.atlas.cogentco.com [154.54
.2.165]
13 338 ms 437 ms 457 ms te0-1-0-3.mpd21.mci01.atlas.cogentco.com [154.54
.2.209]
14 277 ms 381 ms 349 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54
.45.154]
15 749 ms 314 ms 290 ms te0-3-0-4.mpd21.dca01.atlas.cogentco.com [154.54
.40.229]
16 287 ms 266 ms 268 ms te0-0-0-2.mpd21.iad02.atlas.cogentco.com [154.54
.1.206]
17 270 ms 270 ms 268 ms te2-1.mpd01.iad01.atlas.cogentco.com [154.54.31.
162]
18 274 ms 269 ms 433 ms te2-7.ccr01.iad04.atlas.cogentco.com [154.54.80.
78]
19 314 ms 371 ms 316 ms 38.104.30.102
20 478 ms 537 ms 390 ms sc-smv2206.servint.net [209.50.237.198]
21 313 ms 320 ms 419 ms server.ghihost.com [207.58.176.213]
Trace complete.
[/quote]
however his trace from his Bigpond Cable network doesnāt show an effective tracert, they must block ICMP requests to the mid-point routersā¦
[quote]Tracing route to tinyclr.com [207.58.176.213]
over a maximum of 30 hops:
1 1 ms 3 ms 1 ms 192.168.1.1
2 22 ms 21 ms 7 ms 10.253.176.1
3 * * * Request timed out.
4 * * * Request timed out.
[/quote]
So potentially heās still seeing the same issue as me, but just canāt prove it with tracert to see the full path. But since weāre on different ISPs I think thereās a lesser chance that the response is caused by our ISPs. I donāt think Iāve had any widespread issues on the internet ever from my home network, so really I think the problem must be in the datacentre the GHI servers are in.
From a tracking perspective, the first few times I posted about āserver outagesā in this thread had similar symptoms, but then the server came back up (so I thought it was a real outage). But then it stopped coming back online at all⦠It certainly seemed to have got worse after the site release, I donāt think Iād ever seen an outage prior to that; I donāt know whether there were infrastructure changes at the same time? But the bigger concern to me is the fact that all sites including the shop are down - not that I need more fezzez in my life, but you never know the way Gus keeps hinting at new stuff when Iāll need to place my next order !
We are investigating I promise.
donāt doubt that for a second
Happy Weekend ! Oh yeah, right, itās still Friday over there 
@ Brett - Apparently your IP was blocked:
csf.deny: xxx # lfd: (PERMBLOCK) xxx has had more than 4 temp blocks in the last 86400 secs - Sat May 12 06:25:13 2012
The block has been removed and youāve been added to the whitelist.
If Rob has a static IP he should email me - josh.young at ghielectronics dot com.
Josh, itās alive !