HELP! Cannot access photo.net !

<p>I can access photo.net through an open proxy in the US, but not with the "no proxy" setting in my browser. This was not the case before the recent downtime. I do not know if my ISP runs a transparent proxy. I am near Calcutta and my ISP is BSNL (can somebody from Calcutta/Kolkata confirm if they are having a similar problem?). No other site is causing a problem, and I have already rebooted my DSL modem, wireless router and Vista 32bit machine.</p>

<p>edit: sorry about the horrible formatting below, I have no idea how to copy without formatting from chrome or firefox... and the html is hard to look at...</p>

<p>Chrome shows this:<br /> Google Chrome could not load the webpage because <strong>photo.net</strong> took too long to respond. The website may be down, or you may be experiencing issues with your Internet connection.<br /> Firefox shows this:<br /> The connection has timed out<br />The server at photo.net is taking too long to respond.<br /> nslookup output (using google and my ISP's DNS; I am using google, but both DNS servers seem to tally) (cygwin on vista)<br /> > server 8.8.8.8<br />Default Server: google-public-dns-a.google.com<br />Address: 8.8.8.8<br /><br />> photo.net<br />Server: google-public-dns-a.google.com<br />Address: 8.8.8.8<br /><br />Non-authoritative answer:<br />photo.net<br /> primary name server = ns1.photo.net<br /> responsible mail addr = hostmaster.photo.net<br /> serial = 2011081102<br /> refresh = 14400 (4 hours)<br /> retry = 7200 (2 hours)<br /> expire = 604800 (7 days)<br /> default TTL = 7200 (2 hours)<br />photo.net nameserver = ns2.photo.net<br />photo.net nameserver = ns1.photo.net<br />photo.net MX preference = 0, mail exchanger = mail.photo.net<br />photo.net text =<br /><br /> "v=spf1 mx a:mail.photo.net a:smtpout1.namemedia.com a:smtpout2.namemedi<br />emedia.com a:mail.buydomains.com ip4:206.83.79.0/24 ~all"<br />photo.net internet address = 64.95.64.39 > server 218.248.241.6<br />Default Server: [218.248.241.6]<br />Address: 218.248.241.6<br /><br />> photo.net<br />Server: [218.248.241.6]<br />Address: 218.248.241.6<br /><br />photo.net<br /> primary name server = ns1.photo.net<br /> responsible mail addr = hostmaster.photo.net<br /> serial = 2011081102<br /> refresh = 14400 (4 hours)<br /> retry = 7200 (2 hours)<br /> expire = 604800 (7 days)<br /> default TTL = 7200 (2 hours)<br />photo.net nameserver = ns1.photo.net<br />photo.net nameserver = ns2.photo.net<br />photo.net MX preference = 0, mail exchanger = mail.photo.net<br />photo.net text =<br /><br /> "v=spf1 mx a:mail.photo.net a:smtpout1.namemedia.com a:smtpout2.namemedi<br />emedia.com a:mail.buydomains.com ip4:206.83.79.0/24 ~all"<br />photo.net internet address = 64.95.64.39<br />ns1.photo.net internet address = 64.95.64.94<br />ns2.photo.net internet address = 64.95.64.97<br />mail.photo.net internet address = 64.95.64.44<br /> So how do I get to access photo.net normally? Is my IP (dynamic, currently 59.93.192.115) / ISP on a blacklist of some sort? I sometimes have problems accessing some moderated forums elsewhere, but have never had a problem on photo.net?</p>

<p>What happens when you run a trace route from your desktop to 64.95.64.39?<br /><br />That will show at which hop along the way your traffic is dying.</p>

<p>Thanks Matt, here's the output from windows.. probably does not show UDP, I'm going to look where tracert is in cygwin...<br /> (Quite a trip, wish I were a packet..)</p>

<p>PS: tracert in cygwin shows the same as below</p>

<p>C:\Users\indraneel>tracert 64.95.64.39<br /><br />Tracing route to www.photo.net [64.95.64.39]<br />over a maximum of 30 hops:<br /><br /> 1 <1 ms <1 ms <1 ms 192.168.2.1<br /> 2 7 ms 7 ms 7 ms 59.93.192.1<br /> 3 6 ms 6 ms 5 ms 218.248.255.10<br /> 4 40 ms 40 ms 40 ms 59.163.207.81.static.chennai.vsnl.net.in [59.163<br />.207.81]<br /> 5 65 ms 65 ms 65 ms 59.163.16.1.static.vsnl.net.in [59.163.16.1]<br /> 6 66 ms 65 ms 65 ms 59.163.16.1.static.vsnl.net.in [59.163.16.1]<br /> 7 64 ms 64 ms 64 ms if-15-1-0.core1.MLV-Mumbai.as6453.net [209.58.10<br />5.153]<br /> 8 325 ms 326 ms 336 ms if-3-1-0-0.tcore1.MLV-Mumbai.as6453.net [180.87.<br />38.10]<br /> 9 337 ms 336 ms 337 ms if-2-2.tcore2.MLV-Mumbai.as6453.net [180.87.38.2<br />]<br /> 10 323 ms 324 ms 324 ms if-6-2.tcore1.L78-London.as6453.net [80.231.130.<br />5]<br /> 11 329 ms 329 ms 330 ms if-2-2.tcore2.L78-London.as6453.net [80.231.131.<br />1]<br /> 12 330 ms 330 ms 330 ms if-8-23.tcore1.NYY-NewYork.as6453.net [80.231.13<br />1.46]<br /> 13 317 ms 317 ms 318 ms jfk-brdr-04.inet.qwest.net [63.146.27.41]<br /> 14 * * * Request timed out.<br /> 15 347 ms 350 ms 351 ms 65.120.117.250<br /> 16 355 ms 353 ms 350 ms border7.po2-bbnet2.bsn.pnap.net [63.251.128.76]<br /><br /> 17 348 ms 348 ms 348 ms 66.150.193.153<br /> 18 * * * Request timed out.<br /> 19 * * * Request timed out.<br /> 20 * * * Request timed out.<br /> 21 * * * Request timed out.<br /> 22 * * * Request timed out.<br /> 23 * * * Request timed out.<br /> 24 * * * Request timed out.<br /> 25 * * * Request timed out.<br /> 26 * * * Request timed out.<br /> 27 * * * Request timed out.<br /> 28 * * * Request timed out.<br /> 29 * * * Request timed out.<br /> 30 * * * Request timed out.<br /><br />Trace complete.<br /><br />C:\Users\indraneel></p>

<p>I'm accessing the site just fine, and a trace from my end stops at exactly the same IP address. Safe to say that's a firewall, and the rest of the trip is behind that firewall, where TRACERT and PING type stuff isn't allowed to report back. That's perfectly normal.<br /><br />Your route through Mumbai and London does include some pretty sleepy-looking hops, though ... over two seconds from Mumbai to New York, which seems inordinately long, even for the distance. That section of the trip is across some devices owned by the amusingly named Tata Communications, Ltd, of Alandhi Road, Dighi. <br /><br />Your packets are certainly making it to whatever network layer is just upstream from PN's servers, but that firewall may indeed have a bee in its bonnet over traffic coming in from that range of IP addresses. Josh and company will have to see there's a blacklist involved, or if perhaps that firewall doesn't play nice with remote hosts that are on such a slow round trip, packet-wise.</p>

<p>I'm surprised my measly packet is making all the way below the Atlantic and getting stuck on the East coast! Tata happens to be one of the biggest conglomerates in india, seems like I can't blame them this time :(</p>

<p>Hope Josh looks at this soon. I've never encountered such a silent firewall before, even if I'm blacklisted (wonder how big the address block is...). It's no fun going through an open proxy, it's even slower, and probably no security to boot.</p>

<p>If you are using an open proxy, we may have blocked it in the past. Please email me your IP address as it appears from the outside and I will check (whatismyip.net).</p>

 

<p>The open proxy is working. My connection without a proxy is not (ie. the way I normally access all sites on the internet) . IP is 59.93.192.115 (currently; also, please see above).</p>

<p>This is a problem for me only with photo.net, and did not exist before the move.</p>

<p>I still cannot access photo.net without a proxy :( All other sites work fine.</p>

<p>I'll have Jin look at it again.</p>

<p>I will say that PN gets a LOT of comment/SEO spam from india. We end up blocking IP's from the region every so often when the spammers are particularly active.</p>

<p>Still cannot access directly! Am I really the only one having this problem, can't believe it!</p>

<p>Would that mean that India's biggest spammers live in my neighborhood ?!</p>

<p>Please give it another try. You should be able to reach the site now.</p>

<p>Yep, it works now ! Thanks a bunch !</p>