From: "Michael D. Berger" <m_d_berger_1900@yahoo.com>
To: netdev@vger.kernel.org
Subject: Fail Transfer of Large Files
Date: Fri, 19 Nov 2010 23:45:14 +0000 (UTC) [thread overview]
Message-ID: <ic726a$dep$1@dough.gmane.org> (raw)
On my intranet, I sometimes transfer large files, about 4G,
to an CentOS old box that I use for a web server. I transfer
with ftp or sftp. Usually, before the file is complete, the
transfer "stalls". At that point, ping from the destination box
to the router fails. I then deactivate the net interface on the
destination box and then activate it. Ping is then successful,
and the transfer is completed. The transferred file is correct,
as verified with sha1sum.
All connections are via cat6 wire.
So what do you think? Should I try changing the net card?
Any tests to run? Any other suggestions?
Thanks for your help.
Mike.
next reply other threads:[~2010-11-19 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 23:45 Michael D. Berger [this message]
2010-11-22 21:48 ` Fail Transfer of Large Files Francois Romieu
2010-11-23 18:02 ` Michael D. Berger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ic726a$dep$1@dough.gmane.org' \
--to=m_d_berger_1900@yahoo.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).