Shop OBEX P1 Docs P2 Docs Learn Events
trouble connecting to www.sxlist.com — Parallax Forums

trouble connecting to www.sxlist.com

loserloser Posts: 17
edited 2005-02-15 09:30 in General Discussion
hi, i dont know if its just me, but i have trouble connecting to the www.sxlist.com site.
for a while it was just sitting there and not ever acually loading the page (i am on adsl, so it really shouldnt be a problem :P) so i tried using a public proxy server and then the page did load...

however now i get a 'page contains no data' error.

when i ping the page i get its ip as being 66.13.172.18. is this correct? if not, what is it?
i am wondering if maybe my ISPs DNS servers may have problems.. especially since one time when i tried to load the sxlist site i got some other page altogether, even though it was definately www.sxlist.com in my browsers address bar.

i have tried using firefox and IE6, i get the same problems with each browser.

are there any mirrors of sxlist?
does anyone else have access problems?

thanks

Comments

  • James NewtonJames Newton Posts: 329
    edited 2005-02-07 00:42
    Are you with Bell South? It sould seem they have something against me.... Several Bell South customers have reported that they are not able to see sxlist.com. And no matter how many times I email them, I can't get them to respond to me.

    Several of thier customers have contacted thier support and have been told any number of impossible things. "that site is just not up at this time", "they are using old equipment that isn't compatible" (not true: I run a standard Linksys router and a Windows NT server, Microsoft still supports NT and there are MANY sites hosted on it, and even if that were true, why would other ISP's customers be able to get to the site?) and my favorite "there is no such site"

    The IP address you have is correct, but using the ip address only will not work unless you supply a path. e.g.
    http://66.13.172.18/techref/ubicom/index.htm will get the site if your ISP is on the ball. If you just use the IP, it will appear to be another site since several are hosted at the same IP and the domain is used to decide between them.

    You can PROVE to bell south that THEY are the problem by simply using a proxy outside thier system to view the site. The proxey requests the page from my site, and relays it on to you. Because Bell South doesn't have a problem with the proxey server, the exact same page that they rejected directly, makes it to you via the proxey.

    For example, you can try
    http://www.the-cloak.com/Cloaked/+cfg=32/http://www.sxlist.com/techref/ubicom/index.htm (note: you may have to "fix" the URL in the "starting URL" box on thier page that comes up first.)

    Just ask them exactly what is the difference between
    http://www.the-cloak.com/Cloaked/+cfg=32/http://www.sxlist.com/techref/ubicom/index.htm
    and
    http://www.sxlist.com/techref/ubicom/index.htm

    If sxlist.com is at fault, why does it work via "the-cloak"? How can "the-cloak.com" read the site?

    PLEASE do take the time to verify this and send a flameing email to bell south tech support?

    THANKS!

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    ---
    James Newton, Host of SXList.com
    james@sxlist.com 1-619-652-0593 fax:1-208-279-8767
    SX FAQ / Code / Tutorials / Documentation:
    http://www.sxlist.com Pick faster!



  • loserloser Posts: 17
    edited 2005-02-07 01:15
    i am actually from australia and use the dodo ISP.
    i tried some other public proxies and can access sxlist (once i find a proxy that actually works [noparse]:)[/noparse])
    but just cant access it without a proxy (my ISP doesnt use a proxy by default, at least not one that i have to set up in my settings)

    i emailed them about the issue, and they said to check settings blah blah, then ring their helpline.
    ive rung the helpline before and they just take your name and number and call you back... which can be at anytime :P so i didnt bother to call them.

    i just made sure i saved the relevant stuff from your site so that i can browse it more easily. mainly a couple of source code listings.

    (oh and yes the page also loads using 'the cloak')
  • ForrestForrest Posts: 1,341
    edited 2005-02-07 02:18
    I've also had problems connecting from www.sxlist.com for the past few months. No problem connecting thru a proxy server, but can't connect directly. My ISP (Verizon DSL) hasn't been any help tracking the problem down.
  • James NewtonJames Newton Posts: 329
    edited 2005-02-08 19:56
    If you have Windows NT, XP or a *nix box, would you try doing a

    tracert 66.13.172.18

    and copy the results to this thread? I would really appreciate it...

    In windows, to copy text from the command prompt, just do Alt+Space, E, S (or k for Mark if you don't have Select All, then click in the upper left corner and drag to the lower right) and press Enter. Then you can paste the result into your reply.

    In looking back through other reports of this problem, I've noticed a common node called "bbnplanet" and I'm wondering if both of you are ending up going through that point in the route.

    Thank you!

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    ---
    James Newton, Host of SXList.com
    james@sxlist.com 1-619-652-0593 fax:1-208-279-8767
    SX FAQ / Code / Tutorials / Documentation:
    http://www.sxlist.com Pick faster!



  • Robert KubichekRobert Kubichek Posts: 343
    edited 2005-02-08 21:51
    here you go.

    Bob

    Tracing route to mail.efplus.com [noparse][[/noparse]66.13.172.18]
    over a maximum of 30 hops:


    2 9 ms 9 ms 9 ms adsl-68-249-3-254.dsl.milwwi.ameritech.net [noparse][[/noparse]68.249.3.254]
    3 11 ms 11 ms 10 ms dist2-vlan60.milwwi.ameritech.net [noparse][[/noparse]65.43.19.243]
    4 11 ms 11 ms 10 ms bb1-g2-0.milwwi.ameritech.net [noparse][[/noparse]65.43.19.115]
    5 13 ms 13 ms 13 ms bb1-p3-2.chcgil.ameritech.net [noparse][[/noparse]151.164.190.85]
    6 14 ms 13 ms 13 ms bb2-p11-0.chcgil.ameritech.net [noparse][[/noparse]151.164.191.182]
    7 16 ms 15 ms 14 ms ex1-p3-0.eqchil.sbcglobal.net [noparse][[/noparse]151.164.188.162]
    8 14 ms 14 ms 14 ms ex2-p11-0.eqchil.sbcglobal.net [noparse][[/noparse]151.164.40.126]
    9 14 ms 15 ms 14 ms sl-st20-chi-0-0.sprintlink.net [noparse][[/noparse]144.223.241.57]
    10 15 ms 14 ms 15 ms so-2-1-0.edge1.Chicago1.Level3.net [noparse][[/noparse]209.0.225.21]
    11 15 ms 15 ms 16 ms so-2-1-0.bbr1.Chicago1.Level3.net [noparse][[/noparse]209.244.8.9]
    12 78 ms 79 ms 78 ms ae-0-0.bbr1.LosAngeles1.Level3.net [noparse][[/noparse]64.159.1.125]
    13 78 ms 77 ms 78 ms so-8-0.core1.LosAngeles2.Level3.net [noparse][[/noparse]64.159.4.30]
    14 78 ms 76 ms 77 ms 4.68.115.146
    15 76 ms 76 ms 75 ms 4.68.115.70
    16 80 ms 80 ms 80 ms a-7-0-4.lsanca1-ar11.bbnplanet.net [noparse][[/noparse]4.24.45.38]
    17 109 ms 109 ms 358 ms mail.efplus.com [noparse][[/noparse]66.13.172.18]
  • ForrestForrest Posts: 1,341
    edited 2005-02-08 22:53
    Here's what it looks like thru Verizon DSL:
    traceroute to 66.13.172.18 (66.13.172.18), 30 hops max, 40 byte packets
    1 dslrouter (192.168.1.1) 1.143 ms 0.54 ms 0.475 ms
    2 * * *
    3 * * *
    4 * * *
    5 * * *
    6 * * *
    7 * * *
    8 * * *
    9 * * *
    10 * * *
    11 * * *
    12 * * *
    13 * * *
    14 * * *
    15 * * *
  • Paul BakerPaul Baker Posts: 6,351
    edited 2005-02-08 23:00
    Forrest, looks like Verizon blocks pinging and tracerouting to prevent hackers from using the info (not unheard of). Or they are having problems at your local office.
  • ForrestForrest Posts: 1,341
    edited 2005-02-08 23:02
    And the funny part is I CAN access www.sxlist.com today - even though the traceroute command is timing out.
  • peterjpeterj Posts: 24
    edited 2005-02-09 00:35
    I too have been having problems getting to the [noparse][[/noparse]sx|pic]list websites for the past several months. I've been getting through by tunnelling through a remote host. Here is the output of my traceroute/pings:

    tracert -d www.sxlist.com

    Tracing route to sxlist.com [noparse][[/noparse]66.13.172.18]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 192.168.2.1
    2 28 ms 28 ms 28 ms 10.4.8.1
    3 27 ms 27 ms 27 ms 130.81.10.149
    4 31 ms 31 ms 31 ms 130.81.18.12
    5 30 ms 30 ms 31 ms 130.81.10.90
    6 30 ms 31 ms 30 ms 67.29.172.13
    7 31 ms 30 ms 30 ms 209.244.11.9
    8 102 ms 103 ms 103 ms 64.159.1.157
    9 103 ms 103 ms 103 ms 64.159.4.26
    10 103 ms 103 ms 103 ms 4.68.115.146
    11 103 ms 416 ms 102 ms 4.68.115.66
    12 103 ms 102 ms 102 ms 4.24.45.38
    13 136 ms 137 ms 136 ms 66.13.172.18

    Trace complete.

    D:\Documents and Settings\peter>ping -t www.sxlist.com

    Pinging sxlist.com [noparse][[/noparse]66.13.172.18] with 32 bytes of data:

    Reply from 66.13.172.18: bytes=32 time=154ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=133ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=134ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=151ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=133ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=133ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=136ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=141ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=366ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=133ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=133ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=133ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=133ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=140ms TTL=138
    Reply from 66.13.172.18: bytes=32 time=140ms TTL=138

    Ping statistics for 66.13.172.18:
    Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 133ms, Maximum = 366ms, Average = 152ms

    I'm also on Verizon, so that *might* be a common element...

    -p.
  • loserloser Posts: 17
    edited 2005-02-12 11:39
    C:\>tracert 66.13.172.18

    Tracing route to mail.efplus.com [noparse][[/noparse]66.13.172.18]
    over a maximum of 30 hops:

    1 4 ms 2 ms 2 ms internerd [noparse][[/noparse]192.168.0.1]
    2 1098 ms 486 ms 638 ms rns02-kent-syd.comindico.com.au [noparse][[/noparse]203.194.30.201]
    3 556 ms 818 ms 511 ms vlan100.slb01-kent-syd.comindico.com.au [noparse][[/noparse]203.194.20.193]
    4 1967 ms 1533 ms 2149 ms ge6-3.cor01-kent-syd.comindico.com.au [noparse][[/noparse]203.194.1.77]
    5 509 ms 404 ms 210 ms ge3-0.bdr02-kent-syd.comindico.com.au [noparse][[/noparse]203.194.1.121]
    6 335 ms 689 ms 1019 ms 134.159.123.245
    7 1745 ms 2763 ms 1636 ms i-10-0.syd-core03.net.reach.com [noparse][[/noparse]202.84.221.85]
    8 1021 ms 1537 ms 715 ms i-12-3.wil-core02.net.reach.com [noparse][[/noparse]202.84.144.193]
    9 1659 ms 1840 ms 1739 ms i-3-0.dal-core01.net.reach.com [noparse][[/noparse]202.84.249.106]
    10 1378 ms 609 ms 1948 ms level3.Dal-core01.net.reach.com [noparse][[/noparse]134.159.63.142]
    11 1226 ms 1229 ms 1125 ms ae-1-54.bbr2.Dallas1.Level3.net [noparse][[/noparse]4.68.122.97]
    12 604 ms 414 ms 818 ms ae-0-0.bbr1.LosAngeles1.Level3.net [noparse][[/noparse]64.159.1.125]
    13 1965 ms 1331 ms 2354 ms so-8-0.core1.LosAngeles2.Level3.net [noparse][[/noparse]64.159.4.30]
    14 1635 ms 1331 ms 1228 ms 4.68.115.146
    15 920 ms 2048 ms 1841 ms 4.68.115.70
    16 2229 ms 2149 ms * a-7-0-4.lsanca1-ar11.bbnplanet.net [noparse][[/noparse]4.24.45.38]
    17 1936 ms 1638 ms 817 ms mail.efplus.com [noparse][[/noparse]66.13.172.18]

    Trace complete.
  • JavalinJavalin Posts: 892
    edited 2005-02-13 13:05
    Hi Chaps,

    Also having issues with getting to the site. This weekend (13th feb) - getting

    HTTP 500 - Internal server error
    Internet Explorer

    Using WinXP and IE6

    Cheers

    james
  • Michael ChadwickMichael Chadwick Posts: 80
    edited 2005-02-13 21:54
    Hi James,

    Getting to SXlist from work is OK, getting there from home isn't.· Like everyone else, it works fine through thecloak.· Here is the trace from home:

    Tracing route to sxlist.com [noparse][[/noparse]66.13.172.18]
    over a maximum of 30 hops:
    · 1··· 10 ms··· 10 ms··· 10 ms· 10.41.64.1
    · 2··· 11 ms···· 9 ms··· 12 ms· srp1-0.dytnoh1-rtr1.woh.rr.com [noparse][[/noparse]24.29.160.1]
    · 3··· 15 ms··· 13 ms··· 12 ms· son0-0-3.mtgmoh1-rtr0.cinci.rr.com [noparse][[/noparse]65.25.128.241]
    · 4··· 21 ms··· 21 ms··· 20 ms· son0-1-3.ncntoh1-rtr0.neo.rr.com [noparse][[/noparse]65.25.128.245]
    · 5··· 32 ms··· 31 ms··· 31 ms· so-2-0-0-0.gar1.Chicago1.Level3.net [noparse][[/noparse]67.72.120.5]
    · 6··· 31 ms··· 31 ms··· 30 ms· so-0-3-0.bbr1.Chicago1.Level3.net [noparse][[/noparse]4.68.96.37]
    · 7··· 98 ms··· 98 ms·· 100 ms· ae-0-0.bbr1.LosAngeles1.Level3.net [noparse][[/noparse]64.159.1.125]
    · 8··· 98 ms··· 98 ms··· 98 ms· so-8-0.core1.LosAngeles2.Level3.net [noparse][[/noparse]64.159.4.30]
    · 9··· 99 ms··· 98 ms··· 98 ms· 4.68.115.146
    ·10··· 99 ms··· 98 ms··· 99 ms· 4.68.115.66
    ·11·· 110 ms·· 100 ms··· 99 ms· a-7-0-4.lsanca1-ar11.bbnplanet.net [noparse][[/noparse]4.24.45.38]
    ·12·· 128 ms·· 131 ms·· 128 ms· sxlist.com [noparse][[/noparse]66.13.172.18]
    Trace complete.

    MRC
  • James NewtonJames Newton Posts: 329
    edited 2005-02-14 19:49
    Ahh.. Michael, can you send a tracert from work? If it is being routed through [noparse][[/noparse]4.24.45.38] then it eliminates that as the problem, but if it is going via some other path, then I can be much more sure. Is that two different computers or the same one moving between work and home?

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    ---
    James Newton, Host of SXList.com
    james@sxlist.com 1-619-652-0593 fax:1-208-279-8767
    SX FAQ / Code / Tutorials / Documentation:
    http://www.sxlist.com Pick faster!



  • James NewtonJames Newton Posts: 329
    edited 2005-02-14 19:52
    Javalin said...
    Also having issues with getting to the site. This weekend (13th feb) - getting

    HTTP 500 - Internal server error
    That was me... I blew it and downed the site this weekend. It's fine now.

    See a list of all the server failures and the reasons:
    http://www.sxlist.com/techref/servfail.htm

    This one was
    http://www.sxlist.com/techref/servfail.htm#20050212

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    ---
    James Newton, Host of SXList.com
    james@sxlist.com 1-619-652-0593 fax:1-208-279-8767
    SX FAQ / Code / Tutorials / Documentation:
    http://www.sxlist.com Pick faster!



  • Michael ChadwickMichael Chadwick Posts: 80
    edited 2005-02-14 20:07
    Hi James,

    Different computers at home (WIN982ndEdition)·and work (XP home Service Pack 2).· I will have to try the work laptop at home and see if there is a difference.

    Here is the tracert from work:

    Tracing route to sxlist.com [noparse][[/noparse]66.13.172.18]
    over a maximum of 30 hops:
    · 1···· 8 ms··· <1 ms··· <1 ms· 192.168.0.1
    · 2···· 1 ms···· 1 ms···· 1 ms· 172.16.134.2
    · 3···· 1 ms···· 1 ms···· 1 ms· 216.29.163.1
    · 4···· 3 ms···· 3 ms···· 3 ms· mux.dmvec2.donet.com [noparse][[/noparse]64.56.102.85]
    · 5···· 5 ms···· 4 ms···· 4 ms· giga.donet.com [noparse][[/noparse]64.56.96.254]
    · 6···· 5 ms···· 5 ms···· 5 ms· core1-eth1-DONET.Dayton.fnsi.net [noparse][[/noparse]216.28.125.221]
    · 7···· 9 ms···· 9 ms··· 10 ms· p3-3.core01.cle01.atlas.cogentco.com [noparse][[/noparse]154.54.2.141]
    · 8··· 36 ms··· 32 ms··· 37 ms· p1-0.core01.bos01.atlas.cogentco.com [noparse][[/noparse]66.28.4.189]
    · 9··· 29 ms··· 28 ms··· 28 ms· p5-0.core01.jfk02.atlas.cogentco.com [noparse][[/noparse]66.28.4.118]
    ·10··· 34 ms··· 34 ms··· 34 ms· p4-0.core02.dca01.atlas.cogentco.com [noparse][[/noparse]66.28.4.81]
    ·11··· 40 ms··· 33 ms··· 34 ms· p14-0.core01.iad01.atlas.cogentco.com [noparse][[/noparse]154.54.2.198]
    ·12··· 31 ms··· 31 ms··· 30 ms· so-0-2-0.edge2.Washington1.Level3.net [noparse][[/noparse]4.68.127.9]
    ·13··· 31 ms··· 31 ms··· 31 ms· so-1-1-0.bbr1.Washington1.Level3.net [noparse][[/noparse]64.159.3.61]
    ·14··· 84 ms··· 84 ms··· 84 ms· as-0-0.bbr1.LosAngeles1.Level3.net [noparse][[/noparse]64.159.1.157]
    ·15··· 84 ms··· 84 ms··· 85 ms· so-2-0.core1.LosAngeles2.Level3.net [noparse][[/noparse]64.159.4.26]
    ·16··· 85 ms··· 84 ms··· 85 ms· 4.68.115.146
    ·17··· 84 ms··· 85 ms··· 85 ms· p-2-0.lsanca1-aa2.bbnplanet.net [noparse][[/noparse]4.24.148.70]
    ·18··· 85 ms··· 85 ms··· 85 ms· a-7-0-4.lsanca1-ar11.bbnplanet.net [noparse][[/noparse]4.24.45.38]
    ·19·· 143 ms·· 116 ms·· 116 ms· mail.efplus.com [noparse][[/noparse]66.13.172.18]
    Trace complete.

    MRC
  • JavalinJavalin Posts: 892
    edited 2005-02-15 09:30
    Hi James

    Wondered if that was the case!

    Thanks

    james
Sign In or Register to comment.