Any networking gurus out there?

[BrianG]

I have a server that I wanted to be a web/ftp server available to the outside world.

I installed IIS and configured it. Completed with no troubles.

Then, since my ISP periodically assigns new IP addresses, I needed to 1) configure my router for port forwarding, and 2) sign up for a domain name service that periodically tracks what IP my ISP assigns and updates the domain name I chose. After some fiddling around, both have been completed. I can now access my server's web and ftp functions via anywhere on the net despite my ISP changing the IP address.

Then, I wanted to be able to remotely log into the server for three reasons; 1) to administer it, 2) remote development, and 3) able to remote login to my other computers on the LAN from the server. I have gotten all that to work easily enough. The only computer I can remotely log into from the net is the server. Once in there, I can in turn remotely log into any other PC/Mac in the house. On the server, I've already set the single user that is allowed to remotely log in, and set a strong password for that account.

However, this is obviously not secure enough, and this is where my questions come in.

I've read I can remotely log into the server using a web browser (instead of using Windows Remote Login program). This would be nice since I can do so from any computer (Windows, MAC, linux) as long as it has a web browser and internet connection. To make web remote login secure, change the http port number in IIS. Normally of course, it's port 80 for web. But if I change the port number in IIS for web remote login, that also changes the port number for the regular website. So, that leaves me with a few choices:

1) Change the port number for the web and just remember to type the port number at the end of the web address if I want to just go to the website (not logging in, just regular web). Not a good solution since I may eventually move my rc_speed website, and telling everyone the port number to access the site would defeat the whole purpose of changing the port in the first place.

2) Create a VPN tunnel when I want to remotely log in. This would probably be the most secure, but I'd have to have the executables handy depending on what operating system of the client I happen to be using. Plus, I have no idea how where to start. But at least I won't have to mess with port numbers, which means the regular web/ftp will work, and just use the VPN for remotely logging in.

3) I had thought of a third choice, but I forgot it.

Any ideas/suggestions?