[dansgalaxy]

May seem obvious and You might have done this already... but have you checked if the IP is blocked by rapid share?

It could be that the previous owner of the IP was an abuser or something and was blocked by their system.

[Tabakfeld]

Same problem for me here, from the beginning on
and it is not a Rapidshare problem...
it has to be a problem with my server, but i didn't change anything
It is not working since i have this server -.-
i tried also different browsers, doesn't work...
i do not know what to do....

[Myatu]

tcpdump it... See where it ends up?

[freshwire]

Connecting to rapidshare.com|195.122.131.6|:80... connected.
Created socket 3.
Releasing 0x08a946e0 (new refcount 1).

---request begin---
GET / HTTP/1.0
User-Agent: Wget/1.11.4
Accept: */*
Host: rapidshare.com
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.

[Akd]

Check if there is any useful info in the returned headers (wget -S I think)? (if any)

or with the -d flag to get a full output of what is going on

Tested here and ran fine

[Neil]

No problems here, tested it on two servers and worked fine. The traceroute is fine so something must be causing it to drop.

[freshwire]

I already know the problem doesn't span all of OVH since it works using my other IPs.

But could the problem be IP only related.. perhaps some issue routing traffic back from rapidshare to the IP ?

[makno]

i don't think is something with ovh, just tried and :

:~$ wget http://rapidshare.com/
--2009-10-13 00:00:16-- http://rapidshare.com/
Resolving rapidshare.com... 195.122.131.20, 195.122.131.21, 195.122.131.22, ...
Connecting to rapidshare.com|195.122.131.20|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9284 (9.1K) [text/html]
Saving to: `index.html'

100%[================================================== ========================================>] 9,284 --.-K/s in 0s

2009-10-13 00:00:16 (258 MB/s) - `index.html' saved [9284/9284]

[freshwire]

Rapidshare said this:

Keep in mind that if you can reach us via ICMP (ping), then you should also be
able to reach us on port 80 (http://). If it is not so, there must be
somewhere a filter. We have not applied any filter on HTTP (Port 80).

[freshwire]

Hello.

I have a problem connecting to rapidshare servers from my dedi box ks20857.kimsufi.com on it's primary IP 91.121.175.121.

Some breadcrumbs follow...

myxcp: ~ $ tracert rapidshare.com
traceroute to rapidshare.com (195.122.131.21), 30 hops max, 60 byte packets
1 rbx-53-m2.routers.ovh.net (91.121.175.252) 0.251 ms 0.309 ms 0.391 ms
2 * * *
3 20g.ldn-1-6k.routers.chtix.eu (91.121.131.14) 5.199 ms 5.256 ms 5.098 ms
4 30g.gblx-2.ldn.routers.ovh.net (94.23.122.77) 3.878 ms 3.922 ms 3.986 ms
5 level3-2.ar2.LON3.gblx.net (208.50.13.194) 4.106 ms 4.244 ms 4.230 ms
6 ae-34-52.ebr2.London1.Level3.net (4.69.139.97) 4.762 ms 4.760 ms 4.694 ms
7 ae-2-2.ebr2.Amsterdam1.Level3.net (4.69.132.134) 8.788 ms 8.908 ms 9.000 ms
8 ae-1-100.ebr1.Amsterdam1.Level3.net (4.69.141.169) 10.640 ms 10.757 ms 10.825 ms
9 ae-2-2.ebr2.Dusseldorf1.Level3.net (4.69.133.90) 15.402 ms 15.551 ms 15.546 ms
10 ae-1-100.ebr1.Dusseldorf1.Level3.net (4.69.141.149) 15.365 ms 15.361 ms 25.744 ms
11 ae-2-2.ebr2.Frankfurt1.Level3.net (4.69.132.138) 15.630 ms 15.623 ms 15.492 ms
12 ae-92-92.csw4.Frankfurt1.Level3.net (4.69.140.30) 17.231 ms 15.790 ms 15.836 ms
13 ae-41-99.car1.Frankfurt1.Level3.net (4.68.23.195) 16.065 ms 15.785 ms 16.040 ms
14 rapidshare.com (195.122.131.21) 15.804 ms 15.686 ms 15.686 ms

wget http://rapidshare.com/
--2009-10-12 21:41:31-- http://rapidshare.com/
Resolving rapidshare.com... 195.122.131.21, 195.122.131.22, 195.122.131.2, ...
Connecting to rapidshare.com|195.122.131.21|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

The connection get's reset by all of rapidshare's servers not just the one shown above. In addition email's sent to their server fail to get to there destination.

At first I thought this was a rapidshare problem but they insist that the problem is with another network.

When requests are sent from either of my failover IP's there is no problem. Everything works fine. Only the primary IP 91.121.175.121 has the problem.

So I ask OVH (or anyone with smart ideas) whether there is a problem that prevent's my IP talking with rapidshare other than something rapidshare control?

Jonathan.

- - - - - - - - - - - - - - - - - - - - - - - - - -

... ALSO! I noticed I only start messages with hello if I have a question