I have 4 physical machines all running W2K3 Srvr STD-32bit
x1 = HP x4000 with 1GB RAM with 200GB Raid5 - (DC - FSMO Master)
x2 = HP dc7700 core 2 duo, 8GB RAM, 1TB - (VMware Server 2.0 Host)
x1 = HP dc7600 P4, 4GB, 500GB - WinXP Pro (Management Workstation)
WRT54G - Linksys Wi-Fi router
Comcast ISP (DHCP)
192.168.1 internal LAN
Each VMware host server is hosting 5 guests of varying application roles - directory services, web, database, email, .NET, File/App services. All of the guests can resolve each just fine. I have a VM as my second DC in the domain to back up my physical AD master on both DNS and WINS. I've built to WinXP Pro VMs for .NET development purposes and wish to have them accessible over the web to a couple of developer buddies of mine.
PROBLEM: I'm trying to find the best implementation method for making the VMs accessible over the web. Initially I tried VirtualBox and that was disastrous. So I moved to VMware Server 2.0. All the hosts can resolve each other through DNS just fine and can access them all through RDP within the LAN. However, with port forwarding turned on on the Linksys it's not working.
Linksys: DEVSTA-KA 5900 to 5900 TCP to 192.168.1.99 (guest IP, not the host)
DEVSTA-BJ 5901 to 5901 TCP to 192.168.1.100 (guest IP, not the host)
I have my friend use Remote Desktop Manager from Devolutions because you can change the RDP port number from within their little GUI...easier than having him do through the Registry. But he still cannot connect....and neither can I.
So I got really frustrated with it and decided maybe I should use 2X VirtualDesktop Server and their 2X Application Server to publish the virtual machines and then have them accessible via a portal like in Citrix Metaframe or Presentation Server.
I thought about simply building another virtual W2K3 server and have it be the jump point into the network and have everyone RDP from there to their virtual XP machines, but I thought that'd be too slow for them.
I had Terminal Services turned on but the license will run out in 120 days so I didn;t want that solution.
I need a free, permanent solution to publish ANY virtual machine I want and have them all accessible over the web. Not only do I need a solution but I need a cut & dried method to implement it because once I get it working at home, I will need to do this for my church as well. I;m not a networking newbie, nor am I new to virtualization, but making them available over the web has proved to be pretty challenging at this point.
I'm hoping that 500 points will be enough to convince someone to put me on a clear and manageable path to implementation. Thanks in advance!!