DonationCoder.com Forum

Main Area and Open Discussion => Living Room => Topic started by: nudone on October 08, 2010, 05:16 AM

Title: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 05:16 AM
for, at least, a week i've been unable to view any pages over at www.head-in-the-clouds.com - every attempt just times out.

nor can i access the head in the clouds server using my, once working, FTP settings.

using a proxy service like "hide my ass" allows me to view the HITC website without any problem.

the question is...

does this look like my IP (or mac number) is being blocked by the HITC server, or does it look like my ISP is blocking access to the HITC server? or is it something else completely - or is it impossible to say?

it doesn't matter which computer i use in the house, i've not tried changing the router (so maybe that's the problem). everything worked fine up until this week - it's not like i've changed any network settings on the router or anywhere.

any ideas. thanks.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: 4wd on October 08, 2010, 05:48 AM
Can you tracert or ping to it?
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 06:23 AM
no, pinging just times out also, i.e.

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

and tracert doesn't seem to know where it's going...

Tracing route to www.head-in-the-clouds.com [98.131.45.219]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    15 ms    15 ms    15 ms  88-104-96-1.dynamic.dsl.as9105.com [88.104.96.1]

  3    25 ms    53 ms    24 ms  host108-155-static.40-85-b.business.telecomitali
a.it [85.40.155.108]
  4    62 ms    24 ms    24 ms  host109-155-static.40-85-b.business.telecomitali
a.it [85.40.155.109]
  5    27 ms    26 ms    26 ms  xe-9-3-0.bragg001.log.as13285.net [80.40.155.37]

  6    28 ms    27 ms    27 ms  xe-5-0-0.scr001.loh.as13285.net [80.40.155.60]
  7    29 ms    28 ms    27 ms  Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.21
3]
  8    30 ms    28 ms    28 ms  so-0-0-0.mpr1.lhr2.uk.above.net [64.125.27.225]

  9    28 ms    27 ms    27 ms  xe-0-1-0.mpr1.lhr1.uk.above.net [64.125.27.146]

 10    28 ms    26 ms    27 ms  above-level3.lhr1.uk.above.net [64.125.14.18]
 11    28 ms    27 ms    27 ms  ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
 12    96 ms    96 ms    97 ms  ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

 13    99 ms    99 ms    98 ms  ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
 14    97 ms    95 ms    96 ms  ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254]

 15   122 ms   125 ms   126 ms  ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]
 16   127 ms   125 ms   125 ms  ae-1-100.ebr2.Chicago1.Level3.net [4.69.132.42]

 17   126 ms   124 ms   126 ms  ae-1-10.bar1.Cincinnati1.Level3.net [4.69.136.21
3]
 18   129 ms   129 ms   128 ms  BLUEMILE-IN.bar1.Cincinnati1.Level3.net [4.59.40
.2]
 19   121 ms   120 ms   121 ms  76.10.192.226
 20   119 ms   118 ms   118 ms  76.10.207.14.customer.bluemilenetworks.com [76.1
0.207.14]
 21   128 ms   127 ms   127 ms  OH-MLS1-609.Te-9-2.opentransfer.com [98.130.213.
18]
 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     *        *
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 08, 2010, 06:28 AM
It sounds like a DNS issue. Add more DNS servers & push them up in priority (#1, #2, etc.). Google has free ones available. There are more.

It's not your MAC address. That's not available on the network -- it's only on your local machine. Browsers do not broadcast that information.

Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 08, 2010, 06:31 AM
That's very odd. You're 1 hop away there.

Tracing route to www.head-in-the-clouds.com [98.131.45.219]
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     1 ms    <1 ms    <1 ms  10.0.0.138
  3    29 ms    13 ms    12 ms  10.20.21.105
  4    12 ms    11 ms    12 ms  nme-nxg-wal-csw1-vlan-1.tpgi.com.au [220.245.179
.193]
  5    13 ms    12 ms    12 ms  nme-nxg-wal-crt1-ge-2-0-0.tpgi.com.au [202.7.162
.1]
  6    23 ms    23 ms    23 ms  syd-nxg-men-crt1-ge-3-0-0.tpgi.com.au [202.7.171
.141]
  7   177 ms   174 ms   173 ms  if-5-0-0.core4.SQN-SanJose.as6453.net [216.6.30.
49]
  8   173 ms     *        *     Vlan1280.icore1.SQN-SanJose.as6453.net [216.6.30
.26]
  9   173 ms   192 ms   173 ms  ix-2-0.icore1.SQN-SanJose.as6453.net [209.58.116
.14]
 10   183 ms   180 ms   180 ms  vlan79.csw2.SanJose1.Level3.net [4.68.18.126]
 11   176 ms   175 ms   179 ms  ae-72-72.ebr2.SanJose1.Level3.net [4.69.134.213]

 12   225 ms   218 ms   218 ms  ae-3-3.ebr1.Denver1.Level3.net [4.69.132.58]
 13   218 ms   217 ms   218 ms  ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38]
 14   226 ms   223 ms   224 ms  ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
 15   223 ms   232 ms   233 ms  ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
 16   234 ms   234 ms   234 ms  ae-1-100.ebr2.Chicago1.Level3.net [4.69.132.42]

 17   229 ms   277 ms   230 ms  ae-1-10.bar1.Cincinnati1.Level3.net [4.69.136.21
3]
 18   231 ms   240 ms   233 ms  BLUEMILE-IN.bar1.Cincinnati1.Level3.net [4.59.40
.2]
 19   231 ms   233 ms   232 ms  76.10.192.226
 20   233 ms   232 ms   232 ms  76.10.207.14.customer.bluemilenetworks.com [76.1
0.207.14]
 21   232 ms   233 ms   232 ms  OH-MLS1-609.Te-9-2.opentransfer.com [98.130.213.
18]
 22   231 ms   232 ms   232 ms  rev.opentransfer.com.219.45.131.98.in-addr.arpa
[98.131.45.219]

Trace complete.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 06:33 AM
p.s.

i forgot to mention i can't access any other websites that are hosted on the same server as www.head-in-the-clouds.com

not sure what that means or if it's helpful information.



Renegade, not sure if it's DNS either, well, i've had the google DNS settings in the router for months. this trouble started so i've gone back to automatically letting the router use my ISP's DNS - same problem.

