Using SC with dyndns.org address and DI-624 on Embarq DSL?

[GuyWithDogs]

I've spent most of the day messing about with SC, trying to get it to work. While I've found a number of interesting online articles and tutorials, plus some forum entries, I still end up not being able to establish a connection. Now, I am trying from within my own network and haven't been able to try externally.

I originally followed the tutorial from lifehacker.com, and while I could get a SC executable to test, when I ran that, I did not get a connection to my viewer.

I've previously managed to get BitTorrent, etc. running.

My setup is:

[Internet] -> Zyxel 645M (EMBARQ) -> DI-624 router -> my PC

What I've ended up with now is the following:

1. On my Zyxel 645M that EMBARQ provides, I've told it to forward port 5500 to the IP for the DI-624.

2. The DI-624 has Virtual Servers configured for various VNC ports, including 5500, passing the entries to my PC's IP on port 5500.

I found something that claimed I should make a call to https://www.grc.com/x/portprobe=5500 to see whether my VNCviewer was accessible. Initially it wasn't, but I remembered that I needed the Zyxel 645M to have something "magic", and made that configuration.

Now when I hit that test page with the vncviewer running, I get a Ultr@VNC Message that says it can't work out the protocal. What I'm assuming from this is that my PC can now be accessed externally on that port.

I've just tried to make a connection from an external IP (I can Remote Desktop into a machine at work) and it didn't work. I don't get the interactive panel that tells me to double-click, and instead, I just get a WinVNC icon in the system tray that says "Listening".

Can someone shed some light on what I'm doing wrong? I'm hoping to get this set up so that I can help family and friends with having to drive somewhere, or that are a couple of thousand miles away.

Thanks....

[GuyWithDogs]

I need to learn to post my questions earlier. I sorted out my own answer.

It seems that I just wasn't putting all the pieces together properly. I'd managed to screw up the helpdesk.txt file in my messing around, and when I did everything I described in my earlier post, plus recreated a new helpdesk.exe (after I added an external access using my dyndns account, and an internal access using my IP (which is probably a problem area, since I have DHCP)), I managed to connect both on my LAN and from the WAN.

It seems the trick was forwarding the DSL modem port to the wireless router that all my machines in the house are connected to.