Crashplan for Dummies, aka Step by Step :)

StephenB wrote:
Did you try launching crashplan on the client PC and see if it connects to the crashplan server when putty is launched/logged in?

Thanks for the tip re: not showing the ports forwarding when setting Putty
So i followed your instructions...

Using OSX, launch Putty and setting the port forwarding i can see it in the logs

2014-11-04 10:11:58	Initialised AES-256 SDCTR client->server encryption
2014-11-04 10:11:58	Initialised HMAC-SHA1 client->server MAC algorithm
2014-11-04 10:11:58	Initialised AES-256 SDCTR server->client encryption
2014-11-04 10:11:58	Initialised HMAC-SHA1 server->client MAC algorithm
2014-11-04 10:12:04	Sent password
2014-11-04 10:12:04	Access granted
2014-11-04 10:12:04	Opening session as main channel
2014-11-04 10:12:04	Opened main channel
2014-11-04 10:12:04	Local port 4200 forwarding to localhost:4243
2014-11-04 10:12:04	Allocated pty (ospeed 38400bps, ispeed 38400bps)
2014-11-04 10:12:04	Started a shell/command

Launching CrashPlan on PC - Says 'Unable to connect to backup engine'.
>>I'd assume this is probably NOT correct as the port *should* be forwarded?


- From here: if i run the linux command to port forward in putty... The netstat command still shows only 4200 and not 4243. And If i launch CrashPlan on PC - still says 'unable to connect to backup engine'.
Note: I used my NAS's IP or 'localhost' at times

SmellyNAS:~# ssh -L 4200:192.168.118.17:4243 root@192.168.118.17
root@192.168.118.17's password: 
Last login: Tue Nov  4 10:46:32 2014 from 192.168.118.138
Last login: Tue Nov  4 10:47:28 2014 from smellynas on pts/2
Linux SmellyNAS 2.6.37.6.RNx86_64.2.4 #1 SMP Wed Aug 20 11:41:34 PDT 2014 x86_64 GNU/Linux
SmellyNAS:~# netstat -na | grep LISTEN | grep 4            
tcp        0      0 0.0.0.0:2049            0.0.0.0:*               LISTEN     
tcp        0      0 5.171.174.232:6887      0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:4200          0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:945             0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:4700          0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN     
tcp6       0      0 :::548                  :::*                    LISTEN     
tcp6       0      0 ::1:4200                :::*                    LISTEN     
tcp6       0      0 :::443                  :::*                    LISTEN     
unix  2      [ ACC ]     STREAM     LISTENING     7345     /var/run/avahi-daemon/socket
unix  2      [ ACC ]     STREAM     LISTENING     7474     /var/run/mysqld/mysqld.sock

From here if i launch up CrashPlan it still fails.. I am assuming this is correct as it seems on the NAS that that particular command is not quite correct (or at least on my NAS where it has inverted the ports!)
- I wouldn't have a clue why the command is not fowarding...

So what are my options here?
- i have Ultra 6 and can't move data anywhere as there is too much!