i'll try open DNS and see what happens...
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 08, 2010, 06:37 AM
Try using some looking glasses. They'll help trouble shoot for you. Here's the Level3 Looking Glass (http://www.level3.com/LookingGlass/). You can search for more, but that should be good enough.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Carol Haynes on October 08, 2010, 06:38 AM
DNS screw up - I keep coming across this with random sites and ISPs.

Try changing your router DNS settings to google's public DNS.

8.8.8.8
8.8.4.4

see if that helps.

If it does your ISP DNS is corrupt and it might take a while for it to get fixed.

I had a customer recently who couldn't access bmibaby.com for about 3 months - she called yesterday to say suddenly it works again. Of course the ISP denies all knowledge of a problem ...
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 08, 2010, 06:38 AM
Oh -- Another thought...

Try adding in a HOSTS entry for the site. That should help eliminate or confirm DNS problems.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: 4wd on October 08, 2010, 06:40 AM
Try running ipconfig /flushdns at a CLI to flush out XP's DNS cache also.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 08, 2010, 06:41 AM
DNS screw up - I keep coming across this with random sites and ISPs.

...

I had a customer recently who couldn't access bmibaby.com for about 3 months - she called yesterday to say suddenly it works again. Of course the ISP denies all knowledge of a problem ...

+1 -- I find that ISP DNS services are VERY often poor. I posted before about getting some pretty hosed results for Facebook. I've seen a lot of others as well.

As above -- A HOSTS entry can confirm/eliminate that problem. I never tried it for Facebook because large sites use CDNs and DDNS anyways.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 06:45 AM
google DNS and OpenDNS appear be equally bad. Tracert with OpenDNS provided similar results as posted above.

adding the ip to the hosts file doesn't appear to help either.

i can believe Carol is right as the problem simply just "happened" one day.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: 4wd on October 08, 2010, 06:48 AM
I find that ISP DNS services are VERY often poor.

That's why I gave in and run my own DNS server now.  Haven't had a DNS problem since running it - apart from forgetting that the machine it's hosted on was turned off once or twice.

@nudone
From the tracert you posted, it almost seems like your IP is blocked at the remote end.  Since you're getting resolved IP addresses right up until the last hop that kind of implies the DNS servers are working.

Where's f0dder when you want him  :P
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 08, 2010, 06:50 AM
Did you flush after changing the HOSTS entry? That is extremely bizarre.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 06:53 AM
Try running ipconfig /flushdns at a CLI to flush out XP's DNS cache also.

hmm, still times out after that. yep, flushed after changing the hosts entry.

remember though... this happens on any machine i connect to my router, so i can't see it being a problem beyond the router itself. i suppose i should dig another one out and try that.


4wd, that was my first suspicion. Timns (he has access to it) had a quick look at the server but thought there was nothing being blocked. i'm thinking there is something higher up that he isn't aware of - i've been blocked because someone has decided my FTP access was illegal or something.

Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: 4wd on October 08, 2010, 06:59 AM
i'm thinking there is something higher up that he isn't aware of - i've been blocked because someone has decided my FTP access was illegal or something.

The fact that sites on the same server are unavailable to you seems highly suggestive of you being blocked or filtered by whoever hosts the server at the 2nd last hop:

21   232 ms   233 ms   232 ms  OH-MLS1-609.Te-9-2.opentransfer.com [98.130.213.18]

Do other sites at the same host stop at the same point?

Oh yeah, since you have access to someone who has access to the server, can he check the server logs and see if your attempted connects appear?
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 07:03 AM
Do other sites at the same host stop at the same point?

yep, the requests start timing out at exactly the point after blah, blah, opentransfer.com [...]
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 08, 2010, 07:08 AM
Here are some partial trace routes from all over North America (alphabetical, not done)


Level 3 Site:
      
Traceroute To:
      
IPv6:
      
ALL European sitesAmsterdam, NetherlandsAMSIX NAP AmsterdamBucharest, RomaniaBerlin, GermanyBrussels, BelgiumDublin, IrelandDusseldorf, GermanyFrankfurt, GermanyGeneva, SwitzerlandHamburg, GermanyLondon, EnglandLondon, England (2)Madrid, SpainManchester, UKMilan, ItalyMunich, GermanyParis, FrancePrague, Czech RepublicSofia, BulgariaStockholm, SwedenVienna, AustriaWarsaw, PolandZurich, SwitzerlandALL North American sitesAtlanta, GABaltimore, MDBoston, MABaton Rouge, LABurlington, VTBuffalo, NYColumbia, SCChicago, ILCharlottesville, VACincinnati, OHColumbus, OHCleveland, OHCharlotte, NCDallas, TXDenver, CODetroit, MIFIX-West NAP San JoseFort Lauderdale, FLFort Myers, FLGarden City, NYHarrisburg, PAHouston, TXJackson, MSJacksonville, FLKansas City, MOLos Angeles, CALexington, KYLittle Rock, ARLouisville, KYLas Vegas, NVMiami, FLMinneapolis, MNMobile, ALMontrealNorfolk, VANashville, TNNewark, NJNew York, NYOakland, CAOrlando, FLPhiladelphia, PAPhoenix, AZPittsburgh, PARaleigh, NCRichmond, VASacramento, CAState College, PAScranton, PASan Diego, CASeattle, WASan Francisco, CASan Jose, CASalt Lake City, UTSaint Louis, MOStamford, CTSyracuse, NYTampa, FLTorontoTri-Cities, TNTustin, CAWichita, KSWashington, DCWeehawken, NJ
      
      
   

Show Level 3 (ALL North American sites) Traceroute to www.head-in-the-clouds.com (98.131.45.219)

Traceroute from Atlanta, GA -

  1 ae-72-52.ebr2.Atlanta2.Level3.net (4.68.103.61) 8 msec
    ae-62-51.ebr2.Atlanta2.Level3.net (4.68.103.29) 0 msec
    ae-72-52.ebr2.Atlanta2.Level3.net (4.68.103.61) 4 msec
  2 ae-1-7.bar2.Cincinnati1.Level3.net (4.69.136.217) 12 msec 12 msec 16 msec
  3 ae-0-11.bar1.Cincinnati1.Level3.net (4.69.136.209) 12 msec 12 msec 80 msec
  4 BLUEMILE-IN.bar1.Cincinnati1.Level3.net (4.59.40.2) 16 msec 24 msec 16 msec
  5 76.10.192.226 [AS11013 {USMO-ASN}] 16 msec 16 msec 16 msec
  6 76.10.207.14.customer.bluemilenetworks.com (76.10.207.14) [AS11013 {USMO-ASN}] 16 msec 16 msec 16 msec
  7 OH-MLS1-609.Te-9-2.opentransfer.com (98.130.213.18) [AS32392 {Ecommerce}] 16 msec 16 msec 16 msec
  8  *  *  *
  9  *  *  *
 10  *  *  *
 11  *  *  *
 12  *  *  *
 13  *  *  *
 14  *  *  *
 15  *  *  *
 16  *  *  *
 17  *  *  *
 18  *  *  *
 19  *  *  * timeout !

Traceroute from Baltimore, MD -

  1 ge-6-15-14.car1.Philadelphia1.Level3.net (4.69.135.117) 4 msec 0 msec 0 msec
  2 ae-7-7.ebr2.Washington1.Level3.net (4.69.133.162) 8 msec 8 msec 4 msec
  3 ae-92-92.csw4.Washington1.Level3.net (4.69.134.158) 8 msec
    ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 16 msec 20 msec
  4 ae-91-91.ebr1.Washington1.Level3.net (4.69.134.141) 4 msec 8 msec 8 msec
  5 ae-2-2.ebr3.Atlanta2.Level3.net (4.69.132.85) 28 msec 20 msec 20 msec
  6 ae-72-70.ebr2.Atlanta2.Level3.net (4.69.138.19) 28 msec 20 msec 36 msec
  7 ae-1-7.bar2.Cincinnati1.Level3.net (4.69.136.217) 32 msec 36 msec 32 msec
  8 ae-0-11.bar1.Cincinnati1.Level3.net (4.69.136.209) 88 msec 36 msec 32 msec
  9 BLUEMILE-IN.bar1.Cincinnati1.Level3.net (4.59.40.2) 36 msec 36 msec 36 msec
 10 76.10.192.226 [AS11013 {USMO-ASN}] 36 msec 36 msec 36 msec
 11 76.10.207.14.customer.bluemilenetworks.com (76.10.207.14) [AS11013 {USMO-ASN}] 36 msec 36 msec 36 msec
 12 OH-MLS1-609.Te-9-2.opentransfer.com (98.130.213.18) [AS32392 {Ecommerce}] 36 msec 36 msec 36 msec
 13  *  *  *
 14  *  *  *
 15  *  *  *
 16  *  *  *
 17  *  *  *
 18  *  *  *
 19  *  *  *
 20  *  *  *
 21  *  *  *
 22  *  *  *
 23  *  *  *
 24  *  *  *
 25  *  *  * timeout !

Traceroute from Boston, MA -

  1 ae-2-7.bar1.Boston1.Level3.net (4.69.132.242) 0 msec 0 msec 0 msec
  2 ae-5-5.ebr1.Chicago1.Level3.net (4.69.140.94) 32 msec 24 msec 20 msec
  3 ae-1-100.ebr2.Chicago1.Level3.net (4.69.132.42) 32 msec 24 msec 24 msec
  4 ae-1-10.bar1.Cincinnati1.Level3.net (4.69.136.213) 28 msec 148 msec 28 msec
  5 BLUEMILE-IN.bar1.Cincinnati1.Level3.net (4.59.40.2) 32 msec 28 msec 32 msec
  6 76.10.192.226 [AS11013 {USMO-ASN}] 28 msec 28 msec 32 msec
  7 76.10.207.14.customer.bluemilenetworks.com (76.10.207.14) [AS11013 {USMO-ASN}] 32 msec 28 msec 32 msec
  8 OH-MLS1-609.Te-9-2.opentransfer.com (98.130.213.18) [AS32392 {Ecommerce}] 28 msec 32 msec 28 msec
  9  *  *  *
 10  *  *  *
 11  *  *  *
 12  *  *  *
 13  *  *  *
 14  *  *  *
 15  *  *  *
 16  *  *  *
 17  *  *  *
 18  *  *  *
 19  *  *  *
 20  *  *  *
 21  *  *  * timeout !

Traceroute from Baton Rouge, LA -

  1 ge-6-17-16.car1.Houston1.Level3.net (4.69.135.197) 12 msec 8 msec 8 msec
  2 ae-2-5.bar1.Houston1.Level3.net (4.69.132.230) 4 msec 36 msec 8 msec
  3 ae-0-11.bar2.Houston1.Level3.net (4.69.137.134) 8 msec 8 msec 4 msec
  4 ae-7-7.ebr1.Atlanta2.Level3.net (4.69.137.142) 28 msec 20 msec 36 msec
  5 ae-62-60.ebr2.Atlanta2.Level3.net (4.69.138.3) 28 msec 24 msec 32 msec
  6 ae-1-7.bar2.Cincinnati1.Level3.net (4.69.136.217) 36 msec 76 msec 32 msec
  7 ae-0-11.bar1.Cincinnati1.Level3.net (4.69.136.209) 36 msec 32 msec 36 msec
  8 BLUEMILE-IN.bar1.Cincinnati1.Level3.net (4.59.40.2) 36 msec 36 msec 36 msec
  9 76.10.192.226 [AS11013 {USMO-ASN}] 36 msec 36 msec 36 msec
 10 76.10.207.14.customer.bluemilenetworks.com (76.10.207.14) [AS11013 {USMO-ASN}] 36 msec 36 msec 40 msec
 11 OH-MLS1-609.Te-9-2.opentransfer.com (98.130.213.18) [AS32392 {Ecommerce}] 36 msec 36 msec 36 msec
 12  *  *  *
 13  *  *  *
 14  *  *  *
 15  *  *  *
 16  *  *  *
 17  *  *  *
 18  *  *  *
 19  *  *  *
 20  *  *  *
 21  *  *  *
 22  *  *  *
 23  *  *  *
 24  *  *  * timeout !

Traceroute from Burlington, VT -

  1 ge-6-22-12.car1.Philadelphia1.Level3.net (4.69.135.61) 28 msec 136 msec 92 msec
  2 ae-7-7.ebr2.Washington1.Level3.net (4.69.133.162) 24 msec 20 msec 24 msec
  3 ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 32 msec
    ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 24 msec
    ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 32 msec
  4 ae-91-91.ebr1.Washington1.Level3.net (4.69.134.141) 24 msec
    ae-71-71.ebr1.Washington1.Level3.net (4.69.134.133) 24 msec
    ae-91-91.ebr1.Washington1.Level3.net (4.69.134.141) 20 msec
  5 ae-2-2.ebr3.Atlanta2.Level3.net (4.69.132.85) 36 msec 44 msec 36 msec
  6 ae-72-70.ebr2.Atlanta2.Level3.net (4.69.138.19) 44 msec
    ae-62-60.ebr2.Atlanta2.Level3.net (4.69.138.3) 48 msec
    ae-72-70.ebr2.Atlanta2.Level3.net (4.69.138.19) 44 msec
  7 ae-1-7.bar2.Cincinnati1.Level3.net (4.69.136.217) 52 msec 48 msec 48 msec
  8 ae-0-11.bar1.Cincinnati1.Level3.net (4.69.136.209) 48 msec 48 msec 48 msec
  9 BLUEMILE-IN.bar1.Cincinnati1.Level3.net (4.59.40.2) 52 msec 52 msec 52 msec
 10 76.10.192.226 [AS11013 {USMO-ASN}] 52 msec 52 msec 52 msec
 11 76.10.207.14.customer.bluemilenetworks.com (76.10.207.14) [AS11013 {USMO-ASN}] 52 msec 52 msec 52 msec
 12 OH-MLS1-609.Te-9-2.opentransfer.com (98.130.213.18) [AS32392 {Ecommerce}] 52 msec 52 msec 52 msec
 13  *  *  *
 14  *  *  *
 15  *  *  *
 16  *  *  *
 17  *  *  *
 18  *  *  *
 19  *  *  *
 20  *  *  *
 21  *  *  *
 22  *  *  *
 23  *  *  *
 24  *  *  *
 25  *  * timeout !

Traceroute from Buffalo, NY -

  1 ge-6-18-22.car2.Pittsburgh3.Level3.net (4.69.136.5) 68 msec 8 msec 212 msec
  2 ae-3-3.ebr1.Chicago1.Level3.net (4.69.135.250) 32 msec 20 msec 36 msec
  3 ae-1-100.ebr2.Chicago1.Level3.net (4.69.132.42) 20 msec 20 msec 32 msec
  4 ae-1-10.bar1.Cincinnati1.Level3.net (4.69.136.213) 44 msec 32 msec 180 msec
  5 BLUEMILE-IN.bar1.Cincinnati1.Level3.net (4.59.40.2) 32 msec 32 msec 28 msec
  6 76.10.192.226 [AS11013 {USMO-ASN}] 32 msec 32 msec 32 msec
  7 76.10.207.14.customer.bluemilenetworks.com (76.10.207.14) [AS11013 {USMO-ASN}] 28 msec 32 msec 32 msec
  8 OH-MLS1-609.Te-9-2.opentransfer.com (98.130.213.18) [AS32392 {Ecommerce}] 32 msec 32 msec 32 msec
  9  *  *  *
 10  *  *  *
 11  *  *  *
 12  *  *  *
 13  *  *  *
 14  *  *  *
 15  *  *  *
 16  *  *  *
 17  *  *  *
 18  *  *  *
 19  *  *  *
 20  *  *  *
 21  *  *  * timeout !

Traceroute from Columbia, SC -

  1 ge-7-16.car2.Atlanta1.Level3.net (4.68.107.229) 4 msec *  12 msec
  2 ae-72-52.ebr2.Atlanta2.Level3.net (4.68.103.61) 220 msec
    ae-62-51.ebr2.Atlanta2.Level3.net (4.68.103.29) 220 msec
    ae-72-52.ebr2.Atlanta2.Level3.net (4.68.103.61) 204 msec
  3 ae-1-7.bar2.Cincinnati1.Level3.net (4.69.136.217) 200 msec 200 msec 208 msec
  4 ae-0-11.bar1.Cincinnati1.Level3.net (4.69.136.209) 204 msec 200 msec 200 msec
  5 BLUEMILE-IN.bar1.Cincinnati1.Level3.net (4.59.40.2) 60 msec 76 msec 204 msec
  6 76.10.192.226 [AS11013 {USMO-ASN}] 76 msec 200 msec 32 msec
  7 76.10.207.14.customer.bluemilenetworks.com (76.10.207.14) [AS11013 {USMO-ASN}] 200 msec 32 msec 28 msec
  8 OH-MLS1-609.Te-9-2.opentransfer.com (98.130.213.18) [AS32392 {Ecommerce}] 28 msec 24 msec 28 msec
  9  *  *  *
 10  *  *  *
 11  *  *  *
 12  *  *  *
 13  *  *  *
 14  *  *  *
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 07:08 AM
i'll ask Timns if he can check things out later, see if the server logs say anything.

incidently, my ip number has changed since yesterday so it looks like they aren't blocking me by a specific number - perhaps filtering me out though for a close match?
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 07:09 AM
Renegade, are we saying this really isn't anything specific to me then - it's quite a wide problem?
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: 4wd on October 08, 2010, 07:13 AM
From Renegades list, it looks like Ecommerce have a server problem.

As a temporary work around, you could try Hotspot Shield (http://hotspotshield.com/), (free VPN), that will save the trouble of continually working through an online proxy site.

PS: Here's the comic strip in case you were interested :)

[ You are not allowed to view attachments ]
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 07:14 AM
thanks, 4wd, i'll check out Hotspot Shield.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 08, 2010, 07:15 AM
Renegade, are we saying this really isn't anything specific to me then - it's quite a wide problem?

I'm not sure. Here are pings that resolve:

Spoiler
Level 3 Site:
        
Ping To:
        
Packet Size:
        
Packet Count:
        
IPv6:
    
ALL European sitesAmsterdam, NetherlandsAMSIX NAP AmsterdamBucharest, RomaniaBerlin, GermanyBrussels, BelgiumDublin, IrelandDusseldorf, GermanyFrankfurt, GermanyGeneva, SwitzerlandHamburg, GermanyLondon, EnglandLondon, England (2)Madrid, SpainManchester, UKMilan, ItalyMunich, GermanyParis, FrancePrague, Czech RepublicSofia, BulgariaStockholm, SwedenVienna, AustriaWarsaw, PolandZurich, SwitzerlandALL North American sitesAtlanta, GABaltimore, MDBoston, MABaton Rouge, LABurlington, VTBuffalo, NYColumbia, SCChicago, ILCharlottesville, VACincinnati, OHColumbus, OHCleveland, OHCharlotte, NCDallas, TXDenver, CODetroit, MIFIX-West NAP San JoseFort Lauderdale, FLFort Myers, FLGarden City, NYHarrisburg, PAHouston, TXJackson, MSJacksonville, FLKansas City, MOLos Angeles, CALexington, KYLittle Rock, ARLouisville, KYLas Vegas, NVMiami, FLMinneapolis, MNMobile, ALMontrealNorfolk, VANashville, TNNewark, NJNew York, NYOakland, CAOrlando, FLPhiladelphia, PAPhoenix, AZPittsburgh, PARaleigh, NCRichmond, VASacramento, CAState College, PAScranton, PASan Diego, CASeattle, WASan Francisco, CASan Jose, CASalt Lake City, UTSaint Louis, MOStamford, CTSyracuse, NYTampa, FLTorontoTri-Cities, TNTustin, CAWichita, KSWashington, DCWeehawken, NJ
        
        
        
        

Show Level 3 (ALL North American sites) Ping to www.head-in-the-clouds.com (98.131.45.219)

Ping from Atlanta, GA -

icmp_seq=0 time=16 ms
icmp_seq=1 time=16 ms
icmp_seq=2 time=16 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 16/16/16/16/0/0 ms

Ping from Baltimore, MD -

icmp_seq=0 time=32 ms
icmp_seq=1 time=36 ms
icmp_seq=2 time=36 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 32/34.667/36/36/1.333/1.886 ms

Ping from Boston, MA -

icmp_seq=0 time=32 ms
icmp_seq=1 time=28 ms
icmp_seq=2 time=32 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 28/30.667/32/32/1.886/2.667 ms

Ping from Baton Rouge, LA -

icmp_seq=0 time=36 ms
icmp_seq=1 time=36 ms
icmp_seq=2 time=40 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 36/37.333/36/40/2.309/3.266 ms

Ping from Burlington, VT -

icmp_seq=0 time=56 ms
icmp_seq=1 time=52 ms
icmp_seq=2 time=52 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 52/53.333/52/56/2.667/3.771 ms

Ping from Buffalo, NY -

icmp_seq=0 time=32 ms
icmp_seq=1 time=32 ms
icmp_seq=2 time=28 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 28/30.667/32/32/2.981/4.216 ms

Ping from Columbia, SC -

icmp_seq=0 time=24 ms
icmp_seq=1 time=28 ms
icmp_seq=2 time=28 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 24/26.667/28/28/3.266/4.619 ms

Ping from Chicago, IL -

icmp_seq=0 time=12 ms
icmp_seq=1 time=8 ms
icmp_seq=2 time=12 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 8/10.667/12/12/3.528/4.989 ms

Ping from Charlottesville, VA -

icmp_seq=0 time=52 ms
icmp_seq=1 time=52 ms
icmp_seq=2 time=52 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 52/52/52/52/3.528/4.989 ms

Ping from Cincinnati, OH -

icmp_seq=0 time=200 ms
icmp_seq=1 time=76 ms
icmp_seq=2 time=48 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 48/108/48/200/8.589/66.239 ms

Ping from Columbus, OH -

icmp_seq=0 time=28 ms
icmp_seq=1 time=28 ms
icmp_seq=2 time=24 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 24/26.667/28/28/8.692/66.265 ms

Ping from Cleveland, OH -

icmp_seq=0 time=20 ms
icmp_seq=1 time=20 ms
icmp_seq=2 time=16 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 16/18.667/20/20/8.794/66.292 ms

Ping from Charlotte, NC -

icmp_seq=0 time=20 ms
icmp_seq=1 time=20 ms
icmp_seq=2 time=40 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 20/26.667/20/40/9.286/66.959 ms

Ping from Dallas, TX -

icmp_seq=0 time=36 ms
icmp_seq=1 time=36 ms
icmp_seq=2 time=40 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 36/37.333/36/40/9.381/66.986 ms

Ping from Denver, CO -

icmp_seq=0 time=32 ms
icmp_seq=1 time=32 ms
icmp_seq=2 time=32 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 32/32/32/32/9.381/66.986 ms

Ping from Detroit, MI -

icmp_seq=0 time=16 ms
icmp_seq=1 time=16 ms
icmp_seq=2 time=16 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 16/16/16/16/9.381/66.986 ms

Ping from FIX-West NAP San Jose -

icmp_seq=0 time=56 ms
icmp_seq=1 time=60 ms
icmp_seq=2 time=60 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 56/58.667/60/60/9.475/67.012 ms

Ping from Fort Lauderdale, FL -

icmp_seq=0 time=32 ms
icmp_seq=1 time=32 ms
icmp_seq=2 time=28 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 28/30.667/32/32/9.568/67.039 ms

Ping from Fort Myers, FL -

icmp_seq=0 time=32 ms
icmp_seq=1 time=36 ms
icmp_seq=2 time=32 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 32/33.333/32/36/9.661/67.065 ms

Ping from Garden City, NY -

icmp_seq=0 time=32 ms
icmp_seq=1 time=32 ms
icmp_seq=2 time=32 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 32/32/32/32/9.661/67.065 ms

Ping from Harrisburg, PA -

icmp_seq=0 time=28 ms
icmp_seq=1 time=28 ms
icmp_seq=2 time=24 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 24/26.667/28/28/9.752/67.092 ms

Ping from Houston, TX -

icmp_seq=0 time=200 ms
icmp_seq=1 time=44 ms
icmp_seq=2 time=32 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 32/92/32/200/12.927/101.771 ms

Ping from Jackson, MS -

icmp_seq=0 time=40 ms
icmp_seq=1 time=40 ms
icmp_seq=2 time=40 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 40/40/40/40/12.927/101.771 ms

Ping from Jacksonville, FL -

icmp_seq=0 time=28 ms
icmp_seq=1 time=32 ms
icmp_seq=2 time=32 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 28/30.667/32/32/12.996/101.788 ms

Ping from Kansas City, MO -

icmp_seq=0 time=96 ms
icmp_seq=1 time=44 ms
icmp_seq=2 time=44 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 44/61.333/44/96/13.856/104.699 ms

Ping from Los Angeles, CA -

icmp_seq=0 time=68 ms
icmp_seq=1 time=68 ms
icmp_seq=2 time=68 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 68/68/68/68/13.856/104.699 ms

Ping from Lexington, KY -

icmp_seq=0 time=36 ms
icmp_seq=1 time=36 ms
icmp_seq=2 time=36 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 36/36/36/36/13.856/104.699 ms

Ping from Little Rock, AR -

icmp_seq=0 time=40 ms
icmp_seq=1 time=40 ms
icmp_seq=2 time=40 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 40/40/40/40/13.856/104.699 ms

Ping from Louisville, KY -

icmp_seq=0 time=208 ms
icmp_seq=1 time=204 ms
icmp_seq=2 time=204 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 204/205.333/204/208/13.92/104.715 ms

Ping from Las Vegas, NV -

icmp_seq=0 time=52 ms
icmp_seq=1 time=52 ms
icmp_seq=2 time=52 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 52/52/52/52/13.92/104.715 ms

Ping from Miami, FL -

icmp_seq=0 time=28 ms
icmp_seq=1 time=28 ms
icmp_seq=2 time=28 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 28/28/28/28/13.92/104.715 ms

Ping from Minneapolis, MN -

icmp_seq=0 time=16 ms
icmp_seq=1 time=20 ms
icmp_seq=2 time=20 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 16/18.667/20/20/13.984/104.732 ms

Ping from Mobile, AL -

icmp_seq=0 time=28 ms
icmp_seq=1 time=28 ms
icmp_seq=2 time=28 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 28/28/28/28/13.984/104.732 ms

Ping from Montreal -

icmp_seq=0 time=32 ms
icmp_seq=1 time=32 ms
icmp_seq=2 time=32 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 32/32/32/32/13.984/104.732 ms

Ping from Norfolk, VA -

icmp_seq=0 time=44 ms
icmp_seq=1 time=40 ms
icmp_seq=2 time=40 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 40/41.333/40/44/14.048/104.749 ms

Ping from Nashville, TN -

icmp_seq=0 time=24 ms
icmp_seq=1 time=20 ms
icmp_seq=2 time=20 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 20/21.333/20/24/14.111/104.766 ms

Ping from Newark, NJ -

icmp_seq=0 time=32 ms
icmp_seq=1 time=32 ms
icmp_seq=2 time=32 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 32/32/32/32/14.111/104.766 ms

Ping from New York, NY -

icmp_seq=0 time=32 ms
icmp_seq=1 time=28 ms
icmp_seq=2 time=32 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 28/30.667/32/32/14.174/104.783 ms

Ping from Oakland, CA -

icmp_seq=0 time=56 ms
icmp_seq=1 time=60 ms
icmp_seq=2 time=60 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 56/58.667/60/60/14.236/104.8 ms

Ping from Orlando, FL -

icmp_seq=0 time=28 ms
icmp_seq=1 time=24 ms
icmp_seq=2 time=24 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 24/25.333/24/28/14.298/104.817 ms

Ping from Philadelphia, PA -

icmp_seq=0 time=36 ms
icmp_seq=1 time=32 ms
icmp_seq=2 time=36 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 32/34.667/36/36/14.36/104.834 ms

Ping from Phoenix, AZ -

icmp_seq=0 time=60 ms
icmp_seq=1 time=60 ms
icmp_seq=2 time=60 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 60/60/60/60/14.36/104.834 ms

Ping from Pittsburgh, PA -

icmp_seq=0 time=20 ms
icmp_seq=1 time=24 ms
icmp_seq=2 time=20 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 20/21.333/20/24/14.422/104.851 ms

Ping from Raleigh, NC -

icmp_seq=0 time=36 ms
icmp_seq=1 time=36 ms
icmp_seq=2 time=36 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 36/36/36/36/14.422/104.851 ms

Ping from Richmond, VA -

icmp_seq=0 time=28 ms
icmp_seq=1 time=28 ms
icmp_seq=2 time=28 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 28/28/28/28/14.422/104.851 ms

Ping from Sacramento, CA -

icmp_seq=0 time=64 ms
icmp_seq=1 time=60 ms
icmp_seq=2 time=64 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 60/62.667/64/64/14.484/104.868 ms

Ping from State College, PA -

icmp_seq=0 time=24 ms
icmp_seq=1 time=24 ms
icmp_seq=2 time=24 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 24/24/24/24/14.484/104.868 ms

Ping from Scranton, PA -

icmp_seq=0 time=36 ms
icmp_seq=1 time=40 ms
icmp_seq=2 time=36 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 36/37.333/36/40/14.545/104.885 ms

Ping from San Diego, CA -

icmp_seq=0 time=68 ms
icmp_seq=1 time=68 ms
icmp_seq=2 time=68 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 68/68/68/68/14.545/104.885 ms

Ping from Seattle, WA -

icmp_seq=0 time=60 ms
icmp_seq=1 time=60 ms
icmp_seq=2 time=60 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 60/60/60/60/14.545/104.885 ms

Ping from San Francisco, CA -

icmp_seq=0 time=64 ms
icmp_seq=1 time=60 ms
icmp_seq=2 time=60 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 60/61.333/60/64/14.606/104.902 ms

Ping from San Jose, CA -

icmp_seq=0 time=60 ms
icmp_seq=1 time=56 ms
icmp_seq=2 time=60 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 56/58.667/60/60/14.667/104.919 ms

Ping from Salt Lake City, UT -

icmp_seq=0 time=140 ms
icmp_seq=1 time=44 ms
icmp_seq=2 time=204 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 44/129.333/204/204/16.492/123.821 ms

Ping from Saint Louis, MO -

icmp_seq=0 time=12 ms
icmp_seq=1 time=16 ms
icmp_seq=2 time=16 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 12/14.667/16/16/16.546/123.835 ms

Ping from Stamford, CT -

icmp_seq=0 time=40 ms
icmp_seq=1 time=40 ms
icmp_seq=2 time=40 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 40/40/40/40/16.546/123.835 ms

Ping from Syracuse, NY -

icmp_seq=0 time=40 ms
icmp_seq=1 time=40 ms
icmp_seq=2 time=44 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 40/41.333/40/44/16.6/123.849 ms

Ping from Tampa, FL -

icmp_seq=0 time=32 ms
icmp_seq=1 time=36 ms
icmp_seq=2 time=36 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 32/34.667/36/36/16.653/123.864 ms

Ping from Toronto -

icmp_seq=0 time=28 ms
icmp_seq=1 time=24 ms
icmp_seq=2 time=24 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 24/25.333/24/28/16.707/123.878 ms

Ping from Tri-Cities, TN -

icmp_seq=0 time=28 ms
icmp_seq=1 time=24 ms
icmp_seq=2 time=28 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 24/26.667/28/28/16.76/123.892 ms

Ping from Tustin, CA -

icmp_seq=0 time=68 ms
icmp_seq=1 time=68 ms
icmp_seq=2 time=72 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 68/69.333/68/72/16.813/123.907 ms

Ping from Wichita, KS -

icmp_seq=0 time=44 ms
icmp_seq=1 time=40 ms
icmp_seq=2 time=44 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 40/42.667/44/44/16.865/123.921 ms

Ping from Washington, DC -

icmp_seq=0 time=32 ms
icmp_seq=1 time=28 ms
icmp_seq=2 time=32 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 28/30.667/32/32/16.918/123.935 ms

Ping from Weehawken, NJ -

icmp_seq=0 time=32 ms
icmp_seq=1 time=32 ms
icmp_seq=2 time=28 ms

---- www.head-in-the-clouds.com statistics ----
3 packets transmitted, 3 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 28/30.667/32/32/16.971/123.95 ms



A DNS problem on the server's end? Results from it actually being cached at the ISP level? (unlikely)

I've seen lots of weirdness in the last while on my end here. I've been wondering about it being DNS issues, but they're just messed up. Dunno...

Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 07:17 AM
heheh. thanks, but i've seen the strip - Hide My Ass proxy let me get to the site pretty quick.



I'll see if Tim can answer anything later - if not, then I'll wait for the problem to magically resolve itself. If i'm not being blocked by the server then I don't mind so much - I can't get offended by that  :)
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 08, 2010, 07:31 AM
Everything (ftp and http) works fine with Hotspot Shield. (Seems it adds its own ad banners to the tops of pages though. No problem.)

The FTP access was the biggest problem so if the issues never gets resolved, at least, I know I can use something like HS as an FTP proxy.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Stoic Joker on October 08, 2010, 07:49 AM
I find that ISP DNS services are VERY often poor.

That's why I gave in and run my own DNS server now.  Haven't had a DNS problem since running it - apart from forgetting that the machine it's hosted on was turned off once or twice.

Same here :)

@nudone
From the tracert you posted, it almost seems like your IP is blocked at the remote end.  Since you're getting resolved IP addresses right up until the last hop that kind of implies the DNS servers are working.

Correct, a tracert "fails" at the last place a packet succeeded (that's how you know what's broken) - This is not a DNS issue - It's an address block(s) X got blocked by router config boo-boo Y issue most likely ... Some type of IDS hiccup I'd wager.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: timns on October 08, 2010, 11:06 AM
Hi folks, I just found this thread courtesy of nudone.

Thank you for all your efforts at looking into this. I'm glad Nick picked up on it - I'd hate to think that my other 2 readers are missing out on the comic strip as well  :P
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: web_stalker on October 09, 2010, 07:36 AM
I had similar problem i.e., some websites will not open without proxy server and other sites will open normally. After much troubleshooting and looking through and trying various suggestions, I at last changed MTU setting in my ADSL modem from 1500 (default) to 1400 and now all websites which would not previously open, opened normally. Hope that helps.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 09, 2010, 10:14 AM
I'll try those changes in the router when I get chance in a couple of days. In the meantime, timns has opened a ticket with the admin of the server that's the problem. So that may will lead somewhere yet.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: timns on October 09, 2010, 11:24 AM
and oh boy, were they hopeless when I did a 'live chat support' session.

I pasted a failed tracert to them, and the guy goes "those 3 stars at the end of the tracert mean you've reached your destination"  :-\

Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Stoic Joker on October 09, 2010, 12:13 PM
and oh boy, were they hopeless when I did a 'live chat support' session.

I pasted a failed tracert to them, and the guy goes "those 3 stars at the end of the tracert mean you've reached your destination"  :-\

 :o ...Okay, that's horrifying. Where do they find these people, Burger King?

The three "stars" followed by "Request timed out." mean (that hops) target is down, or not responding...however ICMP could be blocked. (In which case) You can have a perfectly functional target that blocks ICMP traffic that causes a trace to *** RTO all the way till it gives up at (default) hop 30. But that doesn't mean anything unless you know if the target will respond to a ping and/or is configured to do so.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: timns on October 09, 2010, 12:22 PM
I know, it makes you want to weep. I have a ticket so let's see if they have some real tech staff that they simply keep away from the first line support.

Yes, the site is pingable. Well, from here at any rate.

Would someone be able to do some tracerting to the site again next week perhaps please?

Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 09, 2010, 12:36 PM
Renegade was very helpful doing lots of tracerts. Hopefully he'll be so kind to do them again in a few days.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Stoic Joker on October 09, 2010, 12:54 PM
I'll forget by (an hour from now...) next week. But the site loads for me now. Here's how it got there:

C:\Users\Stoic Joker>tracert www.head-in-the-clouds.com

Tracing route to www.head-in-the-clouds.com [98.131.45.219]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    44 ms    44 ms    44 ms  fl-71-2-51-1.sta.embarqhsd.net [71.2.51.1]
  3    45 ms    44 ms    44 ms  205.245.63.13
  4    44 ms    45 ms    44 ms  host53.embarqservices.net [205.245.9.53]
  5    69 ms    69 ms    68 ms  te-7-2.car2.Orlando1.Level3.net [4.79.118.177]
  6    68 ms    69 ms    68 ms  ae-2-9.bar2.Orlando1.Level3.net [4.69.133.70]
  7    69 ms    69 ms    68 ms  ae-0-11.bar1.Orlando1.Level3.net [4.69.137.145]
  8    74 ms    71 ms    71 ms  ae-8-8.ebr1.Atlanta2.Level3.net [4.69.137.150]
  9    76 ms    71 ms    72 ms  ae-72-70.ebr2.Atlanta2.Level3.net [4.69.138.19]
 10    90 ms    90 ms   147 ms  ae-1-7.bar2.Cincinnati1.Level3.net [4.69.136.217]
 11    90 ms    90 ms    89 ms  ae-0-11.bar1.Cincinnati1.Level3.net [4.69.136.209]
 12    92 ms    93 ms    93 ms  BLUEMILE-IN.bar1.Cincinnati1.Level3.net [4.59.40.2]
 13    92 ms    92 ms    92 ms  76.10.192.226
 14    93 ms    92 ms    93 ms  76.10.207.14.customer.bluemilenetworks.com [76.10.207.14]
 15    92 ms    93 ms    92 ms  oh-mls1-609.te-9-2.opentransfer.com [98.130.213.18]
 16    93 ms    93 ms    95 ms  rev.opentransfer.com.219.45.131.98.in-addr.arpa [98.131.45.219]

Trace complete.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: timns on October 09, 2010, 03:31 PM
Oh, it must have "magically gone right all by itself"
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 09, 2010, 06:37 PM
Renegade was very helpful doing lots of tracerts. Hopefully he'll be so kind to do them again in a few days.

You don't need me to do it. All you need is a looking glass. There are lots of them out there. I was using the Level 3 Looking Glass (http://www.level3.com/LookingGlass/).

Here's a list of them (http://www.traceroute.org/).

Just find a trace route in one of them and enter the address along with something like "All North America" or a specific city. It takes a while though. Expect it to take 45 minutes or more. Just leave your browser open.

Looking glasses are essential for a lot of things, and it's good to keep them in mind as they are such valuable tools. If you're not familiar with them, try some out and bookmark a few.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: timns on October 11, 2010, 11:00 AM
I just got this reply from the admins on my host:

I want to let you know that our system administrators reviewed your traceroute logs and explained that they are absolutely normal, there is nothing strange. They explained that for other networks (ourside of our office) it is normal to have time outs after our MLSes, right after this line:
OH-MLS1-609.Te-9-2.opentransfer.com (98.130.213.18) [AS32392 {Ecommerce}]
That's why please re-check this issue from your side once again, make sure that there are no problems in your network, contact your ISP to investigate it from their side as well.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Carol Haynes on October 11, 2010, 11:59 AM
What you have to realise is that all support centres assume that if there is a problem it must be on your computer/network.

They are absolutely perfect and couldn't possibly have a fault.

I have had the same problem with BT in the past in the UK - my IP dies or get allocated a dead IP but it isn't their fault. Strange though that when I disconnect and reconnect it all works fine with an IP on a different server!

If it is a DNS fault there is nothing you can do about it except use a different DNS at least temporarily - try Google DNS or OpenDNS and see if that resolves the problem.

Set up TCP/IP on your connection to use the chosen DNS then open a command window and try the following:

ipconfig /flushdns
ipconfig /release
ipconfig /renew
ipconfig /all

check that your active connection has the correct DNS servers - can you connect now?
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 11, 2010, 01:32 PM
Doesn't work for me, Carol. As mentioned before, using Google DNS or Open DNS settings didn't make any difference (my default dns is google's). I've just had another go after trying the above ipconfig commands again - problem remains.

I'll see what my ISP has to say, TalkTalk. I imagine that it will be a waste of time doing so.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Carol Haynes on October 11, 2010, 05:44 PM
Can you configure the DNS in the router?
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: 4wd on October 11, 2010, 08:26 PM
I want to let you know that our system administrators reviewed your traceroute logs and explained that they are absolutely normal, there is nothing strange. They explained that for other networks (ourside of our office) it is normal to have time outs after our MLSes, right after this line:
OH-MLS1-609.Te-9-2.opentransfer.com (98.130.213.18) [AS32392 {Ecommerce}]
That's why please re-check this issue from your side once again, make sure that there are no problems in your network, contact your ISP to investigate it from their side as well.

It always makes me glad that they refer to themselves as 'administrators', (which has connotations more towards management), if they were technicians I'd be ashamed - plus they wouldn't last 10 minutes in a real job.

Honestly, does that really explain why it works from Australia?

EDIT: Then again, every dog and his man seems to think they're a technician these days: eg. Hair Technician.

Sorry if you refer to yourself as a System Administrator.  :P
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 11, 2010, 10:26 PM
Sigh...

[ You are not allowed to view attachments ]

[ You are not allowed to view attachments ]

I just don't know HOW this stuff gets so screwed up!

If anyone has any clues, please speak up.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 11, 2010, 11:27 PM
My wife just got the same 403 there, and I'm getting the normal Facebook. She hit CTRL + F5 and it's back to normal. Facebook is just bizarre.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 12, 2010, 02:03 AM
Can you configure the DNS in the router?

Yes, that's using the router dns settings. I haven't changed anything on any of the computers connected to the router, i.e. the computers don't have any specific dns settings.

I suppose I really will have to try another router. I was just trying to avoid that because of all the faffing about that'll be involved.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Carol Haynes on October 12, 2010, 03:10 AM
I suppose you checked the router firewall logs?

Have you tried factory resetting the router and setting it up from scratch?
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 12, 2010, 04:02 AM
Router log doesn't show anything other than Admin logins, so nothing helpful there. I've tried changing the MTU to 1500 and 1400, no improvement there either.

I'm going to try swapping over the router later today. That way I can eliminate the current router completely and I don't need to factory reset it. If the other router allows the connection to work, then I'll reset the dodgy router.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Stoic Joker on October 12, 2010, 07:38 AM
It always makes me glad that they refer to themselves as 'administrators', (which has connotations more towards management), if they were technicians I'd be ashamed - plus they wouldn't last 10 minutes in a real job.

Speaking as one whose job title actually is Network Administrator, I'd just like to say that I've always found the connotations a bit troubling myself. ;)

Side note if this was a DNS issue you'd either have no target, or the wrong target. Unless it was the hosting companies internal DNS that was borking the Host Header resolution (I have seen that happen). However, given that the site loads with either the FQDN or the IP address it can't be an HH issue.

Try pinging the site (www.head-in-the-clouds.com) ... Now reguardless of if/how it answers if the IP resolve to 98.131.45.219, stop looking at DNS because its job is done. :)

