Link to home
Start Free TrialLog in
Avatar of philodendrin

asked on

Why Can't We Access our Server 2016 Essentials RWA/Anywhere Access site Internally?

Working through some issues on a Server 2016 Essentials server and noticed that the remote web access portal site (remote, is not accessible internally (on the LAN) but works fine externally. If I ping the site internally from the Server 2016 Essentials server, it replies back with the public IP address of the server. This seems correct and matches what we see on other Server 2016 Essentials servers with Anywhere Access/RWA working internally and externally. Likewise, if we compare DNS settings (Forward Lookup Zones) between working and non-working servers, settings appear to be the same.

Internally, if I enter the public IP in a browser, the page does not resolve. Externally, it does resolve, as does the DNS address -

Running the Anywhere Access repair wizard did not address the issue. It completes successfully, but does not allow us to access the site internally on the same LAN as the server. Doesn't matter if I try from the server itself or a client workstation.
Avatar of Jackie Man
Jackie Man
Flag of Hong Kong image

What is the public IP address of your computers in your internal network when you use a browser to access
Avatar of footech
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of philodendrin


Thanks. That fixed it. I guess what I don't understand is why that happened. We had this all setup and tested months ago and no Forward Lookup Zone was necessary. Then, out of the blue, it stopped working internally.

But, it makes sense that it's a split DNS issue. Kinda figured it was, but just can't put my finger on what changed to make it necessary to implement split DNS.