There are numerous reasons that you may either want to connect to Windows Remote Desktop on a different port or have Remote Desktop listen on a different port. The primary reason I wanted to configure this was my ISP does network scans every couple of months and if you have external ports listening they will suspend your service in an attempt to both cut down on viruses, spam, and to get you to upgrade your service to a business account that allows you to run servers. I wanted to be able to connect to a Windows Vista box at my house remotely and one of the ports included in my ISP’s scan list is the RDP (Remote Desktop Protocol) TCP port 3389. To get around this you can either configure RDP to run on a different port and simply use your router to directly NAT through the new port or I suggest you simply using Port Forward on your router to route another port from the external IP address to the TCP RDP port 3389 on the Windows computer running Remote Desktop. Below I describe connecting to a port other than the default TCP port 3389 from the Remote Desktop client.
I was messing around with the CPAN the Perl world wide archive of resources earlier today and it was asking for the default location of ncftpget. By default this is no longer installed on CentOS so you will first need to install the EPEL repository and then install NCFTP using yum. Follow the directions below to install ncftp which includes ncftpput, ncftpget, ncftpbatch, ncftpspooler, and more.
I have numerous D-Link DCS-950G network cameras and a D-Link DCS-3220 at my house and needed to upgrade the firmware recently to provide some new features on the DCS-950G’s. The DCS-950G is one of the lower end models provided by D-Link however they work fairly well. They lack many features of something like the DCS-3220 such as pan and zoom however upgrading to the DCS-950G 1.08 firmware actually adds a digital zoom feature. Below i describe some of the benefits of upgrading from DCS-950G 1.07 to 1.08 along with the steps actually taken to complete the upgrade.
One of my favorite plugins for WordPress is the Google Analyticator plugin that provides an easy way for you to interface your WordPress site with Google Analytics. There have been a couple times after upgrades that I wanted to verify that Google Analyticator was functioning properly and wasn’t exactly sure of the best method. After a couple emails back and forth with the developer he shared how he suggests to troubleshoot it and verify it is functioning properly. So thanks to Ronald Heft for providing not only the plugin but also for taking the time to share some extra information with me. Follow the directions below to verify the Google Analyticator plugin using the Firefox addon Firebug.
I have been using the Shashin WordPress plugin for awhile now to display my Google Picasa image galleries. This plugin basically generates pages on your site that embed the images from your Picasa image galleries. So far I have been really satisfied with the plugin and tried numerous other Picasa plugins before settling on this one. One thing I needed to change because of the layout of my site was the default size for the album thumbnails which is 160 pixels. Below I describe how to modify this size so you can display more albums in a smaller amount of space.