2 replies
by cpfeiffe
by nico baggus
My Assumption is you use FTP as your protocol.
The first thing to look for is you network
topology.
What parts are involved in the transfer.
1 Your Sun
2 Switch/Hub....
...
? (Firewall?/Nat router?)
N-1 Remote Switch/Hub
N Remote System
You need to check you local topology. (Is you
switch matched to your system, Same speed, Same
Fullor Half Duplex, when in doubt set fixed speed
& dulex).
Check that for the whole path.... switch ->
switch etc.
(Hub is allways 10 or 100Mbps/Half duplex, on a
switch YMMV).
Then the firewall or nat router.
Telnet won't be a problem there as long as there
is trafic,
But FTP is a different bird, it uses a link on
port 21 for commands and a link on port 20 for
data delivery, with large files the link on port
20 is busy, but on port 21 nothing happens.
A NAT device or Firewall will drop the knowlegde
of such a setting when a certain time without
trafic expires. (30 minutes on Checkpoint AFAIK)
Also here YMMV.
The solution might be to try to use SCP (uses a
single link) or a different protocol that uses
a single link, or build a special ftp client that
set the command link socket to SO_KEEPALIVE
to ensure artificial traffic on the command link.
Success,
Nico
This discussion is closed to new replies.
Trending Linux posts
Sort by Trending