Site not accessible, nor torrent trackers from gotwoot

[Myllonn]

Hello,

I tried for weeks now to get on your homepage (www.gotwoot.net). I always have the same error message (can't find the server). It's the same with every torrent i tried to DL from gotwoot (I find your links on downloadanime.org). By chance, i found your forum. It's separated from the main site, and i believe, on another server.

Do you know what is the problem ? Is my ISP (tiscali.fr, in france) blocking the access on this site ? Is there any special command to access here ? First time i have this problem with a site (and torrents btw).

[-ANBU-Sasuke-]

My best guest would be your internet filtering, and settings. Somethings restricting your downloads and the page.

if not im not sure sorry.

[martes]

I got the same problem.I can't access Gotwoot.net because of error message.Should I use proxy settings.What should I use?I haven't got problems before.Since famous "Port blocking" I can do nothing.
What's the point?And one more thing.I got DSL connection and IP starting 83.xx...Isn't your site blocking connections with IP starting from 83.xx...?

[Myllonn]

It's very specific to gotwoot. I'm going to check with my ISP then. Thx for the answers. (and i am not behind a proxy, only a firewall)

[martes]

Now I can access gotwoot site.How did I do it? I've changed proxy settings.I live in Poland and use proxy adress: w3cache.icm.edu.pl port: 8080.I haven't use any proxy before so this can help.

[Lego]

It might not be you martes. Sometimes the gotwoot forums are unaccedible to me for a few hours, but others can go on them. Maybe wilik or ciber can answer why this happens.

[Majkel]

It's not only for martes. I have the same problem and it is because of IP pool Polish Telecom recently bought (ip starting with 83). Since it was not used for a long time, to prevent hackers from using it many administrators have blocked it entirely on their routers/servers. And now it seems, that some of them have not updated their settings.
Problems with WWW are easily solved with a proxy, but I don't think you can use proxy with bittorrent [img]i/expressions/face-icon-small-sad.gif[/img] At least not the versions I have seen.

Maybe GotWoot admins could do something about it?

[Myllonn]

I found that i have an ip with 83.xxx etc I can't reach the site, but with a proxy, i can. And i can download too torrents from gotwoot now. It's very slow but it's working. Thx again.

[tranq]

I too cannot access www.gotwoot.net or download any eps via Bittorrent using gotwoots tracker.
I live in the Isle of Man (a small island around the UK) and my IP is also 83.x.x.x

I did used to have an IP starting with 195 or 217 but since switching ISPs I now only have 83.x.x.x IP's.

A trace route to www.gotwoot.net (69.56.211.107) gave the following results...

1 48 ms 27 ms 13 ms 195.10.119.94
2 19 ms 60 ms 101 ms 195.10.119.158
3 21 ms 24 ms 16 ms 217.23.160.1
4 12 ms 12 ms 12 ms 217.23.162.122
5 14 ms 13 ms 55 ms 217.23.160.85
6 85 ms 135 ms 155 ms 217.23.160.186
7 30 ms 151 ms 83 ms tier1-1.BUD2.psie.net [154.14.68.113]
8 157 ms 76 ms 68 ms ge3-0.pr1.lhr1.uk.above.net [195.66.224.76]
9 73 ms 47 ms 53 ms pos3-0.mpr1.lhr1.uk.above.net [208.184.231.69]
10 27 ms 36 ms 24 ms so-5-3-0.cr1.lhr3.uk.above.net [208.184.231.178]
11 107 ms 100 ms 187 ms so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
12 314 ms 142 ms 140 ms so-0-0-0.cr2.dca2.us.above.net [64.125.29.122]
13 125 ms 269 ms 272 ms so-2-2-0.cr2.dfw2.us.above.net [64.125.29.9]
14 254 ms 186 ms 145 ms 216.200.88.141.available.above.net [216.200.88.141]
15 132 ms 134 ms 129 ms car2-2-v1.dllstx2.theplanet.com [12.96.160.14]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.

Which suggests the router at #15 is sending my packets to a router refusing my IP by some rule or another. (or #15 could have a deny access list with 83.x.x.x on it's out interface - but unlikely)

Perfoming a whois on theplanet.com gives...

Registrant:
ThePlanet.com Internet Services, Inc.

Address:
1950 Stemmons Frwy
Suite 3048
Dallas, TX 75207
US

First Registered:
March 11, 1999

Last Updated:
February 24, 2003

Administrative Contact:
Planet, The support@theplanet.com
1950 Stemmons Frwy
Suite 3048
Dallas, TX 75207
US
2148005999 Fax: 2148005998

Technical Contact:
Support, Technical support@theplanet.com
1950 Stemmons Fwy
Suite 3048
Dallas, Texas 75207
US
214-800-5999 Fax: 214-800-5998

Name Servers:
NS1.THEPLANET.COM 216.234.234.30
NS2.THEPLANET.COM 12.96.160.115

Information Source:
OpenSRS



I guess they are the only ones who knows where IP packets from 83.x.x.x are going.

It would be interesting to see if a Gotwoot admin could perform a trace to a known 83.x.x.x address and see where the packets stopped.

I don't have access to a proxy so I guess I'm doomed... DOOMED I say!!!

[hiroshi]

(Sigh). Oh if only you people knew how sneaky ISPs really are. The reason you are able to access some sites, and not others, and the reason it suddenly works after changing your proxy, is because:

When an ISP considers that you're using up a lot of bandwidth, they redirect your IP to a 'cached' proxy. They may have only one, or multiple amounts of these servers, but the idea is, that instead of you using their precious bandwidth to load up websites, the proxy instead sends you a 'cached' version of that website. But then what happens if the website you're visiting isn't cached in the proxy?

Well sometimes it does actually retrieve the information properly, but quite often they will simply fail to get the website and return an error of some kind. This is just one among many nasty tactics that ISP tend to use.

Another nasty tactic is to reduce your speed. They will do this without notification, and quite often they get away with it, because people are fooled into thinking it's the server/client they are connecting to rather than their actual ISP. For instance, i've noticed on my own connection that my download rates tend to max out my bandwidth at the beginning of each month when my IP has refreshed and is new. But later on in the month, perhaps about halfway through, my speeds will reduce to about 30 - 40KBps instead of their usual 112KBps. At first i figured it was just the file i was downloading, but after about 3 or 4 months of observation i can clearly see a pattern. That's when i did some checking and found out it's my ISP. It isn't just my ISP that does that either, it's a lot of ISP's. This is how they are able to offer 'unlimited' bandwidth without capping the amount. They slow the connection down a little so that by the end of the month, you would of only used so much of their bandwidth up as to act as an invisible cap limit. That way, it's more subtle and causes less complaints and problems with customers. =P

Anyway, in order to fix your said problem, manually put in one of their alternative proxy servers. Make a quick google on your ISP + Proxy addresses or something and see what alternative addresses you can find. Generally most ISPs have quite a few of them hanging around.

[hiroshi]

Oh and in regards to the tracker. If the front page says "Server Status: Down" which it did for a very long time indeed, then it's no surprise that the tracker will stop working too.

Simply wait things out for the Tracker to pop back up. The website should work fine, using a proxy as mentioned would fix the problem in regards to accessing the actual website.

No doubt the trackers are probably back up and working now that the status is back to "Online" ^_^

[Justhecuke]

ok, my isp uses a 61.xxx and 221.XXX ip, and i still cant get onto www.gotwoot.net .... it is very strange sine i almost couldnt even post this message. Also, I HAVE NO IDEA WHAT TO DO. a proxy didnt solve the problem for me, and my isp is an obscure chinese adsl company........ anything info would be fine [img]i/expressions/face-icon-small-smile.gif[/img]

[kaleyeope]

OK, I'm sorry but pretty much this whole post is bunk!

Originally posted by: hiroshi
(Sigh). Oh if only you people knew how sneaky ISPs really are. The reason you are able to access some sites, and not others, and the reason it suddenly works after changing your proxy, is because:

When an ISP considers that you're using up a lot of bandwidth, they redirect your IP to a 'cached' proxy. They may have only one, or multiple amounts of these servers, but the idea is, that instead of you using their precious bandwidth to load up websites, the proxy instead sends you a 'cached' version of that website.

Partial bunk. Web proxies and mass caching machines are a standard part of the internet. There is NO correlation between their use and ISP bandwidth policies for an individual. They are you friends! They make things faster for you.

But then what happens if the website you're visiting isn't cached in the proxy?

Well sometimes it does actually retrieve the information properly, but quite often they will simply fail to get the website and return an error of some kind. This is just one among many nasty tactics that ISP tend to use.

Complete and utter Bunk. If you are going through a caching server and your information is not there, then you get redirected to the original server, the information that you receive is sent to both your home machine and the cache server so that the next time someone wants to access that site, there is information already available. The information will expire so you don't get stale web sites. If it doesn't work like this, then the cache servers are broken.

Another nasty tactic is to reduce your speed. They will do this without notification, and quite often they get away with it, because people are fooled into thinking it's the server/client they are connecting to rather than their actual ISP. For instance, i've noticed on my own connection that my download rates tend to max out my bandwidth at the beginning of each month when my IP has refreshed and is new. But later on in the month, perhaps about halfway through, my speeds will reduce to about 30 - 40KBps instead of their usual 112KBps. At first i figured it was just the file i was downloading, but after about 3 or 4 months of observation i can clearly see a pattern. That's when i did some checking and found out it's my ISP. It isn't just my ISP that does that either, it's a lot of ISP's.

I wont argue that ISPs have some weird and arbitrary bandwidth policies, but what you describe does not make sense unless you are encountering a monthly cap limit (which is usually only seen in things like server co-location services, not home access). If they advertise unlimited access and you find that they actually have placed bandwidth caps on you account regularly, complain, loudly.

This is how they are able to offer 'unlimited' bandwidth without capping the amount. They slow the connection down a little so that by the end of the month, you would of only used so much of their bandwidth up as to act as an invisible cap limit. That way, it's more subtle and causes less complaints and problems with customers. =P

This makes absolutely no sense at all. You cannot save or build up a storage of bandwidth. There is not one monthly supply that can be doled out however you wish. There is a constant amount of bandwidth available at all times. If it goes unused, it is lost forever. If your going to get capped, it will most likely be real time not a couple weeks later.

also, it would be an across the board cap. Not site specific.

Anyway, in order to fix your said problem, manually put in one of their alternative proxy servers. Make a quick google on your ISP + Proxy addresses or something and see what alternative addresses you can find. Generally most ISPs have quite a few of them hanging around.

I disagree with this. I don't think new proxies or even new IP addresses are the solution for this problem because I have had the same problem and I have many sources to test from. This is the only place I can't get too.

GotWoot might be getting Rate Limited though (much more likely then an individual user). They could be exceeding their daily caps which would explain there on and off again status.

It looks like they are getting services through ThePlanet. Maybe another server on their farm segment is getting attacked.

Maybe there is a DNS problem?

K.

[Ciber]

Originally posted by: hiroshi
Oh and in regards to the tracker. If the front page says "Server Status: Down" which it did for a very long time indeed, then it's no surprise that the tracker will stop working too.

Simply wait things out for the Tracker to pop back up. The website should work fine, using a proxy as mentioned would fix the problem in regards to accessing the actual website.

No doubt the trackers are probably back up and working now that the status is back to "Online" ^_^

The "Server Status" thing refers to the status of the Shoutcast stream and nothing else.


As for those of you that can't access the site, I'm on the phone with our host now trying to find out if/why you're blocked.

[Uzumaki]

I am also having this problem, cannot access the main site (unless I go via proxy) or use the torrents [img]i/expressions/face-icon-small-sad.gif[/img] Probably have to find a site with direct download link to naruto 83 now grrr! [img]i/expressions/face-icon-small-smile.gif[/img]

How did your talk go with your hosts btw?

[cormer]

Greetings,

I'm also having the same problem and also have a 83.132.x.x IP. I've put this question on my ISP forum, and they said that it wasn't been blocked. They even succeed in accessing the site, this also has been confirmed by other people i talked and have the same ISP.

Making a quick thought, apparently this is something with the 83.x.x.x.x addresses, any way to determine this??

Thz

Here is my tracert:

C:\>tracert www.gotwoot.net

Tracing route to gotwoot.net [69.56.211.107]
over a maximum of 30 hops:

1 8 ms 34 ms 11 ms 10.31.255.254
2 6 ms 8 ms 10 ms vl-81.cr01pc08.netcabo.net [212.113.162.14]
3 12 ms 11 ms 11 ms ge-5-1.cr01pc02.netcabo.net [212.113.160.62]
4 379 ms 215 ms 243 ms lisbon1-br1-pos60.cprm.net [195.8.10.193]
5 9 ms 68 ms 7 ms lisbon1-br1-pos60.cprm.net [195.8.10.193]
6 49 ms 41 ms 41 ms london1-cr1-p20.cprm.net [195.8.0.94]
7 41 ms 39 ms 39 ms sl-gw20-lon-7-0.sprintlink.net [213.206.159.169]
8 46 ms 42 ms 42 ms sl-bb22-lon-9-0.sprintlink.net [213.206.128.104]
9 109 ms 117 ms 108 ms sl-bb20-nyc-2-0.sprintlink.net [144.232.9.163]
10 110 ms 117 ms 121 ms sl-bb22-nyc-8-0.sprintlink.net [144.232.7.106]
11 131 ms 129 ms 133 ms sl-bb21-chi-9-0.sprintlink.net [144.232.9.149]
12 157 ms 149 ms 166 ms sl-bb21-fw-10-0.sprintlink.net [144.232.8.54]
13 149 ms 151 ms 150 ms sl-bb20-fw-14-0.sprintlink.net [144.232.11.217]
14 160 ms 174 ms 169 ms sl-st21-dal-1-0.sprintlink.net [144.232.20.17]
15 157 ms 151 ms 179 ms 144.232.29.97
16 152 ms 188 ms 151 ms sl-theplanet-2-0.sprintlink.net [144.228.250.126]
17 151 ms 151 ms 151 ms car2-2-v1.dllstx2.theplanet.com [12.96.160.14]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 ^C
C:\>

[kaleyeope]

Originally posted by: cormer
Making a quick thought, apparently this is something with the 83.x.x.x.x addresses, any way to determine this??

Uhm, I have had this problem and I do not come from an 83.x.x.x network.

K.

[cormer]

Originally posted by: kaleyeope

Uhm, I have had this problem and I do not come from an 83.x.x.x network.

K.

And how did you solve it ??

Thz

[kaleyeope]

Originally posted by: cormer

Originally posted by: kaleyeope

Uhm, I have had this problem and I do not come from an 83.x.x.x network.

K.

And how did you solve it ??

Thz

I didn't. It hasn't happened for me in the last couple of days.

K.

[teric]

My IP is 84.xx.xx.xx and I'm also having this prob. Can reach the forums fine obviously, but not the main site, or the tracker. Ran a traceroute on all of them, and the tracker + site are failing at hop 12, just after car2-2-v2.dllstx2.theplanet.com.

To reach the forums, i go through the same route, except the 2nd-last hop is through car2-4-v2.dllstx2.

From the other tracert's posted, it looks like we're all having probs with the last hop through theplanet.com's servers... how about a tracert from someone who *can* reach the main site?

Tracing route to gotwoot.net [69.56.211.107]
over a maximum of 30 hops:

1 703 ms 625 ms 422 ms ge0-2.lns5-c4.bhm.planet.net.uk [62.25.204.202]

2 610 ms 78 ms 47 ms ge5-2.pbr-1.brm.as5388.net [62.25.204.194]
3 1062 ms 250 ms 375 ms ber-1.r18.telc.as5388.net [195.92.55.156]
4 344 ms 531 ms 781 ms 195.50.91.9
5 953 ms 297 ms 578 ms so-7-0-0.mp1.London1.Level3.net [212.113.3.1]
6 328 ms 157 ms 562 ms so-3-0-0.mp1.London2.Level3.net [212.187.128.46]

7 562 ms 328 ms 125 ms as-0-0.bbr2.Washington1.Level3.net [4.68.128.102
]
8 453 ms 422 ms 672 ms so-0-0-0.bbr2.Dallas1.Level3.net [64.159.0.137]

9 656 ms 516 ms 953 ms so-6-0.ipcolo2.Dallas1.Level3.net [4.68.112.186]

10 328 ms 219 ms 266 ms unknown.Level3.net [63.209.48.110]
11 406 ms 375 ms 344 ms car2-2-v2.dllstx2.theplanet.com [12.96.160.46]
12 * * * Request timed out.