rsync - Jun 2003 - rsync behind NAT

Hi

I use rsync as a client to copy a directory structure from a remote
server, once every month.

Until a few weeks ago, we had direct access to the internet - and the way
it would work is that the guy maintaining the rsync server would add my
machine's IP to an access list and I would run the rsync command from my
machine.

Recently however, our network was 'upgraded' to a NAT system. I do not
know what exactly that means - but in effect, the remote rsync server
cannot see my computer's IP address anymore. I use a 'proxy' server
to
connect to the internet.

Can someone tell me how I can continue rsyncing from the remote server in
this setup ?

regs,
AnandO.

On Thu, Jun 05, 2003 at 11:43:20AM +0530, Anand wrote:
> 
> Hi
> 
> I use rsync as a client to copy a directory structure from a remote
> server, once every month.
> 
> Until a few weeks ago, we had direct access to the internet - and the way
> it would work is that the guy maintaining the rsync server would add my
> machine's IP to an access list and I would run the rsync command from
my
> machine.
> 
> Recently however, our network was 'upgraded' to a NAT system. I do
not
> know what exactly that means - but in effect, the remote rsync server
> cannot see my computer's IP address anymore. I use a 'proxy'
server to
> connect to the internet.
> 
> Can someone tell me how I can continue rsyncing from the remote server in
> this setup ?
Nat can go two ways.  You could ask the guy to assign a port
that would be forwarded to the appropriate port on your
machine.  Or you can use ssh with port forwarding which will
be much easier to keep operational.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

Hi Tomasz,

Thanks for the reply. I have a couple of more questions and would
appreciate some response:

I can't ping to the remote server in the new setup.

    enif >> ping ldas-sw.ligo.caltech.edu
    PING ldas-sw.ligo.caltech.edu (131.215.115.247) from 192.168.11.25 :
    56(84) bytes of data.

    --- ldas-sw.ligo.caltech.edu ping statistics ---
    210 packets transmitted, 0 received, 100% loss, time 208999ms

Question : Is it a bare minimum requirement that I should be able to ping
the remote rsync server in order to be able to rsync ?

Question : Is it true that I can't ping the rsync server because my proxy
server is not on it's access list ?

Question : Other than getting my proxy server's IP on the access list of
the remote rsync server, what settings are required on my local machine.

Thanks a lot again,
AnandO.


On Thu, 5 Jun 2003, Tomasz Ciolek wrote:

| The same as you did so far, with the proviso the remote server must
| allow your "proxy server" access...
|
|
|On Thu, Jun 05, 2003 at 11:43:20AM +0530, Anand wrote:
|>
|> Hi
|>
|> I use rsync as a client to copy a directory structure from a remote
|> server, once every month.
|>
|> Until a few weeks ago, we had direct access to the internet - and the way
|> it would work is that the guy maintaining the rsync server would add my
|> machine's IP to an access list and I would run the rsync command from
my
|> machine.
|>
|> Recently however, our network was 'upgraded' to a NAT system. I do
not
|> know what exactly that means - but in effect, the remote rsync server
|> cannot see my computer's IP address anymore. I use a 'proxy'
server to
|> connect to the internet.
|>
|> Can someone tell me how I can continue rsyncing from the remote server in
|> this setup ?
|>
|> regs,
|> AnandO.
|>
|> --
|> To unsubscribe or change options:
http://lists.samba.org/mailman/listinfo/rsync
|> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
|
|