After the application has been made available internally, external access will be performed by redirecting external traffic in the modem to the computer where E3Server and IIS are being executed, creating a Virtual Server (NAT). You will need to redirect the ports used by Elipse E3 (6515) and by IIS to the server computer on the internal network. The modem must be configured on its settings panel, via IP address. The figure below shows the configuration added to the device.
Next, you will need to add exceptions to the internal firewall existing in the server micro, which will contain the specific ports where access must be cleared (in this case, 6515 and IIS) under Entry Rules. NOTE: if the firewall is disabled, you can disregard this information.
For connections with a dynamic IP, you must use a Dynamic DNS service, where a registered host address starts pointing constantly to the current IP. According to the image below, this configuration can be set directly in the modem, if it has this functionality.
Finally, inform in the external machine the DNS or IP address where the domain is being executed. Example: http://deliodamin.dyndns.org.
To develop this article, we used a D-Link DSL-2640B modem.
