LinuxQuestions.org - Copy directories/files from Fedora 8 machine to SuSE 10.3 machine

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Copy directories/files from Fedora 8 machine to SuSE 10.3 machine (https://www.linuxquestions.org/questions/linux-newbie-8/copy-directories-files-from-fedora-8-machine-to-suse-10-3-machine-627180/)

Copy directories/files from Fedora 8 machine to SuSE 10.3 machine

I've had two Fedora 8 machines networked together for some time, where I backed up the newer one to the older one using rsync. I could also start nfs and mount the home directory of one on the other (since I had enough disc space). Problems with Fedora (probably to do with recent kernel upgrade) made me decide to try SuSE 10.3 on the newer one. The trouble is I cannot transfer files from one to the other (I'm resorting to burning dvd's). I've tried cp, scp, rysnc and ftp and running nfs and mounting one home file system on the other, all with no luck. Anyone can tell me the simplest, effective way of going about it, please?

Sounds like a firewall issue. What are your Suse settings?

I've tried with both firewalls switched completely off. (With Fedora this did not matter with rysnc, though it did with nfs and mount).

Will there be a problem with different file types?

Both rsync and scp seem to function but then I find nothing is actually visible at the destination address (or in the case of rsync it has only bothered about a few files).

What errors are you getting (preferably log entries)

scp and rsync do not produce errors – just there is nothing at the destination.

Trying to mount from nfs server:

Code:

localhost:/home/rt # mount 192.168.1.64:/home/rt /mnt/home

mount: mount to NFS server '192.168.1.64' failed: RPC Error: Program not registered.

localhost:/home/rt #

Code:

localhost:/home/rt # rpcinfo -p 192.168.1.64

  program vers proto  port

    100000    2  tcp    111  portmapper

    100000    2  udp    111  portmapper

localhost:/home/rt #

Code:

localhost:/home/rt # rpcinfo -p 192.168.1.65

  program vers proto  port

    100000    4  tcp    111  portmapper

    100000    3  tcp    111  portmapper

    100000    2  tcp    111  portmapper

    100000    4  udp    111  portmapper

    100000    3  udp    111  portmapper

    100000    2  udp    111  portmapper

    100000    4    0    111  portmapper

    100000    3    0    111  portmapper

    100000    2    0    111  portmapper

    100024    1  udp  46656  status

    100024    1  tcp  39454  status

    100011    1  udp    601  rquotad

    100011    2  udp    601  rquotad

    100011    1  tcp    604  rquotad

    100011    2  tcp    604  rquotad

    100021    1  udp  32888  nlockmgr

    100021    3  udp  32888  nlockmgr

    100021    4  udp  32888  nlockmgr

    100003    2  udp  2049  nfs

    100003    3  udp  2049  nfs

    100003    4  udp  2049  nfs

    100021    1  tcp  41742  nlockmgr

    100021    3  tcp  41742  nlockmgr

    100021    4  tcp  41742  nlockmgr

    100003    2  tcp  2049  nfs

    100003    3  tcp  2049  nfs

    100003    4  tcp  2049  nfs

    100005    1  udp  52396  mountd

    100005    1  tcp  44778  mountd

    100005    2  udp  52396  mountd

    100005    2  tcp  44778  mountd

    100005    3  udp  52396  mountd

    100005    3  tcp  44778  mountd

localhost:/home/rt #

FTP – command line, Konqueror, Krusader, gFTP will not connect

From your output nfs server is running on ip 192.168.1.65, and you are trying to mount directory from 192.168.1.64 (where nfs server is not running, only port mapper is running).

-- your output
# rpcinfo -p 192.168.1.64
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper

start nfs server on 192.18.1.64, then try to mount or otherwise

It looks as if the IP addresses of my machines got swapped (192.168.1.64 had become 192.168.165 and vice versa – DHCP and my SpeedTouch router?) so I was copying and rsyncing to the same machine I was issuing command from and hence the nfs not running problem. Hopefully I might start getting a bit further now!