Web Adaptor and NAT Setup

[KentuckyDGI]

Our new servers are setup in such a way that they have an internal IP address and an external IP address. This is done through a NAT (network address translation) setup by the firewall team. This seems to be presenting a problem as it relates to any external requests through the REST API. There may be a way to resolve this with the ArcGIS Web Adaptor but I'm not really sure.

Does anyone else have this type of setup?

[MattMcGuire]

Yes, we have a similar set up. An external IP address and DNS entry is mapped to an internal IP Address. We are using the web adaptor, and it doesn't seem to be a problem. The external DNS/NAT is pointing at the Web Adaptor, and the Web Adaptor is pointing at the GIS server.

[KentuckyDGI]

Our external IP address has a DNS name that is seen on the web, but the internal IP address is associated with the machine name which is not the same as the external DNS name. Our REST endpoint is visible on the web but all of the requests fail except the root level JSON link. When you examine the request you can see that is looking for <machine name:6080> and not the external DNS name.

Now have an open incident . . .