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.
Network Port Scanning With iPhone, Network Discovery with iPod Touch, Network Troubleshooting with iDevices
I purchased an amazing application from the iTunes store tonight for my iPod Touch called iNet created by Banana Glue. In a nutshell the application makes it very easy to discover all of the devices on the network that the iPhone or iPod Touch is currently connected to. It is by far the best forming application in this class that I have seen.
There are many things that make this application stand out above the rest. The iNet home screen provides links to the each task including Scan Network, Ping, Bonjour Browser, Wak on LAN, Device Info, and Settings. Below I will provide a brief explanation of each of these tasks.