That last hop is across their internal network (whois on IP shows it's a single contiguous block owned by E-Commerce Hosting). This thing has borked routing table written all over it.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Renegade on October 12, 2010, 08:18 AM
That last hop is across their internal network (whois on IP shows it's a single contiguous block owned by E-Commerce Hosting). This thing has borked routing table written all over it.

So, in layman's speak, is that, "the hosting company is dropping the ball, so get a new one"?
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 12, 2010, 09:25 AM
Try pinging the site (www.head-in-the-clouds.com) ... Now reguardless of if/how it answers if the IP resolve to 98.131.45.219, stop looking at DNS because its job is done. :)

hmm, never thought of that. yes. when i ping the domain it does resolve to that IP. so, i guess, we rule out DNS it seems.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: timns on October 12, 2010, 12:30 PM
I just set up an account with 'Pingdom' and I believe they load my homepage every minute from a random server. Here are the first few results:

Date/Time    Status    Response Time    Error    Location   
12/10/10 10:29   UP   784 ms   OK   New York, NY   
12/10/10 10:28   UP   1,101 ms   OK   Chicago, IL   
12/10/10 10:27   UP   1,527 ms   OK   Copenhagen, Denmark   
12/10/10 10:26   UP   1,382 ms   OK   Tampa, Florida   
12/10/10 10:25   UP   1,633 ms   OK   Seattle, WA   
12/10/10 10:24   UP   760 ms   OK   Washington, DC   
12/10/10 10:23   UP   1,426 ms   OK   Madrid, Spain   
12/10/10 10:22   UP   1,102 ms   OK   Las Vegas, NV   
12/10/10 10:21   UP   839 ms   OK   Denver, CO   
12/10/10 10:20   UP   1,092 ms   OK   San Francisco, CA   
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: 4wd on October 12, 2010, 09:53 PM
I just set up an account with 'Pingdom' and I believe they load my homepage every minute from a random server. Here are the first few results:

You seriously need another host, my ping times are lower than the ones from the hosts country, and I'm on the other side of the planet:

C:\>ping 98.131.45.219

Pinging 98.131.45.219 with 32 bytes of data:
Reply from 98.131.45.219: bytes=32 time=288ms TTL=43
Reply from 98.131.45.219: bytes=32 time=330ms TTL=43
Reply from 98.131.45.219: bytes=32 time=492ms TTL=43
Reply from 98.131.45.219: bytes=32 time=541ms TTL=43

Ping statistics for 98.131.45.219:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 288ms, Maximum = 541ms, Average = 412ms
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Stoic Joker on October 13, 2010, 07:22 AM
That last hop is across their internal network (whois on IP shows it's a single contiguous block owned by E-Commerce Hosting). This thing has borked routing table written all over it.

So, in layman's speak, is that, "the hosting company is dropping the ball, so get a new one"?

That seems a bit harsh, but depending on how many people are affected if they're unwilling to fix (or admit to) the problem it may be necessary.

The original question was ISP vs. Host because proxy worked. If the ISP was blocking then the trace would have stopped in the first few hops. If there is a very small number of addresses blocked (e.g. nobody else is complaining) then walking them by the hand to the issue (Given their absurd assertion that intermittent ICMP traffic is normal) could be next to impossible.


@4wd - That is odd, my ping times from here are much faster:

C:\Windows\system32>ping www.head-in-the-clouds.com

Pinging www.head-in-the-clouds.com [98.131.45.219] with 32 bytes of data:
Reply from 98.131.45.219: bytes=32 time=71ms TTL=48
Reply from 98.131.45.219: bytes=32 time=71ms TTL=48
Reply from 98.131.45.219: bytes=32 time=71ms TTL=48
Reply from 98.131.45.219: bytes=32 time=71ms TTL=48

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

C:\Windows\system32>
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: timns on October 13, 2010, 10:01 AM
I just set up an account with 'Pingdom' and I believe they load my homepage every minute from a random server. Here are the first few results:

You seriously need another host, my ping times are lower than the ones from the hosts country, and I'm on the other side of the planet:

C:\>ping 98.131.45.219

Pinging 98.131.45.219 with 32 bytes of data:
Reply from 98.131.45.219: bytes=32 time=288ms TTL=43
Reply from 98.131.45.219: bytes=32 time=330ms TTL=43
Reply from 98.131.45.219: bytes=32 time=492ms TTL=43
Reply from 98.131.45.219: bytes=32 time=541ms TTL=43

Ping statistics for 98.131.45.219:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 288ms, Maximum = 541ms, Average = 412ms

In my post, these were page load times for the front page, so not too bad.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 13, 2010, 10:27 AM
I think it's time to get out the incense and candles and I'll start praying to the god of the internet. One day, I know that this connection will work again - I just have to remain faithful and believe the Internet God will show mercy. Join withe me and let's pray together...
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: 4wd on October 13, 2010, 07:19 PM
I think it's time to get out the incense and candles and I'll start praying to the god of the internet. One day, I know that this connection will work again - I just have to remain faithful and believe the Internet God will show mercy. Join withe me and let's pray together...

I think it would be more appropriate to intone: "OMMM.........", and then hit yourself in the head with a plank of wood.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on October 13, 2010, 09:53 PM
Good idea. Experiencing these kinds of connection problems is not unlike banging your head against a brick wall. The plank of wood will definitely feel more pleasurable in contrast.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on November 05, 2010, 12:04 PM
Well. Hooray for that...

without doing anything at all, I am now able to connect to the Head in the Clouds server once more.

Seems the world wide web weather has stopped blowing my little boat away from the shores of the HITC island.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: timns on November 05, 2010, 12:13 PM
Now if only it had been worth the wait...  :)
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: cranioscopical on November 05, 2010, 02:10 PM
Now if only it had been worth the wait...  :)
Worth its wait in nold!
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: timns on November 05, 2010, 02:13 PM
mold?
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Carol Haynes on November 05, 2010, 02:30 PM
Well. Hooray for that...

