NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bishoptf
Feb 12, 2012Aspirant
Crashplan for Dummies, aka Step by Step :)
I have just went through this and have seen several folks post that they wish there was an all inclusive guide, I just bought a Pro 2 and so far I am pleased with what I see under the hood (looks like...
StephenB
Aug 09, 2012Guru - Experienced User
I am also running 3.2.1 (both the PC and the ReadyNAS autoupdated when 3.2.1 was released). I am seeing the results in the guide:
skim32 wrote: Need some help. I have a ReadyNAS Ultra 4 Plus running the latest Radiator at 4.2.21. I followed the directions to a T except I am running CrashPlan 3.2.1 for linux on my ReadyNAS... The only problem that I can tell is that when I run the netstat command on my Readynas, I don't see it trying to listen on 4242. It does however listen on 4343. I am on a windows box and made sure I have tunneling setup on my putty settings. I also rebooted both the desktop and readynas. But still it won't listen on 4242. I do however see that it listen on 4243..
tcp 0 0 *.4242 *.* LISTEN
tcp 0 0 127.0.0.1.4243 *.* LISTEN
Did you use the same command options that are in the guide? The -na is important.
Yes, this is normal. BTW, make sure you select the shares under the "C" volume for backup, the top level folders you will see are symbolic links (shortcuts) - if you pick them, crashplan will backup the shortcut file, but not the data.
skim32 wrote: So it turns out that even though I get a connection refused when trying to telnet to localhost on port 4200, the Desktop Client works fine and I can see my Readynas. Has anyone seen this situation? Anyways, it appears to be working and I am going to attempt a backup and see if it works.
If you change ui.properties back, you can run the desktop client to manage the crashplan server that is locally installed on your PC. This would be important to people who have a multi-PC license. So this behavior is expected.
skim32 wrote: According to the dummy guide, it says I should be able to close everything out and change my ui.properties back to default and I should be able to use the desktop client without puttying first. while it does connect, it no longer sees my readynas, but now it sees my desktop.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!