Commodore Remix

hi guys, I am new to the forums, but not to the R64. Recently, I noticed that I cannot download remixes. Is there something wrong with me?
Thanks.

works for me... you use some kind of proxy?

Actually, I can download stuff anywhere but here... Isn't it weird?
Well... Anybody? I will got to a long road trip and I need to have something nice in my car's audio.
Pleeaaassseee... Help.

By the way, I cannot open Remix.kwed.org page either... Maaan@@!@#$ that sucks.

Look at your browsers settings. Maybe you accidentally forbid downloads from RKO or banned the site. Or somebody else did that.

Very unprobably but... do you have a joker at home?
If you use Windows, look for a file named "hosts". Open it with Editor (You need administrative powers for this) and look for remix.kwed.org.
If it's in there, delete the line, save and restart your network eg. reboot. You should be able to connect now. Also look for "lmhosts". That may contain such entries, too.

I looked those files, found, opened with notepad. There is no such information as you suggested... I am hopeless...
I have two diffrent browsers, firefox and ie. both are not working.

Any suggestions?

Ps: By the way, what is joker?

If you open up a DOS command window (start/run, type "cmd" and press return in XP) and type "ping remix.kwed.org", what does it say?

Here's what it says for me (and it shows that my computer thinks that remix.kwed.org is at 195.139.52.132.

What happens if you type "http://195.139.52.132" into MSIE?

Here's what the ping says for me:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Chris>ping remix.kwed.org

Pinging remix.kwed.org [195.139.52.132] with 32 bytes of data:

Reply from 195.139.52.132: bytes=32 time=103ms TTL=47
Reply from 195.139.52.132: bytes=32 time=79ms TTL=47
Reply from 195.139.52.132: bytes=32 time=58ms TTL=47
Reply from 195.139.52.132: bytes=32 time=75ms TTL=47

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

I tried to go to RKO with my wife's laptop, it cannot go either. (We are using the same wireless)

When I try to ping the RKO, it shows me this:

Pinging remix.kwed.org [195.139.52.132] with 32 bytes of

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 195.139.52.132:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

SO? I am not able to download anything, am I?

Please guys, I am in pain... I need some quality music for my trip...

That's odd.
Just to test a theory try a ping on 194.77.48.164 (deutsche presse agentur, 5 hops from me).
Maybe this refers to your general TTL (time to live) and the packets are dropped before they reach RKO. It's 12 hops from me. Wherever you are, this could take a lot longer.

This is the stuff I am getting...


Pinging 194.77.48.164 with 32 bytes of data:

Reply from 194.77.48.164: bytes=32 time=130ms TTL=52
Reply from 194.77.48.164: bytes=32 time=128ms TTL=52
Reply from 194.77.48.164: bytes=32 time=124ms TTL=52
Reply from 194.77.48.164: bytes=32 time=124ms TTL=52

Ping statistics for 194.77.48.164:
Packets: Sent = 4, Received = 4, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 124ms, Maximum = 130ms, Average = 126ms

I really do not understand why this thing happening.

I am in US by the way.

Hmmm... your ISP isn't blocking some ranges, or does it?
Maybe in "illegal MP3 hysteria" your ISP blocked ALL non commercial MP3 sites for downloading.

Else this MUST have to do with your machine. Even if you horribly misconfigured your browsers, a simple ping to rko should have come through.

Next step is:

tracert remix.kwed.org

See where the signal stops.

Chris

Hi Chris!

I tried that from my position and odd enough: tracert didn't show details about stations in between (timeouts - host didn't respond to ping). Sadly I don't have access to a real unix shell now, so I can't say for sure that's tracert (as it's the crippled windows traceroute) fault.

@mcescher:
You may use an internet version here:
http://www.fh-friedberg.de:81/tracerout ... x.kwed.org
This shows at least details. I hope this works in the US. Only catch: the traceroute starts at the server fh-friedberg.de in germany.
Try to get a university near your position with a similar service.