Sign up with GoogleHello y'all @ MyBB
I was hoping someone could assist me with the following problem I am experiencing with a customers DynDNS account and remote connections. The problem goes like this:
DynDNS Updater is installed on the server at the office, latest version and all that. It is also set to update change of IP addresses automatically etc etc and running 100% error free. No worries there. The server also supports remote desktops etc etc.
When I try and initiate a remote connection to the DynDNS Computer Name registered with DynDNS [free account] eg: piet.pompies.org via Remote Desktop (from home), the connection fails with an obligatory M$ notification stating: Remote Desktop can't connect to the remote computer for one of these reasons, and goes on to list the possible causes of why I could not connect. Fair enough!
Here is where I am really puzzled and some guidance would be appreciated please.
When I type in the physical IP address of the server I am trying to connect to, eg: 00.123.456.78, bang! I am in, no problems, errors, nada. The IP address I use is the address displayed in the DynDNS Updater Settings page. I know this IP address because I use LogMeIn to obtain that IP in the DynDNS Updater Settings page, phew... all with me?
Anyone have any ideas how to solve the wee challenge so my customer may use the friendly computer name instead of using LogMeIn to first get the DynDNS IP and then use only use Windows RDC to connect?
Lastly, I also thought the IP address I was using for RDC was the same one allocated by the ISP [as displayed on the status page of the ADSL router's GUI] and not DynDNS, but it isn't, weird?
EDIT: The DynDNS log file reports that DynDNS is Unable to determine WAN IP, can't update, could this be it?
Many thanks,
I was hoping someone could assist me with the following problem I am experiencing with a customers DynDNS account and remote connections. The problem goes like this:
DynDNS Updater is installed on the server at the office, latest version and all that. It is also set to update change of IP addresses automatically etc etc and running 100% error free. No worries there. The server also supports remote desktops etc etc.
When I try and initiate a remote connection to the DynDNS Computer Name registered with DynDNS [free account] eg: piet.pompies.org via Remote Desktop (from home), the connection fails with an obligatory M$ notification stating: Remote Desktop can't connect to the remote computer for one of these reasons, and goes on to list the possible causes of why I could not connect. Fair enough!
Here is where I am really puzzled and some guidance would be appreciated please.
When I type in the physical IP address of the server I am trying to connect to, eg: 00.123.456.78, bang! I am in, no problems, errors, nada. The IP address I use is the address displayed in the DynDNS Updater Settings page. I know this IP address because I use LogMeIn to obtain that IP in the DynDNS Updater Settings page, phew... all with me?
Anyone have any ideas how to solve the wee challenge so my customer may use the friendly computer name instead of using LogMeIn to first get the DynDNS IP and then use only use Windows RDC to connect?
Lastly, I also thought the IP address I was using for RDC was the same one allocated by the ISP [as displayed on the status page of the ADSL router's GUI] and not DynDNS, but it isn't, weird?
EDIT: The DynDNS log file reports that DynDNS is Unable to determine WAN IP, can't update, could this be it?
Many thanks,
Last edited:
