Can't access wilders

Discussion in 'Forum Related Discussions' started by Tarnak, Jun 5, 2011.

Thread Status:
Not open for further replies.
Page 2 of 2
  1. LowWaterMark

    LowWaterMark Administrator

    Joined:
    Aug 10, 2002
    Posts:
    18,280
    Location:
    New England
    Hey, believe me... I hope your restored access is a sign that the whole problem is fixed. That'd be great. But, I remain doubtful that it suddenly resolved itself after occurring for so long (i.e. the people with weeks worth of access issues). But, time will tell, as more people check in and report.
     
    LowWaterMark, Jun 16, 2011
    #26
  2. BeanCounter

    BeanCounter Registered Member

    Joined:
    Apr 8, 2006
    Posts:
    66
    Location:
    Melbourne, Australia
    Well it is certainly not fixed. It is just that only some IP address ranges are blocked. Looking at the various route traces the blockage occurs after 66.227.69.99 and since that is the final hop, the problem must reside with the server hosting wilderssecurity.com.
     
    BeanCounter, Jun 19, 2011
    #27
  3. Togg

    Togg Registered Member

    Joined:
    Jun 24, 2003
    Posts:
    177
    I've only just seen this thread now everything appears to be OK but, for the record, I, a UK resident, also lost access to Wilders for about two days last week. I can't now recollect what,if any, error message I received.
     
    Togg, Jun 19, 2011
    #28
  4. MikeNash

    MikeNash Security Expert

    Joined:
    Jun 9, 2005
    Posts:
    1,658
    Location:
    Sydney, Australia
    Mine fails still as of last night.

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\miken>tracert www.wilderssecurity.com

    Tracing route to www.wilderssecurity.com [65.175.38.194]
    over a maximum of 30 hops:

    1 <1 ms 1 ms 1 ms 192-168-1-1.tpgi.com.au [192.168.1.1]
    2 19 ms 19 ms 18 ms nexthop.nsw.iinet.net.au [203.215.19.247]
    3 19 ms 26 ms 19 ms te1-1.syd-mas-bdr2.iinet.net.au [203.215.18.20]

    4 19 ms 19 ms 19 ms te1-2.syd-mas-bdr1.iinet.net.au [203.215.20.153]

    5 20 ms 19 ms 19 ms xe-1-1-0-0.syd-mas-core1.iinet.net.au [203.215.2
    0.94]
    6 211 ms 210 ms 210 ms 34023.sydp06.cu.reach.com [134.159.160.57]
    7 211 ms 210 ms 210 ms i-0-5-0-0.tlot-core01.bx.reach.com [202.84.140.1
    02]
    8 212 ms 210 ms 211 ms i-1-1.eqla01.bi.reach.com [202.84.251.194]
    9 201 ms 200 ms 201 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
    10 264 ms 278 ms 264 ms ip-208.49.147.126.gblx.net [208.49.147.126]
    11 266 ms 266 ms 265 ms 66.227.69.99
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    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 * * * Request timed out.
    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.

    C:\Users\miken>
     
    MikeNash, Jun 20, 2011
    #29
  5. Triple Helix

    Triple Helix Specialist

    Joined:
    Nov 20, 2004
    Posts:
    13,275
    Location:
    Ontario, Canada
    Could it because of the Australia Internet Censorship as I see some of you are from there or is that not the issue anymore?

    TH
     
    Last edited: Jun 21, 2011
    Triple Helix, Jun 20, 2011
    #30
  6. LowWaterMark

    LowWaterMark Administrator

    Joined:
    Aug 10, 2002
    Posts:
    18,280
    Location:
    New England
    No, we know what it is now... Our hosting company reported to me on it Friday. It's a new configuration in their network security, which they do not intend to change for reasons I can not post about in public. Our only solution is to move the forum to a new network. I've been looking into doing that since then and currently have a new server environment being built for us. It'll take a few days at least to test it and then we'll schedule a downtime to migrate everything over.

    I asked a couple people from Australia, who currently have no access to here, to test that the new network is accessible for them. One has replied so far, and he got access to a machine on that network without any problems.

    So, hopefully in a week or a little more, we'll be moved and this issue will be resolved.
     
    LowWaterMark, Jun 20, 2011
    #31
  7. Triple Helix

    Triple Helix Specialist

    Joined:
    Nov 20, 2004
    Posts:
    13,275
    Location:
    Ontario, Canada
    Ok thanks for the info LWM!

    TH
     
    Triple Helix, Jun 20, 2011
    #32
  8. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    4,660
    Hi Mike,

    Would that mean that the ip-address of the board will also change?

    Some of us have the current one in their HOSTS file:

    Code:
    65.175.38.194 wilderssecurity.com
65.175.38.194 www.wilderssecurity.com
    We will need to change that when the board gets a new ip-address.

    Good luck with the move and keep up the good work :thumb:
     
    FanJ, Jun 21, 2011
    #33
  9. Longboard

    Longboard Registered Member

    Joined:
    Oct 2, 2004
    Posts:
    3,238
    Location:
    Sydney, Australia
    Ok..from DU..ISP is Telstra.
    Not sure if this helps but from here:
    no problems accessing https://www.wilderssecurity.com/

    Tracert and ping:

    C:\Documents and Settings\USER>tracert www.wilderssecurity.com

    Tracing route to www.wilderssecurity.com [65.175.38.194]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms xxx.xxx.x.x
    2 6 ms 5 ms 6 ms 10.236.192.1
    3 * * * Request timed out.
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    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 * * * Request timed out.
    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.

    C:\Documents and Settings\USER>ping www.wilderssecurity.com

    Pinging www.wilderssecurity.com [65.175.38.194] with 32 bytes of data:

    Reply from 65.175.38.194: bytes=32 time=231ms TTL=45
    Reply from 65.175.38.194: bytes=32 time=232ms TTL=45
    Reply from 65.175.38.194: bytes=32 time=226ms TTL=45
    Reply from 65.175.38.194: bytes=32 time=226ms TTL=45

    Ping statistics for 65.175.38.194:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 226ms, Maximum = 232ms, Average = 228ms

    I'm not sure what that tracert result means in view of the fact i am currently on wilders .. o_O

    @TH: currently there is no public censorship programme that I know of.
    I thinkthe last abortive attempt has been binned unless there is some secret plot afoot. :rolleyes:
    The Federal Govt may still be maintaing a secret list of links related to sex crimes and some other issues.

    The ISPs are about to start an "opt-in" programme.
    As far as I know LWM is not a recognised web threat ;)
     
    Longboard, Jun 22, 2011
    #34
  10. Tarnak

    Tarnak Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    5,296
    Three bad IP's in a row, 58.178.13.190, 58.178.38.23 and 58.178.44.145. ...and, I am back with 202.67.xx.yyy.
     
    Tarnak, Jun 23, 2011
    #35
  11. Dude111

    Dude111 Registered Member

    Joined:
    Sep 30, 2008
    Posts:
    212
    Yes i have read recently they are now CENSORING THE INTERNET (Blocking things @ will) I dunno if moving networks will fix anything :( (maybe for a short time it may)

    If people typed in the IP address to get here instead of the domain name it may prove workable a bit longer...

    Luckily i have always been able to access this excellent site :)


    Im sorry your having these problems mark :(
     
    Dude111, Jun 26, 2011
    #36
Page 2 of 2
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...