Problem with www.remix64.com

moog · Post by **moog** » 20/11/2006 - 17:42

I have problem, so maybe someone of You guys could help me. For about one month I've been unable to get to http://www.remix64.com. I have no idea why. Seems that the problem concerns only my internet connection (my friend in Poland gets to remix64 without any problem). I tried to make trace-route, but unsuccessfully

. After 19th jump the "tracert"-command says that can't make any more jump. Maybe any proxy server could help me. Does anyone of You know some free proxy server which might work with remix64.com? please , help

!!!

EDIT: Currently i'm at work. Here this problem isn't exist

Analog-X64 · Post by **Analog-X64** » 20/11/2006 - 17:51

Sounds like your ISP has blocked the hosting company serving Remix64.com

I would contact them and explain you cant connect to remix64.com

Chris Abbott · Post by **Chris Abbott** » 20/11/2006 - 18:40

Can you post the tracert here? Remix64.com is hosted on my dedicated server, so in theory you ought not to be able to see C64Audio.com either.

Chris

moog · Post by **moog** » 21/11/2006 - 10:32

Yup Chris, I cannot get to c64audio.com too. When I'll be at home, I'll perform tracert and my friend will put the log here

.

Analog-X64 · Post by **Analog-X64** » 21/11/2006 - 10:52

Two months ago, AOL Users could not reach my Wifes website.

I created a ticket with my Hosting Company and this is the E-Mail I got from them. You may be in the same situation.

So Either Chris has to contact he's hosting company or you have call your ISP.

"Dear Rafi,

Earlier today we received reports from some customers about difficulty accessing their web sites. After some investigation, we narrowed the problem down to Level3 Communications, an international backbone provider.

We contacted one of our upstream providers, Mzima, for assistance on the matter, as we are not customers of Level3. Mzima received confirmation from Level3, that they are blocking traffic to/from web4, the server hosting your web site. From the last update we received, Level3 is investigating into why they are blocking the traffic to/from the server.

Unfortunately, until Level3 removes the block, you or visitors to your site may have difficulty reaching it. Rest assured, we are working closely with our upstream provider to get this matter resolved, and they are working actively with Level3 on this."

It turned out AOL was also using "Level3" and their proxy's were going through "Level3" So after 24 hours the ban was lifted and people who are subscribed to AOL were able to reach our site again.

moog · Post by **moog** » 24/11/2006 - 11:29

I performed 'tracert' command, and this is the result:

remix64.com [207.210.231.82]
Number of jumps exceeded, 30:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms <1 ms <1 ms apu145.internetdsl.tpnet.pl [83.17.154.145]
3 7 ms 8 ms 6 ms kat-ru4.idsl.tpnet.pl [213.25.2.204]
4 8 ms 6 ms 6 ms z.kat-ru4.do.kat-r1.tpnet.pl [212.160.0.61]
5 11 ms 10 ms 11 ms so-2-3-0.war-r3.tpnet.pl [194.204.175.113]
6 * 19 ms 11 ms ge-5-0-0.war-tr4.tpnet.pl [195.149.232.141]
7 33 ms 31 ms 32 ms po6-1.fftcr3.FrankfurtAmMain.opentransit.net [19
3.251.250.113]
8 * * * Upłynął limit czasu żądania.
9 * * * Upłynął limit czasu żądania.
10 55 ms 52 ms 51 ms p12-0.core01.par01.atlas.cogentco.com [130.117.1
.238]
11 222 ms 212 ms 208 ms p14-0.core02.dca01.atlas.cogentco.com [66.28.4.2
06]
12 * 214 ms 201 ms p15-0.core01.dca01.atlas.cogentco.com [66.28.4.2
1]
13 246 ms 270 ms 246 ms p3-0.core01.iah01.atlas.cogentco.com [66.28.4.90
]
14 247 ms 247 ms 245 ms p5-0.core01.dfw01.atlas.cogentco.com [66.28.4.97
]
15 248 ms 248 ms 247 ms g0-1.na21.b010621-0.dfw01.atlas.cogentco.com [66
.250.10.166]
16 247 ms 246 ms * colo4dallas_dot_com.demarc.cognetco.com [38.101.
48.58]
17 247 ms 244 ms 243 ms 65.99.248.254
18 * * * Upłynął limit czasu żądania.
19 * * * Upłynął limit czasu żądania.
20 *

Any ideas guys

?

it always stops at 65.99.248.254 addy.

Chris Abbott · Post by **Chris Abbott** » 24/11/2006 - 11:43

Looks like the datacentre the server is in doesn't like you. Or the IPTABLES firewall doesn't like your IP address or something...

You might have to wait until we move server back into Europe...

Chris

Analog-X64 · Post by **Analog-X64** » 24/11/2006 - 11:44

I did a check on the IP Address 65.99.248.254 and it belongs to a company called "Colo4Dallas" and here is how they describe their business.

"At Colo4Dallas weÃ¢â‚¬â„¢re committed to providing high quality, carrier-neutral colocation at a competitive price'

So its possible that they are the ones blocking Hosting Company who provides remix64.com

OrgName: Colo4Dallas LP
OrgID: COLO4
Address: 2000 Irving Blvd
City: Dallas
StateProv: TX
PostalCode: 75247
Country: US

NetRange: 65.99.192.0 - 65.99.255.255
CIDR: 65.99.192.0/18
NetName: COLO4-BLK5
NetHandle: NET-65-99-192-0-1
Parent: NET-65-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.COLO4DALLAS.NET
NameServer: NS2.COLO4DALLAS.NET
Comment:
RegDate: 2005-09-23
Updated: 2006-03-09

OrgTechHandle: NOC1718-ARIN
OrgTechName: NOC
OrgTechPhone: +1-214-630-3100
OrgTechEmail: support@colo4dallas.com

Chris Abbott · Post by **Chris Abbott** » 24/11/2006 - 11:48

Analog-X wrote:I did a check on the IP Address 65.99.248.254 and it belongs to a company called "Colo4Dallas" and here is how they describe their business.

"At Colo4Dallas weÃ¢â‚¬â„¢re committed to providing high quality, carrier-neutral colocation at a competitive price'

So its possible that they are the ones blocking Hosting Company who provides remix64.com

OrgName: Colo4Dallas LP
OrgID: COLO4
Address: 2000 Irving Blvd
City: Dallas
StateProv: TX
PostalCode: 75247
Country: US

NetRange: 65.99.192.0 - 65.99.255.255
CIDR: 65.99.192.0/18
NetName: COLO4-BLK5
NetHandle: NET-65-99-192-0-1
Parent: NET-65-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.COLO4DALLAS.NET
NameServer: NS2.COLO4DALLAS.NET
Comment:
RegDate: 2005-09-23
Updated: 2006-03-09

OrgTechHandle: NOC1718-ARIN
OrgTechName: NOC
OrgTechPhone: +1-214-630-3100
OrgTechEmail: support@colo4dallas.com

That's the datacentre where the machine is. It's a dedicated server, and it doesn't seem to be blocking anyone else...

Chris

Analog-X64 · Post by **Analog-X64** » 24/11/2006 - 11:55

Chris Abbott wrote: That's the datacentre where the machine is. It's a dedicated server, and it doesn't seem to be blocking anyone else...

Chris

He can visit other sites from home but not Remix64. Maybe it's he's ISP Blocking the Datacentre.

I would check "MOOGS" I.P. Range and see the Range of IP's is blocked at the Datacentre or downstream through he's ISP's proxy.