I'm trying to set-up an ASG for a customer of mine to offer SSL connectivity to external clients however, being a cheapskate, he is using a domestic (non-fixed IP) ADSL solution.
The problem is that as the router holds his Public IP and that is constantly changing, How can I get the clients to connect to the ASG portal.
I've set up port forwarding on the router so that port 443 and port 4444 are forwarded by the router to the private IP on the ASG's external interface. I've also set-up a DynDNS account which points to the Public IP on the router and the router is successfully updating DynDNS servers with it's current assigned address.The results so far are:
1.) That a connection to mydomain.dyndns.org on http port 80 connects to the management interface on my router - So DynDNS works ok.
2.) A connection to https://mydomain.dyndns.org (on port443) fails every time.
3.) More importantly a connection to https://mydomain.dyndns.org:4444 fails so no external access to the ASG [:@]
4.) finally a connection to https://mydomain.dyndns.org/portal also fails which means that even if the users did want to connect, they couldn't get to the portal to get the SSL software to do so.
What is a boy to do?
Oh and one final issue, when I connected to the ASG from the internal network to download the SSL software. The software came pre-configured with the internal ASG hostname so couldn't be pointed at the ASG externally i.e it would point to internalhostmname.internaldomain.net and not point to mydomain.dyndns.org. Hours & hours have been spent on this. Please can someone help!
This thread was automatically locked due to age.
