Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an ASP.NET application that I can get to locally by going to I would like to host the application externally by going to (I already have my domain pointing to my router and this works fine - I have apache running on port 80 on another server). I modified the router settings to point any request coming through port 81 to I am still having trouble accessing the ASP.NET site (I get the error message that "This link appears to be broken"). Am I missing something? How can I redirect to my ASP.NET application? Thanks.

share|improve this question

My goodness. Needed to add Windows Firewall exception for port 81. How silly. Problem solved. Good ol' winders...

share|improve this answer

Sounds like you're close. Try testing each part:

  • ping the domain name to confirm that it resolves to your public IP
  • confirm your public IP with Make sure it hasn't recently changed.
  • confirm that your router is set to forwarding port 81 to
  • confirm that your inside computer is still at .102
  • make sure that your forwarding is from port 81 to 81 and not trying to change ports (i.e. to port 80)
  • sometimes your ISP or ISP's router will block port 81 (or most ports) and won't allow the request to get to your router. You may need to check with them to confirm that it's not blocked
  • make sure that your binding on your website is set correctly. It should be the binding that you already have though.
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.