dyndns not able to access website on home network

I have a dyndns account and have the credentials on my home router.  I also use port forwarding for remote desktop which works and port 80 to the same machine.  I have iis on that machine running a small webpage.

When I am on my home network I can go to my dyndns account and view the page.  If I try to do this from work, I get nothing.  I can remote desktop into that computer from the dyndns name at work, but it won't return a ping.

So the dyndns entry works since I can get there with remote desktop, it won't return a ping or serve up a webpage unless on my home network.  I would have thought that even though I was on my home network, the dyndns entry would look like an external connection so it would have been a good test.

I did setup the firewall settings to allow the remote desktop and allow http (which allows me to get there from inside).  I am not an expert, but I knew enough to get this far.  (To save time, please assume that I have already tried the obvious.)
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Steven CarnahanNetwork ManagerCommented:
Even though you say "assume that I have already tried the obvious" I have to ask as this what what caused my issue when I was trying to set this exact scenario up a few years ago.

Are you running a static IP on the home computer? As far as I could tell dyndns didn't come into play as long as I was inside my local network.

Dyndns is designed for the changing IP of the router but doesn't take into account the possibility that the IP of the workstation could also change.
jackjohnson44Author Commented:
Hi, sorry, EE tends to get a lot of terrible answers, I was hoping to weed a few out.

My home computer does have a static ip.  My router port forwards RDP 3389 and port 80 to the static ip (

I can get to the computer by entering the dyndns domain name into a remote desktop popup.  I can't ping, but that is probably because that isn't turned on (which I just read about).  So it appears that my port forwarding is working for 3389 but not for 80.
Steven CarnahanNetwork ManagerCommented:
Have you tried port 8080 instead of 80?  Some ISP's block port 80 and 25 incoming.  Here is DYN's site that explains in better detail than I could:  http://dyn.com/support/webhops-and-redirections/
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

jackjohnson44Author Commented:
I just added port forwarding of 8080 to this computer as well.  I also went into iis and added 8080 to the binding of the website.  This didn't work.  I think there is another step though.  I tried going to mydomain.dynnds.org on that computer and could get to the site, when I tried mydomain.dynnds.org:8080 from the same computer, it didn't work.
jackjohnson44Author Commented:
Can you please explain the following from the link you posted?

"You need to create a destination host, such as ‘site.domain.com’, and assign this to your webserver’s IP address."

"Once site.domain.com has been created, you will need to change www.domain.com into a WebHop host record."
jackjohnson44Author Commented:
I created a new host name redirect.dyndns.org and set it as a Service Type: WebHop, in the redirect url, I entered mydomain.dyndns.org:8080.  I went to redirect.dyndns.org and nothing happened.  Is this necessary if I just add :8080 to the end of my original url?
Steven CarnahanNetwork ManagerCommented:
Sorry, I got a bit busy with some work issues.  

There is a rather good step by step example at:  http://dyn.com/support/wizard/#altport

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jackjohnson44Author Commented:
Thanks, that doesn't really do anything aside from saving you from typing the port

for example you can map http://myredirect.dyndns.org to http://domain.dyndns.org:8080.  You can just as easily add the port to the url.  I am having another issue that is not related to this.  I did set this up correctly though.
jackjohnson44Author Commented:
Thanks for your help.  I used this page to determine that 8080 wasn't working.  I deleted my new firewall rule then readded it allowing 8080.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.