Ebay Classic organs

Collapse

Announcement

Collapse
No announcement yet.

NZOrgan.com won't appear on my computer?

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • NZOrgan.com won't appear on my computer?

    There's a website called nzorgan.com - although I've never seen it. If you google organ pictures, many of the best ones seem to be on nzorgan.com.

    But when I click it, I getting the spinning pinwheel for a minute and then a timed out message.

    It's been about a month since I first discovered it, and it's never worked for me. All other websites work fine on my computer. Plenty of DSL speed, etc.

    And all the "is it online" websites say that nzrorgan.com is working fine and that it's just me.

    Doesn't make sense that only one website won't load on my computer. Are all of you able to get it? Is this some regional thing that it won't appear in the US but it appears in other countries? According to google search results, it's a current and well visited website.

    I'd love to actually see it someday.

    Is it working for you all?

  • #2
    Neumie,

    I am in the USA, and the site came up fine for me using both Internet Explorer and Chrome.

    I don't know what this issue may be.

    Sorry,
    Allen
    Currently own: Roland Atelier AT-90, Yamaha 115D, Roland DP-90SE, Yamaha PSR-S910

    YouTube Channel

    Comment


    • #3
      Thanks, Allen. That's the dardest thing. The site absolutely will not load for me in Firefox or Safari. No other website gives me this trouble.

      I've never experienced anything like this in all the years I've been using the internet.

      One lone website in the world won't load.

      I wouldn't even know where to go ask for advice on this.

      Comment


      • #4
        That site works for me. It may be that your anti-virus/firewall is blocking it for some reason.

        If you're a Windows user, click on Start/Run, type command then press enter. A black scree DOS window should open.

        At the > prompt type tracert www.nzorgan.com and press enter.

        You should now see lines of hops between www nodes as your PC makes a link to the site. If it stops at any point with a timeout message, there's your problem.

        To get back to Windows, type EXIT at the > prompt.

        PS: That's a great site!
        -------

        Hammond M-102 #21000.
        Leslie 147 #F7453 in the queue.
        Hammond S-6 #72421

        Comment


        • #5
          Well, I'm a Mac guy ... but no firewall regardless.

          Remains a mystery.

          Originally posted by gtc View Post
          PS: That's a great site!
          Oh, yeah. Rub it in...

          Comment


          • #6
            I'm running IE8 in the USA and had no difficulty accessing the site.

            David

            Comment


            • #7
              Originally posted by Neumie View Post
              Well, I'm a Mac guy
              Can still be done. See the bottom part of this page:

              http://www.hosting.com/support/info/tracert

              Let us know what it reports.
              -------

              Hammond M-102 #21000.
              Leslie 147 #F7453 in the queue.
              Hammond S-6 #72421

              Comment


              • #8
                HI GTC,

                Thanks for the reply. I don't know any of the terms you're using or anything about a traceroute, but here are the results I received having followed your directions.

                Note that I didn't let it run its course. I hit stop when it got stuck.

                __________________________________________________ _____________________________

                Traceroute has started…

                traceroute to nzorgan.com (202.191.34.81), 64 hops max, 52 byte packets
                1 home (192.168.1.254) 2.637 ms 1.951 ms 2.828 ms
                2 bras1-l0.scrm01.sbcglobal.net (151.164.185.12) 188.014 ms 181.493 ms 194.859 ms
                3 dist1-vlan50.scrm01.pbi.net (64.171.152.66) 160.946 ms 167.912 ms 208.012 ms
                4 151.164.41.106 (151.164.41.106) 200.072 ms 60.116 ms 10.924 ms
                5 ggr6.wswdc.ip.att.net (12.122.86.89) 37.928 ms 13.644 ms 13.246 ms
                6 te2-3.mpd01.sjc03.atlas.cogentco.com (154.54.12.105) 15.734 ms
                te2-7.mpd01.sjc03.atlas.cogentco.com (154.54.12.113) 25.635 ms 14.995 ms
                7 te4-2.mpd01.sjc01.atlas.cogentco.com (154.54.6.105) 15.760 ms
                te7-2.mpd01.sjc01.atlas.cogentco.com (154.54.41.205) 15.595 ms
                te2-4.mpd01.sjc01.atlas.cogentco.com (154.54.41.201) 15.154 ms
                8 te0-2-0-1.mpd21.lax01.atlas.cogentco.com (154.54.6.29) 61.834 ms 93.270 ms 104.081 ms
                9 te8-2.mpd01.lax05.atlas.cogentco.com (154.54.0.218) 109.214 ms
                te7-8.mpd01.lax05.atlas.cogentco.com (154.54.30.190) 125.282 ms
                te9-1.mpd01.lax05.atlas.cogentco.com (154.54.44.138) 127.253 ms
                10 xe-0-1-0.cre1.la1.odyssey.net.nz (38.104.84.30) 130.047 ms 172.585 ms 132.602 ms
                11 121.99.12.0 (121.99.12.0) 290.869 ms 296.216 ms 280.106 ms
                12 orcon-1.cre1.nct.odyssey.net.nz (121.99.12.1) 267.857 ms 248.262 ms 260.987 ms
                13 ge-0-0-1.cre2.wgt.orcon.net.nz (121.98.9.54) 299.405 ms 321.481 ms 342.576 ms
                14 v501.br1.wlg.iserve.net.nz (60.234.62.186) 334.576 ms 331.827 ms 368.683 ms
                15 v20.fw2.wlg.iserve.net.nz (202.191.35.177) 363.900 ms 248.713 ms 298.047 ms
                16 * * *
                17 * * *
                18 * * *
                19 * * *
                20 * * *
                21 * * *
                22 * * *
                23 * * *
                24 * * *
                25 * * *
                26 * * *
                27 * * *
                28 * * *
                29 * * *
                30 *

                Comment


                • #9
                  Here's what I get when it hits New Zealand:

                  Tracing route to nzorgan.com [202.191.34.81]
                  over a maximum of 30 hops:

                  [...]

                  7 41 ms 41 ms 41 ms ae1-0.cre2.nct.odyssey.net.nz [121.99.12.3]
                  8 43 ms 41 ms 41 ms ae1.cre2.nct.odyssey.net.nz [121.99.12.2]
                  9 54 ms 52 ms 53 ms ge-0-0-1.cre2.wgt.orcon.net.nz [121.98.9.54]
                  10 54 ms 52 ms 53 ms v501.br1.wlg.iserve.net.nz [60.234.62.186]
                  11 54 ms 53 ms 53 ms v20.fw2.wlg.iserve.net.nz [202.191.35.177] <--- node where you're getting stuck
                  12 55 ms 53 ms 53 ms v21.cs2.wlg.iserve.net.nz [202.191.35.186]
                  13 65 ms 64 ms 65 ms dns1.mitosis.net.nz [202.191.34.81]

                  Trace complete.

                  --------

                  I'm wondering if the "fw2" bit in the URL for 202.191.35.177 means firewall.

                  Suggest you contact your ISP and send them these traces to point out the problem you're having. They ought to be able to contact the owner of the problematic node, who appears to be Orcon:

                  http://www.orcon.net.nz/work/business_hosting
                  Last edited by gtc; 03-20-2012, 04:49 AM.
                  -------

                  Hammond M-102 #21000.
                  Leslie 147 #F7453 in the queue.
                  Hammond S-6 #72421

                  Comment


                  • #10
                    Ok, GTC. I'll call my ISP people and see what they know. If the pictures on google are any indication, it's worth the hassle to be able to visit this site.

                    Thanks for the help.

                    Comment

                    Working...
                    X