1 |
2008/10/21 Robert Bridge <robert@××××××××.com>: |
2 |
> On Tue, 21 Oct 2008 08:21:49 +0100 |
3 |
> Mick <michaelkintzios@×××××.com> wrote: |
4 |
> |
5 |
>> On Tuesday 21 October 2008, Paul Hartman wrote: |
6 |
>> > On Tue, Oct 21, 2008 at 12:15 AM, Mick <michaelkintzios@×××××.com> |
7 |
>> > wrote: |
8 |
>> > > Hi All, |
9 |
>> > > |
10 |
>> > > Any idea why this happens: |
11 |
>> > > ======================================== |
12 |
>> > > 150 Ok to send data. |
13 |
>> > > 100% |***********************************| 224 MiB 46.74 |
14 |
>> > > KiB/s 00:00 ETA |
15 |
>> > > 226 File receive OK. |
16 |
>> > > 235279855 bytes sent in 1:21:59 (46.70 KiB/s) |
17 |
>> > > local: xab remote: xab |
18 |
>> > > 227 Entering Passive Mode (205,178,145,65,166,71) |
19 |
>> > > 150 Ok to send data. |
20 |
>> > > 34% |*********** | 115 MiB 46.80 |
21 |
>> > > KiB/s 1:19:27 ETAtnftp: Writing to network: Connection reset by |
22 |
>> > > peer 0% | | -1 0.00 |
23 |
>> > > KiB/s --:-- ETA |
24 |
>> > > 500 OOPS: child died |
25 |
>> > > ======================================== |
26 |
>> > > |
27 |
>> > > It is rare that I am able to complete more than a single file |
28 |
>> > > transfer before the "connection is reset by peer". As these are |
29 |
>> > > relatively large files and the upload is unattended this is |
30 |
>> > > rather annoying. -- |
31 |
>> > > Regards, |
32 |
>> > > Mick |
33 |
>> > |
34 |
>> > That used to happen to me when I was using a piece-of-junk D-Link |
35 |
>> > router. It was one of those $29.99 consumer-grade deals. It would |
36 |
>> > reboot itself constantly when it was under any kind of load. I |
37 |
>> > replaced it with a $50 router with DD-WRT and things have been fine |
38 |
>> > ever since. Might not have anything to do with your problem, but I |
39 |
>> > figured I'd mention it. Check your router logs to see if it's having |
40 |
>> > any problems. |
41 |
>> |
42 |
>> Thanks Paul, |
43 |
>> |
44 |
>> On the client side I am running a $500 professional grade router and |
45 |
>> I assume that the server ISP is also running something upmarket in |
46 |
>> their data center. |
47 |
>> |
48 |
>> On this topic the client-server arrangement straddles the Atlantic |
49 |
>> ocean, so who knows how many routers and switches it jumps across. |
50 |
>> That said the failure pattern is consistent: first file always |
51 |
>> transfers cleanly, then second transfer fails after a while. Could |
52 |
>> it be some configured disk/account quote, dropping transfers above a |
53 |
>> certain size on the (Unix) server? |
54 |
> |
55 |
> Are you running through a proxy? |
56 |
|
57 |
No, although I would love to be able to do that at work! They only |
58 |
allow port 80 to get out through the corporate gateway and probably |
59 |
are running some clever filters on their Cisco routers to stop other |
60 |
protocols. |
61 |
-- |
62 |
Regards, |
63 |
Mick |