
I've recently purchased a 4TB ReadyNAS NVX and I'm currently trying to setup a pretty new feature called ReadyNAS Remote, documented here. As far as I can tell, this functionality will allow me to replicate a traditinal VPN setup and I'm really excited to use it. Since I'm having a little trouble getting this setup and there's a lack of documentation on the internet about it, I'm going to highlight the problem solution path I went through to get this setup. Starting with step 1:
I was getting an error. This ReadyNAS cannot connect to ReadyNAS Remote.
OK - I was on the phone with netgear about 4-5 times. I got a support ticket going and got my issue raised to Level 2. Essentially - I think something was wrong with their services because all at once, the ReadyNAS started recognizing the service and my laptop logged into the client. The ReadyNAS remote experience is A+. When it's all setup, you can securly using your network attached storage off your LAN. \\ReadNAS\folder\file.txt on your LAN will still be \\ReadNAS\folder\file.txt .. This was a big deal for me because I've got Dreamweaver setup to access web documents on the NAS. If I had to edit the Site Manager everytime I took logged onto a new network, it would be real pain.
Labels: Social-Learning
I recently upgraded my Coldfusion 8 development server to 8,0,1,195765 and a pretty basic FTP task I had sceduled started erroring. It was giving me the following error :
Ultimately, what fixed the error was changing 'cfftp name="xxx"...' to 'cfftp connection="xxx"...'. [I found this solution here]
Labels: Social-Learning
Recently, I've taken steps to create a web development environment for building newer versions of some of my websites. I plan on covering some of the finer details later on but some of the upgrades include things like:
Granted, this setup isn't super unique but if you take the time to do something like this, 2 questions may follow:
The simple answer is to look into editing your HOSTS file. FYI - you will need to edit the HOSTS file on your workstation computer and your server. I recommend using your own top-level domain for your development box. For example, having EXAMPLE.COM go to the internet and EXAMPLE.DEV going to your development server.
If you try doing this yourself, you might not figure it out so easily but this is a pretty straight forward process. All you'll need for that is to read this article : How to create a self-signed SSL Certificate .
Happy Developing!!!
Labels: Social-Learning
November 2008 December 2008 January 2009 February 2009 April 2009 May 2009 September 2009