without doing anything at all, I am now able to connect to the Head in the Clouds server once more.

Seems the world wide web weather has stopped blowing my little boat away from the shores of the HITC island.

Glad it is now working but it doesn't help understand what is going on - the only thing you can say is it was nothing to do with your network or PC !!! Try asking your ISP why it has suddenly started working again.
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: Stoic Joker on November 05, 2010, 02:56 PM
Given where the trace routs were failing his ISP won't have a clue (nor should they really). I was looking like a corrupt routing table at the hosting companies border.

Send packets from network X to ... outer space :)
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on November 06, 2010, 07:33 AM
Yeah, I think I'll just put this down to one of those mysteries of being online. I'm just glad it works 99.9% of the time. I'm STILL amazed that the internet even exists. It's all magic to me.

As for asking TalkTalk what the problem was - they still haven't managed to deliver the router to a friend I know that signed up about 2 months ago. If they have no idea where their routers are going I don't think they'll care where other things are getting lost :-)
Title: Re: if proxy connection works - who is blocking me: my ISP or the server?
Post by: nudone on November 08, 2010, 07:57 AM
Excellent. I'm glad to say that everything is back to normal, i.e. NOT WORKING.

My connection is unable to resolve HITC again. I find it comforting that I can rely on this consistent level of crapness.