I have built an ArcGIS website that is hosted in our internal virtual machine. These is the list of what we have in the virtual machine:
1. ArcGIS Desktop 10.2.2, which includes: ArcCatalog, ArcMap and ArcSDE.
2. ArcGIS Server 10.2.2, with Web Adapter.
3. IIS 7.5.
4. SQL Server Express.
The website consumes 3 services (2 map services and 1 feature service) and is stored on an internal virtual machine. When the virtual machine was still set inside the internal network, all the things run smoothly. The services run OK, the website was perfect too. But after the IT team changed the IP to be able to be accessed from the external, the arcgis services were dead. Every time the network is changed to internal, the services are on and the website run OK. But every time the IT team changes the IP that accessible from external, the services are down. Even the embeded service example from the ESRI is dead.
Maybe I need to let you know more about the services I have. I have got 2 MXD files: comment.mxd and layer.mxd. Layer.mxd contains 8 feature layers and is published as a normal Map Service. Whereas the comment.mxd contains only 1 layer, a point feature that is stored in a SQL server express database and connected to the MXD file with ArcSDE. The geodatabase was created by ArcCatalog. The comment.mxd was then published as a Map Service and a Feature service.
Now, every time the network is set for external, the arcgis services are dead. When the machine is set back inside internal network, the services are always back alive again.
Does anyone have any ideas how to solve this problem? Is it something to do with the ports? Do I need to set something on the virtual machine first so the services can run for external? Any ideas are much appreciated.