clevelus писал(а):
Для WEB сервера (например апач) никакой специфики нет. Разве только если Вы запускаете его не на 80 порту, то нужно правильно прописать порты.
В большинстве DI уже есть готовое правило - его нужно только включить и прописать адрес внутреннего сервера.
если речь идет об Virtual HTTP Server, то было сделано согласно help'а:
Advanced
Virtual Server
Some applications require multiple connections, such as Internet gaming, video conferencing, Internet telephony and others. These applications have difficulties working through NAT (Network Address Translation). If you need to run applications that require multiple connections, specify the port normally associated with an application in the "Trigger Port" field, select the protocol type as TCP (Transmission Control Protocol) or UDP (User Datagram Protocol), then enter the public ports associated with the trigger port to open them for inbound traffic. At the bottom of the screen, there are already defined well-known special applications. To use them, click on the edit icon and enable the service.
Name :The name referencing the virtual service.
Private IP :The server computer in the LAN network that will be providing the virtual services.
Protocol Type :The protocol used for the virtual service.
Private Port :The port number of the service used by the Private IP computer.You can input a single port or a range of ports (ex. 5001-5003).
Public Port :The port number on the WAN side that will be used to access the virtual service.You can input a single port or a range of ports (ex. 5001-5003).
Schedule :The schedule of time when the virtual service will be enabled.
Example: If you have a Web server that you wanted Internet users to access at all times, you would need to enable it. Web (HTTP) server is on LAN computer 192.168.0.25. HTTP uses port 80, TCP.
Name: Web Server
Private IP: 192.168.0.25
Protocol Type: TCP
Private Port: 80
Public Port: 80
Schedule: always
Однако, эффекта - нет.