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...
skim32
Aug 09, 2012Tutor
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 point where I am failing is that I am unable to telnet to localhost on port 4200 from the readynas. I have properly setup my ui.properties file with servicePort=4200. When I try to launch the Desktop Client I get the failure message and if I would like to try the backup. 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.
*EDIT*
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.
*Edit Again*
So it appears all is working well and fine even though the readynas is not listening on port 4242 and the telnet localhost 4200 fails to connect. My last problem seems to be using the desktop client without SSHing first. 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. Any suggestions? I guess for now I can always just putty first. A little annoying but not a big deal.
*EDIT*
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.
*Edit Again*
So it appears all is working well and fine even though the readynas is not listening on port 4242 and the telnet localhost 4200 fails to connect. My last problem seems to be using the desktop client without SSHing first. 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. Any suggestions? I guess for now I can always just putty first. A little annoying but not a big deal.
Related Content
NETGEAR Academy

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