ftp from one remote to another without passing through own PC

[Liam]

I have someone in my company that needs to, from home, FTP large groups
of large files from one remote server to another remote server, and
because the FTP passes though her cient, it's VERY slow.

Her PC is Windows XP, and both servers are Linux (one RedHat ES 4 and
the other Fedora Core 5.)

Is there some way to get this setup to pass the files from one remote
server to the other directly?

Note, this user is VERY very VERY x 10 ^ 100 computer illiterate.
Beyond the very basics of operating a PC. This is someone that really
shouldn't be around computers, but, I didn't hire her. I can't replace
her. I'm just doing what I'm told to support her.
So, SSH and SCP and RCP are out of the question.
Is there some kind of method of creating a folder in one remote server
that connects to the other server, sort of like a sym or hard link? So
it shows in her FTP client for one server but actually is housed in the
other machine, so that the file copying the FTP client initiates is
done at the server and not being regulated by the local PC?

Something like that?

Any ideas would be greatly appreciated!
-Liam

 

[Tauno Voipio]

I have someone in my company that needs to, from home, FTP large groups
of large files from one remote server to another remote server, and
because the FTP passes though her cient, it's VERY slow.

Her PC is Windows XP, and both servers are Linux (one RedHat ES 4 and
the other Fedora Core 5.)

Is there some way to get this setup to pass the files from one remote
server to the other directly?

Note, this user is VERY very VERY x 10 ^ 100 computer illiterate.
Beyond the very basics of operating a PC. This is someone that really
shouldn't be around computers, but, I didn't hire her. I can't replace
her. I'm just doing what I'm told to support her.
So, SSH and SCP and RCP are out of the question.
Is there some kind of method of creating a folder in one remote server
that connects to the other server, sort of like a sym or hard link? So
it shows in her FTP client for one server but actually is housed in the
other machine, so that the file copying the FTP client initiates is
done at the server and not being regulated by the local PC?

Something like that?

Set up SSH into both Linux boxes (preferably into
some weird high port to avoid most script kiddies),
log in into Linux system A and use scp to transfer
to/from Linux system B.

The PC will be used here as the controlling terminal
only. The data will pass directly between the Linux
boxes.

For the Windows box, Putty can be uase as the SSH
client needed to get out of the Windows world.

--

Tauno Voipio
tauno voipio (at) iki fi

PS. If there's need for file transfers between the
Windows box and either Linux box, WinSCP works
well as the scp client in Windows box.

TV

 

[Tauno Voipio]

Set up SSH into both Linux boxes (preferably into
some weird high port to avoid most script kiddies),
log in into Linux system A and use scp to transfer
to/from Linux system B.

The PC will be used here as the controlling terminal
only. The data will pass directly between the Linux
boxes.

For the Windows box, Putty can be uase as the SSH

OOPS: used

 

[news]

Set up SSH into both Linux boxes (preferably into
some weird high port to avoid most script kiddies),
log in into Linux system A and use scp to transfer
to/from Linux system B.

The PC will be used here as the controlling terminal
only. The data will pass directly between the Linux
boxes.

For the Windows box, Putty can be uase as the SSH
client needed to get out of the Windows world.

[..]
Thanks for the reply. I agree, SSH, SCP would be the best option.
As I mentioned in my original post.
Bust as I also mentioned, that's not an option for this user.
This is a user for which The Clapper is too complicated for. She
double-clicks hyperlinks no matter how often you tell her that's not
necessary. Having her do anything that rquires her to type in commands
would be a nightmare. Giving her any kind oc shell access into a
production server is asking for trouble.

Thanks for replying, though. =)
-Liam

 

[David Schwartz]

I have someone in my company that needs to, from home, FTP large groups
of large files from one remote server to another remote server, and
because the FTP passes though her cient, it's VERY slow.

Her PC is Windows XP, and both servers are Linux (one RedHat ES 4 and
the other Fedora Core 5.)

Is there some way to get this setup to pass the files from one remote
server to the other directly?

Note, this user is VERY very VERY x 10 ^ 100 computer illiterate.
Beyond the very basics of operating a PC. This is someone that really
shouldn't be around computers, but, I didn't hire her. I can't replace
her. I'm just doing what I'm told to support her.
So, SSH and SCP and RCP are out of the question.
Is there some kind of method of creating a folder in one remote server
that connects to the other server, sort of like a sym or hard link? So
it shows in her FTP client for one server but actually is housed in the
other machine, so that the file copying the FTP client initiates is
done at the server and not being regulated by the local PC?

Something like that?

Any ideas would be greatly appreciated!

I have thought over the possibilities and I think the best way is a web
interface that can only do exactly what this person needs to do. If the
paths are more or less constant or correspond, all she needs is a file
browser with a 'publish' button that scp's it automatically to the
other.

Think through her workflow carefully, limit the possibilities as much
as you can (both to prevent mistakes, keep her work simple, and
minimize yours).

DS

 

[stan]

: I have someone in my company that needs to, from home, FTP large groups
: of large files from one remote server to another remote server, and
: because the FTP passes though her cient, it's VERY slow.

