Don wrote:No idea. Maybe if you supplied some information like backup settings on both systems. Firmware versions? Network configurations? Using SSH? You have provided no useful information except that it doesn't work.
Pretty hard to troubleshoot any Linux system without SSH. It might help you to troubleshoot this issue if you learned how to use it. Check out Suso Support document: SSH Tutorial for Windows.adesnoyer wrote:Some more informaton :
My firmware is 4.13 on both NAS
I don't use SSH
Code: Select all
echo "NAS Model: $(getsysinfo model)"
echo "Firmware: $(getcfg system version) Build $(getcfg system 'Build Number')"
echo "System Name: $(/bin/hostname)"
echo "Workgroup: $(getcfg system workgroup)"
echo "NAS IP address: $(ifconfig $(getcfg network 'Default GW Device') | grep addr: | awk '{ print $2 }' | cut -d: -f2)"
echo " "
echo "Default Gateway Device: $(getcfg network 'Default GW Device')"
echo " "
ifconfig $(getcfg network 'Default GW Device') | grep -v HWaddr
echo " "
#done
The drops suggests you have some kind of connection issue.adesnoyer wrote:RX packets:748920405 errors:1 dropped:726743 overruns:0 frame:1
Different traffic patterns could very well lead to different results. Ping is useful to verify a connection is possible, it doesn't say much about the performance and quality (unless extremely bad) of the path.And it's not a network problem because meanwhile I can ping the remote NAS without any paket loss....
