Storm season is back, bringing with it the potential for significant weather events. If you have clients in areas prone to infrastructure disruption, visit the Disaster Recovery Resources guide for preparedness information. Datto recommends performing proactive disaster recovery testing to mitigate potential downtime. See our articles about the importance of disaster recovery testing and Preparing For A Cloud Virtualization Test: Policies, Procedures, And Partner Responsibilities to learn more. For live updates, follow @datto on Twitter.

Why Can't I Access an Internal Server via Its External IP Address?

Follow

Scope

This article explains the causes behind an internal server reporting as unreachable via its external IP address.

Overview

Typically this problem is seen on guest SSIDs where an alternate DNS is configured to provide guest clients with the external IP address of the internal server. This can result in guest clients being unable to communicate with the internal server via the external IP address.

Trying to access an internal server via its external IP address on the same network the internal server is hosted on will typically not work as expected, unless your router supports (and you've enabled) NAT Hairpinning. NAT Hairpinning may also be called NAT Reflection or NAT Loopback.

Not all routers offer this functionality, call it by the same name or have the same configuration options. You'll need to review your router documentation or talk to the router manufacturer's support staff for more details about whether it's supported, and how to configure it.


Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Calling all Partners! We want to hear your feedback! Please participate in this quick survey and help us build a better, more-relevant Knowledge Base!

Want to talk about it? Head on over to our Community Forum!