: Her PC is Windows XP, and both servers are Linux (one RedHat ES 4 and
: the other Fedora Core 5.)

: Is there some way to get this setup to pass the files from one remote
: server to the other directly?

: Note, this user is VERY very VERY x 10 ^ 100 computer illiterate.
: Beyond the very basics of operating a PC. This is someone that really
: shouldn't be around computers, but, I didn't hire her. I can't replace


Sounds like you need to find a GUI SSH client for your Linux Box,
then export that to the Windows box and user can go at it. Use
Xming or another simple X server and the end user need not even
know that the open GUI is running remotely.

As long as the GUI isn't too arcane ( like ancient MOTIF stuff)
then the user should be able to just drag-and-drop as they are used to.

No matter what though it sounds like you need to be running
an app on Linux and export the display to Windows--- which means
an X server.

Failing that I suppose that you could get fancy and create some sort
of custom client/server application.

Stan

 

[Handover Phist]

Liam :

I have someone in my company that needs to, from home, FTP large groups
of large files from one remote server to another remote server, and
because the FTP passes though her cient, it's VERY slow.

Her PC is Windows XP, and both servers are Linux (one RedHat ES 4 and
the other Fedora Core 5.)

Is there some way to get this setup to pass the files from one remote
server to the other directly?

Note, this user is VERY very VERY x 10 ^ 100 computer illiterate.
Beyond the very basics of operating a PC. This is someone that really
shouldn't be around computers, but, I didn't hire her. I can't replace
her. I'm just doing what I'm told to support her.
So, SSH and SCP and RCP are out of the question.
Is there some kind of method of creating a folder in one remote server
that connects to the other server, sort of like a sym or hard link? So
it shows in her FTP client for one server but actually is housed in the
other machine, so that the file copying the FTP client initiates is
done at the server and not being regulated by the local PC?

Something like that?

Any ideas would be greatly appreciated!
-Liam

Set up a SAMBA/NFS system so the transfers happen without her knowledge.
Transferring to a directory on which is mounted an NFS filesystem share
would send the file without the knowledge of the end user.

It's a kludge, but it would work (I think).

 

[stan]

: Liam :
:> I have someone in my company that needs to, from home, FTP large groups
:> of large files from one remote server to another remote server, and
:> because the FTP passes though her cient, it's VERY slow.
:>
:> Something like that?
:>
:> Any ideas would be greatly appreciated!
:> -Liam

: Set up a SAMBA/NFS system so the transfers happen without her knowledge.
: Transferring to a directory on which is mounted an NFS filesystem share
: would send the file without the knowledge of the end user.

I think you missed the OP's basic dilemma - which is that the
two hops to the home system are slow. The files need to move
directly from one server to another, but need to be
controlled from the home machine.

Stan

 

[Tauno Voipio]

Set up SSH into both Linux boxes (preferably into
some weird high port to avoid most script kiddies),
log in into Linux system A and use scp to transfer
to/from Linux system B.

The PC will be used here as the controlling terminal
only. The data will pass directly between the Linux
boxes.

For the Windows box, Putty can be uase as the SSH
client needed to get out of the Windows world.

[..]
Thanks for the reply. I agree, SSH, SCP would be the best option.
As I mentioned in my original post.
Bust as I also mentioned, that's not an option for this user.
This is a user for which The Clapper is too complicated for. She
double-clicks hyperlinks no matter how often you tell her that's not
necessary. Having her do anything that rquires her to type in commands
would be a nightmare. Giving her any kind oc shell access into a
production server is asking for trouble.

How about a webpage-triggered script doing the scp?

I'd stay away from FTP, NFS and SMB kludges here.

 

[news]

Liam wrote:

I have someone in my company that needs to, from home, FTP large groups
of large files from one remote server to another remote server, and
because the FTP passes though her cient, it's VERY slow.

Her PC is Windows XP, and both servers are Linux (one RedHat ES 4 and
the other Fedora Core 5.)

Is there some way to get this setup to pass the files from one remote
server to the other directly?

Note, this user is VERY very VERY x 10 ^ 100 computer illiterate.
Beyond the very basics of operating a PC. This is someone that really
shouldn't be around computers, but, I didn't hire her. I can't replace
her. I'm just doing what I'm told to support her.
So, SSH and SCP and RCP are out of the question.
Is there some kind of method of creating a folder in one remote server
that connects to the other server, sort of like a sym or hard link? So
it shows in her FTP client for one server but actually is housed in the
other machine, so that the file copying the FTP client initiates is
done at the server and not being regulated by the local PC?

Something like that?

Set up SSH into both Linux boxes (preferably into
some weird high port to avoid most script kiddies),
log in into Linux system A and use scp to transfer
to/from Linux system B.

The PC will be used here as the controlling terminal
only. The data will pass directly between the Linux
boxes.

For the Windows box, Putty can be uase as the SSH
client needed to get out of the Windows world.

[..]
Thanks for the reply. I agree, SSH, SCP would be the best option.
As I mentioned in my original post.
Bust as I also mentioned, that's not an option for this user.
This is a user for which The Clapper is too complicated for. She
double-clicks hyperlinks no matter how often you tell her that's not
necessary. Having her do anything that rquires her to type in commands
would be a nightmare. Giving her any kind oc shell access into a
production server is asking for trouble.

How about a webpage-triggered script doing the scp?

I'd stay away from FTP, NFS and SMB kludges here.

Yeah, that's kind of what I was thinking we'd have to go with.
Probably have to do a dir listing into a form, checkboxes, and initiate
an exec(scp...) upon submission.
Thanks,
Liam

 

[The Natural Philosopher]

Set up SSH into both Linux boxes (preferably into
some weird high port to avoid most script kiddies),
log in into Linux system A and use scp to transfer
to/from Linux system B.

The PC will be used here as the controlling terminal
only. The data will pass directly between the Linux
boxes.

For the Windows box, Putty can be uase as the SSH
client needed to get out of the Windows world.

[..]
Thanks for the reply. I agree, SSH, SCP would be the best option.
As I mentioned in my original post.
Bust as I also mentioned, that's not an option for this user.
This is a user for which The Clapper is too complicated for. She
double-clicks hyperlinks no matter how often you tell her that's not
necessary. Having her do anything that rquires her to type in commands
would be a nightmare. Giving her any kind oc shell access into a
production server is asking for trouble.

Thanks for replying, though. =)
-Liam

Set up a script that can be invoked from a web page.

If ALL the script does is transfer all files from one location to
another...its fairly safe.

If the web server is set to an unknown port and she simply has an icon
on her desktop, its pretty easy to click on it and hit the 'submit'
button..but has she any other access? I mean, how do the files get there
ands so on? Via SAMBA?

 

[Rick Jones]

I have someone in my company that needs to, from home, FTP large
groups of large files from one remote server to another remote
server, and because the FTP passes though her cient, it's VERY slow.

Across a DSL/Cable/Dial link I presume?

Her PC is Windows XP, and both servers are Linux (one RedHat ES 4
and the other Fedora Core 5.)

Is there some way to get this setup to pass the files from one remote
server to the other directly?

Is there IP connectivity between the two servers, or just from each
server to the PC?

Note, this user is VERY very VERY x 10 ^ 100 computer illiterate.
Beyond the very basics of operating a PC. This is someone that really
shouldn't be around computers, but, I didn't hire her. I can't replace
her. I'm just doing what I'm told to support her.
So, SSH and SCP and RCP are out of the question.
Is there some kind of method of creating a folder in one remote server
that connects to the other server, sort of like a sym or hard link? So
it shows in her FTP client for one server but actually is housed in the
other machine, so that the file copying the FTP client initiates is
done at the server and not being regulated by the local PC?

Something like that?

IIRC FTP has no "third party" support which means that while you may
be able to arrive at the illusion of a direct transfer from one server
to the other with clever scripting etc, I suspect that a solution
involving only FTP would still be staging the files via the PC.

rick jones

 

[The Natural Philosopher]

Across a DSL/Cable/Dial link I presume?



Is there IP connectivity between the two servers, or just from each
server to the PC?



IIRC FTP has no "third party" support which means that while you may
be able to arrive at the illusion of a direct transfer from one server
to the other with clever scripting etc, I suspect that a solution
involving only FTP would still be staging the files via the PC.

rick jones

Not at all.

FTP can be driven from a batch file..at least most versions can.

Its pretty insecure...but all you need is a way of setting uyp teh batch
file and triggering it from the third party.

ISTR some years ago the 'lads' set up some kind of script that
synchronised files on many machines using I think ftp, though it might
have ben - gasp - RCP.


Heres a script fragment I found on the 'net that does things automatically.
#!/bin/bash
#FTP the file to the backup directory on the backup server
ftp -in <<EOF
open IP.ADDRESS.OF.SERVER
user USERNAME PASSWORD
bin
hash
prompt
dele fullback.tar.gz
put fullback.tar.gz
bye

 

[Handover Phist]

The Natural Philosopher :

ISTR some years ago the 'lads' set up some kind of script that
synchronised files on many machines using I think ftp, though it might
have ben - gasp - RCP.


Heres a script fragment I found on the 'net that does things automatically.
#!/bin/bash
#FTP the file to the backup directory on the backup server
ftp -in <<EOF
open IP.ADDRESS.OF.SERVER
user USERNAME PASSWORD
bin
hash
prompt
dele fullback.tar.gz
put fullback.tar.gz
bye

This would be much easier using wput.

#> wput ftp://userasswd@IPADDR fullback.tar.gz; rm fullback.tar.gz

That does essentially the same thing as the script fragment.

 

[The Natural Philosopher]

The Natural Philosopher :

This would be much easier using wput.

#> wput ftp://userasswd@IPADDR fullback.tar.gz; rm fullback.tar.gz

That does essentially the same thing as the script fragment.

Ah..another thing dimly remembered in /brain/swap now back in RAM...

Ta m8.